check-consistencylisted

# Skill: check-consistency **What it does.** Checks chapters against the project's established facts: world rules, timeline markers, character consistency rules, and knowledge states. Finds contradictions before readers do. **Triggers** - "check consistency of chapter X.Y" - "/check-consistency {scope}" - "does chapter X contradict anything?" - "run a continuity check on Act {N}" - Equivalent phrasing in the project's output language **Input.** Scope: one chapter, an Act, or the whole book. **Output.** Report in chat; confirmed contradictions logged to the contradictions table in `.project/knowledge/worldbuilding.md`. > **Write the report in the project's output language.** --- ## Core principle > **Flag only what is actually contradicted, with evidence from both sides. Never resolve silently.** A consistency check that cries wolf trains the author to ignore it. Every flag must cite **two passages that cannot both be true** — or one passage against one established rule. Ambiguity, stylistic variation, and things merely *unstated* are not contradictions. And when a real contradiction is found, which side wins is an **author decision**. The skill presents; it never picks. --- ## Execution protocol ### Step 1 — Load the sources of truth 1. `.project/config/project.yaml` — output language, `paths.layout` 2. `.project/knowledge/worldbuilding.md` — rules (ESTABLISHED ones especially) and their costs 3. `.project/knowledge/timeline.md` — chronology and the time-markers