planning

To turn a feature design document into an implementation plan, you describe the feature to generate a structured plan.md and phase-*.md files. These documents organize complex work into phased, testable milestones with clear dependencies and acceptance criteria.

Planning a codebase migration involves generating phase-*.md documents that specify clear phase boundaries and dependencies. This creates a repeatable planning scaffold that captures codebase context, design decisions, and test strategy to guide iterative execution.

An implementation plan for complex tasks should include phased milestones, acceptance criteria, codebase context, design decisions, and test strategy. Organizing these elements into plan.md and phase-*.md documents ensures teams can execute iteratively with clear dependencies.

Yes, you can use design docs to generate a phased test strategy for bug fixes. By describing the bug fix task, the system produces plan.md and phase-*.md documents that specify testable milestones, acceptance criteria, and test strategy to guide development.

The best way to organize platform changes into testable milestones is to generate a plan folder with phase documentation. This approach captures codebase context and design decisions, producing phased milestones with specified acceptance criteria for iterative team execution.

You need to generate a plan folder with phase documentation when planning complex work that requires clear phase boundaries and dependencies. This applies to feature design, bug fixes, migrations, and platform changes where capturing test strategy and design decisions is essential.