What MetaGPT's 'standard operating procedure' framing buys over generic agent teams

Attempt it

Generic agent teams emit free-form conversation between roles and hope the structure emerges. MetaGPT enforces the structure: each role takes a typed input artefact and produces a typed output artefact (PRD document, design diagram, code module). Downstream roles consume the typed artefact, not a chat transcript.

The win is that role bleed and meandering conversations collapse, because the only thing that crosses role boundaries is a structured document. The engineer cannot 'rewrite the PRD' in conversation because the PRD already exists as a sealed artefact. The trade is rigidity: MetaGPT works well for SWE-shaped pipelines where the artefact sequence is well-known and badly for open-ended workflows where the right next step is not knowable in advance. It is a domain framework masquerading as a general one.

Your answer

Generic multi-agent frameworks (CrewAI, AutoGen, basic LangGraph crews) let roles **talk to each other in free-form text**. The product manager agent writes prose; the engineer agent reads the prose and writes more prose; the QA agent reads all of it and produces tests. The structure is hoped-for, not enforced. **MetaGPT casts the team as a standard operating procedure**. Each role consumes a **typed input artefact** and produces a **typed output artefact**: - Product manager produces a **PRD document** (structured: features, requirements, acceptance criteria). - Architect reads the PRD and produces a **design document** (structured: modules, data flow, interfaces). - Engineer reads the design and produces **code modules**. - QA reads code plus design and produces **tests**. The only thing crossing role boundaries is a typed artefact. Roles do not chat; they hand over sealed documents. **The win**: role bleed collapses. The engineer cannot rewrite the PRD in conversation because the PRD already exists as a sealed artefact. The QA cannot influence the design mid-stream because it consumes the design as input, not as collaboration. **The trade**: rigidity. The artefact sequence is fixed at framework-design time. MetaGPT works beautifully for SWE-shaped pipelines (where the artefact sequence is well-known) and badly for open-ended work (research, exploration, undefined-scope) where the right next step is not knowable in advance.

**MetaGPT replaces free-form inter-agent chat with typed artefact handoff.** That single structural choice is the whole value proposition - and the whole limitation. In a generic crew, messages between agents are conversational. The PM writes a paragraph; the engineer reads the paragraph; the QA reads everything. Failure modes pile up: the engineer reinterprets requirements mid-coding, the QA writes tests based on the engineer's interpretation, role bleed makes the supervisor sound like the engineer in traces. MetaGPT enforces structure: each role is a function from one typed artefact to another. - **PM**: `(user_request) -> PRD`. Structured: features, requirements, acceptance criteria. - **Architect**: `(PRD) -> Design`. Modules, interfaces, data flow. - **Engineer**: `(Design) -> CodeModules`. Conforms to design interfaces. - **QA**: `(Design, Code) -> Tests`. Verifies against acceptance criteria. **Wins**: - **No role bleed**: engineer never sees the PRD's prose, only the design. - **Versioned artefacts**: re-run engineer + QA against a stable design without redoing PM + architect. - **Queryable trace**: four documents to inspect, not a 50-turn chat log. - **Concurrent collaboration**: roles work in parallel once inputs exist. **Cost**: the artefact sequence is hardcoded. MetaGPT's framework is built around the SWE SOP (PM, architect, engineer, QA). For open-ended work where the right next step is not knowable (research, exploration), the rigid sequence does not fit. MetaGPT is a **domain framework** for SWE teams, not a general crew framework.

Quick reference

TL;DR

MetaGPT enforces typed artefacts between roles, so the only thing crossing role boundaries is a structured document, not a chat transcript.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Imagine two ways to run a small software shop. In the first way, the product person, the designer, and the engineer all talk in a group chat, hoping the right details make it to the right person. In the second way, the product person writes a one-page brief, hands it over as a sealed envelope, the designer reads only the brief and produces a design document, and the engineer reads only the design and writes code. The second way is MetaGPT. The sealed envelope is the typed artefact. The trade-off is that the envelopes must be designed up front, so the second way only works when the work has a known shape - it is great for building a small app, much worse for figuring out what to build in the first place.

Key concepts

Multi-Agent Systems

Detailed answer & concept explanation

~8 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Sign in for 5 free unlocks/day or go Pro for unlimited. See Pro pricing.

Quick scan · 2–4 min

Everything important, quickly.

5 min: typed artefacts vs free-form chat + SOP framing + what role bleed and drift lose + rigidity cost + when MetaGPT fits (SWE) and when it does not (research) + getting most wins without MetaGPT.

Real-world examples

Real products, models, and research that use this idea.

MetaGPT's original paper (2023) demonstrated a 'one-line requirement to working repo' pipeline producing PRD, design, code, and tests as separate documents.
Microsoft's GitHub Copilot Workspace echoes the artefact pattern: it produces a spec, a plan, then code, with each as a discrete reviewable artefact.
Devin (Cognition) uses a planner that produces a structured task list before the executor writes code, mirroring MetaGPT's artefact-first discipline.
Production CrewAI deployments that need MetaGPT's structural wins typically layer Pydantic output_pydantic on every task, achieving artefact handoff without committing to MetaGPT's framework.
AutoGen 0.4 Magentic-One similarly emits structured plans and progress artefacts rather than free-form chat between team members.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QHow would you get MetaGPT's structural wins without committing to MetaGPT?

Sign in or go Pro to see the approach for this follow-up.

QWhat goes wrong when MetaGPT is applied to a non-SWE workflow?

Sign in or go Pro to see the approach for this follow-up.

QWhy does versioned artefact handoff make debugging easier than reading chat logs?

Sign in or go Pro to see the approach for this follow-up.

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Picking MetaGPT for open-ended workflows. The SOP framing is the win for fixed pipelines and the cost for everything else; it does not fit research, exploration, or undefined-scope work.

Sign in or go Pro to see all red flags and common mistakes. See Pro pricing.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.