elaborate-phase

To elaborate a migration phase, you convert a high-level master plan into a complete, self-contained implementation plan. This process decomposes the phase into concrete tasks, prerequisites, dependencies, and validation steps, outputting a detailed PhaseN.md document.

Phase elaboration is the process of translating a high-level migration phase into a detailed, executable set of steps and verification criteria. It ensures an actionable plan with background context and tasks, ready for dry-walkthrough validation.

You validate a migration plan by conducting a dry-walkthrough. This iterative elaboration step checks the self-contained implementation plan, ensuring all prerequisites, dependencies, and verification steps are complete and ready for execution.

A migration phase document should include background context, prerequisites, dependencies, concrete tasks, and verification criteria. It must be a complete, self-contained implementation plan generated from assessing the current codebase state.

Yes, you need to assess the current codebase state before elaborating a migration phase. This assessment satisfies requirements to generate the PhaseN.md plan and ensures the detailed tasks and verification steps are executable.

The best way to break down a master migration plan is to elaborate each phase into a self-contained implementation plan. This converts high-level goals into concrete tasks, dependencies, and acceptance criteria for immediate developer execution.