33 lines
1.8 KiB
Markdown
33 lines
1.8 KiB
Markdown
---
|
|
description: Show the Planka backlog cards relevant to the current repo, on demand. Pull-only — ONLY use when the user explicitly asks what's on the board / backlog / what's next; never inject board state into a session unasked. Invoked by `/os-backlog:list`.
|
|
---
|
|
|
|
Show the current repo's board state when — and only when — the user asks for it.
|
|
|
|
## Pull-only rule (notification policy v2)
|
|
|
|
This skill is strictly pull-based. **Never volunteer board state**: not at session start, not after a capture, not "while you're here". The only trigger is an explicit user request ("what's on the backlog?", "/os-backlog:list", "show the board").
|
|
|
|
## Column-ownership rules (also apply here)
|
|
|
|
Listing is read-only. While discussing the listed cards:
|
|
- Never pull cards into or out of Next; never move anything past Review; never move Review → Done.
|
|
- If the user asks you to start work from the list, cards labeled `hitl` are off-limits for self-assignment — flag them back to the human instead.
|
|
|
|
## Procedure
|
|
|
|
1. Resolve the board for the current repo the same way capture does (`resolve` — see `/os-backlog:capture`). On `stop-and-discuss`, ask the user which board they mean instead of guessing.
|
|
2. Show the cards:
|
|
```bash
|
|
${CLAUDE_PLUGIN_ROOT}/bin/os-backlog cards --board <board>
|
|
```
|
|
For a structured view (filtering, counting), use JSON instead:
|
|
```bash
|
|
${CLAUDE_PLUGIN_ROOT}/bin/os-backlog snapshot --board <board>
|
|
```
|
|
3. Relay the listing compactly, in board-column order (Backlog, Next, Doing, Waiting, Review, Done). If the user asked a narrower question ("what's in review?"), answer only that.
|
|
|
|
## Failure behavior
|
|
|
|
Fail soft: if the planka-api gem or Planka is unreachable, the CLI prints one clear error and exits nonzero — relay it and stop. Never fabricate board state.
|