gsd-complete-milestone

Archive milestone artifacts and update planning docs with a release tag.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-complete-milestone-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-complete-milestone
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-complete-milestone-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed milestones and aligning planning artifacts is error-prone and manual. This skill standardizes the process so shipped versions are properly archived and next milestones are prepared automatically.

Core Features & Use Cases

  • Archive completed milestone artifacts to milestones/, including versioned ROADMAP.md and REQUIREMENTS.md snapshots.
  • Update PROJECT.md with the current state and outline goals for the next milestone.
  • Create a release tag to mark the milestone in version control and enable traceability.
  • Use Case: When a milestone is released, run this skill to generate a historical record and prep for the next planning cycle.

Quick Start

Provide the version number and run the complete-milestone workflow to archive the milestone and prepare the next one.

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 planning documents?

To archive completed milestones, you can automate the process by generating versioned ROADMAP.md and REQUIREMENTS.md snapshots, updating PROJECT.md with current state, and creating a git tag for release traceability.

What is milestone archiving in project management and when is it needed?

Milestone archiving is the process of saving completed project artifacts into a milestones directory and tagging the release in version control. It is needed during release governance to ensure traceability before starting the next planning cycle.

How do I tag a release version and prepare a roadmap for the next cycle?

You can tag a release version and prep the next cycle by running a workflow that archives current milestone artifacts, applies a git tag for version control, and automatically updates PROJECT.md with new goals.

Does this milestone archival workflow require any external dependencies?

No external dependencies are required to run this milestone archival workflow. It operates independently to update planning docs, create milestone archives, and apply version tagging.

What is the best way to maintain traceability across released project versions?

The best way to maintain version traceability is standardizing release governance by archiving milestone artifacts to a dedicated directory and creating a git tag to mark the milestone in version control.