complete-milestone

Name: complete-milestone
Availability: InStock
Author: VirtEngine

Archive milestone docs, update governance files, and tag releases in Git.

17|4|Updated Oct 8, 2021

Search Tags:#documentation #roadmap #release-management #project-management #milestone #git-tag

Ready to run

npx skills add https://github.com/virtengine/virtengine --skill complete-milestone-virtengine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: complete-milestone
Source: https://github.com/virtengine/virtengine/tree/main/.github/skills/complete-milestone
Command: npx skills add https://github.com/virtengine/virtengine --skill complete-milestone-virtengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the milestone completion process by creating historical records, validating and evolving project documentation, and ensuring releases are properly tagged and traceable.

Core Features & Use Cases

Milestone archival: Append a new milestone entry to MILESTONES.md with summary, stats, and key decisions.
Docs evolution: Run full PROJECT.md evolution review and reorganize ROADMAP.md to reflect completed work.
Release tagging: Tag the shipped release in git and prepare archives for governance records.

Quick Start

Run the complete-milestone workflow to archive current milestone, update governance docs, and tag the release.

Frequently Asked Questions about complete-milestone

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

FAQPage Schema

How do I automate milestone completion for Markdown-based project governance docs?▼

Automate milestone completion by appending entries to MILESTONES.md, running a full PROJECT.md evolution review, and reorganizing ROADMAP.md to reflect completed work. This workflow ensures historical records are validated and releases are properly traceable.

How does git tag creation work during release management?▼

Git tag creation works by tagging the shipped release in Git after archiving ROADMAP.md and REQUIREMENTS.md. This process ensures releases are properly tagged and traceable, streamlining the end-to-end milestone lifecycle for software projects.

What is the best way to archive project requirements and roadmaps after a release?▼

The best way to archive requirements and roadmaps is to append a milestone entry with summaries and stats to MILESTONES.md, then reorganize ROADMAP.md and archive REQUIREMENTS.md to maintain accurate historical governance records.

Do I need specific dependencies to run milestone archival and documentation updates?▼

No specific dependencies are required to run milestone archival and documentation updates. The workflow operates on software projects using Markdown-based governance documents and Git tagging to complete the milestone lifecycle.

Can I use this workflow for software projects without Markdown governance documents?▼

This workflow applies specifically to software projects using Markdown-based governance documents such as PROJECT.md, ROADMAP.md, and REQUIREMENTS.md. Projects without these files will not benefit from the automated archival and evolution review features.

Why does my milestone release process lack traceability across project documentation?▼

Milestone release processes lack traceability when governance documents are not archived and updated consistently. Automating the archival of ROADMAP.md and REQUIREMENTS.md while updating PROJECT.md ensures historical records and releases remain traceable.