gsd-complete-milestone

Archive milestone artifacts, update PROJECT.md, and create a git tag.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-complete-milestone-novatech2210-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-complete-milestone
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-complete-milestone-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestones and prepare artifacts for the next version to ensure traceability and a clean handoff for the next cycle.

Core Features & Use Cases

  • Archive completed milestone artifacts (ROADMAP.md, REQUIREMENTS.md) and create a milestone-specific archive in .planning/milestones.
  • Update PROJECT.md with current state and next milestone goals; collapse previous progress for reference.
  • Tag the release (git tag) and commit changes to maintain an auditable history for stakeholders.

Quick Start

Initiate the complete-milestone workflow for version {{version}} to archive the milestone, update ROADMAP.md and REQUIREMENTS.md, and prepare the next milestone.

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 prepare for the next version?▼

Archiving completed project milestones involves moving ROADMAP and REQUIREMENTS artifacts into a milestone-specific directory, updating PROJECT.md with the next goals, and creating a git tag to maintain an auditable history.

What is the best way to maintain an auditable history for project milestones?▼

Maintaining an auditable history for project milestones is achieved by enforcing audit readiness gates, creating a git tag for the release, and committing all changes to leave a traceable record for stakeholders.

How do I update PROJECT.md after a milestone is completed?▼

Updating PROJECT.md after a milestone involves recording the current state and next milestone goals, while collapsing previous progress entries for reference to ensure a clean handoff for the next cycle.

Does archiving milestones work with git tagging and REQUIREMENTS files?▼

Yes, archiving milestones works with git tagging and REQUIREMENTS files by tagging the release in git, archiving the REQUIREMENTS.md artifacts, and generating one-line ROADMAP entries for future reference.

What are the limitations of manually archiving ROADMAP and REQUIREMENTS artifacts?▼

Manually archiving ROADMAP and REQUIREMENTS artifacts often lacks enforced audit readiness gates and consistent one-line ROADMAP entries, risking broken traceability and an incomplete auditable history for stakeholders.