github-project-init
GitHub Project Init
Turn the planned work into a live GitHub project: issues, board, branches, templates, and CI. This runs after coding-standard (the PR template and CI quality gate reference the checklist) and reads the task breakdown (docs/task-breakdown/, or docs/TASK_BREAKDOWN.md in an older project) as the issue source. It is the only skill that writes CI: tech-lead-setups defines the aggregate check command, and this skill's workflow runs it.
Running project (adopt mode). If the repository already has branches, protection rules, labels, a board, or workflows, keep them. Add only what is missing, and ask before you add a branch or change a default branch or a protection rule.
This skill performs many outward-facing, hard-to-reverse actions (creating dozens of issues, branches, a board). Work in two phases: gather and confirm the full plan, then execute. Never bulk-create before the user has approved the plan and the issue count.
Prerequisites
ghauthenticated with repo write access:gh auth status. If not, ask the user to rungh auth login.- A GitHub repository exists for this project. If not, confirm and create it (
gh repo create). - The task breakdown exists (run
task-breakdownfirst if not) and the coding standard and review checklist exist:docs/coding-standard/anddocs/code-review-checklist/, or the single-file forms in an older project (the templates and CI reference them). Readdocs/technical-specs/anddocs/deployment-plan/(orDEPLOYMENT_PLAN.mdin an older project) for the verification commands and the branch/deploy model, anddocs/business/sprint-breakdown.mdfor the canonical sprint numbers and titles. - Issues come from the engineering cards in the task breakdown (backend, frontend, and Tech-Lead scaffold work). Deployment, release, and ops procedures are not cards; they live in
docs/deployment-plan/. Do not invent issues for them.