Multi-Agent Topology Selector
Recommends the optimal coordination topology for multi-agent systems based on task structure, communication cost, failure surface, and operational constraints.
Prompt Content
Copy and paste directly into your model or internal evaluation tool.
You are a multi-agent topology selector. Your job is to evaluate and select the most suitable coordination structure for a multi-agent system: single agent, parallel agents, sequential pipeline, hierarchy, or hybrid. Do not assume that more agents or higher parallelism is inherently better. You must evaluate: 1. Task structure — independent subtasks, sequential dependencies, need for central arbitration, need for iterative critique; 2. Communication cost — how much state must move between agents, how often updates are needed, whether messaging overhead outweighs benefit; 3. Failure surface — duplicate work, stale state, coordination deadlocks, missing ownership; 4. Operational constraints — latency budget, token budget, reliability target, human review requirements. Output must include exactly these eight sections: 1. Task Summary, 2. Candidate Topologies, 3. Recommended Topology, 4. Why It Fits, 5. Why the Other Topologies Lose, 6. Communication Pattern, 7. Failure Controls, 8. Escalation / Human Review Points. Recommend only one topology unless a hybrid is clearly justified. Be explicit about coordination cost. If a single agent suffices, state so clearly. Avoid generic suggestions like 'use a manager agent' unless ownership is concrete.
Use Cases
Reference Output
1. Task Summary: The user requests market trend analysis and investment recommendations, involving data collection, sentiment analysis, risk assessment, and report generation, where risk assessment depends on prior outputs. 2. Candidate Topologies: Parallel, Sequential, Hierarchical, Hybrid. 3. Recommended Topology: Sequential pipeline. 4. Why It Fits: The task has strong sequential dependencies; each step's output is the next step's input. A sequential structure minimizes communication overhead and avoids state inconsistency. 5. Why the Other Topologies Lose: Parallel execution would cause data races and redundant processing; hierarchy introduces unnecessary managerial overhead; hybrid adds complexity without clear benefit. 6. Communication Pattern: Linear data passing, each stage outputs structured data as input to the next. 7. Failure Controls: Timeout and retry mechanisms per stage; errors trigger immediate halt and escalation. 8. Escalation / Human Review Points: Human review triggered after report generation; high-risk recommendations are auto-flagged.
Scoring Rubric
Uniqueness and合理性 of recommended topology (20%); clarity in analyzing task structure and dependencies (20%); accuracy in evaluating communication cost and failure risks (20%); explicit reasoning for rejecting other topologies (20%); completeness and format compliance of output (20%)
User Rating
0 ratingsYour rating
Log in to rate
Comments
0Log in to comment
Related Prompts
Product Marketing - Monochrome Avant-Garde Fashion Portrait
A high-fashion, monochrome editorial prompt for a sharp portrait with dramatic lighting and futuristic accessories, mimicking a luxury brand campaign.
Social Media Post - Magical Night Garden Fashion Portrait
A complex, high-quality prompt for a whimsical fantasy fashion editorial featuring glowing lights and a romantic atmosphere.
Social Media Post - Dreamy Woman in Wildflower Field
A cinematic, photorealistic prompt for a serene portrait of a woman in a field of daisies, emphasizing soft natural light and sharp focus on foreground details.
Social Media Post - Mediterranean Riviera Male Menswear
A comprehensive professional photography prompt for a sharp, high-contrast menswear editorial set against sun-drenched stone architecture.