# Workflow Init - Game Project Setup Instructions The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: workflow-init/workflow.yaml Communicate in {communication_language} with {user_name} This workflow handles BOTH new game projects AND existing game projects Welcome to BMGD Game Development, {user_name}! 🎮 Perform comprehensive scan for existing work: - BMGD artifacts: GDD, game brief, architecture, narrative design - Implementation: stories, sprint-status, workflow-status - Game project: engine files (Unity, Unreal, Godot), source directories - Check both {output_folder} and {implementation_artifacts} locations Categorize into one of these states: - CLEAN: No artifacts or code (or scaffold only) - DESIGN: Has GDD/brief but no implementation - ACTIVE: Has stories or sprint status - EXISTING: Has game code but no BMGD artifacts - UNCLEAR: Mixed state needs clarification What's your game project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}} Store project_name project_name Perfect! Fresh start detected. Let's design your game! Continue to step 3 ✅ You already have workflow tracking at: {{workflow_status_path}} To check progress: Load any BMGD agent and run /bmad:bmgd:workflows:workflow-status Happy game dev! 🎮 Exit workflow (already initialized) Found existing work: {{summary_of_findings}} How would you like to proceed? 1. **Continue** - Work with existing artifacts 2. **Archive & Start Fresh** - Move old work to archive 3. **Express Setup** - I know exactly what I need 4. **Guided Setup** - Walk me through options Choice [1-4] Set continuing_existing = true Store found artifacts Continue to step 7 (detect track from artifacts) Archive existing work? (y/n) Move artifacts to {output_folder}/archive/ Ready for fresh start! Continue to step 3 Jump to step 3 (express path) Continue to step 4 (guided path) Setup approach: 1. **Express** - I know what I need 2. **Guided** - Show me the options Choice [1 or 2]: Continue to step 3 (express) Continue to step 4 (guided) Is this for: 1. **New game** (greenfield) 2. **Existing game codebase** (brownfield) Choice [1/2]: Set field_type based on choice Development approach: 1. **Full Game Dev** - Complete GDD + Architecture + Production pipeline 2. **Quick Flow** - Rapid prototyping and iteration Choice [1/2]: Map to selected_track: gamedev/quickflow field_type selected_track Jump to step 6 (discovery options) Tell me about your game. What are you making? Store user_description Analyze for field type indicators: - Brownfield: "existing", "current", "enhance", "update", "add to" - Greenfield: "new", "build", "create", "from scratch", "fresh" - If game project exists, default to brownfield unless user indicates new I see existing game files. Are you: 1. **Modifying** existing game (brownfield) 2. **Starting fresh** - code is just scaffold (greenfield) Choice [1/2]: Set field_type based on answer Set based on project presence user_description field_type Continue to step 5 Based on your game, here are your BMGD development options: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **1. Full Game Dev** 🎮 {{#if recommended}}(RECOMMENDED){{/if}} - Complete: Game Brief + GDD + Architecture + Production - Best for: Indie games, AA projects, complete releases - Benefit: AI agents have full game context for better results **2. Quick Flow** 🚀 - Rapid: Prototype → Iterate → Ship - Best for: Game jams, prototypes, experiments - Benefit: Get playable builds fast ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ {{#if brownfield}} 💡 Architecture helps integrate new features with your existing game systems. {{/if}} Which approach fits your game? 1. Full Game Dev {{#if recommended}}(recommended){{/if}} 2. Quick Flow 3. Help me decide Choice [1/2/3]: What concerns you about choosing? Provide tailored guidance based on concerns Loop back to choice Map choice to selected_track selected_track Determine available discovery workflows based on: - field_type (greenfield gets game-brief option) - selected_track (gamedev/quickflow options) Optional pre-production workflows can help clarify your game vision: Select any you'd like to include: 1. 🧠 **Brainstorm Game** - Creative exploration and ideation 2. 📋 **Game Brief** - Strategic game planning (recommended) Enter numbers (e.g., "1,2" or "all" or "none"): Optional discovery workflows: Include any of these? 1. 🧠 **Brainstorm Game** - Creative exploration for new features Enter "1" or "none": Quick Flow focuses on rapid iteration. You can brainstorm during development. Parse selections and set: - brainstorm_requested - game_brief_requested (if applicable) brainstorm_requested game_brief_requested Analyze artifacts to detect track: - Has GDD → Full Game Dev - Has tech-spec only → Quick Flow Detected: **{{detected_track}}** based on {{found_artifacts}} Correct? (y/n) Which BMGD track instead? 1. Full Game Dev 2. Quick Flow Choice: Set selected_track selected_track Load path file: {path_files}/{{selected_track}}-{{field_type}}.yaml Build workflow_items from path file Scan for existing completed work and update statuses Set generated date generated workflow_path_file workflow_items Your BMGD workflow path: **Track:** {{selected_track}} **Type:** {{field_type}} **Project:** {{project_name}} {{#if brownfield}}Prerequisites: Analyze existing game code{{/if}} {{#if has_discovery}}Pre-production: {{list_selected_discovery}}{{/if}} {{workflow_path_summary}} Create workflow tracking file? (y/n) Generate YAML from template with all variables Save to {output_folder}/bmgd-workflow-status.yaml Identify next workflow and agent ✅ **Created:** {output_folder}/bmgd-workflow-status.yaml **Next:** {{next_workflow_name}} **Agent:** {{next_agent}} **Command:** /bmad:bmgd:workflows:{{next_workflow_id}} {{#if next_agent not in [game-designer]}} 💡 Start new chat with **{{next_agent}}** agent first. {{/if}} To check progress: /bmad:bmgd:workflows:workflow-status Happy game dev! 🎮