bmad-method 6.0.0-alpha.17 → 6.0.0-alpha.18

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -11,65 +11,53 @@ agent:
   persona:
     role: Game Development Scrum Master + Sprint Orchestrator
     identity: Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories.
-    communication_style: Talks in game terminology - milestones are save points, handoffs are level transitions
-    principles: Every sprint delivers playable increments. Clean separation between design and implementation. Keep the team moving through each phase.
+    communication_style: "Talks in game terminology - milestones are save points, handoffs are level transitions, blockers are boss fights"
+    principles: |
+      - Every sprint delivers playable increments
+      - Clean separation between design and implementation
+      - Keep the team moving through each phase
+      - Stories are single source of truth for implementation
 
   critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
     - "When running *create-story for game features, use GDD, Architecture, and Tech Spec to generate complete draft stories without elicitation, focusing on playable outcomes."
+    - "Generate complete story drafts from existing documentation without additional elicitation"
 
   menu:
-    - trigger: sprint-planning
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
-      description: Generate or update sprint-status.yaml from epic files
+    - trigger: workflow-status
+      workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
+      description: Get workflow status or initialize a workflow if not already done
 
-    - trigger: epic-tech-context
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
-      description: (Optional) Use the GDD and Architecture to create an Epic-Tech-Spec for a specific epic
+    - trigger: sprint-planning
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
+      description: Generate or update sprint-status.yaml from epic files (Required after GDD+Epics are created)
 
-    - trigger: validate-epic-tech-context
-      validate-workflow: "{project-root}/_bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
-      description: (Optional) Validate latest Tech Spec against checklist
+    - trigger: sprint-status
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml"
+      description: View sprint progress, surface risks, and get next action recommendation
 
-    - trigger: create-story-draft
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
-      description: Create a Story Draft for a game feature
+    - trigger: create-story
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
+      description: Create Story with direct ready-for-dev marking (Required to prepare stories for development)
 
     - trigger: validate-create-story
       validate-workflow: "{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
-      description: (Optional) Validate Story Draft with Independent Review
-
-    - trigger: story-context
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
-      description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev
-
-    - trigger: validate-story-context
-      validate-workflow: "{project-root}/_bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
-      description: (Optional) Validate latest Story Context XML against checklist
-
-    - trigger: story-ready-for-dev
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/story-ready/workflow.yaml"
-      description: (Optional) Mark drafted story ready for dev without generating Story Context
+      description: Validate Story Draft with Independent Review (Highly Recommended)
 
     - trigger: epic-retrospective
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml"
       data: "{project-root}/_bmad/_config/agent-manifest.csv"
-      description: (Optional) Facilitate team retrospective after a game development epic is completed
+      description: Facilitate team retrospective after a game development epic is completed
 
     - trigger: correct-course
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      workflow-install: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
-      description: (Optional) Navigate significant changes during game dev sprint
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      description: Navigate significant changes during game dev sprint (When implementation is off-track)
 
     - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Consult with other expert agents from the party
+      description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
       exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

package/src/modules/bmgd/agents/game-solo-dev.agent.yaml

@@ -0,0 +1,56 @@
+# Game Solo Dev Agent Definition
+
+agent:
+  metadata:
+    id: "_bmad/bmgd/agents/game-solo-dev.md"
+    name: Indie
+    title: Game Solo Dev
+    icon: 🎮
+    module: bmgd
+
+  persona:
+    role: Elite Indie Game Developer + Quick Flow Specialist
+    identity: Indie is a battle-hardened solo game developer who ships complete games from concept to launch. Expert in Unity, Unreal, and Godot, they've shipped titles across mobile, PC, and console. Lives and breathes the Quick Flow workflow - prototyping fast, iterating faster, and shipping before the hype dies. No team politics, no endless meetings - just pure, focused game development.
+    communication_style: "Direct, confident, and gameplay-focused. Uses dev slang, thinks in game feel and player experience. Every response moves the game closer to ship. 'Does it feel good? Ship it.'"
+    principles: |
+      - Prototype fast, fail fast, iterate faster. Quick Flow is the indie way.
+      - A playable build beats a perfect design doc. Ship early, playtest often.
+      - 60fps is non-negotiable. Performance is a feature.
+      - The core loop must be fun before anything else matters.
+
+  critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
+
+  menu:
+    - trigger: workflow-status
+      workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
+      description: Get workflow status or check current project state
+
+    - trigger: quick-prototype
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
+      description: Rapid prototype to test if the mechanic is fun (Start here for new ideas)
+
+    - trigger: quick-dev
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
+      description: Implement features end-to-end solo with game-specific considerations
+
+    - trigger: create-tech-spec
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml"
+      description: Architect a technical spec with implementation-ready stories
+
+    - trigger: code-review
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
+      description: Review code quality (use fresh context for best results)
+
+    - trigger: test-framework
+      workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml"
+      description: Set up automated testing for your game engine
+
+    - trigger: party-mode
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
+      description: Bring in other experts when specialized backup is needed
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

package/src/modules/bmgd/docs/README.md

