knowledgelisted

Use when work surfaces something epistemic worth keeping — "we're assuming / proceeding as if X", "we decided X over Y", "open question worth outliving this session", "we're bound by X", "evidence for/against X", "testable hypothesis", or a stable concept worth naming — and when settling, relating, or surveying such records. Routes capture, settle, and survey intent to the correct `doctrine knowledge` verb.
davidlee/doctrine · ★ 1 · Code & Development · score 69

Install: claude install-skill davidlee/doctrine

# Knowledge Knowledge records are the **epistemic home** — typed, citable entities for what the project believes, chose, wonders about, observes, or is bound by. Records *shape* work; they are never work items themselves. Four homes, one line: work intent → backlog; epistemic state → knowledge record; architectural decision → ADR; agent guidance → memory. See `using-doctrine.md` § Which home for which record. The CLI is the source of truth for exact flags and each kind's status vocabulary: `doctrine knowledge --help`. ## Which kind | phrase shape | kind | |---|---| | "proceeding as if X" (unvalidated premise) | assumption (ASM) | | "we chose X over Y" (scoped/operational) | decision (DEC) | | "unresolved — X?" (needs an answer) | question (QUE) | | "bound by X" (externally imposed limit) | constraint (CON) | | "observed — X" (citable observation) | evidence (EVD) | | "testable claim X" (awaiting evidence) | hypothesis (HYP) | | "stable mental model / term X" | concept (CPT) | **DEC or ADR?** Project-global with architectural consequences → `doctrine adr new`; scoped or operational → DEC. ## Verbs | intent | verb | |---|---| | capture | `doctrine knowledge new <kind> [title]` | | survey | `doctrine knowledge list` | | read one | `doctrine knowledge show <ID>` | | settle / transition | `doctrine knowledge status <ID> <STATE>` | | relate to the work it shapes | `doctrine link <REC-ID> shapes <TARGET>` (`spawns` for work it caused) | | evidentiary edge | `doctrine link EV