planning-workflowlisted

# Planning Workflow A structured 7-step process for creating validated plans before implementation. Plans are critiqued adversarially by the plan-critic agent and enforced by the plan_gate hook. ## 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 codebase + web for prior art before building new | Grep, Glob, WebSearch | | Step 4 | **Minimal Path** | Design the smallest change that achieves the goal | Read | | Step 5 | **Adversarial Critique** | plan-critic agent reviews the plan (min 2 rounds) | plan-critic agent | | Step 6 | **Issue Decomposition** | Break into trackable issues if needed (via /create-issue) | Bash | | Step 7 | **Plan Output** | Write validated plan to .claude/plans/<slug>.md | Write | ### Step 1: Problem Statement Define: - **WHY** this change is needed (not what, not how) - **SCOPE** boundary -- what is IN and what is OUT - **Success criteria** -- how do we know it's done? ### Step 2: Scope Check Estimate the number of files t