gsd-complete-milestone

Archive project milestones by validating audits, consolidating documentation, and tagging git versions.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-complete-milestone-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-complete-milestone
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-complete-milestone-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex, multi-step process of closing out a project milestone, ensuring that documentation is archived, requirements are validated, and the repository state is correctly tagged for release.

Core Features & Use Cases

  • Milestone Archiving: Automatically moves roadmap and requirement artifacts into historical folders.
  • Audit Verification: Ensures all project phases have been audited and summarized before finalization.
  • Version Control: Handles the creation of git tags and commit logs for shipped versions.
  • Use Case: When a development cycle ends, use this skill to generate a clean audit trail, archive the current requirements, and prepare the project structure for the next version.

Quick Start

Invoke the gsd-complete-milestone skill by typing the command followed by the version number you wish to archive.

Frequently Asked Questions about gsd-complete-milestone

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

FAQPage Schema
How do I automate milestone archiving and finalize a project version in git?

Automating milestone archiving validates audit status, consolidates roadmap and requirement documentation, and performs git tagging operations to finalize project versions. This creates a clean state transition between milestones and generates a structured version history.

What is the best way to archive project requirements and roadmap documentation after a development cycle?

Archiving project requirements involves automatically moving roadmap and requirement artifacts into historical folders after verifying audit status. This ensures all project phases are audited and summarized before finalizing the release.

Does milestone finalization require specific git repository permissions?

Milestone finalization requires git repository permissions to execute archival and tagging tasks, along with access to project planning files. These permissions allow the workflow to create git tags and commit logs for shipped versions.

Can I use milestone archiving for software lifecycles that need structured version history?

Milestone archiving applies to software development lifecycles requiring structured version history and clean state transitions. It consolidates documentation and validates audits to prepare the project structure for the next version.

Why does milestone completion require audit verification before generating a git tag?

Audit verification ensures all project phases are audited and summarized before finalization. This validation step prevents incomplete development cycles from being archived and guarantees a clean audit trail for the shipped version.

What are the limitations of automating project milestone archival without access to planning files?

Automating project milestone archival requires access to project planning files to consolidate roadmap and requirement documentation. Without this access, the workflow cannot validate audit status or move artifacts into historical folders.