gsd-complete-milestone

Archive completed milestones and prepare projects for the next version.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-complete-milestone-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-complete-milestone
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-complete-milestone-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you formally close out a finished milestone so the project history stays accurate, release notes remain traceable, and the next version starts from a clean planning state.

Core Features & Use Cases

  • Milestone verification: Checks that all planned phases are complete and that audit status is ready before archival.
  • Historical archiving: Moves roadmap and requirements details into milestone archives so shipped work is preserved without bloating active planning files.
  • Project rollover: Updates project state, collapses the completed roadmap into a summary, and prepares fresh requirements for the next milestone.
  • Release finalization: Coordinates commit and git tag creation so the completed version is formally recorded.
  • Use case: After shipping a version, use this Skill to validate completion, archive the milestone, and set up the repository for the next development cycle.

Quick Start

Use the skill with the target milestone version to archive the completed release, verify readiness, update the planning documents, and create the corresponding git tag.

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 a completed milestone and prepare the next release cycle?

To archive a completed milestone, you verify audit status, move roadmap and requirements files into archives, update project state, and create a git commit and tag to finalize the release.

What is the best way to preserve roadmap and requirements history before rolling over a project version?

Preserving roadmap and requirements history involves moving active planning files into milestone archives to keep shipped work traceable without bloating the next version's planning state.

Can I automatically create a git tag when finalizing a release archive?

Yes, release finalization includes coordinating git commit and tag creation to formally record the completed version during the milestone archival process.

What checks are needed before archiving a milestone and collapsing the roadmap?

Before archiving a milestone, you must verify that all planned phases are complete and that the audit status is ready to ensure the project is prepared for roadmap collapsing.

How do I rollover requirements for the next milestone after shipping a version?

Rollover requirements by updating the project state, collapsing the completed roadmap into a summary, and preparing fresh requirements documents for the next development cycle.