Sign in

A worked example, in five steps

How a SwarmPlan gets made.

One brief lands. A room assembles. They argue. A plan emerges. Here is the path the sample plan took, with the actual artifact from each step.

A brief lands.

The Creator writes one paragraph. What they want to build, plan, or decide. Then the orchestrator interviews them (a few multiple-choice prompts) to pin down the shape of the plan and who should be in the room. No blank text box, no settings to guess at.

The brief below is real: it is the plan for SwarmReview, Product 03 on our masthead, argued into shape by the product you are reading about.

The Creator's brief

Add SwarmReview to SwarmStack: a quick way for a Creator to get feedback on one thing (a prototype, a doc, a task list) from teammates and outside customers. Each person gives a 1 to 5 rating plus an optional comment. Every response gets summarised into one document at the end, in one of three shapes the Creator picks: a ranked list of themes, a structured decision, or a written report. No back-and-forth thread, no extra rounds.

The intake interview · turn 1

Before the room assembles, the orchestrator interviews you to pin down the brief.

What should the swarm hand back?
A buildable feature specRecommendedSections, permissions, and lifecycle an engineer can implement from.
A decision recordOne recommendation, the alternatives, and why they lost.
A discovery briefOpen questions and risks, before anyone commits to a build.
Who should argue it?choose any
Software engineerOwns feasibility and the data shape.
QA / test leadPushes on edge cases and how it's verified.
Security reviewerChecks who can see customer responses.
Priya · productYour coworker · remote joinerYour coworker, invited by join code to plan alongside you in realtime.
UX consultant · human SMEHuman SMEHire from the marketplace for the rating flow.
Define your own personaName a seat the defaults miss, brief it, and assign it to a coworker or the AI.
Answered. The room assembles next

A room assembles.

The orchestrator proposes a default lineup of AI specialists. The Creator pulls in a teammate by join code, and hires a UX consultant off the marketplace. Eight seats, four kinds.

  1. 1You

    • You

  2. 1Your team

    • Sam Reyes

  3. 1Hired experts

    • Maya Chen

  4. 5AI specialists

    • Product
    • Backend SWE
    • Frontend SWE
    • Security
    • QA

They argue.

Each seat pushes its own corner. The orchestrator runs the debate and logs every disagreement as a Decision Record. Here are the three the room could not converge on without a fight.

  1. DR-2

    How Customers authenticate

    Maya Chen wanted:Magic-link would convert dramatically better for a stranger asked to log in just to leave one rating.

    Security + Product blocked it:Anonymous auth shreds the RLS story. Magic-link adds a new auth path we have to maintain.

    ResolutionOAuth-only for v1. Magic-link deferred to v1.1 as a conversion optimization.

  2. DR-8

    Reaction scale

    Product wanted:Ship NPS in v1 for B2B parity. A fixed 1 to 5 Likert reads as toy.

    Sam Reyes blocked it:We have not shipped NPS anywhere in the product. Carrying two scales doubles the synthesis surface.

    ResolutionLikert ships v1. The scale column is reserved on the schema so v1.1 customisation does not need a migration.

  3. DR-10

    Real-time visibility for Collaborators

    Backend SWE wanted:Loosen RLS for trusted Collaborators. It would keep the query path simple and the aggregates honest.

    Security blocked it:NN-1, multi-tenant isolation, is a hard constraint. Loosening it for any role is a one-way door.

    ResolutionOrchestrator computes aggregates under the system role and broadcasts as SSE activity frames. RLS untouched.

A plan emerges.

The orchestrator merges everything the room agreed on, marks the 3 arguments that survived as Decision Records, and writes the document in 47 minutes of wall clock. The Creator gets a versioned plan, not a transcript.

SwarmPlanv59 sections9 decisions

SwarmReview Feature, Synthesis Plan

  1. Overview
  2. What we agreed on
  3. Participant permissions
  4. Lifecycle
  5. The three output formats
  6. What we argued over and decided
  7. Flagged ambiguities (resolved)
  8. Deferred to v1.1
  9. Success metrics (v1 GA)
Read the full plan

You decide what happens next.

You can run another round if a Decision still feels soft. You can share the plan with the room as a read-only link. You can hire a different SME for a different angle. Or you can stop here and ship.

Bring your own briefBrowse marketplace experts

Your first SwarmPlan is on us. Pro $29 · Team $99. See plans.