Skip to content

Phase 2: Plan

Design and architecture planning using the conceptual-orchestrator. Creates specs, identifies risks, and produces implementation plans.

Command: /2-plan "Your feature or task description"

When to use

After bootstrapping (Phase 1), or whenever you are about to start implementing a new feature. This phase converts a feature idea into a concrete, researched plan.

What happens

  1. SpecKit check -- Loads .specify/memory/constitution.md and the active specs/[N]-feature/spec.md (via .design-state.yaml) if present. All planning respects constitution constraints.
  2. Institutional knowledge -- Loads docs/solutions/patterns/critical-patterns.md and past solutions to avoid repeating mistakes.
  3. Conceptual orchestrator -- Dispatches four sub-agents in parallel:
  4. best-practices-researcher -- Industry patterns and standards
  5. framework-docs-researcher -- Library documentation
  6. architecture-strategist -- System design decisions
  7. spec-flow-analyzer -- User flow mapping and edge cases
  8. Plan generation -- Produces a prioritized implementation plan, architecture decisions with rationale, risk assessment, and user flow analysis.

Output

  • Step-by-step implementation plan
  • Architecture Decision Records (ADRs)
  • Risk assessment with mitigations
  • User flow maps with edge cases identified

Next step

Phase 3: Build