From brewcode
Creates, improves, reviews, and reports on Claude Code subagents from a single free-form prompt. Handles batch operations and status checks across agent files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brewcode:agents <free-form prompt: what to do with agents><free-form prompt: what to do with agents>opusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Agent Management:** create, improve, review, and report on Claude Code agents from one free-form prompt.
Agent Management: create, improve, review, and report on Claude Code agents from one free-form prompt.
| Const | Value |
|---|---|
| ARTIFACT | agents |
| SPECIALIST | brewcode:agent-creator |
| LIST_CMD | Glob *.md over .claude/agents/, ~/.claude/agents/, brewcode/agents/ |
Treat the entire user input ($ARGUMENTS) as ONE free-form natural-language prompt.
There is NO keyword grammar and NO argument parser — argument-hint is only a loose example.
Classify the prompt + recent conversation context into exactly ONE mode:
| Mode | Chosen when prompt signals |
|---|---|
status | "статус", "что есть", "состояние", health / overview / "show me" (DEFAULT for any "show me" intent) |
list | explicit "список" / "list" / "перечисли" ONLY |
create | "создай" / "create" / "new" / "добавь" / "scaffold" |
improve | "улучши" / "improve" / "refactor" / "fix" / "почини", OR a bare existing name/path |
review | "ревью" / "review" / "validate" / "проверь корректность" |
Batch flag: plural form, "все" / "all", or multiple names/paths -> fan-out (one specialist spawn per item).
Then ANNOUNCE the chosen mode (MANDATORY, before any work):
Mode: <mode> (agents) — chosen because <evidence quoted from the prompt>
Proceed to Step 4.
Ask ONE AskUserQuestion. Question: What do you want to do with agents?
Options (in this order):
Status (agents) — (Recommended) rich status of this artifactStatus (all: agents+rules+skills) — cross-link: run the collector for all threeCreate new agentsImprove existing agentsReview agentsList (plain)Nothing / cancelAfter the choice:
Nothing / cancel -> stop.create or improve -> ask ONE follow-up AskUserQuestion for the target/description
plus the artifact-specific params (see "Artifact-specific params" below).status -> go to Step 5.status (all) -> go to Step 5, running the collector for agents + rules + skills together.list -> run LIST_CMD, print the plain inventory it produces, then STOP (no status assembly).create -> gather minimal params (Step 3 / artifact-specific), spawn SPECIALIST via Task.
Batch -> spawn one SPECIALIST per item, ALL in ONE message (parallel).improve -> resolve target(s), spawn SPECIALIST via Task per target (parallel for batch).review -> spawn brewcode:reviewer (two-phase: review -> double-check findings -> report).Delegate collection to ONE Explore/Bash subagent, then assemble a rich status (never a bare list):
.claude/) / global (~/.claude/) — counts + names + load path._SKILL.md / _<name>.md), model.Bash in tools: (macOS search rule);
skills with weak description triggers; rules duplicated in CLAUDE.md.For the Status (all) menu option: run the SAME collector for agents + rules + skills together.
list)# agents [<mode>]
## Detection
| Input | <prompt or "(none -> menu)"> |
| Mode | <mode> |
| Reason | <why this mode> |
| Targets| <names/paths> |
## Result
(create/improve/review: each output path + specialist agent + scope/model)
## Status
(status mode: full table from Step 5; else short "what changed" for touched artifacts)
## Next Steps
(recommendations; ALWAYS remind to run /docs for any created/changed artifact)
For status mode the report is the Step 5 status table.
For create: ONE AskUserQuestion batch — (Q1) scope: Project .claude/agents/ /
Global ~/.claude/agents/ / Plugin brewcode/agents/; (Q2) model: sonnet (Recommended) /
opus-or-fable / haiku / inherit (omit model: field); (Q3) update CLAUDE.md agents table? yes/no.
Frontmatter description budget: <= 100 chars, single line, role + 2-3 triggers, EN only.
Spawn SPECIALIST (brewcode:agent-creator) with the description, scope+path, model.
After creation, if user approved, update the CLAUDE.md agents table via Edit (add/replace row).
For improve: resolve agent by name/path across the 3 scopes; ONE AskUserQuestion —
(Q1) focus: triggers / system-prompt / both (Recommended) / full review; (Q2) update CLAUDE.md? yes/no.
Spawn SPECIALIST to improve, then optional CLAUDE.md row update.
npx claudepluginhub kochetkov-ma/claude-brewcode --plugin brewcodeCreate custom agents for Claude Code including YAML frontmatter, system prompts, tool restrictions, and discovery optimization. Use when creating, building, or designing agents, or when asked about agent creation, subagent configuration, Task tool delegation, or agent best practices.
Guides creation of custom agents for Claude Code with specialized behaviors and tool access. Covers agent vs skill differences, file structure, and writing style.
Guides creation of autonomous agents for Claude Code plugins, covering Markdown file structure, YAML frontmatter (name, description, model, color, tools), system prompts, triggering examples, and best practices.