plan-implementation

To create a phased implementation plan, provide your research document to generate stage-by-stage instructions, sequencing, and design decisions. This grounds the formal planning output directly in your prior research, ensuring alignment with project goals before coding begins.

Sequencing design options for a codebase change is handled by generating a template-driven plan that structures formal planning stages. It guides risk assessment and design decisions to align with project goals and captures acceptance criteria through conversation-driven refinement.

A research document is required to generate a structured project management plan. The phased implementation process grounds its stage-by-stage instructions, design decisions, and risk assessment directly in the findings of that document to ensure accurate formal planning.

Acceptance criteria and success metrics can be refined through conversation-driven refinement during the implementation planning process. This collaborative approach captures project goals and integrates them directly into the template-driven phased plan output.

Phase-based planning is needed for projects that require design options, sequencing, and formal planning before coding. You should use it when a codebase change is complex enough to require grounding in a research document and structured risk assessment.