project-decisionslisted

# Decisions A targeted lookup against the Decisions section. The user names a topic, an ID, or a rough description; this skill finds the matching decision and its full supersession chain, not just the single entry that happens to match the words. ## Step 0: read the contracts Read these before doing anything. Do not work from memory of them. - `${CLAUDE_PLUGIN_ROOT}/docs/reading.md` -- the shared resolve-and-parse mechanism every read skill follows. - `${CLAUDE_PLUGIN_ROOT}/docs/ledger-format.md` -- entry grammar, supersession. - `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- how the reply to the user is shaped. The result in Step 5 follows it. ## Step 1: resolve config, project and ledger Follow `reading.md` § Step A and § Step B. ## Step 2: read the ledger Follow `reading.md` § Step C. Only the Decisions section is needed for the match, but read the whole file -- a decision's body may reference an open item or a context link worth surfacing alongside it. ## Step 3: match the query - **An ID was given** (`D-003`). Exact match. - **A topic or description was given.** Match by meaning against decision bodies, not just keyword overlap -- "the cutover schedule" should find a decision about cutting over on a Saturday even without the word "schedule." - **No match found.** Say so plainly. Do not guess at a near match without naming it as a guess: ``` No decision found about "<query>". Closest thing on record: the schema freeze from 2026-08-20 (D-003)