What problem does it solve? Turning a multi-step implementation plan into trackable GitHub issues is tedious and error-prone: you must create a parent tracking issue, one child issue per plan step, wire up real blocking dependencies, and keep everything consistent. This Skill automates that entire filing workflow while preventing duplicates and premature implementation. ## Core Features & Use Cases - Plan-to-Epic Conversion: Reads a plan package (plan.md plus expanded steps/*.md) and proposes one parent issue plus one child sub-issue per step, where each child maps to exactly one future PR. - Duplicate Detection: Searches existing open issues for the plan title before creating anything, avoiding duplicate epics. - Approval-Gated Creation: Presents a proposal table with titles, dependencies, and split/merge recommendations, then waits for explicit approval before a single subagent performs all GitHub mutations via gh. - Use Case: After finalizing a five-step implementation plan, invoke /create-epic to file a tracking epic with five child issues, real blocked-by edges, and a plan-only PR referencing all issues. ## Quick Start Invoke /create-epic after your implementation plan is complete to file the GitHub epic and child issues.
