crew-hire
Decides how to add a capability to the agent team (role addendum, skill, or new agent) and adds it after the user's one-line OK. Use when the lead pasted the same long instructions into several briefs
SKILL.mdskills/crew-hire/SKILL.md
GitHubcrew-hire
Run by the lead. $CREW is ~/.claude/agent-crew. The lead proposes; the user approves in
one line; only then is anything written.
When to hire
Hire only on evidence, never on a hunch:
- the lead pasted the same 300+ words of instructions into 3 or more briefs; or
- a class of failure keeps slipping through (the reviewer or CI finds the same kind of bug again).
State the evidence in the proposal (which briefs, which failures).
The ladder: use the cheapest rung that works
- Role addendum: a file
.claude/team/roles/<agent>.mdwith extra rules for an agent that already exists (every agent reads its own addendum). Best for project-specific rules. - Skill: a
SKILL.mdfor a procedure that several agents or sessions repeat. Put it in.claude/skills/<name>/SKILL.md(project) or~/.claude/skills/(every project). - New agent: only if the job needs its own tools, model or isolation that no existing agent
has. First look in
$CREW/catalog/(tester, ui-reviewer, security-reviewer, docs-writer, perf-profiler); copy it unchanged instead of writing a new one.
Limits
- At most 7 active agents. Over the limit: retire one first (
crew-retire). - One-line
description, written as when to use it. - A new agent starts as
trialinroster.mdand is judged after 3 uses (kept or retired).
Steps
- Write the proposal to the user in at most 6 lines: what, which rung, the evidence, the model and effort, the retire criterion. Wait for a one-line OK.
- Do it:
- addendum or skill: write the file (addenda are under
.claude/team/, which the lead may write; a project skill is acoderjob); - catalog agent: the
codercopies$CREW/catalog/<name>.mdunchanged to.claude/agents/<name>.md(give it the path); the lead does not write there; - new agent: the
coderwrites.claude/agents/<name>.mdfrom your brief (frontmatter: name, one-line description, tools, model, effort).
- addendum or skill: write the file (addenda are under
- Add the row to
roster.md(why, evidence, statustrial, uses 0, retire criterion) and a row torouting.mdif the agent has its own job type. - Run
check-team.ps1 -Project .. Updatestate.mdIndex if useful.