bmad-method 6.0.0-alpha.19 → 6.0.0-alpha.20

package/src/modules/bmgd/README.md

@@ -1,209 +0,0 @@
-# BMad Game Development (BMGD)
-
-A comprehensive game development toolkit providing specialized agents and workflows for creating games from initial concept through production.
-
-## Overview
-
-The BMGD module brings together game-specific development workflows organized around industry-standard development phases:
-
-- **Preproduction** - Concept development, brainstorming, game brief creation
-- **Design** - Game Design Document (GDD) and narrative design
-- **Technical** - Game architecture and technical specifications
-- **Production** - Sprint-based implementation using BMM workflows
-
-## Installation
-
-```bash
-bmad install bmgd
-```
-
-During installation, you'll be asked to configure:
-
-- Game project name
-- Document storage locations
-- Development experience level
-- Primary target platform
-
-## Components
-
-### Agents (4)
-
-**Game Designer** 🎨
-Creative vision and game design documentation specialist. Creates compelling GDDs and defines game mechanics.
-
-**Game Developer** 🕹️
-Senior implementation specialist with expertise across Unity, Unreal, and custom engines. Handles gameplay programming, physics, AI, and optimization.
-
-**Game Architect** 🏗️
-Technical systems and infrastructure expert. Designs scalable game architecture and engine-level solutions.
-
-**Game Dev Scrum Master** 🎯
-Sprint orchestrator specialized in game development workflows. Coordinates multi-disciplinary teams and translates GDDs into actionable development stories.
-
-### Team Bundle
-
-**Team Game Development** 🎮
-Pre-configured team including Game Designer, Game Developer, and Game Architect for comprehensive game projects.
-
-### Workflows
-
-#### Phase 1: Preproduction
-
-- **brainstorm-game** - Interactive game concept brainstorming
-- **game-brief** - Create focused game brief document
-
-#### Phase 2: Design
-
-- **gdd** - Generate comprehensive Game Design Document
-- **narrative** - Design narrative structure and story elements
-
-#### Phase 3: Technical
-
-- **game-architecture** - Define technical architecture (adapted from BMM architecture workflow)
-
-#### Phase 4: Production
-
-Production workflows are provided by the BMM module and accessible through the Game Dev Scrum Master agent:
-
-- Sprint planning
-- Story creation and management
-- Epic technical specifications
-- Code review and retrospectives
-
-## Quick Start
-
-### 1. Start with Concept Development
-
-```
-Load agent: game-designer
-Run workflow: brainstorm-game
-```
-
-### 2. Create Game Brief
-
-```
-Run workflow: game-brief
-```
-
-### 3. Develop Game Design Document
-
-```
-Run workflow: gdd
-```
-
-### 4. Define Technical Architecture
-
-```
-Load agent: game-architect
-Run workflow: game-architecture
-```
-
-### 5. Begin Production Sprints
-
-```
-Load agent: game-scrum-master
-Run: *sprint-planning
-```
-
-## Module Structure
-
-```
-bmgd/
-├── agents/
-│   ├── game-designer.agent.yaml
-│   ├── game-dev.agent.yaml
-│   ├── game-architect.agent.yaml
-│   └── game-scrum-master.agent.yaml
-├── teams/
-│   └── team-gamedev.yaml
-├── workflows/
-│   ├── 1-preproduction/
-│   │   ├── brainstorm-game/
-│   │   └── game-brief/
-│   ├── 2-design/
-│   │   ├── gdd/
-│   │   └── narrative/
-│   ├── 3-technical/
-│   │   └── game-architecture/
-│   └── 4-production/
-│       (Uses BMM workflows via cross-module references)
-├── templates/
-├── data/
-├── module.yaml
-└── _module-installer/
-    └── installer.js (optional)
-```
-
-## Configuration
-
-After installation, configure the module in `_bmad/bmgd/config.yaml`
-
-Key settings:
-
-- **game_project_name** - Your game's working title
-- **game_design_docs** - Location for GDD and design documents
-- **game_tech_docs** - Location for technical documentation
-- **game_story_location** - Location for development user stories
-- **game_dev_experience** - Your experience level (affects agent communication)
-- **primary_platform** - Target platform (PC, mobile, console, web, multi-platform)
-
-## Workflow Integration
-
-BMGD leverages the BMM module for production/implementation workflows. The Game Dev Scrum Master agent provides access to:
-
-- Sprint planning and management
-- Story creation from GDD specifications
-- Epic technical context generation
-- Code review workflows
-- Retrospectives and course correction
-
-This separation allows BMGD to focus on game-specific design and architecture while using battle-tested agile implementation workflows.
-
-## Example: Creating a 2D Platformer
-
-1. **Brainstorm** concepts with `brainstorm-game` workflow
-2. **Define** the vision with `game-brief` workflow
-3. **Design** mechanics and progression with `gdd` workflow
-4. **Craft** character arcs and story with `narrative` workflow
-5. **Architect** technical systems with `game-architecture` workflow
-6. **Implement** via Game Dev Scrum Master sprint workflows
-
-## Development Roadmap
-
-### Phase 1: Core Enhancement
-
-- [ ] Customize game-architecture workflow for game-specific patterns
-- [ ] Add game-specific templates (level design, character sheets, etc.)
-- [ ] Create asset pipeline workflows
-
-### Phase 2: Expanded Features
-
-- [ ] Add monetization planning workflows
-- [ ] Create playtesting and feedback workflows
-- [ ] Develop game balancing tools
-
-### Phase 3: Platform Integration
-
-- [ ] Add platform-specific deployment workflows
-- [ ] Create build and release automation
-- [ ] Develop live ops workflows
-
-## Contributing
-
-To extend this module:
-
-1. Add new agents using `/bmad:bmb:workflows:create-agent`
-2. Add new workflows using `/bmad:bmb:workflows:create-workflow`
-3. Submit improvements via pull request
-
-## Dependencies
-
-- **BMM Module** - Required for production/implementation workflows
-
-## Author
-
-Extracted and refined from BMM module on 2025-11-05
-
-## License
-
-Part of the BMAD Method ecosystem

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/checklist.md

