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.

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), 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.

Ask with the question tool. Without one, list the options numbered and end your turn to wait. The question is the last thing in the reply: no path, note or advice after it. A skipped or dismissed question is not an answer: ask again in plain text.

The questions in Phases 2, 4 and 5 shape the project, so they are asked in every automation mode. The engine is not one of them: /setup-engine chooses it. Phase 6's last question follows a modes.automation already in project.yaml, per .claude/docs/automation-modes.md; with none set, ask it.

Phase 1: Read the project

Run bash .claude/scripts/project-state.sh and keep its rows. Do not show them yet; they check the user's answer in Phase 2.