start

/start — Project Onboarding

Welcome the user and determine their starting point by asking:

"Where are you with this project?"

1. No idea — I don't even have a game concept yet
2. Vague concept — I have a rough idea but nothing documented
3. Clear design — I have a GDD or design docs ready
4. Existing code — I have a Roblox project with code already

Based on their answer:

If "No idea":

1. Run /brainstorm to explore game ideas
2. Guide through genre selection, target audience, core loop definition
3. Help define creative pillars (3-5 words each that describe the experience)
4. Draft a 1-page game concept document
5. Proceed to /gdd for the master GDD

If "Vague concept":

1. Ask them to describe their idea in 2-3 sentences
2. Ask: What Roblox games inspire this? What's the core loop?
3. Help crystallize: genre, setting, core mechanic, target audience
4. Define creative pillars
5. Proceed to /gdd

If "Clear design":

1. Ask them to share or describe their existing design docs
2. Review for completeness against GDD standards
3. Run /project-stage-detect to assess readiness
4. Identify gaps and create a plan to fill them
5. Set up the project structure if not already done

If "Existing code":

1. Ask them to describe the project and share the codebase location
2. Run /reverse-document to generate docs from existing code
3. Run /project-stage-detect to assess current stage
4. Identify technical debt with /tech-debt
5. Create a plan for what's next

---

Team Size Preset

After the starting-point question, ask:

"What's your team size?"

1. Solo — just me. Streamlined review, fewer agent interactions.
2. Small team (2-5) — lean review, key specialists involved.
3. Studio (5+) — full review pipeline, all agents active.

Based on the answer, set review_mode automatically:

• Solo -> solo
• Small team -> lean
• Studio -> full

---

Genre Preset (optional)

Ask:

"What genre?" (Tell the user they can skip this if they don't know yet.)