# Multi-Agent Role Designer

Designs a clean division of labor for a multi-agent system, defining each sub-agent's role, boundaries, and handoff protocol so agents don't overlap or conflict.

## Prompt

You are a multi-agent systems architect who designs clean, non-overlapping agent role structures.

Overall system goal: {{overall_system_goal}}
Workflow the agents need to cover: {{workflow_description}}
Orchestration approach (if known, e.g., a manager agent, sequential pipeline, or peer-to-peer): {{orchestration_approach}}

Do the following:
1. Propose a set of distinct sub-agents needed to cover the full workflow (aim for the minimum number that avoids overlap, typically 2-5). For each agent, define: its name/role, its single core responsibility, and what it should explicitly NOT do (to prevent scope overlap with other agents).
2. Define the handoff protocol between agents: what exact information or artifact gets passed from one agent to the next, and in what format.
3. Identify the orchestration pattern that fits best (a manager/coordinator agent directing others, a sequential pipeline, or independent agents working in parallel with a final merge step) and explain why, if not already specified.
4. Flag the single most likely coordination failure point in this design (e.g., where two agents might both think they own a task, or where a handoff could lose important context) and suggest a specific safeguard.

## Best for

Developers and technical founders building multi-agent systems (using tools like Claude Agent SDK, LangGraph, or CrewAI) who need a clear role architecture before writing orchestration code.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Describe the overall system goal and the full workflow it needs to accomplish.
- Mention your intended orchestration approach if you already have one in mind, or leave it open for a recommendation.
- Use the defined agent roles and 'explicitly NOT do' boundaries directly as scoping guidance when writing each agent's system prompt.
- Build the suggested safeguard into your orchestration logic to prevent the flagged coordination failure.

## Customization tips

- If you already have some agents built, describe them so the design only proposes new agents needed to fill genuine gaps.
- For cost-sensitive systems, ask for a version that minimizes the number of agents and LLM calls even if it means slightly broader individual roles.
- Request a visual description of the data flow between agents if you need to communicate the architecture to a team.

## Example input

Overall goal: Automatically research, write, and fact-check blog posts for a company blog. Workflow: Topic research, draft writing, fact verification, final formatting. Orchestration approach: Not yet decided.

## Example output

4 proposed agents: a Research Agent (gathers sources, does not write content), a Writer Agent (drafts the post from research, does not verify facts itself), a Fact-Checker Agent (verifies claims against sources, does not rewrite prose), and a Formatter Agent (applies final formatting, does not alter factual content), a defined handoff protocol specifying research gets passed as a structured source list, a recommendation for a sequential pipeline given the linear dependency between steps, and a flagged risk that the Fact-Checker might lose context on which claims came from which source, with a safeguard of requiring the Writer Agent to inline-tag claims with source references.