recipes
CommandWrite (or rewrite) the meta-recipes a local model follows to plan from this memory, then lint them
Compile this project's instructions (CLAUDE.md, AGENTS.md, auto-memory, agents, skills) into the director's memory of linked atomic statements
> /plugin marketplace add EvolvingAgentsLabs/evolving-agents> /plugin install director@evolvingagentslabs
description: Compile this project's instructions (CLAUDE.md, AGENTS.md, auto-memory, agents, skills) into the director's memory of linked atomic statements argument-hint: "[extra files or folders to include]" allowed-tools: Bash(python3 *), Bash(git *), Read, Glob
Compile this project's instructions into the director's memory. From the next session on, the director's SessionStart hook has every plan walk it.
1. Find the sources, and read nothing the user did not agree to:
`.director`);
`~/.claude/projects/<the project's absolute path with every non-alphanumeric character replaced by "-">/memory`;
2. Show the user the list and tell them: the compile sends these files to Claude (Opus by default), takes about 15 minutes and costs about US$5 for ~60 files; the memory is written to `.director/memory/`. Ask before going on. 3. If this is a git repository and `.director/` is not ignored, add `.director/` to `.git/info/exclude` (local, never committed) unless the user says the memory should be shared through the repository. 4. Run, in the background, from the project root:
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m director.compile \
--claude-md <each CLAUDE.md / AGENTS.md> --memory-dir <the auto-memory dir, if any> --extra <each extra> \
--out .director/memory --config .director/server.json --workdir .5. Report what it printed: pages, statements, cost, and the lint problems (if any, show them; they are the compile's, and `memory_lint` re-checks them). Tell the user the walk starts with their next session, and that `/director:reflect` after a task turns a correction into a gated edit of this memory. Where Claude Code supports plugin UI, the status line names the memory from then on, and a band above the prompt shows each proposed lesson for them to accept or reject. `/director:recipes` writes the recipes a local model follows to plan from it.
The director remembers how your team works — and makes every agent session work that way. Your decisions, conventions and hard-won methods become a small memory of linked rules.
Write (or rewrite) the meta-recipes a local model follows to plan from this memory, then lint them
Turn the user's corrections and decisions, and the methods a task had to find, since the last reflection into gated edits of the…
You are the **Anti-Pattern Czar**, an expert at identifying and fixing error handling anti-patterns.
Score how well organized your memory palace is, then run a guided repair session — one decision at a time.
Score how well organized your memory palace is, then run a guided repair session — one decision at a time.
Convert a Claude Code plan file into beads epic + tasks for cross-session tracking.