recruitlisted

Recruit a new team member. Gap: $ARGUMENTS 1. Justify or drop. A new role is warranted only when it needs (a) a permission boundary no current role has, or (b) a judgment separated from execution. If only knowledge is missing, propose a skill instead (team-planner writes .claude/skills/<name>/SKILL.md after approval) and stop here. 2. One proposal, one AskUserQuestion call: role name `team-<slug>`, one-line description, when you will invoke it, permission preset (researcher: read-only + web · author: docs/ only · engineer: edit + bash + commits · judge: read-only, report ends with a verdict line), and the model with effort. Take them from the current roster without asking a budget question again: the sibling role of the same kind (judge → team-reviewer, engineer → team-implementer, author → team-planner, researcher → team-verifier) and name it explicitly. Offer "skill only" as the alternative and give your recommendation with the reason. 3. After approval: have team-planner write the role prompt to docs/roles/team-<slug>.md (identity, procedure, report format; under 60 lines; no permissions — the preset carries them) and add one line to docs/DECISIONS.md. 4. Run `node .claude/scripts/new-agent.mjs --flavor claude --dest .claude/agents --name team-<slug> --preset <preset> --description "<one line>" --body docs/roles/team-<slug>.md --like team-<sibling>` (`--model <model>:<effort>` instead of `--like` when the CEO named one). The script writes the new agent file and adds the n