checklisted

Checks live as `.claude/agents/check-<name>.md` — one isolated agent per check, each defined by what it verifies, said in its `description`; the roster is the scan of those files. Adding a check means adding an agent file from `templates/check.md`; this command does not change (who creates a check, and when: CLAUDE.md, Isolated reviewers; a rule verified by two checks is a defect). The rules shared by every check — isolation, the conformance-only remit, read-only, findings only, the shape of the report — live in the contract skill `.claude/skills/check-contract/SKILL.md`, preloaded into every check file through its front-matter, whose own part is its Lens section; nothing of them is restated here (POS.1070, POS.1140). The check runs on the same mechanism as the critic (`/critique`) and the challenger (`/challenge`): a roster, one agent per entry, a walkthrough after. Unlike them it files nothing: the report returns to the session and its findings are settled there. This command only chooses the check, passes the target and presents the report. **Bare `/check` — the roster.** List the available checks (scan `.claude/agents/check-*.md`, their `description` fields) and recommend which fits the moment — `single-source-of-truth` before a major or after a round on the operating layer; what a save or a release runs is `/save`'s and `/release`'s to say. A recommendation, never a gate; no check runs on Claude's own judgement. **`/check <name> [slug]` — run it.** The target: for `pr