milestone-management

Creates and tracks GitHub milestones to group issues into delivery phases.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill milestone-management-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: milestone-management
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/milestone-management
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill milestone-management-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to answer "what will be done by when?" when issues pile up without time-based grouping. This Skill organizes GitHub issues and epics into milestones with due dates, progress tracking, and slippage handling so delivery commitments stay visible. ## Core Features & Use Cases - Milestone Creation & Naming: Create milestones via the GitHub CLI with conventions for versions, quarters, phases, and sprints, plus a structured description template covering goals, deliverables, and success criteria. - Issue & Epic Assignment: Assign individual issues or bulk-assign all issues in an epic to a milestone using gh commands. - Progress Tracking & Reports: Query milestone open/closed counts, compute completion percentages, and generate weekly status reports with on-track/at-risk indicators. - Slippage Handling: Move issues to the next milestone, extend due dates, or reduce scope, and document the changes as comments. - Use Case: A team planning a v2.0.0 release creates a milestone with a due date, assigns three epics and their issues, then generates a weekly progress report showing 60% completion with blockers flagged. ## Quick Start Ask the AI to create a GitHub milestone named v1.0.0 with a due date, assign your open issues to it, and show a progress report.

Frequently Asked Questions about milestone-management

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

FAQPage Schema
How do I create a GitHub milestone with a due date using the CLI?▼

Use gh api repos/OWNER/REPO/milestones with -X POST, passing -f title, -f description, and -f due_on in ISO 8601 format like 2026-03-01T00:00:00Z. Omit due_on to create a milestone without a deadline.

How do I assign all issues in an epic to a milestone?▼

List the epic's issues with gh issue list --label "epic-NAME" --json number, then loop through the numbers running gh issue edit NUMBER --milestone "MILESTONE_NAME". Also assign the epic tracking issue itself.

What is the difference between a milestone and an epic in GitHub?▼

A milestone groups work by time or delivery phase and usually has a due date, while an epic groups issues by feature or capability. An epic can be assigned to a milestone, and multiple epics can share one milestone.

How do I track milestone progress and generate a status report?▼

Query gh api repos/OWNER/REPO/milestones to get open_issues and closed_issues counts, then compute the completion percentage. The Skill includes a script pattern that formats this into a weekly report with on-track, at-risk, and not-started statuses.

What should I do when issues will miss a milestone deadline?▼

You have three options: move issues to the next milestone with gh issue edit, extend the due date via a PATCH to the milestone API, or reduce scope by removing non-critical issues. Document the slippage as a comment on the epic or initiative.