brainstorming-skill-stop-hook-blocks-incomplete-workflows
The stop hook actively blocks session termination if the brainstorming skill was invoked but the full pipeline (design presentation → user approval → spec write → spec review loop → writing-plans invocation) was not completed. Even a user’s prior approval statement (‘yes, complete all three phases’) does not satisfy the hook — it checks for workflow completion steps, not intent. Design sessions must fully execute the spec-review loop before the agent can stop.
Related
- stop-hook-blocks-until-brainstorming-workflow-terminal-state
- brainstorming-skill-hard-gate-blocks-stop-without-user-appro
- 2026-04-04-oracle-001-self-architecture-analysis
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- self-evolving-is-model-discipline-not-hook-enforced
- brainstorming-hardgate-causes-repeated-stop-hook-blocks
- brainstorming-skill-stop-hook-blocking-loop-on-user-approval
- brainstorming-hardgate-upfront-approval-counts
- brainstorming-hard-gate-blocks-stop-hook-exemption
- stop-hook-blocks-infinitely-when-brainstorming-awaits-user-i
- brainstorming-hardgate-conflicts-with-stop-hook-exemption
- stop-hook-brainstorming-hardgate-deadlock-pattern
- brainstorm-hard-gate-blocks-stop-hook-until-writing-plans-in