living-docslisted

Run a project's engineering decisions as a living log — MADR-lite ADRs (supersede, never delete) for decisions expensive to reverse, issues for the work (and its cheap-to-reverse choices), research artifacts, an optional PRD, a project constitution, and living Mermaid architecture views, where every record has exactly one home, indexes never drift, and a record is earned by materiality, not written per layer. Use when setting up or maintaining project docs, writing an ADR/PRD/constitution/issue/research note, drawing or updating an architecture diagram, or enforcing the no-drift maintenance rule.
ejklock/living-docs-skill · ★ 13 · AI & Automation · score 73

Install: claude install-skill ejklock/living-docs-skill

# Living Docs Living Docs is a **decision log with a gate**. It records the engineering decisions a future reader would pay to rediscover, traces each from its rationale to the code, and refuses to let a record exist unindexed, untyped, or silently rewritten. The spine — **every piece of knowledge has exactly one home, that home is indexed, and a material decision ships with its record** — carries a small set of record types: ADRs, issues, research, a constitution, an optional PRD, and living architecture views. This skill is stack-agnostic. It governs *how* decisions are recorded and maintained, never *what* technology a project uses. --- ## Using this skill (progressive disclosure) This SKILL.md is a **slim stub** — a trigger plus a task→topic router. The `living-docs` CLI holds the full, authoritative conventions and templates and discloses them progressively. **Before authoring anything, load the topic for your task and operate from it, not from this stub:** - `living-docs guide --list` — discover every topic. - `living-docs guide <topic>` — load that topic's full rules (+ template). Piped output is minified JSON (machine default); `--plain` for human text, `--json` to force JSON. Write ONLY the body below the closing ---. Frontmatter and indexes are CLI-owned: `living-docs set` / `supersede` / `index`. - The spine invariants → `living-docs guide spine`. - Authoring mechanics — CLI owns every deterministic step, you write only the prose → `living-docs guide pro