← ClaudeAtlas

researchlisted

Use when a slice is scoped but not yet designed — run the pre-design research round and persist its evidence artefact — or when a consuming skill's staleness advisory reports drift. Produces a cited, verification-legended research.md that design and plan load-bear instead of recall.
davidlee/doctrine · ★ 1 · Code & Development · score 69
Install: claude install-skill davidlee/doctrine
# Research The pre-design research round produces a persisted evidence artefact — `research.md` — that later stages cite instead of re-deriving. Two read-only threads (governance applicability; code map) plus cross-thread synthesis, assembled by the orchestrating agent into one document. The artefact lives at `.doctrine/slice/NNN/research/` — directly in the slice folder, gitignored in place. Runtime tier: disposable working evidence; durable findings are harvested at slice close. **The verb:** `doctrine slice research <id>` — run it when the round starts (it mints the research folder and stamps the staleness baseline, `baseline.toml`), and again whenever you consume the artefact, to check freshness. It is advisory, never a gate: drift output is a prompt to refresh, and the command always succeeds. Flags and mechanics: the CLI's help. ## The artefact — `research.md` Mandated skeleton; refresh rounds revise sections **in place**, extra sections are free-form: - **Header** — producers (who/what ran each thread), baseline pointer. - **Verification legend** — the ✓ discipline below. - **Thread 1 — governance applicability** — binding constraints; checked-not-applicable *with stated reasons*; revision candidates. - **Thread 2 — code map** — hotspots (files likely to change), cited facts, naming precedents. - **Cross-thread findings** — where the threads intersect or conflict; often the highest-value section. - **Design-input deltas** — what this research changes about