store

name

store

description

This skill should be used when the user asks for maintenance or analysis across the WHOLE memory store — "audit the whole store", "store-wide retro", "check every project for X", "rebuild all the indexes", "run an agent inside the memory dir" — or invokes /tm:store <task>. Store-root scope (all projects plus global), unlike the project-scoped verbs. Dispatches a delegate agent inside the memory dir: read-then-report first, then every proposed write is confirm-gated per action.

tm — store-level maintenance (root scope)

Runs a delegated agent inside the memory dir, across all projects/* and global/ — for system/store-level work the project verbs don't cover. Read-then-report first; nothing is written without per-action confirmation.

Guard (run first, always)

Run ${CLAUDE_PLUGIN_ROOT}/scripts/tm-guard.sh "$PWD" and read its KEY=VALUE output. Require TM_STATUS=OK — otherwise stop and follow the repair flows in <MEMORY_DIR>/references/bootstrap.md. PROJECT_EXISTS is irrelevant here: this verb is store-scoped, not project-scoped. Keep MEMORY_DIR.

Steps

1. Pin the task. Restate the user's task in one line. If no task was given, ask for one (examples: index-drift audit across all projects, store-wide retro, orphaned-notes sweep, ## Projects table reconciliation).

2. Dispatch tm-archivist via the Task tool — report pass. Pass exactly:

   • mode: store
   • memory_dir: <MEMORY_DIR>
   • project_path: .
   • project_id: store
   • task: <the pinned task> It investigates the whole store and returns a numbered plan (≤10 lines), writing nothing.

3. Relay the plan and confirm via AskUserQuestion which actions to apply (multi-select: each action / all / none). Purely informational tasks end here — relay the findings and stop.

4. Apply pass. Re-dispatch tm-archivist with the same inputs plus apply: <confirmed numbers>. It executes exactly those actions. Relay its per-action report. The store git rule applies (own-repo commits itself; nested stores are committed by the parent repo's workflow).

Scope map (which verb owns what)

• Project scope: remember, consolidate, retro, reindex (default), link.
• Project + global read: recall.
• Store root: store (this verb), reindex global, init (setup/repair), status (reports both).
• Project → global: promote (the only path that writes global memory content).

Codex fallback

Not installed on Codex — run store-level maintenance from Claude Code. For a read-only look on Codex, follow the retrieval protocol in the store's AGENTS.md instead (never bulk-load the store).