auditing-upstream-drif…
Use when checking if beads-superpowers is outdated, before a plugin release, or when auditing for missing capabilities — covers upstream drift, test execution,…
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
$ npx -y skills add DollarDill/beads-superpowers --skill memory-curator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memory-curatorContext preview
The summary Claude sees to decide when to auto-load this skill.
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
name: memory-curator description: Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
Turn a session's raw `bd remember` notes into deduplicated, consolidated, well-structured memories — and prune the pile — using `bd` over text already in context. No runtime, no embeddings.
**Announce at start:** "I'm using the memory-curator skill to consolidate and structure the memory store."
Two classes; **procedural** memory (how-to / workflow) lives in the **skills**, never the memory store.
**The `@type` is the routing decision.** Classify once; the type deterministically sets store, injection, and lifecycle.
| `@type` | store | injected at session start? | lifecycle | |---|---|---|---| | `semantic:lesson` | memory | yes (salience≥4) | durable; consolidate near-dups | | `semantic:root-cause` | memory | yes (salience≥4) | durable; consolidate | | `semantic:pattern` | memory | yes (salience≥4) | durable; consolidate | | `semantic:correction` | memory | yes | durable (supersedes a wrong memory) | | `semantic:research` | **deferred knowledge-bead** | **no** | deferred bead; pointer to a research doc (`metadata.doc`); `bd supersede` on replacement | | `semantic:design` | **deferred knowledge-bead** | **no** | deferred bead; pointer to an ADR/spec (`metadata.doc`); `bd supersede` on replacement | | `semantic:decision` | **deferred knowledge-bead** | **no** | deferred bead; pointer to an ADR (`metadata.doc`); `bd supersede` on replacement | | `episodic:continuation` | memory | latest only | supersede on next | | `episodic:done` / `cleanup` / `review` | memory → retire | no | consolidate into a semantic fact, then drop; age-out (>30d) safety net |
**Crisp routing definitions (the boundary that keeps determinism honest):**
Map a non-canonical prefix to the nearest canonical subtype — e.g. `stress-test`/`plan-stress-test`→`design`, `bug`→`root-cause`, `sdd`→`lesson`, `upstream`→`research`, `docs`→`pattern`. If none fits, ask — don't invent. If an extracted "memory" is really procedural, flag it for a skill — don't store it.
Every memory keeps its existing key and carries one greppable header line:
@type=semantic:lesson @created=2026-06-28 @salience=4 @refs=<bead-id>,<memory-key> @tags=memory,curation <self-contained fact body>
`@refs` — related bead IDs / memory keys. `@tags` — lexical filter.
The class makes the prune signal greppable (`bd memories | grep '@type=episodic:'`); `@salience`/`@tags` filter recall.
Reference-class memories (`research`/`design`/`decision`) live as **deferred knowledge-beads**, not in `memory.` — a deferred bead is never auto-injected at session start, so pointers stay out of every session's context but keep persistence + Dolt sync.
printf '%s' "<distilled summary: what this note establishes>" | \
bd create "<one-line summary>" -t <research|design|decision> -l kb,<topic-labels> \
--defer 2099-01-01 --metadata "$(jq -nc --arg d "<doc-path>" '{doc:$d}')" --body-file - --silentOne pass. Input: the session (i
Superpowers & Beads task memory for AI coding agents - supports Claude Code, Codex, OpenCode, Cursor, Gemini CLI, GitHub Copilot CLI, Kimi Code, Antigravity, Factory Droid, and Pi.
Use when checking if beads-superpowers is outdated, before a plugin release, or when auditing for missing capabilities — covers upstream drift, test execution,…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…