gsd-complete-milestone

Archive completed milestone documents, update project state, and create a Git tag.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of archiving a completed development milestone, ensuring a clean historical record and preparing the project for the next iteration.

Core Features & Use Cases

  • Milestone Archiving: Saves completed roadmap and requirements documents into a historical archive.
  • Project State Update: Updates the main project file to reflect the newly shipped version.
  • Version Tagging: Creates a Git tag for the completed milestone.
  • Use Case: After successfully releasing version 1.0 of your software, use this Skill to archive the v1.0 roadmap and requirements, update the PROJECT.md file, and tag the release in Git.

Quick Start

Run the gsd-complete-milestone skill for version 1.0.

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 software milestone and create a Git tag for the release?

To archive a completed milestone, this Skill saves roadmap and requirements documents to a historical archive, updates the main project file with the current state, and creates a Git tag for the version. It requires all phase summaries to be completed first.

What happens to roadmap and requirements documents when a project version is archived?

When a project version is archived, roadmap and requirements documents are saved into a historical archive. The main project file is then updated to reflect the newly shipped version and prepare for the next milestone goals.

How do I prepare a project file for the next development milestone after a release?

Preparing for the next milestone involves updating the main project file with the current state and next milestone goals. This Skill automates that update while simultaneously archiving the completed release documents.

Does milestone archiving require completed summary files for all development phases?

Yes, milestone archiving requires all phases within the milestone to have completed summary files before proceeding. The workflow also includes verification gates requiring user confirmation to ensure everything is finalized.

Can I update the project state and tag a release in Git at the same time?

Yes, you can update the project state and tag a release simultaneously. This Skill updates the main project file to reflect the shipped version while creating a Git tag to mark the completed milestone in version control.

Why should I archive project requirements and roadmap documents after shipping a version?

Archiving project requirements and roadmap documents after shipping ensures a clean historical record of the completed milestone. This preserves the development context while the main project file resets for the next iteration.