project-loglisted

# Log The ledger is the project's memory. This skill is the only thing that writes it. ## Hard rules **Never write lines the user has not stated or approved.** For interpreted material -- threads, pastes, transcripts, anything this skill classifies -- show the exact lines first, wait for the user to say yes, then write. "Yes" means the user said so in this conversation, and an approval of one proposal does not carry to the next one. For a fact the user dictated (Step 5's same-turn path), the dictation is the approval, given in advance -- and it stays valid only while the written lines add nothing the user did not say. **Never invent an entry.** Everything written comes from the material the user gave you. If something is implied but not said, put it in the proposal as a question, not as an entry. **Never repair a broken ledger on your own initiative.** Report the problem, name the line, and stop. Repair is a separate write and needs its own approval. **Never write the ledger from any other skill.** Another skill that needs an entry runs this one. The Changelog then records the writer as `project-log via <skill>`. ## Step 0: read the contracts Read these before writing anything. They are binding, and they are the only place their detail lives. Do not work from memory of them. - `${CLAUDE_PLUGIN_ROOT}/docs/ledger-format.md` -- section names, entry grammar, IDs, tails, body markers, Changelog, and the reading rules. - `${CLAUDE_PLUGIN_ROOT}/docs/config-resolution.md`