stop-hook-brainstorm-workflow-infinite-block-pattern
When a brainstorming session is mid-flow awaiting user section approval and the user goes idle, the Stop hook and the brainstorming skill’s section-validation requirement create an infinite loop: the hook blocks every stop attempt with ‘structurally incomplete’, forcing the agent to respond with holding messages indefinitely. This is a known deadlock pattern when the stop hook evaluates ‘structural completeness’ independently of whether the user is actively present. Consider adding a timeout or idle-detection condition to the stop hook evaluation for pure planning sessions.
Related
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- stop-hook-brainstorming-skill-deadlock-loop
- brainstorm-stop-hook-deadlock-on-blocked-user-input
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- docker
- 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-brainstorm-workflow-infinite-block-when-user-away
- stop-hook-blocks-mid-stream-brainstorming-sessions
- stop-hook-brainstorming-infinite-loop-pattern
- doc-sync-deferral-to-post-checkpoint-is-invalid
- stop-hook-needs-agent-stop-intent-guard