plan-roadmap-step

To document design decisions for a roadmap phase, analyze the world-design-document and roadmap context to surface constraints, then generate a formal phase_n.n.md file capturing rationale and acceptance criteria for sign-off.

Turning a roadmap into an approved plan involves synthesizing dependencies and stakeholder questions from related guides, producing a detailed phase plan that ensures alignment and updates related documents automatically.

Creating a phase_n.n.md planning document requires analyzing the world-design-document alongside roadmap dependencies, capturing questions for clarity, and outputting a structured plan anchored by formal design decisions.

Yes, a world-design-document is needed to plan a roadmap step because the workflow synthesizes context from it and related guides to ensure the generated phase plan maintains strict alignment with overall project goals.

Yes, you can update the project-roadmap.md and world-design-document while planning a new phase, as the workflow ensures docs synchronization by automatically applying captured design decisions and constraints back to related documents.