stop-hook-brainstorming-skill-deadlock-loop
The Stop hook blocks session termination when brainstorming is mid-section-validation, and the brainstorming skill blocks progression until the user responds — together they create an infinite wait loop if the user goes idle. The stop hook correctly identifies structural incompleteness, but the session becomes unrecoverable without user input. Stop hook logic for pure planning sessions should APPROVE after a reasonable idle threshold rather than indefinitely blocking.
Related
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- brainstorm-stop-hook-deadlock-on-blocked-user-input
- brainstorming-skill-hardgate-overrides-stop-hook-pure-planni
- stop-hook-blocks-infinitely-when-brainstorming-awaits-user-i
- stop-hook-brainstorm-workflow-infinite-block-pattern
- stop-hook-loop-on-mid-workflow-user-silence
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-blocks-pure-planning-sessions-infinite-loop
- stop-hook-infinite-loop-on-pure-planning-sessions
- stop-hook-brainstorm-workflow-infinite-block-when-user-away
- stop-hook-blocks-mid-brainstorm-workflow-correctly
- stop-hook-blocks-mid-stream-brainstorming-sessions
- stop-hook-blocks-on-brainstorming-mid-flow
- stop-hook-brainstorming-infinite-loop-pattern
- marketing-speak-in-skill-files-reduces-intelligence-density
- documentation-cascade-must-not-defer-past-checkpoint