Handbook

Wizard 201 — Mission modes

The first wizard step asks for a mission mode. Four options set the posture for the rest of the session so targets, scope, and run plan stay coherent.

Updated

What it is

The first wizard step asks for a mission mode. Four options set the posture for the rest of the session so targets, scope, and run plan stay coherent.

When to use it

When you pick Mission in a new or resumed session (Wizard 101).

Prerequisites

Mission modes at a glance

Mode Choose it when… Deep dive
Start from idea Discovery is open; problem and constraints are still fuzzy Start from idea
Assess current project Code exists but Forge / Blueprints practices are uneven Assess current project
Resume and advance Foundation work exists; you need the next chapter (for example MVP to scale) Resume and advance
Repair stage Process drift, inconsistent artifacts, or a blocked stage Repair stage

Decision prompts (plain language)

Question If “yes” →
Are we still proving the problem and value? Start from idea
Do we have shipping code but messy process or docs? Assess current project
Do we already have a plan and need the next increment? Resume and advance
Are we stuck, inconsistent, or blocked on a stage? Repair stage

Mission modes (visual)

The four modes differ by how much is unknown vs how much is already shipping; use the table above to pick a child page.

Mission modes at a glance

  Start
      |
      v
  Core steps (see walkthrough below)
      |
      v
  Outcome

  Note: one session per initiative

Sessions

  • Prefer one session per initiative; start a new session on a hard pivot.
  • Name sessions on the hub so you can find them later.

Server vs local-only

Mode What you get
Server-enabled Durable sessions, autosave when APIs are healthy
Local-only draft Browser storage if the server or wizard is unavailable — retry when fixed

How to verify success

  • The mode you picked matches the team’s actual posture.
  • Downstream steps do not fight the mission (e.g. “idea” vs “repair”).

What to do next