Planning
A structured workflow for breaking features or projects into phased, actionable plans.
When to Use
- Large features that span multiple pages or components
- Redesigns or major refactors
- New sections with unclear scope
- When the user asks "how should we approach this?"
When NOT to Use
- Single-component tasks
- Bug fixes
- Simple content updates
Core Principles
- Break work into shippable increments
- Each phase should be independently deployable
- Identify dependencies between phases
- Estimate relative complexity (S/M/L)
The 6 Phases
Phase 1: Discovery
Goal: Understand the full scope.
- Read the user's request and any reference materials
- Identify all deliverables
- List assumptions and open questions
Phase 2: Exploration
Goal: Understand what exists.
- Survey the current codebase structure
- Identify reusable components and patterns
- Note technical constraints (stack, dependencies)
- Check for similar implementations to reference
Phase 3: Questions
Goal: Resolve ambiguity.
- List open questions (max 5)
- Propose defaults for minor decisions
- Confirm priorities and must-haves vs. nice-to-haves
Phase 4: Plan Design
Goal: Structure the work into phases.
- Group deliverables into logical phases
- Order phases by dependency and priority
- Identify shared components to build first
- Estimate complexity per phase (S/M/L)
Phase 5: Plan Output
Goal: Produce the actionable plan.
Format:
# Implementation Plan: [Feature Name]
## Overview
[1-2 sentence summary]
## Phases
### Phase 1: [Name] (Size: S/M/L)
**Goal**: [What this achieves]
**Files**:
- [ ] `path/to/file.tsx` — [what to do]
**Dependencies**: None
### Phase 2: [Name] (Size: S/M/L)
**Goal**: [What this achieves]
**Files**:
- [ ] `path/to/file.tsx` — [what to do]
**Dependencies**: Phase 1
## Shared Components
- [Component]: [used in phases X, Y]
## Risks
- [risk]: [mitigation]
Phase 6: Summary
Goal: Confirm the plan with the user.
- Present the plan
- Ask for approval or adjustments
- Identify which phase to start with
Related Skills
| Skill | When to Chain |
|---|---|
| feature-dev | After planning, to implement each phase |
| web-test | After each phase, to verify |