github-boardslisted

Manage a GitHub Projects v2 Kanban board in natural language. Use when the user wants to put tasks or issues on a board, see what they (the human) need to work on versus what the AI is working on, move cards between lanes, route work as agent-actionable or human-actionable, reject with learnings, summarize what changed on the board, promote mapped backlog onto the board, sync TODOs or other skills' plans onto the board, check or heal ledger drift, browse board history, or undo recent board changes. Also use when ANOTHER skill needs to record tasks onto the board after research or planning. Reads and edits the board via the gh CLI and GitHub GraphQL, always previewing changes before writing and reporting back. Trigger phrases: put this on the board, add to kanban, what's on my plate, what is Claude working on, move card, update the board, show board status, reject with learnings, promote the backlog, sync my TODOs onto the board, heal the ledger, what changed this week, what did the board look like before, und
Deocracy/github-boards-skill · ★ 0 · Code & Development · score 78

Install: claude install-skill Deocracy/github-boards-skill

# GitHub Boards Drive a GitHub Projects (v2) Kanban board for the user in plain language, and let other skills record work onto it. This instruction body is **vendor-neutral** (it must mirror to `AGENTS.md` with no rewrite) — all board logic lives in the bundled script, not in this prose. > **STATUS:** the engine (`scripts/board.mjs`), the verb layer (`scripts/board-manager.mjs`), the ledger pipeline (sync → map → promote), reconcile, and snapshots are implemented and tested. Before first use, configure `board.json` — run `node "<skill-dir>/scripts/board.mjs" doctor` for the setup checklist. ## How to run it All board operations go through the bundled Node script (never hand-built `gh`/GraphQL — the script carries the safety rules). Invoke it cross-platform with an absolute path: ``` node "<skill-dir>/scripts/board-manager.mjs" <verb> [args] --config <path-to/board.json> ``` If the board isn't configured yet, run `node "<skill-dir>/scripts/board.mjs" doctor` first — it checks `gh`/Node, finds the project/field IDs, and prints the one-time human board-setup checklist. ## The pipeline (which verb when) ``` sources (TODO.md, plans, other skills' artifacts) └─ sync scan / sync record ─► intent LEDGER ─► map prepare / map record ─► promote plan / promote apply ─► BOARD maintenance loops: reconcile scan/apply (drift report → ledger-only healing)