start

# Guided Onboarding This skill writes up to two files: - `production/stage.txt` — set to `exploration` when user picks Path E (pre-workflow exploration). - `production/review-mode.txt` — review mode config (set in Phase 3b, skipped for Path E). This skill is the entry point for new users. It does NOT assume you have a game idea, an engine preference, or any prior experience. It asks first, then routes you to the right workflow. --- ## Phase 1: Detect Project State Before asking anything, silently gather context so you can tailor your guidance. Do NOT show these results unprompted — they inform your recommendations, not the conversation opener. Check: - **Engine configured?** Read `docs/framework/technical-preferences.md`. If the Engine field contains `[TO BE CONFIGURED]`, the engine is not set. - **Game concept exists?** Check for `design/gdd/game-concept.md`. - **Source code exists?** Glob for source files in `src/` (`*.gd`, `*.cs`, `*.cpp`, `*.h`, `*.rs`, `*.py`, `*.js`, `*.ts`). - **Prototypes exist?** Check for subdirectories in `prototypes/`. - **Design docs exist?** Count markdown files in `design/gdd/`. - **Production artifacts?** Check for files in `production/sprints/` or `production/milestones/`. Store these findings internally to validate the user's self-assessment and tailor recommendations. --- ## Phase 2: Ask Where the User Is This is the first thing the user sees. Use `question` with these exact options so the user can click rather than type: - **Pro...