---
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 — this skill never moves cards itself. While discussing the listed cards:
- Working a card means moving it (via `card-move`, see `/os-backlog:capture`): Doing when started, Waiting plus a blocker comment when blocked, Review when a semi card ships, Done when an afk-ready card ships and is verified.
- Next stays human-curated in both directions — never move a card into or out of Next.
- If the user asks you to start work from the list, cards labeled `hitl` are off-limits — never moved by the AI, flag them back to the human instead.
- These rules are enforced deterministically by the CLI (`card-move`), not just documented here.

## 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.
