plan-phases

# /phase-plan Take an existing flat or unstructured plan and restructure it into phased execution with `/verify` gates after each phase and critical steps. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. > **Plan Restructuring Protocol — transforms any plan into a gated, phased structure for structural legibility and explicit checkpointing.** Restructure, never delete. All original content is preserved. ## What is `/verify`? `/verify` is a verification gate — a point where execution stops and the current state is validated before proceeding. When you encounter a `/verify` gate in a restructured plan: 1. Review what the gate specifies 2. Verify each condition is met 3. Only continue to the next phase/step once the gate passes If `/verify` is not a recognized command in your session, replace it with an explicit user confirmation prompt: pause, state what you're verifying, and wait for the user to confirm before continuing. ## Phase 1 — Locate & Load Existing Plan 1. **Find the plan** — check `implementation_plan.md`, `PLAN.md`, `task.md`, recent conversation context, or user-provided file. Load the full content. If multiple candidates exist, use the most recently modified file and note the choice. 2. **Assess structure** — flat (single list)? Partially phased? Missing verification step...