epic-management

Creates and tracks GitHub epic issues with labels, milestones, and project board fields.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features spanning many issues are hard to track in GitHub without a unifying structure. This Skill creates epic tracking issues, groups related issues under a shared label, and keeps progress visible through project board fields and milestone coordination. ## Core Features & Use Cases - Epic Creation: Generates an epic-specific label and a structured tracking issue with goals, success criteria, dependencies, and progress sections. - Project Board Enforcement: Adds epics and child issues to a GitHub project board as a mandatory gate, setting Status and Type fields via the gh CLI. - Progress Tracking & Lifecycle: Updates epic bodies with Ready/In Progress/Done issue lists, posts progress comments, and closes epics with completion summaries. - Use Case: You are planning a dark mode feature spanning six issues. Use this Skill to create the epic issue, label and link all child issues, place everything on the project board, and track completion through to closure. ## Quick Start Use the epic-management skill to create a tracked epic for the dark mode feature with its related issues on the GitHub project board.

Frequently Asked Questions about epic-management

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

FAQPage Schema
How do I create an epic in GitHub Issues?

Create an epic-specific label with gh label create, then open a tracking issue titled "[Epic] NAME" with the epic and epic-name labels. The issue body should include the goal, success criteria, dependencies, and an issue checklist grouped by status.

How do I link child issues to a GitHub epic?

Add the epic-name label to each child issue, reference the epic in the body with "Part of epic #N", and share the same milestone. Also add each child to the project board and set its Status and Type fields.

Can I track epic progress on a GitHub project board?

Yes. Add the epic issue to the project with gh project item-add, then set Status to Backlog and Type to Epic using gh project item-edit. Child issues are added the same way and can be linked via an Epic field if one exists.

When should I use an epic instead of a single issue?

Use an epic when work is large enough to require feature-level grouping across multiple issues that together deliver user value. Single issues are better for self-contained tasks without cross-issue dependencies or progress rollups.

How do I close a GitHub epic when work is complete?

Verify all child issues are closed and success criteria are checked, post a final completion comment summarizing resolved issues and duration, then run gh issue close on the epic. Update any parent initiative with the completion status.