What problem does it solve? Keeping GitHub issues and milestones aligned with BMAD planning artifacts (epics files and sprint-status.yaml) is tedious and error-prone when done by hand. This Skill automates the one-way mirror so GitHub always reflects the current plan without duplicate or stale issues. ## Core Features & Use Cases - Idempotent issue mirroring: Marker comments in issue bodies identify managed issues, so repeated runs create or update exactly what changed and never touch human-created issues. - Epic and story hierarchy: Creates one milestone per epic, one epic issue with a task list of story issues, and story issues with labels derived from the modules they mention (area, fairness, touches-upstream). - Status synchronization: Stories marked done in sprint-status.yaml close their issues; anything else keeps or reopens them, and docs/roadmap.md is refreshed afterward. - Use Case: After updating the epics file for a Shattered Pixel Dungeon engine project, run the dry run to review the create/update plan, then apply it to sync all milestones and issues in one pass. ## Quick Start Ask the assistant to sync issues by saying "sync issues" or "mirror the stories to GitHub", and it will dry-run scripts/sync_issues.py, review the plan, and apply it.
