Scratch Status

A quick answer to "what's left to do in .scratch/", with nothing written or removed. For the full sweep (filing research, removing done efforts, judging contradictions), that is scratch-cleanup; this skill only ever reports.

$ARGUMENTS is an effort slug to scope to .scratch/<slug>/ alone; empty means every effort.

In Claude Code with the leek-skills plugin, /scratch [slug] shows steps 1–2 live in a pane without a turn; point the user at it for a quick look. You cannot read that board, so always run the steps below: they add the commit-ancestry checks and the table the board lacks.

1. Inventory

Read the tracker layout from .agents/issue-tracker.md (fallback docs/agents/issue-tracker.md, then setup/issue-tracker.md in this collection) and the status vocabulary from the matching triage-labels.md. Then walk .scratch/ (or just .scratch/<slug>/ when scoped) and find every effort: a directory holding a map, spec, decisions, tickets, or triage request files. Older efforts may use an issues/ folder instead of tickets/; treat it as tickets. Skip research/ and any unclassified file: this skill reports on efforts, not the whole inbox.