Public export
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.
npx -y skills add ejklock/living-docs-skill --skill public-exportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Publish a clean public version of a private living-docs project — the method/scaffold and a curated showcase — WITHOUT exposing your research, decisions, accumulated lessons, client specifics, or secrets. Use when you want to open-source a skill, a tool, or a framework whose private repo holds the "why" and the moat. Treats the public repo as a generated build artifact (never hand-edited): a default-deny allowlist export driven by document visibility, a deterministic leak gate, and a human-gated clean-history publish. The three-bucket model — scaffold (public), accumulation (never), curated showcase (deliberately published). Invocable as /public-export.
SKILL.md
2.7 KB, as published. Nobody here has run it
public-export — ship the method, keep the moat
Publish the scaffold and a curated showcase of your reasoning while keeping the accumulation private. The public repo is a build artifact of the private one — generated, gated, and human-published, never hand-edited.
Using this skill (progressive disclosure)
This SKILL.md is a pure router (ADR 0017) — a trigger plus a task→topic router. The
living-docs CLI holds the full model, rules, and procedure and discloses them progressively.
Before exporting or publishing, load the topic for your step:
living-docs skill public-export --list— discover every topic.living-docs skill public-export --topic <topic>— load that topic.
Piped output is minified JSON (machine default); --plain for human text, --json to force JSON.
Topics: about, buckets, visibility-model, rules, procedure.
When to invoke
- Understanding why this skill exists, its build-artifact mental model, how it composes with
living-docs/okf-knowledge-format, and its provenance →living-docs skill public-export --topic about. - Deciding what goes where — scaffold vs accumulation vs curated showcase, and the
derived-artifacts rule →
living-docs skill public-export --topic buckets. - Understanding how private stays private — the
visibilityfrontmatter field, default-deny, and why the tool never judges at publish →living-docs skill public-export --topic visibility-model. - Enforcing the hard rules (allowlist-not-denylist, gate vetoes the push, PRIVATE-first repo,
rotate a leaked secret) →
living-docs skill public-export --topic rules. - Running the export → gate → clean-history publish steps →
living-docs skill public-export --topic procedure.