complete-milestone

Automate GitHub milestone closure with audit, summary, and state archiving.

Updated Apr 12, 2026

Search Tags:#automation #workflow #github #release #project-management #milestone

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill complete-milestone-olivermorgan2

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of closing project milestones by automating the audit, summary, and state-archiving process, ensuring consistent project documentation.

Core Features & Use Cases

End-to-End Milestone Closure: Orchestrates the audit, summary, and GitHub state update in a single, safe workflow.
State Management: Automatically updates design/state.md to reflect the closed milestone and prepare for the next phase.
Use Case: Use this at the end of a development sprint to verify all issues are addressed, generate a retrospective summary, and transition the project state to the next milestone or release.

Quick Start

Run the complete-milestone skill for milestone number 5 to close it and archive the current project state.

Frequently Asked Questions about complete-milestone

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

FAQPage Schema

How do I automate closing GitHub milestones at the end of a sprint?▼

You can automate GitHub milestone closure by orchestrating an audit, summary, and state-archiving workflow. This automatically verifies all issues are addressed, generates a retrospective summary, and transitions the project state to the next release.

What do I need to set up before automating project milestone lifecycle tracking?▼

Automating milestone lifecycle tracking requires authenticated GitHub CLI access and a structured design/state.md file. These prerequisites allow the workflow to perform repository mutations and update project documentation safely.

How does milestone state management work when a development sprint finishes?▼

State management during milestone closure automatically updates the design/state.md file to reflect the closed sprint. It archives the current project state and prepares the documentation for the next development phase or release.

Can I use GitHub CLI to audit issues and archive project state in one workflow?▼

Yes, you can use authenticated GitHub CLI access to chain audit, summary, and state-archiving tasks into a single workflow. This eliminates manual overhead and ensures consistent project documentation when closing milestones.

What is the best way to document retrospective summaries for completed project milestones?▼

The best way to document retrospective summaries is through an automated milestone closure workflow. It audits completed issues, generates the retrospective summary, and writes the results directly into your project's state management file.

Why does automated milestone closure require a structured state.md file?▼

Automated milestone closure requires a structured state.md file to accurately archive the project state and prepare for the next phase. Without this structured documentation, the workflow cannot perform safe repository mutations or track the milestone lifecycle consistently.