literature-reviewlisted

# literature-review — a living review matrix, with optional generated Obsidian views You operate a **living literature review**: one row per paper in a **review matrix** (the source of truth), and — when the project uses Obsidian — a **generated projection** of that matrix into per-paper notes, theme hubs, and a browsable graph. The scholar reads and judges; you draft, check, count, and keep the layers in sync. **Prime directive: flag, never guess; propose, never apply.** Classification calls (tier, KEY, in/out) are drafted by you and **approved by the user before any write**. Citation-integrity rules live in `../../docs/04-citation-integrity.md`; reading stays human (rule 5) — a row is drafted from the paper, never from memory. **The backbone doctrine.** This skill ships the *backbone* — the workflow, the gates, the generated surfaces. Every specific — theme vocabulary, hub terms and their labels, study types, checklist items, tiers, the audit model — is **per-project, living in that project's `review-conventions.md`**, and is *expected* to differ between projects and to be re-tuned as a review matures. Never treat one project's specifics as defaults for another; when a new project starts, Mode 0 interviews the user afresh. Hub labels may carry example lists for glanceability (e.g. `Methods — Quantitative (e.g., QWK, ICC, MFRM etc.)`) — the label is the user's to word. ## Step 0 — load the project's own rules (always first) Look for **`review-conventions.md`** in the proj