os-backlog slice 4: capture + list skills #13

New Issue

Closed

opened 2026-07-10 17:22:34 +00:00 by jared · 1 comment

jared commented

2026-07-10 17:22:34 +00:00

Owner

Type: AFK · Triage: ready

Parent

PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051

What to build

The capture and list skills (/os-backlog:capture, /os-backlog:list). Capture: work discovered mid-session becomes a Backlog card on the board resolved deterministically from the current repo (via the routing resolver); a missing board is created through board-ensure transparently. Cards always enter at Backlog — column ownership rules (AI never pulls Next, never moves past Review, never self-assigns hitl cards) are stated in the skill wording. List: pull-based, shows cards relevant to the current repo/board on demand; never injected unasked (notification policy v2).

Both skills fail soft: Planka or gem binary unreachable → explicit error on these user-invoked paths, but nothing at session start breaks.

Acceptance criteria

Capture creates a card at Backlog on the correct board from any repo under ~/dev/* / ~/clients/*
Missing board auto-created with uniform lists/labels before the card lands
List shows current-repo cards on demand; no push/injection of board state anywhere
Column-ownership and hitl rules present in skill wording
Deterministic parts covered by stubbed-client tests; one manual live verification recorded

Blocked by

#10 (plugin scaffold + board-ensure)
#12 (routing resolver)

**Type:** AFK · **Triage:** ready ## Parent PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051 ## What to build The capture and list skills (`/os-backlog:capture`, `/os-backlog:list`). Capture: work discovered mid-session becomes a Backlog card on the board resolved deterministically from the current repo (via the routing resolver); a missing board is created through `board-ensure` transparently. Cards always enter at Backlog — column ownership rules (AI never pulls Next, never moves past Review, never self-assigns `hitl` cards) are stated in the skill wording. List: pull-based, shows cards relevant to the current repo/board on demand; never injected unasked (notification policy v2). Both skills fail soft: Planka or gem binary unreachable → explicit error on these user-invoked paths, but nothing at session start breaks. ## Acceptance criteria - [ ] Capture creates a card at Backlog on the correct board from any repo under `~/dev/*` / `~/clients/*` - [ ] Missing board auto-created with uniform lists/labels before the card lands - [ ] List shows current-repo cards on demand; no push/injection of board state anywhere - [ ] Column-ownership and hitl rules present in skill wording - [ ] Deterministic parts covered by stubbed-client tests; one manual live verification recorded ## Blocked by - #10 (plugin scaffold + board-ensure) - #12 (routing resolver)