create-boardReplicates a GitHub ProjectV2 board (Kanban view, Status columns, Milestone swimlanes, custom fields) onto a target repository by copying a known-good template, then verifies the copy and reports the one workflow that must be enabled by hand. Also audits existing boards for drift, read-only. Use whe
move-cardMoves a GitHub issue or PR's Project (v2) board card to a target Status column via a deterministic script (scripts/board-move.sh). Use when: (1) moving an issue to 'In Progress' when work starts, (2) moving a card to 'Development Complete'/'In Review'/'Done in develop' when its PR merges, (3) any mi
plan-milestonesRe-organises open GitHub issues across milestones so each milestone stays small, themed, and shippable, deferring the rest to a themed backlog rather than letting one milestone absorb everything. Use when: (1) a milestone keeps growing and never ships, (2) new issues land in the open milestone by de
plan-weekAnswers what to work on next from the cross-repo Weekly Focus board, plans the week, and sets the board up. Use when: (1) 'what do I work on next' or 'what should I work on', (2) 'what's my focus this week', (3) 'plan my next week' or 'weekly plan', (4) 'weekly focus' or /weekly-focus (the old name
promote-shippedMoves GitHub Projects (v2) board items to Done after a release or hotfix merges to main. Use when: (1) a release branch finished via Git Flow and the GitHub Release is published, (2) a hotfix shipped to main + back-merged to develop, (3) /finish just completed a release or hotfix, (4) the board has
prune-branchesAudits and cleans stale git branches across local and remote. Use when: (1) repository has accumulated stale feature/hotfix/release branches after merges, (2) Dependabot PRs pile up with superseded older versions, (3) temp branches from git-flow-finish scripts linger as orphans, (4) git branch -d fa
triage-issuesReviews, triages, updates, prioritizes, and closes open GitHub issues against the current codebase state. Use when: (1) open issues have accumulated and need audit, (2) user asks to clean up or review GitHub issues, (3) after a release to close resolved issues, (4) periodic backlog grooming to ident