Documentation
Plan

45 of 187 pages

Studio Getting Started

Intent to Shipped — the Happy Path

The shortest complete journey through the Studio: one idea, one work package, one agent run, one review, one release. Everything else in the Studio is a variation on this loop.

1

Capture the intent

Open the Intent Pad and describe what you want in plain language. An intent is a want, not a specification — the Studio's job is to turn it into one.

2

Shape it

On the intent's page, write the brief and let the Composer break it into workstreams and Work Packages, grounded in your Context Library. Review the breakdownsition here — correcting it now is far cheaper than correcting the output later.

3

Promote to a work package

Shaped work becomes a Work Package — the unit agents execute against. It carries its own checklist, acceptance criteria and lifecycle. Work packages move across the board as they progress.

4

Run it, and clear the plan gate

Dispatch the package from the Run Board. The agent produces a plan first and stops. A human approves the plan before any work happens — this is the single most important control in the Studio.

5

Review the output

The package’s Definition of Done reads the pull request: its agents say what falls short and send it back to the coding agent. The Review feed shows everything they are waiting on — rework, questions to answer, stale evidence — and Verify collates what they found across the studio, next to your own CI.

6

Release and learn

The Release plan puts completed packages on a release, approved on two keys, and names the key results it should move; Release comms drafts what each audience needs to know. Afterwards, Outcome Telemetry and the Outcome Feedback Loop judge whether the release actually moved what it said it would.

Every step is auditable. The Audit Explorer reconstructs any run: the intent, the context bundle, the plan, who approved it, what changed and what shipped.

When the happy path does not happen

  • The plan looks wrong — reject at the plan gate and improve the context, not the prompt. Most bad plans are a context problem.
  • Output fails review repeatedly — tighten the work package's DoR and DoD so the gate catches the problem earlier.
  • Runs cost more than expected — Capabilities and Model Config hold the guardrails; AI Effectiveness shows where the spend is going.

All Studio Getting Started documentation

Build v0.3.2 · deployed 2026-10-19T23:52:31Z