curate

# /curate Power-user audit lever. Most users do not need /curate in daily flow: - **Pending revisions** surface in `/brief` automatically (top 3 with inline accept/dismiss). - **Pending captures from this session** surface in `/handoff`'s preview block (top 3). - **Orphan wikilinks** surface in `/distill`'s topic-suggestion block. Use /curate only when you want the deep walk those skills intentionally do not force. **Captures are meant to decay.** A capture lands unconfirmed and, if nothing ever conflicts with it, it quietly fades — that is by design, not a backlog you owe the system. The only items that *need* a human are genuine conflicts (a contradiction, or a richer re-capture worth merging); those surface as pending revisions. `/curate captures` is an **opt-in audit** for when you *want* to seal a batch (e.g. after a bulk import), not a daily chore to zero out. ## Decide in native cards, not prose Walk the queue with `AskUserQuestion` — the same native picker `/pages` uses. **Never narrate items one-by-one in chat prose.** A card is a real decision; prose is a wall of text the user has to reply to by hand. `AskUserQuestion` takes **up to 4 questions per card** (one per item) and **2-4 options** each, plus an auto "Other" free-text slot. So batch the queue in groups of ≤4: 1. List the pending items (per section below). 2. Take the next ≤4. Build ONE `AskUserQuestion` call: - one **question** per item — `question` is the item's content, trimmed to ~1-2 lines. ...