Stats
Actions
Tags
From sprint
Universal kanban standards that apply to every board in this project. Use when creating a card, moving a card between lanes, querying card state, or understanding kanban conventions. This is required reading before touching any kanban board. Trigger phrases include "work a ticket", "advance a card", "update the board", "create a card", "kanban rules", "card format". After reading this, also read the board-specific skill (sprint:board for sprint, retro:kanban for retrospective-actions) for lane definitions. Do NOT use this as the sole reference for a specific board -- always pair with the board-specific skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sprint:kanbanThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
All kanban boards in this project follow these rules. Board-specific rules
All kanban boards in this project follow these rules. Board-specific rules (card format, naming, lifecycle details) are documented alongside each board.
Cards are Beads issues. Status is a field (open, in_progress, closed). Lane is a label (lane-backlog, lane-in-progress, etc.).
Moving a card between lanes = updating labels:
bd --db <board.db> update <id> --remove-label lane-<old> --add-label lane-<new>
Claiming a card (sets assignee and status to in_progress):
BD_ACTOR=<your-name> bd --db <board.db> update <id> --claim --add-label lane-<working-lane>
Completing a card:
bd --db <board.db> close <id> --reason "Review passed."
No directory structure is needed — the database is the source of truth.
Every board uses Beads statuses (open, in_progress, closed) combined with lane labels to represent workflow stages. The specific lane labels and their meaning are defined in each board's documentation.
All lane labels use the lane- prefix:
lane-backlog ← Entry point for new cards
lane-<stage> ← Intermediate stages (board-specific)
...
closed ← Terminal state (no lane label needed)
Why labels: Labels are queryable (bd list -l lane-backlog), composable (a card can have multiple lane and metadata labels), and don't require filesystem operations to change.
Rule: Every formal pipeline stage uses a lane- prefixed label. Boards may define as many intermediate lane labels as needed in their own documentation.
bd update <id> --claim before starting. This is how the team knows work is claimed.closed is terminal — only close a card (bd close) when the work is fully verified, not just completed.--append-notes, never rewritten or deleted.
YYYY-MM-DD: Note. (by @name)--claim sets the assignee. Use --assignee "" to clear when handing off.| Board | Database | Board-specific docs |
|---|---|---|
| Team sprint | bd | sprint:board |
| Retrospective actions | bd | retro:kanban |
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub cosmicdreams/claude-plugins --plugin sprint