brainstorm-hard-gate-blocks-stop-hook-until-writing-plans-invoked
The brainstorming skill’s hard-gate will block every stop attempt (repeatedly triggering the Stop hook) until the complete sequence is fulfilled: design presented → user approval → spec written → spec review loop completed → user reviews spec → writing-plans skill invoked. This is expected contractual behavior, not a malfunction. Sessions with active brainstorming will generate many stop hook blocks if the user steps away mid-session without completing the sequence. The only way to satisfy the gate is to reach the writing-plans terminal state.
Related
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- brainstorming-skill-hard-gate-blocks-stop-hook-approval
- 2026-04-04-oracle-001-self-architecture-analysis
- brainstorming-hard-gate-overrides-stop-hook-pure-planning-ex
- brainstorming-skill-stop-hook-blocks-incomplete-workflows
- brainstorming-skill-hardgate-overrides-stop-hook-pure-planni
- spec-reviewer-blocks-on-os-system-in-test-code
- destructive-ops-blocker-false-positive-on-backup-suffixes
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- project-memory-file-update-cannot-be-deferred-to-post-checkp
- ucg-explicit-invocation-required-stop-hook-blocks-otherwise