← ClaudeAtlas

map-prior-worklisted

Sweep the competitive landscape for a paper idea BEFORE drafting — find everyone already working on it, date each against your submission (prior vs concurrent is a five-month question, not a vibe), triage by whether they threaten your claimed contribution, deep-read the ones that do, and emit a verdict on WHAT YOU CAN STILL CLAIM plus a related-work skeleton. Saves the full map, not a summary. Use right after research-ideate and before draft-paper, and re-run as a cheap delta pass before submit (hot fields move). Distinct from analyze-sibling-paper (one known competitor, deep) — this one FINDS the competitors and decides which deserve that treatment; distinct from verify-citations (checks cites you already wrote, too late to reshape a contribution); distinct from study-accepted-papers (mines a venue's bar, not your rivals). Compose with research-ideate (upstream), analyze-sibling-paper (it hands off), draft-paper and find-venue (downstream).
zernie/paperlint · ★ 7 · Code & Development · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:353e5a21b731a548 compiled from skills/map-prior-work/SKILL.md.spec.ts --> # map-prior-work — find out who already did it, while you can still change course ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs map-prior-work <paper-dir> ``` An advisory pass cannot be observed failing — silence is both its error state and its normal state — so starting is an event, and events get written down. The expensive failure this prevents, in one sentence: **you discover the paper that already did your contribution after the draft is finished, when the only move left is rewriting the claim under deadline.** Grounding: the original-contribution criterion. A paper a reviewer reads as a repackaging earns no authorship credit even if it is accepted. Composes with `research-ideate` (upstream: it validated *whether* the idea is worth doing; this validates whether it is still *yours*), `analyze-sibling-paper` (this hands it the papers that need a full read), and `draft-paper` (which consumes the related-work skeleton). ## Why this exists — the failure it was written from **Real case, 2026-07 (paper #3).** The idea was validated, the venue picked, the study run, the paper drafted, the artifact built. At **T−10 days** a *citation audit* — a late mechanical check, not a search — stumbled onto a paper that had shipped the same construction **five months earlier**, with an implementation matching the paper's own §6. Conse