Agents

Agents (brewers) are specialized roles defined in markdown files with frontmatter metadata. Each agent has its own model, toolset, and system prompt. Brewcode ships 5 agents (4 public + 1 internal helper) — specialists only, for building skills, agents, hooks, and shell scripts.

Generic roles (developer, tester, reviewer, architect) are no longer shipped: every project generates its own agents into .claude/agents/ via /brewcode:teams-setup or /brewcode:agents, tuned to that project’s stack. Skills that need a reviewer or an implementer pick the project’s agent from .claude/agents/, falling back to general-purpose.

Summary table

Purpose column = the agent’s own description frontmatter, verbatim. That string is what Claude matches against when auto-selecting an agent.

#	Agent	Model	Write tools	Description (verbatim)
1	skill-creator	inherit	Read, Write, Edit, Bash	Creates and improves Claude Code skills. Triggers: create skill, improve skill, fix activation.
2	agent-creator	inherit	Read, Write, Edit, Bash	Creates and improves Claude Code agents. Triggers: create agent, improve agent, scaffold agent.
3	hook-creator	inherit	Read, Write, Edit, Bash	Creates and debugs Claude Code hooks. Triggers: create hook, PreToolUse hook, debug hook.
4	bash-expert	inherit	Read, Write, Edit, Bash	Creates sh/bash scripts for Mac/Linux. Triggers: create script, bash script, shell script.
5	bc-rules-organizer	haiku	Read, Write, Edit, Bash	Internal. Spawned only by /brewcode:rules. No direct/auto use.

model: inherit means the agent runs on whatever model the session runs on — no per-agent pin. Only the internal bc-rules-organizer (haiku) is pinned.

Scope guard — shared by all 4 public agents

Every public brewcode agent sizes the task before starting. One bounded unit = one deliverable, roughly 5 files, roughly 10 steps. Anything larger is refused up front.

Situation	What the agent does
Brief fits one bounded unit	Starts immediately
Brief exceeds ~5 files / ~10 steps, or bundles several independent deliverables	Stops before starting, returns a split proposal: 2-N bounded subtasks, each with scope and a suggested owner
Scope grows mid-flight	Stops at the next clean boundary, reports done / remaining / how to split
Brief is missing GOAL, SCOPE, CONTEXT, CONSUMER or acceptance	States the assumption explicitly in the report, or asks once — never invents scope

Agents deliver for the CONSUMER, not the literal wording: the result must be usable as-is by whoever picks it up next, with the whole briefed scope covered.

Models

Model	Agents	Meaning
inherit	skill-creator, agent-creator, hook-creator, bash-expert	Runs on the session’s model — you control the tier
haiku	bc-rules-organizer	Pinned: cheap file reorganization