agent-designerlisted

# Agent Designer Skill Design robust multi-agent systems: define agent roles, choose an architecture pattern, design tool interfaces, add safety guardrails, and evaluate performance. ## Workflow 1. **Define roles** -- Identify distinct agent responsibilities. Each agent should have a single clear purpose. 2. **Choose architecture** -- Select the orchestration pattern that fits the problem. See [architecture-patterns.md](architecture-patterns.md). 3. **Design tools** -- Define the tool schemas agents will use. See [tool-design.md](tool-design.md). 4. **Add guardrails** -- Layer in validation, human-in-the-loop gates, and failure handling. See [guardrails.md](guardrails.md). 5. **Evaluate** -- Measure task completion, quality, cost, and latency. Iterate on weak points. ## Agent Role Definition Each agent should be specified with: ``` Agent: code-reviewer Purpose: Review code changes for bugs, security issues, and style violations Inputs: diff (string), file_context (string[]), review_guidelines (string) Outputs: findings (Finding[]), verdict (PASS | FAIL), summary (string) Tools: read_file, grep_codebase, run_linter Constraints: read-only access, no code modification, max 5 tool calls per file ``` Keep agent scope narrow. An agent that "does everything" is just a prompt with no structure. If an agent needs more than 5-7 tools, it is probably two agents. ## Architecture Selection Guide | Agents | Complexity | Pattern | Example | |--------|