spec-plan

# /spec-plan - Planning Phase **Phase 1 of the /spec workflow.** Explores codebase, designs implementation plan, verifies it, gets user approval. **Input:** Task description (new) or plan path (continue unapproved) **Output:** Approved plan at `docs/plans/YYYY-MM-DD-<slug>.md` **Next:** On approval → `Skill(skill='spec-implement', args='<plan-path>')` --- ## ⛔ Critical Constraints - **NO sub-agents during planning** except Step 1.7 (spec-review, when enabled in settings) - **Run spec-review when enabled** — it runs for every feature spec when `$PILOT_SPEC_REVIEW_ENABLED` is not `"false"`. Context level is NOT a valid reason to skip. To disable, use Console Settings → Reviewers → Spec Review toggle. - **NEVER write code during planning** — planning and implementation are separate phases - **NEVER assume — verify by reading files** - **ONLY stopping point is plan approval** — everything else is automatic. Never ask "Should I fix these?" - **Re-read plan after user edits** — before asking for approval again - **Plan file is source of truth** — survives across auto-compaction cycles - **Quality over speed** — never rush due to context pressure --- ## Step 0: Read Toggle Configuration **⛔ Run FIRST, before any other step.** Read all toggle env vars in a single Bash call: ```bash echo "QUESTIONS=$PILOT_PLAN_QUESTIONS_ENABLED REVIEWER=$PILOT_SPEC_REVIEW_ENABLED CODEX_SPEC=$PILOT_CODEX_SPEC_REVIEW_ENABLED APPROVAL=$PILOT_PLAN_APPROVAL_ENABLED" ``` Reference these values thr...