planlisted

# Plan — Plan Phase Read an approved spec, verify assumptions with a scout, write an intent-driven task list, and hand off to `/flow:execute`. Plans describe WHAT to achieve — never HOW to implement it. <HARD-GATE> Do NOT include implementation code (function bodies, test files, class definitions, step-by-step instructions) in tasks. This is the one inviolable rule of intent-driven planning. Plans that contain prescriptive code age immediately and suppress agent expertise. </HARD-GATE> --- ## Process Flow ``` Start | v [1. Read the spec] Load the approved spec file from brainstorm. Note: goal, components, constraints, acceptance criteria. | v [2. Scout phase] If fakoli-crew is installed: dispatch scout to verify assumptions. Wait for scout status file. Read findings before writing any task. | v [3. Map files and responsibilities] Identify which files will be created or modified. Assign clear ownership — one task per file group. | v [4. Write intent-driven tasks] For each task: intent, acceptance criteria, scope, agent, verify, depends on. No code. No step-by-step instructions. Acceptance criteria only. | v [5. Self-review] Check: spec coverage, criteria clarity, dependency graph, agent assignments. Fix issues inline. | v [6. Save plan] Save to docs/plans/<YYYY-MM-DD>-<feature>.md (or the path CLAUDE.md specifies). | v [7. Hand off to /flow:execute] ``` --- ## Step-by-Step Rules ### Step 1: Read the Spec Load the spe