brainstorm-stop-hook-deadlock-on-blocked-user-input
When the brainstorming skill hard-gate is active and the agent is blocked waiting for user input, the stop hook repeatedly fires and blocks the stop attempt — creating a repeated loop of stop-blocked messages consuming token budget. The hook correctly identifies the incomplete brainstorming state but has no mechanism to distinguish ‘blocked on user input’ from ‘agent abandoned the process’. This pattern repeated 15+ times in one session.
Related
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- brainstorming-hardgate-blocks-stop-hook-pure-planning-sessio
- brainstorming-hard-gate-blocks-stop-hook-even-without-file-c
- brainstorming-stop-hook-deadlock-when-user-unresponsive
- stop-hook-brainstorm-hardgate-creates-blocking-feedback-loop
- destructive-ops-blocker-false-positive-on-backup-suffixes
- destructive-hook-regex-word-boundary-backup-false-positive
- superpowers-plugin-gap-brainstorming-gate-not-enforced
- stop-hook-catches-code-gen-missing-verification
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- stop-hook-brainstorming-skill-deadlock-loop
- stop-hook-brainstorm-workflow-infinite-block-pattern
- stop-hook-false-positive-during-active-waiting-state