From board-superpowers
Use when the user wants a morning briefing, asks "what should I work on", wants to see the current board state, or needs to orient at the start of a session. Triggers on: "morning briefing", "what should I work on", "today's plan", "board overview", "what's running", "what's in progress", "board state", "show me the board", "daily briefing". Use even when the user phrases it casually ("what's up on the board", "catch me up") — the orientation signal is what matters, not formality. Do NOT use when the user wants to bring in a new requirement (that's intaking-requirement), review open PRs (that's reviewing-pr-queue), or investigate blocked cards (that's triaging-board).
How this skill is triggered — by the user, by Claude, or both
Slash command
/board-superpowers:briefing-dailyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is the Producer's daily orientation skill. It reads the board, produces a
This is the Producer's daily orientation skill. It reads the board, produces a one-screen summary, flags WIP issues and stale claims, and recommends ONE next action.
Required sub-skills:
board-superpowers:board-canon — read before any Status or WIP decision.board-superpowers:operating-kanban — dispatch the read_board protocol
action; resolves the active projection from settings.board-superpowers:composing-siblings — consult before any sibling-plugin
handoff (e.g., if overflow delegation to gstack:* / superpowers:* is
needed in an extended orientation session).board-superpowers:classifying-actions + board-superpowers:auditing-actions
— applied at every mutating action (stale-claim administrative release if any).
The daily read itself is non-mutating and does NOT invoke auditing-actions.The daily briefing answers three questions:
This skill does NOT merge, transition, or create cards (those are reviewing-pr-queue, triaging-board, intaking-requirement). If the briefing surfaces something that needs action, route to the appropriate routine SKILL.
Invoke board-superpowers:board-canon to load the state machine and WIP
counting formula. Then invoke board-superpowers:operating-kanban with action
read_board. The projection (GitHub Project v2 / Linear / Jira) is resolved
from <repo>/.board-superpowers/settings.yml § modules.m10_kanban; operating-
kanban handles the backend routing transparently.
Parse the JSON output. Expect fields: number, title, status, url,
item_id per card.
Produce a markdown summary in this exact format (omit groups with 0 items, unless ALL groups are 0):
## Board state — <YYYY-MM-DD>
### In Progress (<count>)
- #<N> <title> — claimed by <consumer>, <age>
### In Review (<count>)
- #<N> <title> — PR #<P>, <age> since opened
### Blocked (<count>)
- #<N> <title> — blocker: <one-line>
### Ready (<count>)
- #<N> <title> — <estimate or XS/S/M/L>
### Backlog (<count>)
- <count> cards (names omitted when > 5 total)
If ALL statuses are empty, use the empty-board format in
references/daily-detail.md.
Hot-card ordering: In Progress + In Review first; collapse Backlog to a count when > 5 items.
Single-Consumer projects: drop the "by " suffix when there is
only one person. See references/daily-detail.md for the simplified format.
Per board-superpowers:board-canon § "WIP counting formula" (In Progress +
In Review count; Blocked is excluded):
Stale-claim age computation:
git log origin/claim/<N>-<slug> --not main --oneline | wc -l
If 0 (or 1 for the initial empty-marker commit), count the time since branch
creation. See references/daily-detail.md for the exact git invocation.
Priority order (pick the first that applies):
In Review count > 0. Invoke
board-superpowers:reviewing-pr-queue.Blocked count > 0. Invoke
board-superpowers:triaging-board.Ready count > 0 and the Producer wants to
context-switch into Consumer mode. Show the top card by priority.board-superpowers:intaking-requirement.State the recommendation as ONE sentence: "Recommend: review the PR queue — #12 and #14 are awaiting validation."
Do NOT list multiple recommendations. The value is the single opinionated recommendation, not a menu. If the Producer wants a different action, they can say so.
After the board state is presented, the Producer may respond with a strategic question ("Is this the right work to be doing?", "Should we drop card #N and start on X instead?") that goes beyond what board data can answer. This is a sibling-plugin handoff scenario.
When the Producer's response to the briefing reads as a direction or prioritization question rather than a "what's on the board" question:
board-superpowers:composing-siblings to confirm the appropriate
sibling and its invocation safety (Mode-2 compatibility check).gstack:/office-hours for a demand-reality check."gstack:/office-hours or
gstack:/plan-ceo-review.gstack:/plan-eng-review.board-superpowers:intaking-requirement which then routes to
superpowers:brainstorming via composing-siblings.This extended orientation path is the ONLY place in briefing-daily where
a sibling-plugin handoff occurs. All other sibling-plugin calls are routed
through the appropriate routine (intaking-requirement, reviewing-pr-queue,
triaging-board) rather than initiated from within the briefing.
On rare occasions the briefing surfaces a clear administrative action (e.g., deleting a ghost branch for a card that is already Done). Apply the 5-step governance sequence:
board-superpowers:classifying-actions
references/action-id-catalog.md).board-superpowers:classifying-actions with that action_id;
receive A (auto), R (requires approval), or N (forbidden).board-superpowers:auditing-actions to record one
entry.Prefer to route to triaging-board rather than taking administrative action from within the briefing. The briefing's job is to orient, not to mutate.
When the Producer returns to an old card or Thread after a gap, the briefing skill runs first to re-establish context before routing to the appropriate routine. The briefing narrows its output to the card in question:
This re-entry variant fires when the user signals orientation desire —
"catch me up on #N", "what's the status of #N", "orient me on #N",
"where did we leave off on #N" — NOT resume desire ("claim #N", "work on #N",
"pick up #N"); resume phrases route to consuming-card directly. See
references/daily-detail.md § "Context-switch reload" for the truncated
output format.
When the Producer asks "what should I work on today" with a time-window qualifier ("I have 2 hours", "I can ship one card today"), extend the recommendation to a dispatch list:
The dispatch recommendation is read-only and non-binding — the Producer decides. Do NOT pre-claim cards.
When the board shows consecutive Done cards from the past 5 days, append a one-line velocity note below the recommendation:
Velocity: N cards shipped in the last 5 days. Pace: [above / at / below] target.
This is informational only. Do NOT compute a prediction or a sprint burn-down — those are human-team cadence constructs that don't translate directly to the AI-agent throughput model. Surface the raw count; let the Producer interpret it.
| Situation | Correct handling |
|---|---|
read_board returns empty (network / auth failure) | Surface the failure verbatim. Do NOT synthesize a board state from memory or cache. "Board read failed — operating-kanban returned: . Fix the connection before proceeding." |
read_board returns a stale dataset (e.g., GitHub Project sync lag) | Note the timestamp of the response if available. "Board data as of — if this looks stale, re-run after <30 seconds> to pick up the latest sync." |
| WIP count exceeds cap but no obvious stale claims | Flag the cap violation. Do NOT attempt to release claims or transition cards. Route to triaging-board for the investigation. |
| Producer ignores the recommendation and asks for the next one | Give the next item in the priority list and explain why it ranked lower. Still surface only ONE at a time. |
| All groups are empty (fresh project) | Show the empty-board format (see references/daily-detail.md). Recommend intake: "Board is clear — run board-superpowers:intaking-requirement to add the first card." |
The briefing is for a busy Producer. Go straight to the data — no preamble ("Here is your morning briefing:"). Skip group headers with 0 items (unless all are 0). One screen, no scroll. Sentence fragments are fine: "In Progress: 2 cards, both on track."
Single-page discipline: if the card list would require scrolling, collapse lower-priority groups. In Progress + In Review always display in full; Ready shows the top 3 cards with a "(+N more)" trailer; Backlog collapses to a count.
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 panqiwei/board-superpowers --plugin board-superpowers