planning-workflowlisted

# Planning Workflow A structured 7-step process for creating validated plans before implementation. Plans are critiqued adversarially by the plan-critic agent. Two different enforcers, two different things enforced — do not conflate them: | What is enforced | Enforcer | |------------------|----------| | A plan EXISTS with the three required sections, before a complex write | `plan_gate.py` hook (PreToolUse). Transport-independent since Issue #1503 — MultiEdit, NotebookEdit, and MCP editors are gated identically to Write/Edit. | | The plan-critic CRITIQUE actually ran (plan-mode path) | `unified_pre_tool.py` plan-exit marker gate (Issue #926) — the marker must reach `stage: critique_done`. | | The plan-critic VERDICT is PROCEED (`/implement` path) | `/implement` STEP 5.5b verdict gate. | `plan_gate.py` does NOT enforce the critique. It checks only that a validated planning document is present. ## When to Use - Before any complex implementation (>3 files or >100 lines) - When the approach is uncertain or multiple solutions exist - When the feature touches multiple components - When scope needs to be explicitly bounded ## The 7-Step Workflow | Step | Name | Description | Tools | |------|------|-------------|-------| | Step 1 | **Problem Statement** | Define WHY this change is needed and WHAT is in scope | Read, Grep | | Step 2 | **Scope Check** | Estimate files affected; halt if >50% drift from initial estimate | Glob, Grep | | Step 3 | **Existing Solutions** | Search co