How it works

Crew turns a request into one finished, practical page by splitting the work the way a small team would.

Who does what

1. The lead reads the job, writes down what it has to assume, splits the page into 3 or 4 parts, gives each part to a specialist with a clear brief, and sets the checks the page must pass.
2. The specialists write their parts at the same time. Each one sees the whole outline so the parts do not overlap.
3. The reviewer reads every part against the lead's checks, sends up to two parts back with specific notes, and lists any places where parts disagree.
4. The editor assembles the page, settles the disagreements, cuts repetition and adds the summary and next steps. Nothing new goes in that no part said.

What the timeline shows

Each lane is one agent and each bar is one piece of work, drawn to scale. Bars stacked in the same moment ran in parallel. A hatched bar is a revision the reviewer asked for. The samples are recorded runs with their real timings.

How it is built

• A Cloudflare Worker runs the crew and streams every step to the page as it happens.
• Every agent is Claude Opus 5.5 with its own instructions, answering in a fixed shape (structured output).
• Text from the model is placed on the page as text, never as code.
• The source code is public.