skills.rest
AO-Cyber-Systems
AO-Cyber-SystemsOFFICIAL
Explore all skills by this author →
GitHub

df:complete-milestone

Archive completed milestones and create Git tags for released versions.

Updated Feb 6, 2026
Search Tags:#git#workflow#requirements#roadmap#milestones
One-click install
npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-complete-milestone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: df:complete-milestone
Source: https://github.com/AO-Cyber-Systems/devflow-claude/tree/main/skills/df-complete-milestone
Command: npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-complete-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestones and preserve their release history, ensuring a durable record of shipped versions and decisions.

Core Features & Use Cases

  • Archive milestone artifacts to .planning/milestones/v{{version}}-ROADMAP.md and v{{version}}-REQUIREMENTS.md, preserving linkage to ROADMAP and REQUIREMENTS.
  • Update PROJECT.md with current state and planned next milestone goals.
  • Tag releases in Git and provide a clear historical narrative for audits and handoffs.

Quick Start

Run the complete-milestone workflow for the target version to archive the milestone and prepare the next.

Frequently Asked Questions about df:complete-milestone

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

FAQPage Schema
How do I archive completed milestones and preserve their release history in Git?▼

To archive completed milestones and preserve release history, this workflow archives artifacts to .planning/milestones, updates ROADMAP.md, REQUIREMENTS.md, and PROJECT.md, and creates a Git tag for the version.

What is the best way to update ROADMAP.md and REQUIREMENTS.md after a release?▼

The best way to update ROADMAP.md and REQUIREMENTS.md after a release is to run a complete-milestone workflow that archives artifacts, enforces a verified audit, and primes the next milestone with fresh requirements.

How does Git tagging work when archiving project milestones?▼

Git tagging during milestone archiving marks the specific version release, providing a clear historical narrative for audits and handoffs while linking project documentation to the durable record of shipped versions.

Do I need a verified audit before archiving milestone artifacts?▼

Yes, archiving milestone artifacts requires a verified audit to ensure a durable record of shipped versions and decisions before updating PROJECT.md and tagging the release in Git.

What limitations exist when priming the next milestone with fresh requirements?▼

The workflow primes the next milestone with fresh requirements by updating PROJECT.md with planned goals, but it focuses solely on archiving and preparing rather than executing the actual development work for the new milestone.

Related Skills

Explore More Software Engineering Skills→
thecomputer07thecomputer07

qsd-complete-milestone

Archives completed milestone docs and updates ROADMAP.md, REQUIREMENTS.md, STATE.md for the next version.

Community
Advanced
onelee85onelee85

gsd-complete-milestone

Archive versioned milestones by updating ROADMAP.md, REQUIREMENTS.md, and PROJECT.md with a git tag.

Community
Advanced
sumilee-pcusumilee-pcu

changelog

Generate internal and external changelogs from git history and sprint reports.

Community
Intermediate
optaveoptave
86

release

Generate release notes and PR scaffolding from commit history.

Official
Advanced