setup-memory · git:20261108.36c5a0f · 2026-11-08 · sha256 b1da7489ed682ae0

setup-memory git:20261108.36c5a0fA

Immutable. This exact content never changes and is served at /api/v1/blob/b1da7489ed682ae0.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2d73bxoeyqxg4qno/b1da7489ed682ae077bfbb678d7c3093790b90ed748a02d381fba64ea58d9a86.json

Then /plugin install setup-memory@markdownregistry-2d73bxoeyqxg4qno in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: setup-memory
description: Set up the shared project memory (docs/memory) in this repository and fill it from the code
argument-hint: "[notes about the project]"
disable-model-invocation: true
---

Use the team-workflow skill to set up the project memory of this repository.

1. If `docs/memory/INDEX.md` already exists, say so, run memcheck and stop.
2. Run `python3 <team-workflow skill folder>/scripts/init_memory.py --root <repository root>`.
3. Fill the memory from the real code, facts only:
   - `STATE.md`: version and the file that holds it, CI, known limits.
   - `PLAYBOOKS.md`: run the detected commands to confirm them; add the release steps.
   - `MAP.md`: every module or package in one line, grouped by area.
   - One card per area in `areas/`, from `areas/_TEMPLATE.md`: key files, contracts, tests,
     known traps.
   - `ACCESS.md`: what each folder holds and what must never be touched.
   In a large repository, split the reading of the areas between `doc-keeper` agents and
   check what they write.
4. Run memcheck and fix what it reports.
5. Report what was created, which commands you confirmed and what the user should check.

Notes from the user: $ARGUMENTS