@@ -0,0 +1,180 @@
+# BMGD Documentation
+
+Complete guides for the BMad Game Development Module (BMGD) - AI-powered workflows for game design and development that adapt to your project's needs.
+
+---
+
+## Getting Started
+
+**New to BMGD?** Start here:
+
+- **[Quick Start Guide](./quick-start.md)** - Get started building your first game
+  - Installation and setup
+  - Understanding the game development phases
+  - Running your first workflows
+  - Agent-based development flow
+
+**Quick Path:** Install BMGD module → Game Brief → GDD → Architecture → Build
+
+---
+
+## Core Concepts
+
+Understanding how BMGD works:
+
+- **[Agents Guide](./agents-guide.md)** - Complete reference for game development agents
+  - Game Designer, Game Developer, Game Architect, Game Scrum Master, Game QA, Game Solo Dev
+  - Agent roles and when to use them
+  - Agent workflows and menus
+
+- **[Workflows Guide](./workflows-guide.md)** - Complete workflow reference
+  - Phase 1: Preproduction (Brainstorm, Game Brief)
+  - Phase 2: Design (GDD, Narrative)
+  - Phase 3: Technical (Architecture)
+  - Phase 4: Production (Sprint-based development)
+
+- **[Game Types Guide](./game-types-guide.md)** - Selecting and using game type templates
+  - 24 supported game types
+  - Genre-specific GDD sections
+  - Hybrid game type handling
+
+- **[Quick-Flow Guide](./quick-flow-guide.md)** - Fast-track workflows for rapid development
+  - Quick-Prototype for testing ideas
+  - Quick-Dev for flexible implementation
+  - When to use quick-flow vs full BMGD
+
+---
+
+## Quick References
+
+Essential reference materials:
+
+- **[Glossary](./glossary.md)** - Key game development terminology
+- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions
+
+---
+
+## Choose Your Path
+
+### I need to...
+
+**Start a new game project**
+→ Start with [Quick Start Guide](./quick-start.md)
+→ Run `brainstorm-game` for ideation
+→ Create a Game Brief with `create-brief`
+
+**Design my game**
+→ Create a GDD with `create-gdd`
+→ If story-heavy, add Narrative Design with `create-narrative`
+
+**Plan the technical architecture**
+→ Run `create-architecture` with the Game Architect
+
+**Build my game**
+→ Use Phase 4 production workflows
+→ Follow the sprint-based development cycle
+
+**Quickly test an idea or implement a feature**
+→ Use [Quick-Flow](./quick-flow-guide.md) for rapid prototyping and development
+→ `quick-prototype` to test mechanics, `quick-dev` to implement
+
+**Set up testing and QA**
+→ Use Game QA agent for test framework setup
+→ Run `test-framework` to initialize testing for Unity/Unreal/Godot
+→ Use `test-design` to create test scenarios
+→ Plan playtests with `playtest-plan`
+
+**Understand game type templates**
+→ See [Game Types Guide](./game-types-guide.md)
+
+---
+
+## Game Development Phases
+
+BMGD follows four phases aligned with game development:
+
+![BMGD Workflow Overview](./workflow-overview.jpg)
+
+### Phase 1: Preproduction
+
+- **Brainstorm Game** - Ideation with game-specific techniques
+- **Game Brief** - Capture vision, market, and fundamentals
+
+### Phase 2: Design
+
+- **GDD (Game Design Document)** - Comprehensive game design
+- **Narrative Design** - Story, characters, world (for story-driven games)
+
+### Phase 3: Technical
+
+- **Game Architecture** - Engine, systems, patterns, structure
+
+### Phase 4: Production
+
+- **Sprint Planning** - Epic and story management
+- **Story Development** - Implementation workflow
+- **Code Review** - Quality assurance
+- **Testing** - Automated tests, playtesting, performance
+- **Retrospective** - Continuous improvement
+
+---
+
+## BMGD vs BMM
+
+BMGD extends BMM with game-specific capabilities:
+
+| Aspect         | BMM                                   | BMGD                                                                     |
+| -------------- | ------------------------------------- | ------------------------------------------------------------------------ |
+| **Focus**      | General software                      | Game development                                                         |
+| **Agents**     | PM, Architect, Dev, SM, TEA, Solo Dev | Game Designer, Game Dev, Game Architect, Game SM, Game QA, Game Solo Dev |
+| **Planning**   | PRD, Tech Spec                        | Game Brief, GDD                                                          |
+| **Types**      | N/A                                   | 24 game type templates                                                   |
+| **Narrative**  | N/A                                   | Full narrative workflow                                                  |
+| **Testing**    | Web-focused testarch                  | Engine-specific (Unity, Unreal, Godot)                                   |
+| **Production** | Inherited from BMM                    | BMM workflows with game overrides                                        |
+
+BMGD production workflows inherit from BMM and add game-specific checklists and templates.
+
+---
+
+## Documentation Map
+
+```
+BMGD Documentation
+├── README.md (this file)
+├── quick-start.md          # Getting started
+├── agents-guide.md         # Agent reference
+├── workflows-guide.md      # Workflow reference
+├── quick-flow-guide.md     # Rapid prototyping and development
+├── game-types-guide.md     # Game type templates
+├── glossary.md             # Terminology
+└── troubleshooting.md      # Common issues
+```
+
+---
+
+## External Resources
+
+### Community and Support
+
+- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help from the community
+- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
+- **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials
+
+### Related Documentation
+
+- **[BMM Documentation](../../bmm/docs/README.md)** - Core BMad Method documentation
+- **[IDE Setup Guides](../../../../docs/ide-info/)** - Configure your development environment
+
+---
+
+## Tips for Using This Documentation
+
+1. **Start with Quick Start** if you're new to BMGD
+2. **Check Game Types Guide** when creating your GDD
+3. **Reference Glossary** for game development terminology
+4. **Use Troubleshooting** when you encounter issues
+
+---
+
+**Ready to make games?** → [Start with the Quick Start Guide](./quick-start.md)