stop-hook-blocks-pure-planning-sessions-in-brainstorm-loop
The stop hook’s ‘structural incompleteness’ check conflicts with the brainstorming skill’s section-by-section approval requirement: when the user goes idle mid-brainstorm, the stop hook fires repeatedly (40+ times) blocking termination even though no files were modified. The condition ‘pure Q&A/planning with no file modifications → APPROVE stop’ should take precedence over brainstorming workflow state, since the user is absent and the session cannot progress. Fix: stop hook should APPROVE if no file changes occurred regardless of brainstorming workflow state.
Related
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-loop-on-mid-workflow-user-silence
- brainstorming-skill-hardgate-overrides-stop-hook-pure-planni
- brainstorming-skill-hard-gate-blocks-stop-hook-approval
- stop-hook-infinite-loop-during-brainstorming-await
- stop-hook-blocks-on-brainstorming-mid-flow
- stop-hook-blocks-mid-brainstorming-session-by-design
- stop-hook-blocks-pure-planning-sessions-pathological-loop
- stop-hook-false-positive-during-active-waiting-state
- stop-hook-false-positive-during-waiting-state