Implementation Planning

Overview

Implementation planning combines a Planner Agent with the /plan command to create comprehensive, actionable plans before writing any code. The core discipline: analyze requirements, break down complexity, identify risks, and get explicit user confirmation before touching code.

/plan Command

What It Does

1. Restates Requirements -- Clarifies what needs to be built
2. Identifies Risks -- Surfaces potential issues and blockers
3. Creates Step Plan -- Breaks implementation into phases
4. Waits for Confirmation -- Will NOT write code until explicit approval

When to Use

• Starting a new feature
• Making significant architectural changes
• Complex refactoring affecting multiple files
• Requirements that are unclear or ambiguous

Critical Rule

The planner agent will never write code until you explicitly confirm. Respond with:

• "yes" / "proceed" to approve
• "modify: [changes]" to adjust the plan
• "different approach: [alternative]" to change direction

Integration

After planning, combine with:

• /tdd for test-driven implementation
• /build-fix for build error resolution
• /code-review for post-implementation review