# Workflow Init - 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 projects AND legacy projects being migrated to BMad Method Welcome to BMad Method, {user_name}! Perform comprehensive scan for existing work: - BMM artifacts: PRD, tech-spec, epics, architecture, UX, brief, research, brainstorm - Implementation: stories, sprint-status, workflow-status - Codebase: source directories, package files, git repo - Check both {output_folder} and {sprint_artifacts} locations Categorize into one of these states: - CLEAN: No artifacts or code (or scaffold only) - PLANNING: Has PRD/spec but no implementation - ACTIVE: Has stories or sprint status - LEGACY: Has code but no BMM artifacts - UNCLEAR: Mixed state needs clarification What's your project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}} Store project_name project_name Perfect! Fresh start detected. Continue to step 3 ✅ You already have workflow tracking at: {{workflow_status_path}} To check progress: Load any BMM agent and run /bmad:bmm:workflows:workflow-status Happy building! 🚀 Exit workflow (already initialized) Found existing work: {{summary_of_findings}} How would you like to proceed? a) **Continue** - Work with existing artifacts b) **Archive & Start Fresh** - Move old work to archive c) **Express Setup** - I know exactly what I need d) **Guided Setup** - Walk me through options Choice [a/b/c/d]: 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: a) **Express** - I know what I need b) **Guided** - Show me the options Choice [a/b]: Continue to step 3 (express) Continue to step 4 (guided) Is this for: 1) **New project** (greenfield) 2) **Existing codebase** (brownfield) Choice [1/2]: Set field_type based on choice Planning approach: 1. **Quick Flow** - Minimal planning, fast to code 2. **BMad Method** - Full planning for complex projects 3. **Enterprise Method** - Extended planning with security/DevOps Choice [1/2/3]: Map to selected_track: quick-flow/method/enterprise field_type selected_track Jump to step 6 (discovery options) Tell me about what you're working on. What's the goal? Store user_description Analyze for field type indicators: - Brownfield: "existing", "current", "enhance", "modify" - Greenfield: "new", "build", "create", "from scratch" - If codebase exists, default to brownfield unless user indicates scaffold I see existing code. Are you: 1) **Modifying** existing codebase (brownfield) 2) **Starting fresh** - code is just scaffold (greenfield) Choice [1/2]: Set field_type based on answer Set based on codebase presence Check for game development keywords 🎮 **GAME DEVELOPMENT DETECTED** For game development, install the BMGD module: ```bash bmad install bmgd ``` Continue with software workflows? (y/n) Choice: Exit workflow user_description field_type Continue to step 5 Based on your project, here are your planning options: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **1. Quick Flow** 🚀 - Minimal planning, straight to code - Best for: Simple features, bug fixes - Risk: Potential rework if complexity emerges **2. BMad Method** 🎯 {{#if recommended}}(RECOMMENDED){{/if}} - Full planning: PRD + UX + Architecture - Best for: Products, platforms, complex features - Benefit: AI agents have complete context for better results **3. Enterprise Method** 🏢 - Extended: Method + Security + DevOps + Testing - Best for: Enterprise, compliance, mission-critical - Benefit: Comprehensive planning for complex systems ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ {{#if brownfield}} 💡 Architecture creates focused solution design from your codebase, keeping AI agents on track. {{/if}} Which approach fits best? 1. Quick Flow 2. BMad Method {{#if recommended}}(recommended){{/if}} 3. Enterprise Method 4. Help me decide Choice [1/2/3/4]: 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 product-brief option) - selected_track (quick-flow skips product-brief) Optional discovery workflows can help clarify your vision: Select any you'd like to include: 1. 🧠 **Brainstorm** - Creative exploration and ideation 2. 🔍 **Research** - Technical/competitive analysis 3. 📋 **Product Brief** - Strategic product planning (recommended) Enter numbers (e.g., "1,3" or "all" or "none"): Optional discovery workflows: Include any of these? 1. 🧠 **Brainstorm** - Creative exploration 2. 🔍 **Research** - Domain analysis Enter numbers (e.g., "1,2" or "none"): Parse selections and set: - brainstorm_requested - research_requested - product_brief_requested (if applicable) brainstorm_requested research_requested product_brief_requested 💡 **Note:** For brownfield projects, run document-project workflow first to analyze your codebase. Analyze artifacts to detect track: - Has PRD → BMad Method - Has tech-spec only → Quick Flow - Has Security/DevOps → Enterprise Method Detected: **{{detected_track}}** based on {{found_artifacts}} Correct? (y/n) Which track instead? 1. Quick Flow 2. BMad Method 3. Enterprise Method 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 BMad workflow path: **Track:** {{selected_track}} **Type:** {{field_type}} **Project:** {{project_name}} {{#if brownfield}}Prerequisites: document-project{{/if}} {{#if has_discovery}}Discovery: {{list_selected_discovery}}{{/if}} ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ {{workflow_path_summary}} ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Create workflow tracking file? (y/n) Generate YAML from template with all variables Save to {output_folder}/bmm-workflow-status.yaml Identify next workflow and agent ✅ **Created:** {output_folder}/bmm-workflow-status.yaml **Next:** {{next_workflow_name}} **Agent:** {{next_agent}} **Command:** /bmad:bmm:workflows:{{next_workflow_id}} {{#if next_agent not in [analyst, pm]}} 💡 Start new chat with **{{next_agent}}** agent first. {{/if}} To check progress: /bmad:bmm:workflows:workflow-status Happy building! 🚀 No problem! Run workflow-init again when ready.