complete-milestone

Archive completed milestones in MILESTONES.md, review PROJECT.md, reorganize ROADMAP.md, and tag releases in git.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/bhanukushwah/parinaya-os --skill complete-milestone-bhanukushwah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete-milestone
Source: https://github.com/bhanukushwah/parinaya-os/tree/main/.kilocode/skills/complete-milestone
Command: npx skills add https://github.com/bhanukushwah/parinaya-os --skill complete-milestone-bhanukushwah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the critical process of marking a software milestone as complete, ensuring all necessary documentation, reviews, and archival steps are performed consistently.

Core Features & Use Cases

  • Milestone Archival: Creates historical records of roadmap and requirements for each shipped version.
  • Project Evolution Review: Guides a thorough review and update of the project's core definition, value, and requirements.
  • Roadmap Reorganization: Updates the project roadmap to reflect completed milestones and phases.
  • Git Tagging & Committing: Creates a Git tag for the milestone and commits all changes.
  • Use Case: After successfully developing and testing version 1.0 of your application, you use this Skill to formally close out the milestone, archive the work done, update the project's long-term vision, and prepare for the next development cycle.

Quick Start

Use the complete-milestone skill to mark version 1.0 as shipped.

Frequently Asked Questions about complete-milestone

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

FAQPage Schema
How do I automate software milestone archival and update project documentation in git?

Automate software milestone archival by generating historical records in MILESTONES.md, reviewing PROJECT.md, reorganizing ROADMAP.md, and tagging the release in git. This ensures all project lifecycle documentation is consistently updated and committed when a version ships.

What is the best way to close out a formal release process and prepare for the next development cycle?

The best way to close out a formal release process is to perform a project evolution review, archive the roadmap and requirements, and commit a git tag for the milestone. This formalizes the release and prepares the project for the next cycle.

Do I need specific directory structures and the git CLI to automate release tagging and milestone completion?

Yes, automating milestone completion requires the git CLI for tagging and committing. It also requires specific file structures within the .gsd/ directory to manage roadmap, requirements, and project documentation.

How does a project evolution review work when shipping a new version?

A project evolution review guides a thorough update of the project's core definition, value, and requirements during milestone completion. This ensures the PROJECT.md file accurately reflects the current state of the shipped version.

Can I use this milestone archival process if my project documentation is not in the .gsd/ directory?

No, this milestone archival process requires adherence to specific file structures within the .gsd/ directory. You must organize your roadmap, requirements, and project documentation in this structure before execution.

Why does roadmap reorganization matter after completing a software milestone?

Roadmap reorganization matters because it updates the project roadmap to reflect completed milestones and phases. This keeps your ROADMAP.md accurate for future planning immediately after a release is shipped.