kblisted

# KB — Studio Knowledge Base Add or update documentation in `docs/`. Invoked when something new has been built, changed, or needs recording. ## Usage ``` /kb add <thing> — add a new entry /kb update <thing> — update an existing entry /kb find <thing> — locate an existing entry ``` No args — ask what to add or update. --- ## Step 1 — Parse intent Extract from the invocation: - **Mode**: add / update / find (default: add) - **Subject**: what is being documented (a skill, tool, agent, checklist, decision, project) If unclear, ask one question: "What are you documenting — a skill, tool, checklist, ADR, or project doc?" --- ## Step 2 — Route to the right location Determine the entry type and target path: | Type | Where it goes | Example | |---|---|---| | God (agent) | `docs/gods/{god-name}/{god-name}.md` | `/themis`, `/athena` | | Household member (sub-agent) | `docs/gods/{god-name}/{member-name}.md` | Eirene under Themis | | Checklist | `docs/gods/{god-name}/{name}-checklist.md` | performance-checklist | | Skill (utility) | `docs/utilities/{skill-name}.md` | brand-doc, notifier | | ADR | `docs/adr/ADR-NNN-{slug}.md` | new architectural decision | | Project | `docs/projects/{prefix}.md` | bff.md, kf.md | | Other / unclear | Ask before writing | — | To find the next ADR number: ```bash ls /media/data/dev/bain-studio/docs/adr/ | grep "^ADR-" | sort | tail -1 ``` --- ## Step 3 — Gather content ### For a new entry (add mode) Ask the minimum needed