53 lines
2.0 KiB
YAML
Raw Normal View History

Major Enhancements: - Installation path is now fully configurable, allowing users to specify custom installation directories during setup - Default installation location changed to .bmad (hidden directory) for cleaner project root organization Web Bundle Improvements: - All web bundles (single agent and team) now include party mode support for multi-agent collaboration! - Advanced elicitation capabilities integrated into standalone agents - All bundles enhanced with party mode agent manifests - Added default-party.csv files to bmm, bmgd, and cis module teams - The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file - New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad) Phase 4 Workflow Updates (In Progress): - Initiated shift to separate phase 4 implementation artifacts from documentation - Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder - Installer questions and configuration added for artifact path selection - Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates Additional Changes: - New agent and action command header models for standardization - Enhanced web-bundle-activation-steps fragment - Updated web-bundler.js to support new structure - VS Code settings updated for new .bmad directory - Party mode instructions and workflow enhanced for better orchestration IDE Installer Updates: - Show version number of installer in cli - improved Installer UX - Gemini TOML Improved to have clear loading instructions with @ commands - All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
# Game Development - Use BMGD Module
# Game development workflows have been moved to the BMad Game Development module
project_type: "game"
level: "all"
field_type: "any"
description: "⚠️ Game development requires the BMGD module"
error_message: |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎮 **GAME DEVELOPMENT DETECTED**
Game development workflows are now part of the **BMad Game Development (BMGD)** module,
which provides specialized workflows and agents for game creation.
**To proceed with game development:**
1. Install the BMGD module:
```bash
bmad install bmgd
```
2. The BMGD module includes:
- Game Designer, Game Developer, Game Architect agents
- Game Dev Scrum Master for sprint coordination
- Industry-standard game dev workflows:
• Phase 1 (Preproduction): brainstorm-game, game-brief
• Phase 2 (Design): GDD, narrative design
• Phase 3 (Technical): game architecture
• Phase 4 (Production): sprint planning, story management
3. After installation, load the Game Designer or Game Dev Scrum Master agent
to begin your game development workflow
**Why a separate module?**
- Game development follows different phases than software development
- Specialized agents understand game-specific terminology and patterns
- Workflows configured for game development needs (playtesting, balancing, etc.)
- Can be used standalone or alongside BMM for complete coverage
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
# Placeholder phases - this file should not be used for actual workflow tracking
# Users should install BMGD module instead
phases:
- phase: 1
name: "ERROR - Install BMGD Module"
workflows:
- id: "install-bmgd"
required: true
note: "Run: bmad install bmgd"