plan-phase

To create a technical implementation plan, you define the target phase to generate comprehensive step implementations, dependencies, test mappings, and acceptance criteria. This converts high-level project goals into actionable, testable engineering tasks.

Phase planning documents align with overall project scope by reconciling decisions and dependencies from main planning artifacts like docs/project-plan.md, docs/decisions/, and docs/phases to maintain cross-phase consistency.

The best way to generate execution plans with step definitions and acceptance criteria is to apply phase detailing to the project plan, producing a reusable phase document that can be turned into concrete engineering tasks.

Yes, you can use phase planning to detail dependencies and test mappings for an execution plan. The process generates a comprehensive set of step implementations that align with the project's technical decisions and phase scope.

You need existing project planning artifacts to ensure cross-phase consistency. The phase generation process reconciles inputs from docs/project-plan.md, docs/decisions/, and docs/phases to produce aligned and testable technical steps.

Your project phase execution plan lacks testable step definitions because it has not reconciled the phase scope with the main project planning artifacts. Generating a phase document from these decisions ensures step implementations include proper acceptance criteria.