@@ -1,25 +0,0 @@
-# Quick-Dev Checklist
-
-## Before Implementation
-
-- [ ] Context loaded (tech-spec or user guidance)
-- [ ] Files to modify identified
-- [ ] Patterns understood
-
-## Implementation
-
-- [ ] All tasks completed
-- [ ] Code follows existing patterns
-- [ ] Error handling appropriate
-
-## Testing
-
-- [ ] Tests written (where appropriate)
-- [ ] All tests passing
-- [ ] No regressions
-
-## Completion
-
-- [ ] Acceptance criteria satisfied
-- [ ] Tech-spec updated (if applicable)
-- [ ] Summary provided to user

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md

@@ -1,202 +0,0 @@
-# Quick-Dev - Flexible Development Workflow
-
-<workflow>
-
-<critical>Communicate in {communication_language}, tailored to {user_skill_level}</critical>
-<critical>Execute continuously until COMPLETE - do not stop for milestones</critical>
-<critical>Flexible - handles tech-specs OR direct instructions</critical>
-<critical>ALWAYS respect {project_context} if it exists - it defines project standards</critical>
-
-<checkpoint-handlers>
-  <on-select key="a">Load and execute {advanced_elicitation}, then return</on-select>
-  <on-select key="p">Load and execute {party_mode_workflow}, then return</on-select>
-  <on-select key="t">Load and execute {create_tech_spec_workflow}</on-select>
-</checkpoint-handlers>
-
-<step n="1" goal="Load project context and determine execution mode">
-
-<action>Check if {project_context} exists. If yes, load it - this is your foundational reference for ALL implementation decisions (patterns, conventions, architecture).</action>
-
-<action>Parse user input:
-
-**Mode A: Tech-Spec** - e.g., `quick-dev tech-spec-auth.md`
-→ Load spec, extract tasks/context/AC, goto step 3
-
-**Mode B: Direct Instructions** - e.g., `refactor src/foo.ts...`
-→ Offer planning choice
-</action>
-
-<check if="Mode A">
-  <action>Load tech-spec, extract tasks/context/AC</action>
-  <goto>step_3</goto>
-</check>
-
-<check if="Mode B">
-
-  <!-- Escalation Threshold: Lightweight check - should we invoke scale-adaptive? -->
-
-<action>Evaluate escalation threshold against user input (minimal tokens, no file loading):
-
-**Triggers escalation** (if 2+ signals present):
-
-- Multiple components mentioned (e.g., dashboard + api + database)
-- System-level language (e.g., platform, integration, architecture)
-- Uncertainty about approach (e.g., "how should I", "best way to")
-- Multi-layer scope (e.g., UI + backend + data together)
-- Extended timeframe (e.g., "this week", "over the next few days")
-
-**Reduces signal:**
-
-- Simplicity markers (e.g., "just", "quickly", "fix", "bug", "typo", "simple", "basic", "minor")
-- Single file/component focus
-- Confident, specific request
-
-Use holistic judgment, not mechanical keyword matching.</action>
-
-  <!-- No Escalation: Simple request, offer existing choice -->
-  <check if="escalation threshold NOT triggered">
-    <ask>**[t] Plan first** - Create tech-spec then implement
-**[e] Execute directly** - Start now</ask>
-
-    <check if="t">
-      <action>Load and execute {create_tech_spec_workflow}</action>
-      <action>Continue to implementation after spec complete</action>
-    </check>
-
-    <check if="e">
-      <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
-      <goto>step_2</goto>
-    </check>
-
-  </check>
-
-  <!-- Escalation Triggered: Load scale-adaptive and evaluate level -->
-  <check if="escalation threshold triggered">
-    <action>Load {project_levels} and evaluate user input against detection_hints.keywords</action>
-    <action>Determine level (0-4) using scale-adaptive definitions</action>
-
-    <!-- Level 0: Scale-adaptive confirms simple, fall back to standard choice -->
-    <check if="level 0">
-      <ask>**[t] Plan first** - Create tech-spec then implement
-
-**[e] Execute directly** - Start now</ask>
-
-      <check if="t">
-        <action>Load and execute {create_tech_spec_workflow}</action>
-        <action>Continue to implementation after spec complete</action>
-      </check>
-
-      <check if="e">
-        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
-        <goto>step_2</goto>
-      </check>
-    </check>
-
-    <check if="level 1 or 2 or couldn't determine level">
-      <ask>This looks like a focused feature with multiple components.
-
-**[t] Create tech-spec first** (recommended)
-**[w] Seems bigger than quick-dev** — see what BMad Method recommends (workflow-init)
-**[e] Execute directly**</ask>
-
-      <check if="t">
-        <action>Load and execute {create_tech_spec_workflow}</action>
-        <action>Continue to implementation after spec complete</action>
-      </check>
-
-      <check if="w">
-        <action>Load and execute {workflow_init}</action>
-        <action>EXIT quick-dev - user has been routed to BMad Method</action>
-      </check>
-
-      <check if="e">
-        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
-        <goto>step_2</goto>
-      </check>
-    </check>
-
-    <!-- Level 3+: BMad Method territory, recommend workflow-init -->
-    <check if="level 3 or higher">
-      <ask>This sounds like platform/system work.
-
-**[w] Start BMad Method** (recommended) (workflow-init)
-**[t] Create tech-spec** (lighter planning)
-**[e] Execute directly** - feeling lucky</ask>
-
-      <check if="w">
-        <action>Load and execute {workflow_init}</action>
-        <action>EXIT quick-dev - user has been routed to BMad Method</action>
-      </check>
-
-      <check if="t">
-        <action>Load and execute {create_tech_spec_workflow}</action>
-        <action>Continue to implementation after spec complete</action>
-      </check>
-
-      <check if="e">
-        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
-        <goto>step_2</goto>
-      </check>
-    </check>
-
-  </check>
-
-</check>
-
-</step>
-
-<step n="2" goal="Quick context gathering (direct mode)">
-
-<action>Identify files to modify, find relevant patterns, note dependencies</action>
-
-<action>Create mental plan: tasks, acceptance criteria, files to touch</action>
-
-</step>
-
-<step n="3" goal="Execute implementation" id="step_3">
-
-<action>For each task:
-
-1. **Load Context** - read files from spec or relevant to change
-2. **Implement** - follow patterns, handle errors, follow conventions
-3. **Test** - write tests, run existing tests, verify AC
-4. **Mark Complete** - check off task [x], continue
-   </action>
-
-<action if="3 failures">HALT and request guidance</action>
-<action if="tests fail">Fix before continuing</action>
-
-<critical>Continue through ALL tasks without stopping</critical>
-
-</step>
-
-<step n="4" goal="Verify and complete">
-
-<action>Verify: all tasks [x], tests passing, AC satisfied, patterns followed</action>
-
-<check if="using tech-spec">
-  <action>Update tech-spec status to "Completed", mark all tasks [x]</action>
-</check>
-
-<output>**Implementation Complete!**
-
-**Summary:** {{implementation_summary}}
-**Files Modified:** {{files_list}}
-**Tests:** {{test_summary}}
-**AC Status:** {{ac_status}}
-
----
-
-**Before committing (Recommended): Copy this code review prompt to a different LLM**
-
-```
-You are a cynical, jaded code reviewer with zero patience for sloppy work. These uncommitted changes were submitted by a clueless weasel and you expect to find problems. Find at least five issues to fix or improve in it. Number them. Be skeptical of everything.
-```
-
-</output>
-
-<action>You must explain what was implemented based on {user_skill_level}</action>
-
-</step>
-
-</workflow>

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml

@@ -1,33 +0,0 @@
-# Quick-Flow: Quick-Dev
-name: quick-dev
-description: "Flexible development - execute tech-specs OR direct instructions with optional planning."
-author: "BMad"
-
-# Config
-config_source: "{project-root}/_bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-sprint_artifacts: "{config_source}:sprint_artifacts"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Project context
-project_context: "**/project-context.md"
-
-# Workflow components
-installed_path: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev"
-instructions: "{installed_path}/instructions.md"
-checklist: "{installed_path}/checklist.md"
-
-# Related workflows
-create_tech_spec_workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
-party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-
-# Routing resources (lazy-loaded)
-project_levels: "{project-root}/_bmad/bmm/workflows/workflow-status/project-levels.yaml"
-workflow_init: "{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml"
-
-standalone: true
-web_bundle: false