Stats
Actions
Tags
From vault
This skill should be used when the user asks about "living documents", "living doc", "update MOC", "MOC maintenance", "how do MOCs work", "keep docs updated", "project brief", or needs to understand or apply the living document pattern.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vault:living-doc-kThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Knowledge skill** — Living document patterns: MOCs, project briefs, what makes docs "living", update signals.
Knowledge skill — Living document patterns: MOCs, project briefs, what makes docs "living", update signals.
Living docs evolve as understanding shifts. They synthesize — not just list. Two types exist in the vault: MOCs and Project Briefs.
Purpose: Synthesize an area's knowledge into navigable structure.
Not an index. A MOC tells you what you know about a topic and how it fits together.
---
type: moc
level: 0
created: YYYY-MM-DD
---
# Area Name
{Thesis paragraph: current understanding. Updated when understanding shifts.}
## Section Name
- [[note-name]] — what it covers, why it matters
- [[other-note]] — key insight from this note
## Another Section
- [[yet-another]] — brief annotation
## Open Questions
- What you don't know yet
- Gaps in understanding
---
Sources cross-linked from: [[00_related-area]], [[00_another-area]]
What makes it living:
L0 vs L1:
00_area-name.md (L0) — one per area, always exists, synthesizes broadly01_subtopic.md (L1) — only when 15+ notes cluster. L0 references L1; L1 goes deep.Purpose: Track a project's state, resources, decisions, and next actions.
---
type: project
status: active
created: YYYY-MM-DD
goal: "One-sentence objective"
deadline: YYYY-MM-DD
---
# Project Name
{Current status paragraph: what's done, what's in progress, what's blocked.}
## Resources
- [[00_area-moc]] — area knowledge feeding this project
- [[resource-note]] — specific reference material
## Backlog
- [ ] Concrete task
- [ ] Another task
## Decisions
- Decision made and why
- Another decision with rationale
What makes it living:
| Situation | Action |
|---|---|
| Filing a new note | Update parent MOC — add link with annotation |
| Understanding shifted | Update MOC thesis paragraph |
| New notes cluster on subtopic (15+) | Create L1 sub-MOC |
| Starting a new project | Create project brief |
| Project milestone hit | Update project brief status + decisions |
| Area has no MOC | Create L0 MOC |
When invoked with an area name or file path:
Read the MOC or project brief.
List all notes. Read frontmatter and first few paragraphs of each.
Present specific edits:
## Proposed Updates to 00_ai-dev-ecosystem.md
1. ADD to "Agent Architecture" section:
- [[2025-02-05_agent-note]] — multi-agent orchestration patterns
2. UPDATE thesis paragraph:
Add sentence about multi-agent patterns emerging as dominant architecture
3. RESOLVE Open Question:
"How does memory continuity work?" → answered in [[2025-02-01_memory-patterns]]
Apply edits. Only modify the living doc — never the notes themselves.
npx claudepluginhub jsai23/claude-tooling --plugin vaultDesigns and runs a documentation system for a team or product: planning what to document, choosing tools, organizing existing docs, fixing stale docs, and establishing maintenance cadence.
Organizes an Obsidian vault: adds documents with auto-categorization, restructures misplaced files, processes meeting notes, and runs health checks.
Creates, opens, and manages project workspaces in LiveDocs for cross-session memory, long-term tracking like diets or investments, and saving key outputs.