Agent Memory Kit

Multi-Agent Driven Development Kit

You talk to one agent. It runs the team.

*Formerly Claude Memory Kit — the plugin id memory-kit and every command name stay the same for compatibility.*

A plugin and a working method for Claude Code. The scarcest resource in agent-driven work is your attention, so the
method spends it in one place: you talk to one agent only — the main session. It holds the whole picture, so you
decide with one counterpart instead of five; it splits the work across the other sessions and their helpers. You
never talk to the windows or the helpers, never relay a brief, never read their raw output: decisions, evidence and
questions reach you from one place.

The team is two levels deep. You → main → three windows → their subagents.

- Main plans the round, writes the specs, rules on every finding, accepts work on evidence, and is the only one
  that acts outward (a push, a PR, a reply others will see).
- Three windows are full Claude Code sessions, not subagents — each opened by you in its own terminal, visible,
  with its own context, tools, hooks and memory, holding one task to its stop points.
- Each window calls its own subagents (a builder, a reviewer, a fact-gatherer), each with an explicit model.

Why sessions, and not only subagents. A subagent lives inside its caller's session: it works in its own context
and hands back a summary, it cannot ask you a question, and its permission prompts surface in the caller's terminal
(Claude Code docs, subagents). A window is a session you can watch and
that starts like any session — your CLAUDE.md, the hooks, this kit's memory and handoff — so it can hold a task
across several stops and reviews and still survive main being cleared. Claude Code's own
agent teams also run teammates as full sessions, but let…