epic-management
Epic Management
Overview
An epic groups related issues that together deliver a feature or capability. This skill creates, tracks, and manages epics using GitHub's native features.
Core principle: An epic is a collection of issues that together deliver user value.
Announce at start: "I'm using epic-management to structure this feature into a tracked epic with related issues."
What is an Epic?
An epic is:
- A parent issue with the
epiclabel - A collection of related issues sharing an
epic-[name]label - Optionally associated with a milestone
- Part of an initiative (if the work is massive)
Epic Structure in GitHub
More from troykelly/codex-skills
error-recovery
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
28documentation-audit
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
21security-review
MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code
16code-explorer
Use when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.
11code-simplifier
Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.
9code-reviewer
Use when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.
7