planlisted

# plan Development planning and architecture design. ## Routes | Subcommand | Action | | ---------- | ------ | | `feature` | Plan a new feature | | `refactor` | Plan refactoring | | `architecture` | Architecture review | ## Usage ```bash /plan # Ask what to plan /plan feature # Plan a feature /plan refactor # Plan refactoring /plan architecture # Architecture review ``` ## Behavior All planning tasks use `EnterPlanMode` to create a structured plan for user approval before any implementation. **After every plan is approved**, follow the [Post-Plan Handoff](#post-plan-handoff) process. ### feature Use `AskUserQuestion` to understand: - What feature? What problem does it solve? - What's the scope? Which files/modules? - Any constraints or preferences? Then use `EnterPlanMode` to design the implementation plan. After approval, follow Post-Plan Handoff. ### refactor Use `AskUserQuestion` to understand: - What code needs refactoring? - What's the goal? (simplify, split, extract) - Any constraints? Then use `EnterPlanMode` to plan the refactoring. After approval, follow Post-Plan Handoff. ### architecture Use `AskUserQuestion` to understand: - What system or subsystem to review? - Any specific concerns? Then analyze the codebase structure and provide architectural recommendations. If the review produces actionable changes, follow Post-Plan Handoff. ## Post-Plan Handoff **This section applies to ALL routes after a plan i