live_docs

Plugin live_docs from marketplace live-docs in mountainbiometrics/live_docs. Commands read from the repo's manifest — 21 days ago.

Skills (27)

• apply-to-docs

  Run a request or plan against the live_docs knowledge base before acting on it: extract key concepts, map them to existing docs, walk the full impact graph to identify the blast radius, pause only for unintended side-effects (not for a supersession the request settles, and not merely because many do

• assess-blast-radius

  Given the mapped concepts and their directly-affected docs, walk the dependency graph BEFORE any write to determine the complete impact set — every doc that will need a change, with a verdict. This is the pre-write impact survey: read-only BFS over requires/belongs_to (upstream) and dependents (down

• audit-docs

  Read-only quality audit of a named set of docs against the store's shared writing standards, by a reader who has not seen the request or conversation that produced them. Reports where a doc fails the standards (register, descriptors, implementation wording in a claim, scope beyond its title, type, m

• cascade-check

  After one or more docs change, walk the dependency graph in BOTH directions (upstream dependencies and downstream dependents) and decide whether each neighbor must be updated, is unaffected, conflicts, or needs clarification, then propagate the updates. The primary consistency-enforcement mechanism

• curate-grouping

  DEPRECATED — use /garden or /garden find homes for orphans instead. Thin alias forwarding to garden-hierarchy (the structure phase of the garden dispatcher). Retained for backward compatibility with existing references.

• garden-collapse

  Gardening phase: enforce singular ownership — merge near-duplicate docs and fold thin cruft into parents. The inverse of garden-decompose. Nested phase; garden dispatcher owns the episode and runs decompose before collapse in full sweeps.

• garden-cruft

  Gardening phase: remove cruft — strip dead implementation detail and existence claims off still-current decisions (excavate), rewrite changelog-shaped bodies to the current state, retype mis-typed docs, add missing whys, and delete refactor-chore docs and replaced stop-gaps whose durable why already

• garden-decompose

  Gardening phase: find docs carrying more than one responsibility and split them. Signals include multiple unrelated body sections, hot-file history, long requires lists, and compound titles. A nested phase sub-skill — never an episode owner; the garden dispatcher owns START, cascade, and review.

• garden-densify

  Gardening phase: build the missing/better edges so the graph becomes well-connected and cascade can self-heal — materialize prose wikilinks into real edges, close gaps in the why-chain, and add genuine missing dependencies (favoring cascade-HARD `requires`). Nested phase; garden dispatcher owns the

• garden-domains

  Gardening phase: curate the domain vocabulary as a finite shared resource — consolidate near-synonyms and underweight domains, assign untagged docs conservatively, validate claimed memberships, and normalize convention drift. Replaces the deprecated ≥2-scopes test. Nested phase; garden dispatcher ow

• garden-hierarchy

  Gardening phase: tree structure — orphan homes, grouping signposts, scope anchors, re-scoping overgrown branches, and placement refinement. Absorbs curate-grouping plus garden tag-curation Part A. Reports signposts whose membership changed for the dispatcher to summarize once at episode close. Neste

• garden-integrity

  Gardening phase: mechanical structural repair — broken requires/belongs_to refs, missing required fields, id != filename, deprecated without superseded_by. Wraps ldoc validate and applies fixes (vs validate which only reports). Nested phase; garden dispatcher owns the episode.

• garden-refine

  Gardening phase: sampling-based surface-quality pass — truncated titles/labels, summary quality, body-shape consistency, and schema normalization (no alias JSON). Catches sporadic agentic formatting drift. Nested phase; garden dispatcher owns the episode.

• garden-summarize

  Gardening phase: given a descendant-bearing doc, write its body as an orientation guide and set a tight frontmatter summary. Synthesize, do not concatenate. Invoked by garden-hierarchy, cascade-check, and the garden dispatcher — never an episode owner when nested. May also be invoked standalone to r

• garden

  Periodic maintenance: thin dispatcher over garden-* phase sub-skills (atomicity, structure, form). Owns the episode — one START, routing, one cascade over the union of changes, one review. Use for working the open flags (`ldoc flag list`), decomposition, drift repair, orphan homes, duplicate cleanup

• identify-key-concepts

  Read an input — a request, a normalized reference, or a proposed doc revision — and emit a typed list of the durable concepts it asserts. Owns the single shared concept-extraction protocol: how to read an input and emit the Concept/Type/Asserts record shape. The type taxonomy it assigns from lives i

• ingest-reference

  Bring external material into the live_docs store without creating non-atomic blobs. Accepts a file path, pasted text, a chat-session summary, a URL's fetched content, or any other raw input. The skill creates a raw clipping doc, a normalized summary doc, then — the critical step — decomposes the mat

• map-concepts-to-docs

  Given an extracted concept list, query the live_docs KB and map each concept to existing docs, recording the relationship: compatible, partial-supersession, full-supersession, or conflict-unresolved. Owns the shared survey + dedup-and-conflict scan that apply-to-docs, ingest-reference, and revise-do

• reconcile-changes

  Catch the docs up to reality. After a working session where decisions were made and changes were built but never written down, reconcile-changes ingests those already-real decisions into the live_docs store as born-`living` docs. Unlike apply-to-docs it does NOT pause before implementing — the chang

• reference

  Canonical store-agnostic reference for working in ANY live_docs store: the ldoc CLI command surface, the frontmatter schema (field order, required fields, the three descriptors), the type/status enums and the facets, the typed edge model and cascade semantics, scope vs domain, and the all-metadata c

• reindex

  Rebuild the generated artifacts in docs/.index/ — the reverse-dependency map, hierarchy rollups, and orphan list. These files are DERIVED caches; they are never hand-edited and can always be regenerated from the flat docs/ store. Use after any bulk doc creation or deletion, after the garden skill sp

• revise-doc

  Edit, update, revise, or amend an existing doc in the live_docs store with the same disciplined care that ingest-reference applies to new material. Performs a dedup/conflict scan before writing, classifies the change as substantive or provenance-only, appends a history entry and runs cascade-check o

• shard-clipping

  Gate 1.5 pre-pass between promote (gate 1) and ingest-reference (gate 2), normally invoked by ingest-reference as its first sub-step (it can also be run standalone). Estimates how many atomic concepts a promoted raw clipping would decompose into. VOLUME is the only trigger: if the clipping fits one

• sync-realization

  Keep the store's `realization` facet in step with the implementation, in both directions. Walks every realizable doc in scope (goal, use-case, requirement, decision, component), checks the code roots for the thing each doc claims, and sets `realization`, `realization_refs`, and `realization_verified

• synthesize-doc-changes

  Given a complete plan — the impact set and/or conflict map plus the concept list — batch-synthesize the coherent new state for every affected doc and write it via ldoc. Deprecate fully-superseded docs (Correction section + superseded_by), revise partially-affected docs, and create new docs for unmat

• validate

  Read-only mechanical check of the entire docs/ store. Verifies every doc has required fields with valid enum values, that labels are trimmed and unique, that all requires/belongs_to/relates/provenance references resolve, that `belongs_to` is acyclic, that deprecated docs have a superseded_by edge, t

• lexicon