stop-hook-brainstorm-hardgate-creates-blocking-feedback-loop
When a brainstorming session is in progress and the agent is awaiting user input, the stop hook repeatedly fires and blocks session end — generating dozens of block messages while the agent can only reiterate its waiting state. The brainstorming skill’s hard-gate (forbids stopping before design + spec) and the stop hook’s block logic create a loop with no resolution path until the user responds. This is expected behavior by design but creates visible UX friction in long awaited-input scenarios.
Related
- stop-hook-blocks-infinitely-when-brainstorming-awaits-user-i
- brainstorming-hardgate-blocks-stop-hook-pure-planning-sessio
- brainstorm-hard-gate-stop-hook-deadlock-pattern
- brainstorming-hard-gate-overrides-stop-hook-pure-planning-ex
- brainstorming-stop-hook-deadlock-when-user-unresponsive
- stop-hook-pure-planning-exemption-overridden-by-brainstormin
- brainstorm-stop-hook-deadlock-on-blocked-user-input