← ClaudeAtlas

knowledgelisted

Understand the knowledge plugin's full taxonomy (docs, memory, context) and which of its 18 commands to reach for. Use this before invoking any $knowledge:* command — it covers the three write boundaries and their role rules, zero-config memory-store discovery, and pointers to each surface's complete write contract.
devgirishattri/agent-plugins · ★ 0 · Data & Documents · score 72
Install: claude install-skill devgirishattri/agent-plugins
# Knowledge `knowledge` is ONE cohesive, internally modular plugin for durable project knowledge: documentation workflows, context snapshots, and a native memory module for `.agents/memory/` — consolidation, promotion, deterministic search/recall, an explicit-link backlink graph, and a read-only cross-store doctor. Every command lives under this one plugin; there is no cross-plugin composition to reason about. All eighteen commands below are shipped. ## The taxonomy: three stores, one question each | Store | Nature | Owner | Where | |---|---|---|---| | **Docs** | durable, git-tracked | human-curated | `docs/` (incl. `docs/decisions/<snake_case>.md`) | | **Memory** | durable, gitignored | agent-maintained | `.agents/memory/` (a directory containing `MEMORY.md`) | | **Context** | ephemeral, expiring | plugin-owned | the inherited `SESSION_CONTEXT_HOME` store | Two questions place any item: (1) durable knowledge or working state? (2) human-curated or agent-maintained? A living doc or a decision record is Docs. A durable learning, how-to-work feedback, or agent-maintained fact is Memory. A session's working state or a resumable handoff is Context. Tracking items (TODO/ISSUES/tickets) are their own tracker, not a knowledge store — every autonomous surface here only ever holds *pointers* to them (a `type: reference` memory, a handoff's `tickets:` list), never a mirror; the one exception is `docs-create`'s explicitly user-invoked TODO/ISSUES maintenance (see "Non-goals" below).