implementation-plan

Implementation Plan

Create a comprehensive, phased implementation plan from requirements documentation.

Trigger

Invoke when the user provides:

• BRD (Business Requirements Document)
• Architecture diagrams or docs
• User flows or journey maps
• User stories or acceptance criteria
• Research or discovery documents
• Any combination of the above

Input

1. Ask the user for input documents if not provided:

   What documents should I use to create the implementation plan?
   Please provide file paths (e.g., docs/brd.md, docs/architecture.md)
   

2. Read all provided documents to understand:

   • Feature scope and boundaries
   • Technical constraints and dependencies
   • User-facing requirements
   • Non-functional requirements (performance, security, accessibility)

Planning Process

1. Analyze the documents and identify:

   • Core functionality clusters (group related features)
   • Technical layers involved (API, database, UI, integrations)
   • Dependency order (what must be built first)
   • Risk areas (complex logic, external dependencies, unknowns)

2. Structure the plan into Phases:

   • Each phase delivers testable, demonstrable functionality
   • Phases build on each other (no circular dependencies)
   • Early phases reduce risk (prove out unknowns first)
   • Phase size: 1-3 days of work typical

3. Break each phase into Steps:

   • Each step is independently actionable
   • Steps take 15-60 minutes each
   • Include specific file paths to create/modify
   • Include commands to run (migrations, tests, builds)

4. Add Test Coverage Requirements at phase boundaries:

   • Insert after phases that introduce significant new code
   • Insert at natural integration points (API complete, UI connected)
   • Specify qualitatively:
     • "Unit tests for all new service methods"
     • "Integration test for the complete user flow"
     • "E2E test covering the happy path"
   • Do NOT use arbitrary percentage targets

5. For UX/Frontend phases, add this instruction:

   AUTO-INVOKE: /frontend-design
   Before implementing UI for this phase, invoke the frontend-design
   skill with the component requirements below.
   

   Include component requirements: purpose, user interactions, data displayed.