StudioOSFive agents, two decisions
Five AI agents turn your brief into a marketing site. You decide twice.
StudioOS is a studio of AI agents that turns a brief into a finished, verified marketing site. A strategist, a copywriter, a designer, a developer and a critic do the work in eleven steps. You pick between two live concepts at the gate and accept the site at the end.
Nothing here is for sale. This site explains how the studio works, and the studio built it.
Eleven steps from brief to accepted site
- 01IntakeYou, in Site Blueprint. Writes blueprint/intake.md and the references.Owner's step, before the run starts.
- 02StrategyStrategist. Writes the purpose, sitemap, sections and acceptance criteria into blueprint/blueprint.json.Runs on its own.
- 03CopyCopywriter. Writes the heading, body and button of every section into the same file.Runs on its own.
- 04Text reviewCritic. Scores strategy and copy against the rubric; one round of fixes follows.Runs on its own.
- 05Two design directionsDesigner. Writes two concept notes: one close to the references, one that pushes further.Runs on its own.
- 06Two concept buildsDesigner. Builds each direction as a live page with the real copy, in its own git worktree.Runs on its own.
- 07Concept reviewCritic. Scores both concepts at 1440, 768 and 390 pixels wide, up to two rounds each.Runs on its own.
- 08The gateYou. Pick A, B, A with named parts of B, or neither with a reason.Owner's decision.
- 09BuildDeveloper. Extends the chosen concept into the full site, page by page.Runs on its own.
- 10VerificationCritic and project checks. Writes PASS, FAIL or NOT RUN for every acceptance criterion into blueprint/verification.md, up to three rounds.Runs on its own.
- 11Final reviewYou. Send notes or accept the site.Owner's decision.
Two decisions are yours. The rest runs until it has to ask.
At the gate
Two concepts are running on live URLs. You answer with one of four: A, B, A with named parts of B, or neither with a reason. Neither sends the designer back for a third concept.
At the final review
You get what was built, the PASS, FAIL and NOT RUN counts, every decision the agents made and every fact still marked [NEEDS: …]. You send notes or accept the site.
Everywhere else
Every other stage runs on its own and stops only to ask: about a decision marked ask-first, a missing business fact, a contradiction between the intake, the references and your notes, a tool or access failure, or a stage still failing the critic at its loop cap.
Five agents, one file
The agents never message each other. Each one reads blueprint/blueprint.json and leaves its work in files the next one reads: the designer in concept notes and live pages, the critic in round files.
- Strategist
Decides what the site is for: the pages, the sections and the acceptance criteria the build is checked against.
- Copywriter
Writes every heading, paragraph and button, and marks a fact it lacks as [NEEDS: …] instead of guessing.
- Designer
Proposes two contrasting directions and builds both as live pages with the real copy.
- Developer
Extends the chosen concept into the full Astrokit site and fixes what verification fails.
- Critic
Scores every stage against a written rubric without being told why the work looks the way it does.
Checked by an agent that never hears the excuses
A critic with fresh eyes
Strategy, copy, both concepts and the finished build are scored 1 to 3 against a written rubric. The critic gets file paths, never the author's reasoning.
Real checks on the real build
Verification runs the type check, unit tests, end-to-end tests and Lighthouse, and the critic checks every acceptance criterion in a browser. Failures go back to the developer for up to three rounds.
No invented facts
A price, a name or a number the intake does not give becomes a visible [NEEDS: …] marker, listed for you at the final review.
This site went through the same eleven steps
StudioOS built these pages on Astrokit (Astro and Sanity on Lumos), from an intake written in Site Blueprint. The pipeline above, the gate included, is how they got here.
The walkthrough follows one run from the owner's side: what you write, when you wait, and the two moments you decide.