project-summarylisted

# Summary The whole ledger, read for someone who was not in the room. No assumed context, no "since last time" framing -- that is `project-catchup`'s job. ## 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, resolution tails. - `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- how the reply to the user is shaped. The overview in Step 3 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. This is the one read skill that genuinely wants every section, so read all four in full. ## Step 3: build the overview **Decisions.** List every decision **currently in force** -- skip an entry carrying `-> superseded by D-nnn`, since the entry that supersedes it is already in the list and says so in its own body. State the count of superseded decisions in one line rather than showing dead ones: "2 earlier decisions were superseded; ask `/daikenja:project-decisions` for the history." **Open items.** Two groups: open (`- [ ] `) and resolved (`- [x] `). Lead with open, since that is what someone new needs to act on. For resolved, a count is enough unless the user asks for detail -- do not repeat every resolved body. **Context links.** List the