{"repo":"ejklock/living-docs-skill","free":true,"listed":false,"github":"https://github.com/ejklock/living-docs-skill","clone":"git clone https://github.com/ejklock/living-docs-skill.git","description":"Living Docs — a AI agent skill that runs your project's documentation as a living system: constitution, ADRs, BDRs, PRDs, issues, research notes & Mermaid architecture diagrams under five no-drift governance invariants. OKF-formatted, stack-agnostic. Works with Claude Code, Cursor, Copilot, OpenCode & Pi.","language":"Rust","stars":10,"topics":["adr","agent-skills","ai-agents","architecture-decision-records","bdr","claude-code","claude-skill","cursor","docs-as-code","documentation"],"license":null,"category":"docs-static-sites","readme_excerpt":"Living Docs Run a project's documentation as a living system — not a write-once artifact that rots. Living Docs is an AI agent skill for documentation-as-code that keeps a codebase's docs in sync with its code. It works with Claude Code , Cursor , GitHub Copilot , OpenCode , Codex , and Pi — any agent that loads markdown \"skills\" / instruction files. It is stack-agnostic: it governs how docs are organized and maintained (Architecture Decision Records, Behavior Decision Records, PRDs, a constitution, a glossary, living Mermaid diagrams), never what technology a project uses. The mechanical half of that discipline is owned end-to-end by the bundled living-docs CLI — one self-contained Rust binary that scaffolds records ( new , brief ), drives their lifecycle ( status , describe , supersede ), rebuilds indexes ( index , fmt ), validates the invariants ( check ), and serves ranked full-text search ( search ) over a derived read-model — embedded SQLite + FTS5 or ParadeDB. There is no LLM inside the tool: the agent writes only the judgment prose; everything mechanical is deterministic and reproducible. The whole discipline collapses to one spine: Every piece of knowledge has exactly one home, that home is indexed, and nothing structural ships without its doc. Everything else — the constitution, ADRs, BDRs, PRDs, issues, research notes, architecture diagrams, and the semantic context index — hangs off that spine. --- Why this exists Most documentation rots because there is no contra","default_branch":null,"files":null,"tree":[],"storefront":"/r/ejklock","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/ejklock/living-docs-skill/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}