complete-milestone

Archive milestone details, update planning documents, and create annotated git tags.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill complete-milestone-rayofsteel-dhbw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete-milestone
Source: https://github.com/RayOfSteel-DHBW/TeilAutoNeu/tree/main/.github/skills/complete-milestone
Command: npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill complete-milestone-rayofsteel-dhbw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, error-prone milestone shipping workflows are tedious and fragmented across ROADMAP.md, PROJECT.md, and REQUIREMENTS.md. This Skill automates the end-to-end milestone completion process, ensuring consistency and traceability.

Core Features & Use Cases

  • Automates archival and summarization of milestone details into MILESTONES.md.
  • Updates ROADMAP.md to group completed milestones and collapse finished work.
  • Tags the release in git and updates STATE.md and PROJECT.md to reflect shipped milestones.
  • Use Case: When you close a milestone, the Skill archives artifacts, updates planning docs, and creates a version tag with a concise summary.

Quick Start

Run complete-milestone to archive the milestone, update documentation, 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 and git release tagging across project documentation?

Automating milestone completion involves validating progress across ROADMAP.md and REQUIREMENTS.md, updating STATE.md and PROJECT.md, archiving details into MILESTONES.md, and creating an annotated git tag. This ensures traceability and consistency throughout the project evolution workflow.

What is the best way to archive completed milestones and update project roadmaps?

Archiving completed milestones requires summarizing details into MILESTONES.md and grouping finished work in ROADMAP.md. The complete-milestone workflow automates this archival process while simultaneously updating planning docs and tagging the release in git to maintain traceability.

Do I need any dependencies or external components to run the complete-milestone workflow?

No dependencies or external components are required to run the complete-milestone workflow. The Skill operates independently to validate progress, update documentation files like PROJECT.md and STATE.md, and create annotated git tags for milestone releases.

How does milestone tagging maintain traceability with requirements and roadmap files?

Milestone tagging maintains traceability by scoping across ROADMAP.md, PROJECT.md evolution, MILESTONES.md, and REQUIREMENTS.md. The workflow validates progress against these files, updates their content to reflect shipped work, and creates an annotated git tag with a concise summary.

Can I use this workflow to update STATE.md and PROJECT.md when closing a milestone?

Yes, updating STATE.md and PROJECT.md is a core part of the milestone completion workflow. When closing a milestone, the Skill validates progress, archives artifacts into MILESTONES.md, updates planning documents, and creates a version tag reflecting the shipped milestone.

What are the limitations of manual milestone shipping workflows compared to automation?

Manual milestone shipping workflows are tedious, error-prone, and fragmented across ROADMAP.md, PROJECT.md, and REQUIREMENTS.md. Automation addresses these limitations by ensuring consistent archival, review, tagging, and documentation updates throughout the end-to-end completion process.