create-plan

To generate a phased implementation plan, you define the feature scope and the system creates a directory layout, a master plan.md document, and individual phase files, breaking the work into atomic, manageable steps.

Atomic phase decomposition is the process of breaking down a large software feature into isolated, manageable phases. Each phase file contains clear requirements and acceptance criteria to ensure focused, incremental implementation.

Yes, the planning process enforces project-specific patterns by referencing and utilizing provided templates like PLAN-TEMPLATE.md and PHASE-TEMPLATE.md to ensure new features match existing codebase architecture.

Yes, the generated implementation plans integrate Test Driven Development (TDD) directly into the phased structure, ensuring testing requirements and acceptance criteria are documented upfront for each development phase.

The best way to structure project documentation is generating a master plan document alongside individual phase files. This ensures all implementation steps, database schemas, and API endpoints are documented upfront to prevent rework.

You need a master plan document when starting a new feature like User Profile Management. It maps out the overall architecture, database schema, and API endpoints, preventing rework by documenting all necessary steps upfront.