Handbook
Wizard 101 — First session
Your first run through the Blueprints Wizard: open the hub, create a session, understand the twelve steps, and complete one short worked example.
What it is
Your first run through the Blueprints Wizard: open the hub, create a session, understand the twelve steps, and complete one short worked example.
When to use it
After Wizard overview and Studio 101.
Prerequisites
- Wizard enabled (Wizard overview).
- Browser on
/studio/.
Steps
Open the wizard
- Start Lenses and open
/studio/. - In the sidebar, choose Blueprints Wizard (wording may vary).
- Land on the Hub — create a new session or resume one.
Hub vs session
| Place | URL pattern | Purpose |
|---|---|---|
| Hub | /studio/blueprints/wizard |
List sessions, create new, see last step |
| Session | /studio/blueprints/wizard/session/<sessionId> |
Full stepper, notes, saves, exports |
Example first session (generic)
| Starting situation | Team agreed to try the Wizard for a small initiative; Studio is already open at /studio/. |
| Action taken | Create a new session from the hub, complete Mission with a mode from Wizard 201, stop after Run plan or Review for a dry run. |
| Expected result | Session URL is shareable; steps show saved notes; at least one artifact or export path is visible before closing. |
| What to check | If the hub is empty, confirm Wizard feature flags and routes from Wizard overview. |
The twelve steps (what you see in the UI)
| Step | Intent | Typical output |
|---|---|---|
| 1 Mission | Why you are here | Mode + posture (see Wizard 201) |
| 2 Contribution setup | Roles, repos, expectations | Named participants and boundaries |
| 3 Context intake | What is already true | Facts and links the team agrees on |
| 4 Understanding | Shared picture | Narrative; Refine may appear |
| 5 Clarification | Resolve ambiguities | Decisions or explicit open questions |
| 6 Target & output pack | Done shape | Artifact emphasis (Wizard 301) |
| 7 Autonomy & mutation | Allowed change vs stability | Guardrails for the plan |
| 8 Scope selection | This increment vs later | Scoped slice |
| 9 Run plan | Ordered steps and checks | Executable sequence |
| 10 Review & generate | Inspect artifacts | Approved or iterated bundle |
| 11 Recheck / repair | Consistency | Pass or listed gaps |
| 12 Experimental build | Handoff | Cursor Launch Pack or related exports when offered |
Detail for each row follows the same order in the stepper UI.
Worked example — “Start from idea”
Scenario: A small internal tool — a team retrospective dashboard (action items and trends).
- Hub — New session; name it (e.g. “Retro dashboard — Q2”).
- Mission — Start from idea; describe scattered retro notes and lack of follow-through visibility.
- Continue through steps with short, honest notes; use Refine where offered.
- Experimental build — Export a Cursor Launch Pack if your build offers it.
How to verify success
- Session persists when the server supports it (otherwise you may see a local draft warning — see Troubleshooting).
- You finish with generated artifacts or exports you can take to engineering.