GitHub Project Management

Primary skill for organizing a repository's issues into an epic-based roadmap on a GitHub Project (v2) and running the day-to-day on it. Covers setup (project, fields, views, native workflows) and operations (create epics with sub-issues, drive Status, move work, prioritize). GitHub-only, via gh project + gh api (REST sub-issues + GraphQL).

Verified against gh v2.103.2 (2026-10-27): every gh subcommand and flag used here, against its --help on v2.102.0 (2026-09-30), then the pkg/cmd sources of v2.102.0 and v2.103.2 diffed (2026-10-27), since --help is generated from them: no flag of a subcommand used here changed (gh issue create/edit changed only how --body-file resolves attachment paths). Minimums are tagged where they matter (gh >= 2.94, >= 2.97). If gh --version is newer, read the release notes since v2.103.2 for gh project and gh issue changes before relying on flag details.

The conventions here are non-obvious and easy to get half-right: the UI nests issues by native parent/child links and tracks progress on a separate board Status field -- neither of which a markdown checklist or a closed issue touches. Get those two wrong and the work looks done while the structure silently drifts. This skill makes the flow correct-by-default.

When to Use

• Setting up a project/roadmap -- create the Project, fields (Status, Priority), the Epic + Upcoming views, enable native workflows
• Creating an epic with issues -- "make an epic X with these issues", "group these under an epic"
• Filing / moving work -- attach an issue under an epic, move an issue between epics, add new work
• Driving the board -- pick up an issue (-> In Progress), close one (-> Done), (re)prioritize
• Classifying work -- set native issue Types (Task/Bug/Feature) instead of type labels
• Milestone scoping -- create a milestone for a deliverable, assign issues, close it out; resolve "current milestone" / "milestone N"
• Migrating an existing repo's loose issues into this structure
• Granting access -- a teammate cannot apply labels, assign, link sub-issues, or edit Status/Priority
• Configuring tool allowlists -- auto-approval patterns for read-only gh project commands