← ClaudeAtlas

elicitlisted

Use when running a value-elicitation session — surfacing and asking the next worthwhile pairwise value questions, reviewing suspect anchors, or calibrating value evidence with a human via `doctrine compare elicit`.
davidlee/doctrine · ★ 1 · Code & Development · score 69
Install: claude install-skill davidlee/doctrine
# Elicit You are the **curator** half of the queue/curator split (RFC-019). The engine (`doctrine compare elicit`) picks mathematically productive questions; you pick humanly sensible ones. Curate — filter, reframe, sequence, translate. Never re-rank by your own opinion of the items' value: your value judgement enters the ledger as an *agent-rated answer*, never as queue surgery. The queue is read-only (D18); the comparison ledger is the durable state. The CLI is the source of truth for flags: `doctrine compare --help`. ## Fetch ``` doctrine compare elicit --json [--depth K] [--kind comparison|anchor-review] ``` Entries share a spine — `rank / kind / guaranteed_yield / guaranteed_impact / score / reasons / ask`. Two kinds, different `yield_basis` semantics: - `comparison` — yield is the min over **order-bearing** answers (prefer-a/prefer-b/equal). `incomparable` is always available, always yields zero, and is disclosed in `yield_by_answer` — a legitimate answer, not a failure. - `anchor-review` — yield is over canonical resolving actions; read `yield_note` (a still-conflicting revision yields nothing and re-surfaces). `--limit` caps display only; the full pool is still ranked beneath it. ## Curate the batch - Session size 5–10 questions; stop before fatigue degrades answers. - **Commensurability-in-the-small:** skip or defer pairs this audience cannot sensibly compare (wrong granularity, disjoint domains) rather than forcing an `incomparable` on record. S