epic-management

Create and track GitHub epics with linked issues and project boards.

10|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/troykelly/codex-skills --skill epic-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-management
Source: https://github.com/troykelly/codex-skills/tree/main/skills/epic-management
Command: npx skills add https://github.com/troykelly/codex-skills --skill epic-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing large, complex features by providing a structured way to group, track, and manage related issues under a single "epic."

Core Features & Use Cases

  • Epic Creation: Generates a parent issue with specific labels and body structure for tracking.
  • Issue Grouping: Facilitates the creation of child issues that belong to an epic, ensuring consistent labeling and referencing.
  • Project Board Integration: Enforces mandatory inclusion of epics and their child issues in GitHub Projects, setting correct status and type fields.
  • Progress Tracking: Provides mechanisms to update epic progress and lifecycle states.
  • Use Case: When developing a new major feature like "User Authentication Revamp," this Skill helps create a central epic, link all related tasks (e.g., UI changes, API updates, security reviews), and track their collective progress towards completion.

Quick Start

Use the epic-management skill to create a new epic for the 'Dark Mode Support' feature.

Frequently Asked Questions about epic-management

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

FAQPage Schema
How do I track large feature development using GitHub issues?

Tracking large feature development with GitHub issues involves grouping related tasks under a parent epic. This skill automates creating that central epic, linking child issues, and enforcing consistent labels to maintain visibility for complex software projects.

Do I need to configure GitHub Projects to manage agile epics?

Yes, GitHub Projects configuration is required to manage agile epics. This skill enforces mandatory inclusion of epics and child issues in GitHub Projects, setting correct status and type fields to maintain organization and progress visibility.

How do I group related GitHub issues into a single epic?

Grouping related GitHub issues into a single epic requires generating a parent issue with specific labels and a structured body. This skill facilitates creating child issues that belong to the epic, ensuring consistent labeling and referencing.

Can I use GitHub CLI to automate project board integration for feature tracking?

Yes, you can use GitHub CLI to automate project board integration for feature tracking. This skill requires GitHub CLI to enforce mandatory inclusion of epics and child issues in GitHub Projects, automatically setting correct status fields.

What is the best way to structure complex software features into trackable epics?

The best way to structure complex software features into trackable epics is using a parent issue to monitor collective progress. This approach links all related tasks like API updates and UI changes, updating lifecycle states to maintain visibility.

Why does epic management require jq and GitHub CLI dependencies?

Epic management requires jq and GitHub CLI dependencies because the skill uses scripts to interact with GitHub APIs. These tools process JSON responses and automate the creation, labeling, and project board integration of epics and child issues.