gsd-complete-milestone

Archive completed milestones and create versioned git tags for releases.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-complete-milestone-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-complete-milestone
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-complete-milestone-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestones often end up scattered and under-documented, making it hard to track version history and plan future work. This skill automates archiving completed milestones, updates planning artifacts, and primes the repository for the next release.

Core Features & Use Cases

  • Archive milestone ROADMAP.md and REQUIREMENTS.md to a versioned milestone folder.
  • Update PROJECT.md with current state and next milestone goals.
  • Create a git tag and commit the milestone as part of release workflows.
  • Ensure artifacts are preserved and the next milestone starts with fresh requirements.

Quick Start

Run the complete milestone workflow with the version parameter to archive the milestone and prepare the next version

Frequently Asked Questions about gsd-complete-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed project milestones and update ROADMAP.md?

To archive completed project milestones and update ROADMAP.md, this skill automates moving ROADMAP.md and REQUIREMENTS.md to a versioned milestone folder, updates PROJECT.md with the current state, and commits the release with a git tag.

What is the best way to finalize a version and prepare git tags for the next milestone?

Finalizing a version and preparing git tags for the next milestone involves archiving artifacts to .planning/milestones, validating summaries, and committing and tagging the release to prime the repository for fresh requirements.

Can I automate project management archiving to update PROJECT.md and REQUIREMENTS.md simultaneously?

Yes, you can automate project management archiving to update PROJECT.md and REQUIREMENTS.md simultaneously by running the complete milestone workflow with a version parameter to finalize the current state and generate fresh requirements for the next cycle.

Does the milestone archiving workflow require any external dependencies to create git tags?

No, the milestone archiving workflow requires no external dependencies to create git tags and commits, operating entirely within your repository to update planning artifacts and preserve version history locally.

Why should I use an automated milestone workflow instead of manually updating project planning files?

Using an automated milestone workflow instead of manually updating project planning files prevents scattered documentation, enforces summary validation, and ensures artifacts are consistently preserved in versioned milestone folders for reliable historical tracking.