bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/bmm/workflows/2-plan/gdd/instructions-gdd.md

@@ -1,480 +0,0 @@
-# GDD Workflow - Game Projects (All Levels)
-
-<workflow>
-
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This is the GDD instruction set for GAME projects - replaces PRD with Game Design Document</critical>
-<critical>Project analysis already completed - proceeding with game-specific design</critical>
-<critical>Uses gdd_template for GDD output, game_types.csv for type-specific sections</critical>
-<critical>Routes to 3-solutioning for architecture (platform-specific decisions handled there)</critical>
-<critical>If users mention technical details, append to technical_preferences with timestamp</critical>
-
-<step n="1" goal="Load context and determine game type">
-
-<action>Load project-workflow-analysis.md</action>
-<action>Confirm project_type == "game"</action>
-
-<check>If continuation_mode == true:</check>
-<action>Load existing GDD.md and check completion status</action>
-<ask>Found existing work. Would you like to:
-
-1. Review what's done and continue
-2. Modify existing sections
-3. Start fresh
-   </ask>
-   <action>If continuing, skip to first incomplete section</action>
-
-<check>If new or starting fresh:</check>
-Check `output_folder` for existing game docs.
-
-<action>Check for existing game-brief in output_folder</action>
-
-<check>If game-brief exists:</check>
-<ask>Found existing game brief! Would you like to:
-
-1. Use it as input (recommended - I'll extract key info)
-2. Ignore it and start fresh
-
-Your choice:</ask>
-
-<check>If using game-brief:</check>
-<action>Load and analyze game-brief document</action>
-<action>Extract: game_name, core_concept, target_audience, platforms, game_pillars, primary_mechanics</action>
-<action>Pre-fill relevant GDD sections with game-brief content</action>
-<action>Note which sections were pre-filled from brief</action>
-
-<ask>What type of game are you designing?
-
-**Common Game Types:**
-
-1. Action Platformer (e.g., Celeste, Hollow Knight)
-2. RPG (e.g., Stardew Valley, Undertale)
-3. Puzzle (e.g., Portal, The Witness)
-4. Roguelike (e.g., Hades, Dead Cells)
-5. Shooter (e.g., DOOM, Enter the Gungeon)
-6. Strategy (e.g., Into the Breach, Slay the Spire)
-7. Adventure (e.g., Firewatch, What Remains of Edith Finch)
-8. Simulation (e.g., Factorio, Rimworld)
-9. Other (I'll ask follow-up questions)
-
-Select a number or describe your game type:</ask>
-
-<action>Map selection to game_types.csv id</action>
-<action>Load corresponding fragment file from game-types/ folder</action>
-<action>Store game_type for later injection</action>
-
-<action>Load gdd_template from workflow.yaml</action>
-
-Get core game concept and vision.
-
-<template-output>description</template-output>
-
-</step>
-
-<step n="2" goal="Define platforms and target audience">
-
-<ask>What platform(s) are you targeting?
-
-- Desktop (Windows/Mac/Linux)
-- Mobile (iOS/Android)
-- Web (Browser-based)
-- Console (which consoles?)
-- Multiple platforms
-
-Your answer:</ask>
-
-<template-output>platforms</template-output>
-
-<ask>Who is your target audience?
-
-Consider:
-
-- Age range
-- Gaming experience level (casual, core, hardcore)
-- Genre familiarity
-- Play session length preferences
-
-Your answer:</ask>
-
-<template-output>target_audience</template-output>
-
-</step>
-
-<step n="3" goal="Define goals and context">
-
-**Goal Guidelines based on project level:**
-
-- Level 0-1: 1-2 primary goals
-- Level 2: 2-3 primary goals
-- Level 3-4: 3-5 strategic goals
-
-<template-output>goals</template-output>
-
-Brief context on why this game matters now.
-
-<template-output>context</template-output>
-
-</step>
-
-<step n="4" goal="Core gameplay definition">
-
-<critical>These are game-defining decisions</critical>
-
-<ask>What are the core game pillars (2-4 fundamental gameplay elements)?
-
-Examples:
-
-- Tight controls + challenging combat + rewarding exploration
-- Strategic depth + replayability + quick sessions
-- Narrative + atmosphere + player agency
-
-Your game pillars:</ask>
-
-<template-output>game_pillars</template-output>
-
-<ask>Describe the core gameplay loop (what the player does repeatedly):
-
-Example: "Player explores level → encounters enemies → defeats enemies with abilities → collects resources → upgrades abilities → explores deeper"
-
-Your gameplay loop:</ask>
-
-<template-output>gameplay_loop</template-output>
-
-<ask>How does the player win? How do they lose?</ask>
-
-<template-output>win_loss_conditions</template-output>
-
-</step>
-
-<step n="5" goal="Game mechanics and controls">
-
-Define the primary game mechanics.
-
-<template-output>primary_mechanics</template-output>
-<elicit-required/>
-
-<ask>Describe the control scheme and input method:
-
-- Keyboard + Mouse
-- Gamepad
-- Touch screen
-- Other
-
-Include key bindings or button layouts if known.</ask>
-
-<template-output>controls</template-output>
-
-</step>
-
-<step n="6" goal="Inject game-type-specific sections">
-
-<action>Load game-type fragment from: {installed_path}/gdd/game-types/{{game_type}}.md</action>
-
-<critical>Process each section in the fragment template</critical>
-
-For each {{placeholder}} in the fragment, elicit and capture that information.
-
-<template-output file="GDD.md">GAME_TYPE_SPECIFIC_SECTIONS</template-output>
-
-<elicit-required/>
-
-</step>
-
-<step n="7" goal="Progression and balance">
-
-<ask>How does player progression work?
-
-- Skill-based (player gets better)
-- Power-based (character gets stronger)
-- Unlock-based (new abilities/areas)
-- Narrative-based (story progression)
-- Combination
-
-Describe:</ask>
-
-<template-output>player_progression</template-output>
-
-<ask>Describe the difficulty curve:
-
-- How does difficulty increase?
-- Pacing (steady, spikes, player-controlled?)
-- Accessibility options?</ask>
-
-<template-output>difficulty_curve</template-output>
-
-<ask optional="true">Is there an in-game economy or resource system?
-
-Skip if not applicable.</ask>
-
-<template-output>economy_resources</template-output>
-
-</step>
-
-<step n="8" goal="Level design framework">
-
-<ask>What types of levels/stages does your game have?
-
-Examples:
-
-- Tutorial, early levels, mid-game, late-game, boss arenas
-- Biomes/themes
-- Procedural vs. handcrafted
-
-Describe:</ask>
-
-<template-output>level_types</template-output>
-
-<ask>How do levels progress or unlock?
-
-- Linear sequence
-- Hub-based
-- Open world
-- Player choice
-
-Describe:</ask>
-
-<template-output>level_progression</template-output>
-
-</step>
-
-<step n="9" goal="Art and audio direction">
-
-<ask>Describe the art style:
-
-- Visual aesthetic (pixel art, low-poly, realistic, stylized, etc.)
-- Color palette
-- Inspirations or references
-
-Your vision:</ask>
-
-<template-output>art_style</template-output>
-
-<ask>Describe audio and music direction:
-
-- Music style/genre
-- Sound effect tone
-- Audio importance to gameplay
-
-Your vision:</ask>
-
-<template-output>audio_music</template-output>
-
-</step>
-
-<step n="10" goal="Technical specifications">
-
-<ask>What are the performance requirements?
-
-Consider:
-
-- Target frame rate
-- Resolution
-- Load times
-- Battery life (mobile)
-
-Requirements:</ask>
-
-<template-output>performance_requirements</template-output>
-
-<ask>Any platform-specific considerations?
-
-- Mobile: Touch controls, screen sizes
-- PC: Keyboard/mouse, settings
-- Console: Controller, certification
-- Web: Browser compatibility, file size
-
-Platform details:</ask>
-
-<template-output>platform_details</template-output>
-
-<ask>What are the key asset requirements?
-
-- Art assets (sprites, models, animations)
-- Audio assets (music, SFX, voice)
-- Estimated asset counts/sizes
-- Asset pipeline needs
-
-Asset requirements:</ask>
-
-<template-output>asset_requirements</template-output>
-
-</step>
-
-<step n="11" goal="Epic structure">
-
-<action>Translate game features into development epics</action>
-
-**Epic Guidelines based on project level:**
-
-- Level 1: 1 epic with 1-10 stories
-- Level 2: 1-2 epics with 5-15 stories total
-- Level 3: 2-5 epics with 12-40 stories
-- Level 4: 5+ epics with 40+ stories
-
-<template-output>epics</template-output>
-<elicit-required/>
-
-</step>
-
-<step n="12" goal="Success metrics">
-
-<ask>What technical metrics will you track?
-
-Examples:
-
-- Frame rate consistency
-- Load times
-- Crash rate
-- Memory usage
-
-Your metrics:</ask>
-
-<template-output>technical_metrics</template-output>
-
-<ask>What gameplay metrics will you track?
-
-Examples:
-
-- Player completion rate
-- Average session length
-- Difficulty pain points
-- Feature engagement
-
-Your metrics:</ask>
-
-<template-output>gameplay_metrics</template-output>
-
-</step>
-
-<step n="13" goal="Document out of scope and assumptions">
-
-<template-output>out_of_scope</template-output>
-
-<template-output>assumptions_and_dependencies</template-output>
-
-</step>
-
-<step n="14" goal="Generate solutioning handoff and next steps">
-
-<action>Check if game-type fragment contained narrative tags</action>
-
-<check>If fragment had <narrative-workflow-critical> or <narrative-workflow-recommended>:</check>
-<action>Set needs_narrative = true</action>
-<action>Extract narrative importance level from tag</action>
-
-## Next Steps for {{game_name}}
-
-<check>If needs_narrative == true:</check>
-<ask>This game type ({{game_type}}) is **{{narrative_importance}}** for narrative.
-
-Your game would benefit from a Narrative Design Document to detail:
-
-- Story structure and beats
-- Character profiles and arcs
-- World lore and history
-- Dialogue framework
-- Environmental storytelling
-
-Would you like to create a Narrative Design Document now?
-
-1. Yes, create Narrative Design Document (recommended)
-2. No, proceed directly to solutioning
-3. Skip for now, I'll do it later
-
-Your choice:</ask>
-
-<check>If user selects option 1:</check>
-<action>LOAD: {installed_path}/narrative/instructions-narrative.md</action>
-<action>Pass GDD context to narrative workflow</action>
-<action>Exit current workflow (narrative will hand off to solutioning when done)</action>
-
-Since this is a Level {{project_level}} game project, you need solutioning for platform/engine architecture.
-
-**Start new chat with solutioning workflow and provide:**
-
-1. This GDD: `{{gdd_output_file}}`
-2. Project analysis: `{{analysis_file}}`
-
-**The solutioning workflow will:**
-
-- Determine game engine/platform (Unity, Godot, Phaser, custom, etc.)
-- Generate solution-architecture.md with engine-specific decisions
-- Create per-epic tech specs
-- Handle platform-specific architecture (from registry.csv game-\* entries)
-
-## Complete Next Steps Checklist
-
-<action>Generate comprehensive checklist based on project analysis</action>
-
-### Phase 1: Solution Architecture & Engine Selection
-
-- [ ] **Run solutioning workflow** (REQUIRED)
-  - Command: `workflow solution-architecture`
-  - Input: GDD.md, project-workflow-analysis.md
-  - Output: solution-architecture.md with engine/platform specifics
-  - Note: Registry.csv will provide engine-specific guidance
-
-### Phase 2: Prototype & Playtesting
-
-- [ ] **Create core mechanic prototype**
-  - Validate game feel
-  - Test control responsiveness
-  - Iterate on game pillars
-
-- [ ] **Playtest early and often**
-  - Internal testing
-  - External playtesting
-  - Feedback integration
-
-### Phase 3: Asset Production
-
-- [ ] **Create asset pipeline**
-  - Art style guides
-  - Technical constraints
-  - Asset naming conventions
-
-- [ ] **Audio integration**
-  - Music composition/licensing
-  - SFX creation
-  - Audio middleware setup
-
-### Phase 4: Development
-
-- [ ] **Generate detailed user stories**
-  - Command: `workflow generate-stories`
-  - Input: GDD.md + solution-architecture.md
-
-- [ ] **Sprint planning**
-  - Vertical slices
-  - Milestone planning
-  - Demo/playable builds
-
-<ask>GDD Complete! Next immediate action:
-
-<check>If needs_narrative == true:</check>
-
-1. Create Narrative Design Document (recommended for {{game_type}})
-2. Start solutioning workflow (engine/architecture)
-3. Create prototype build
-4. Begin asset production planning
-5. Review GDD with team/stakeholders
-6. Exit workflow
-
-<check>Else:</check>
-
-1. Start solutioning workflow (engine/architecture)
-2. Create prototype build
-3. Begin asset production planning
-4. Review GDD with team/stakeholders
-5. Exit workflow
-
-Which would you like to proceed with?</ask>
-
-<check>If user selects narrative option:</check>
-<action>LOAD: {installed_path}/narrative/instructions-narrative.md</action>
-<action>Pass GDD context to narrative workflow</action>
-
-</step>
-
-</workflow>

package/src/modules/bmm/workflows/2-plan/instructions-router.md

@@ -1,222 +0,0 @@
-# PRD Workflow Router Instructions
-
-<workflow>
-
-<critical>This is the INITIAL ASSESSMENT phase - determines which instruction set to load</critical>
-<critical>ALWAYS check for existing project-workflow-analysis.md first</critical>
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-
-<step n="1" goal="Check for existing analysis or perform new assessment">
-
-<action>Check if {output_folder}/project-workflow-analysis.md exists</action>
-
-<check>If exists:</check>
-<action>Load the analysis file</action>
-<action>Check for existing workflow outputs based on level in analysis:</action>
-
-- Level 0: Check for tech-spec.md
-- Level 1-2: Check for PRD.md, epic-stories.md, tech-spec.md
-- Level 3-4: Check for PRD.md, epics.md
-
-<ask>Previous analysis found (Level {{project_level}}).
-
-**Existing documents detected:**
-{{list_existing_docs}}
-
-Options:
-
-1. Continue where left off with existing documents
-2. Start fresh assessment (will archive existing work)
-3. Review and modify previous analysis
-   </ask>
-
-<check>If not exists or starting fresh:</check>
-<action>Proceed to assessment</action>
-
-</step>
-
-<step n="2" goal="Determine workflow path">
-
-<ask>What type of planning do you need?
-
-**Quick Selection:**
-
-- [ ] Full project planning (PRD, Tech Spec, etc.)
-- [ ] UX/UI specification only
-- [ ] Tech spec only (for small changes)
-- [ ] Generate AI Frontend Prompt from existing specs
-
-Select an option or describe your needs:
-</ask>
-
-<check>If "UX/UI specification only":</check>
-<action>LOAD: {installed_path}/ux/instructions-ux.md</action>
-<action>Pass mode="standalone" to UX instructions</action>
-<action>Skip remaining router steps</action>
-
-<check>If "Generate AI Frontend Prompt":</check>
-<action>Check for existing UX spec or PRD</action>
-<invoke-task>{project-root}/bmad/bmm/tasks/ai-fe-prompt.md</invoke-task>
-<action>Exit workflow after prompt generation</action>
-
-<check>If "Tech spec only" or "Full project planning":</check>
-<action>Continue to step 3 for project assessment</action>
-
-</step>
-
-<step n="3" goal="Project context assessment" if="not_ux_only">
-
-<ask>Let's understand your project needs:
-
-**1. Project Type:**
-
-- [ ] Game
-- [ ] Web application
-- [ ] Mobile application
-- [ ] Desktop application
-- [ ] Backend service/API
-- [ ] Library/package
-- [ ] Other
-
-**2. Project Context:**
-
-- [ ] New project (greenfield)
-- [ ] Adding to existing clean codebase
-- [ ] Working with messy/legacy code (needs refactoring)
-
-**3. What are you building?** (brief description)
-</ask>
-
-<action>Detect if project_type == "game"</action>
-
-<check>If project_type == "game":</check>
-<action>Set workflow_type = "gdd"</action>
-<action>Skip level classification (GDD workflow handles all game project levels)</action>
-<action>Jump to step 5 for GDD-specific assessment</action>
-
-<action>Else, based on their description, analyze and suggest scope level:</action>
-
-Examples:
-
-- "Fix login bug" → Suggests Level 0 (single atomic change)
-- "Add OAuth to existing app" → Suggests Level 1 (coherent feature)
-- "Build internal admin dashboard" → Suggests Level 2 (small system)
-- "Create customer portal with payments" → Suggests Level 3 (full product)
-- "Multi-tenant SaaS platform" → Suggests Level 4 (platform)
-
-<ask>Based on your description, this appears to be a **{{suggested_level}}** project.
-
-**3. Quick Scope Guide - Please confirm or adjust:**
-
-- [ ] **Single atomic change** → Bug fix, add endpoint, single file change (Level 0)
-- [ ] **Coherent feature** → Add search, implement SSO, new component (Level 1)
-- [ ] **Small complete system** → Admin tool, team app, prototype (Level 2)
-- [ ] **Full product** → Customer portal, SaaS MVP (Level 3)
-- [ ] **Platform/ecosystem** → Enterprise suite, multi-tenant system (Level 4)
-
-**4. Do you have existing documentation?**
-
-- [ ] Product Brief
-- [ ] Market Research
-- [ ] Technical docs/Architecture
-- [ ] None
-      </ask>
-
-</step>
-
-<step n="4" goal="Determine project level and workflow path">
-
-<action>Based on responses, determine:</action>
-
-**Level Classification:**
-
-- **Level 0**: Single atomic change → tech-spec only
-- **Level 1**: Single feature, 1-10 stories → minimal PRD + tech-spec
-- **Level 2**: Small system, 5-15 stories → focused PRD + tech-spec
-- **Level 3**: Full product, 12-40 stories → full PRD + architect handoff
-- **Level 4**: Platform, 40+ stories → enterprise PRD + architect handoff
-
-<action>For brownfield without docs:</action>
-
-- Levels 0-2: Can proceed with context gathering
-- Levels 3-4: MUST run architect assessment first
-
-</step>
-
-<step n="5" goal="Create workflow analysis document">
-
-<action>Initialize analysis using analysis_template from workflow.yaml</action>
-
-<critical>Capture any technical preferences mentioned during assessment</critical>
-
-Generate comprehensive analysis with all assessment data.
-
-<template-output file="project-workflow-analysis.md">project_type</template-output>
-<template-output file="project-workflow-analysis.md">project_level</template-output>
-<template-output file="project-workflow-analysis.md">instruction_set</template-output>
-<template-output file="project-workflow-analysis.md">scope_description</template-output>
-<template-output file="project-workflow-analysis.md">story_count</template-output>
-<template-output file="project-workflow-analysis.md">epic_count</template-output>
-<template-output file="project-workflow-analysis.md">timeline</template-output>
-<template-output file="project-workflow-analysis.md">field_type</template-output>
-<template-output file="project-workflow-analysis.md">existing_docs</template-output>
-<template-output file="project-workflow-analysis.md">team_size</template-output>
-<template-output file="project-workflow-analysis.md">deployment_intent</template-output>
-<template-output file="project-workflow-analysis.md">expected_outputs</template-output>
-<template-output file="project-workflow-analysis.md">workflow_steps</template-output>
-<template-output file="project-workflow-analysis.md">next_steps</template-output>
-<template-output file="project-workflow-analysis.md">special_notes</template-output>
-<template-output file="project-workflow-analysis.md">technical_preferences</template-output>
-
-</step>
-
-<step n="6" goal="Load appropriate instruction set and handle continuation">
-
-<critical>Based on project type and level, load ONLY the needed instructions:</critical>
-
-<check>If workflow_type == "gdd" (Game projects):</check>
-<action>LOAD: {installed_path}/gdd/instructions-gdd.md</action>
-<check>If continuing:</check>
-
-- Load existing GDD.md if present
-- Check which sections are complete
-- Resume from last completed section
-- GDD workflow handles all game project levels internally
-
-<check>If Level 0:</check>
-<action>LOAD: {installed_path}/tech-spec/instructions-sm.md</action>
-<check>If continuing:</check>
-
-- Load existing tech-spec.md
-- Allow user to review and modify
-- Complete any missing sections
-
-<check>If Level 1-2:</check>
-<action>LOAD: {installed_path}/prd/instructions-med.md</action>
-<check>If continuing:</check>
-
-- Load existing PRD.md if present
-- Check which sections are complete
-- Resume from last completed section
-- If PRD done, show solutioning handoff instructions
-
-<check>If Level 3-4:</check>
-<action>LOAD: {installed_path}/prd/instructions-lg.md</action>
-<check>If continuing:</check>
-
-- Load existing PRD.md and epics.md
-- Identify last completed step (check template variables)
-- Resume from incomplete sections
-- If all done, show architect handoff instructions
-
-<critical>Pass continuation context to loaded instruction set:</critical>
-
-- continuation_mode: true/false
-- last_completed_step: {{step_number}}
-- existing_documents: {{document_list}}
-
-<critical>The loaded instruction set should check continuation_mode and adjust accordingly</critical>
-
-</step>
-
-</workflow>