judgementlisted

# Judgement One subject, one verdict. The subject is a thread or a document; the verdict says what it claims or asks, checks that against the project's ledger first and against general knowledge second, and labels every statement with where it came from. It comes back in one of two forms: `answer`, a reply to the user in the conversation, or `message`, a deliverable a cold reader can be handed as it stands. `thread` summarises and gathers; `compose` writes a reply; `doc-review` runs a fixed checklist over a document's own quality. This skill does none of those. It judges whether what the subject says holds up. ## Hard rule: read-only, and never a reply **Do not draft a reply, a suggested wording or a message to send back into the thread.** Not even in the `message` form: that form is an assessment written as an AI pass, headed as one, and it is never phrased as the user speaking. A user who wants to answer the thread runs `/daikenja:thread` and then `/daikenja:compose`. **Do not write the ledger, the card or `daikenja.yaml`.** A contradiction this skill finds is reported; it is logged, if at all, by the user through `/daikenja:project-log` afterwards. A project this skill cannot resolve is not registered by it and gets no card from it. **Do not edit the document.** A finding names what is wrong and where. The human edits. ## Step 0: read the contracts Read these before the first output: - `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- the `answer` form is a con