PromptFork

Orchestrate a multi-agent team to ship one task

Turn a goal into a coordinated planner→worker→critic agent workflow with clear handoffs and a stop condition.

Open in Studio
Prompt
Act as an agent-systems architect. Design a multi-agent workflow to accomplish: [GOAL].

Define the smallest team that gets it done reliably. For each agent specify: role, the single responsibility it owns, its system prompt (2–4 sentences), its allowed tools, and its input/output contract (what it receives, what it must return).

Then define the orchestration:
- The exact sequence and handoffs (who calls whom, with what).
- A planner that decomposes the goal and a critic/verifier that checks work before it's accepted.
- The stop condition and the max-iterations guard (no infinite loops).
- How state is passed between agents and what gets persisted.
- Failure handling: what happens when a worker fails or the critic rejects.

Return it as a labeled spec plus a simple diagram (as an ordered list) of the message flow. Favor the fewest agents that work — call out where a single agent would actually be better.
Source
promptfork seed
License
CC-BY-4.0
Published
6/23/2026

More prompts you might like

Zapier multi-step Zap to route and enrich new leads

A step-by-step Zap blueprint: trigger, filter, enrich, branch by score, and notify the right channel.

New

Notion task database with smart formulas, automations, and role-based views

Design a Notion task system with genuinely useful formulas (overdue countdown, auto-archive logic, conditional formatting), native automations, and filtered views for different team roles.

New

Make.com scenario blueprint with error handling, rate limits, and operations budgeting

Blueprint a Make.com scenario with exact module configs, exponential backoff retry logic, data transformation pitfalls to avoid, and specific operations-saving patterns like early-filter routing.

New
Editor’s pickAutomation & AgentsSeed

Bulletproof tool-calling JSON schema for AI agents

Design strict, self-validating tool schemas with confidence calibration, discriminated unions, and chain-ready contracts — so your agent calls tools reliably instead of hallucinating arguments.

New

Write a brand-aligned support-agent system prompt with escalation rules

Produces a complete system prompt that defines a support agent's persona, voice, knowledge boundaries, and exact escalation rules — brand-aligned and safe to ship, not a generic 'be helpful'.

#customer-support#system-prompt
New

Design a support-ticket triage agent that classifies and prioritizes

Produces a system prompt and routing logic that classifies incoming tickets by intent, urgency, and language — then routes to the right queue with a priority and confidence score, so nothing critical sits in a generic inbox.

#customer-support#triage
New