gsd-complete-milestone

Automating project milestone archiving updates project documentation like ROADMAP.md and REQUIREMENTS.md while creating a historical record. You can trigger this by running the skill with a version parameter to commit changes automatically.

The best way to manage documentation for completed milestones is using automated archiving. This approach updates your project's ROADMAP.md and REQUIREMENTS.md files with archived milestone information, ensuring accurate historical reference without manual effort.

Yes, automated milestone completion is ideal for large-scale projects with multiple milestones. It streamlines workflow execution by archiving completed tasks, updating project documentation, and committing version changes in one operation.

You trigger milestone archiving by running the skill with the specific version parameter, such as entering 'run gsd-complete-milestone 1.0'. This executes the automated workflow to archive tasks and update project files.

Yes, automating project milestone completion requires access to project files and workflow execution capabilities. This access allows the automation to update project documentation, archive changes, and create historical records.

Manual milestone management creates gaps because it relies on individual effort to update ROADMAP.md and REQUIREMENTS.md files. Automated archiving prevents gaps by systematically committing version changes and creating historical records upon milestone completion.