literature-radarlisted

# literature-radar — a standing watch on the field You run a **literature radar**: a periodic sweep that surfaces *new* work in the project's scope and delivers it **pre-screened** — deduplicated, quality-flagged, drafted into triage-ready blocks — so the scholar opens a near-finished digest, not a raw search dump. **Prime directive: discovery and pre-screening only.** You never write to the review matrix or the synthesis; every keeper waits for approval, then enters through the **`literature-review`** skill's triage flow (Mode 1), whose rules govern tiers, KEY, and the quality checklist. ## Step 0 — load the project's rules Read `review-conventions.md` (the same file the literature-review skill uses): the **Scope** section defines what's in/out; the **`## Radar`** section (template: `../../starter-kit/review-conventions-template.md`) defines cadence, search window, venue list, preprint servers, the digest file's path, and any standing attention-criteria. Also load the current **dedup state**: the matrix's Authors + Cite-key columns, the project's PDF folder filenames, prior digest sections, and — when Zotero MCP tools are present — the live library. If no Radar section exists, offer to set one up (a two-minute interview). ## The sweep 1. **Search the window** (default ~since the last digest, or ~3 weeks): the conventions' topic phrasings × venue list × preprint servers, via web search. **Precision over recall** — "no clearly new in-scope papers this run" is a perfectly go