gsd-new-milestone

Automating project milestone planning involves scaffolding planning documents like PROJECT.md, ROADMAP.md, and REQUIREMENTS.md to establish a new workflow cycle. This process updates your existing project chronology and automatically triggers the requirements phase to begin execution.

Creating a new milestone roadmap requires updating a dedicated .planning directory with structured planning files. This approach preserves milestone history by integrating new cycles into the existing PROJECT.md chronology before routing to execution.

Milestone scaffolding routes to the requirements phase by creating and updating .planning/STATE.md to track workflow progress. Once planning documents are initialized, the system automatically triggers the gsd-plan-phase to start execution.

Yes, you can preserve existing milestone history when starting a new project cycle by integrating new milestones into the existing PROJECT.md chronology. The workflow updates planning documents without overwriting previous milestone records.

Kicking off a milestone cycle requires creating or updating PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md within a dedicated .planning directory. These files provide the structured scaffolding necessary to track project progress and route execution.

Yes, a dedicated .planning directory is required to automate milestone workflows because it stores the PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md files. This structure enables automatic scaffolding and routing to the execution phase.