Guided Onboarding

The entry point for a new user. It assumes no game idea, no engine and no experience: it reads the project, asks where the user is starting from, shows what it assumes about the project, and names the one next step. It never runs that step itself, except for a game the person described in their own words, which goes straight to /prototype (One-shot 1).

The main path leads: make a game (/prototype), change it after play, grow it into a project. The design documents, the agents and the team-* pipelines are studio mode, the path at rigor standard and full (Phase 6).

It writes these settings to project.yaml, all through helpers, and only after an explicit yes: project.stage (with its legacy mirror production/stage.txt), project.goal, modes.rigor and modes.automation. It never writes modes.review_mode or production/review-mode.txt, and none of the other knobs rigor fronts (modes.workflow, docs.density, qa.level, modes.story_granularity, team.size): a written value pins that knob over the rigor expansion, and a mirror file outranks it. The make-me-a-game route writes nothing: /prototype's card is that route's assumptions card.