projects-adminlisted

# projects-admin — GitHub Projects (v2) Board & Issue Admin This skill covers the full lifecycle of a GitHub Projects v2 board and its items: creation, field setup, issue management, bulk operations, CI automation, and gap detection/fill via `/board fill`. > **Diagrams in any artifact** (plan/epic/issue body, handoff, status update): never hand-draw > ASCII art — use the `diagram-authoring` skill (Mermaid by default, escalate to D2/Graphviz via > Kroki). See `skills/diagram-authoring/SKILL.md`. --- ## Step 0 — Identity (always first) **Before every operation in this skill, apply the `gh-account` skill** to load `GH_TOKEN` for the correct account. The default account is **CSalcedoDataBI**; switch to PAL-Devs only when the user explicitly says so or when you receive a 403 on a PAL-owned board. ```powershell # Default — CSalcedoDataBI $t = [System.Environment]::GetEnvironmentVariable('GITHUB_TOKEN_PERSONAL', 'User') $env:GH_TOKEN = $t ``` Every `gh project` and `gh issue` command below assumes `$env:GH_TOKEN` is already set for the correct account. Never run `gh auth switch` — it mutates global `gh` state. --- ## Anchoring: one board, one repo A board must be linked to exactly one origin repo before issue operations begin. ```powershell # Resolve the origin repo (run inside the repo's working directory) $origin = gh repo view --json nameWithOwner -q .nameWithOwner # e.g. "CSalcedoDataBI/agentic-board" ``` Link or verify the link: ```powershell gh project link <num>