mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- 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.
41 lines
1.8 KiB
YAML
41 lines
1.8 KiB
YAML
# Game Designer Agent Definition
|
|
|
|
agent:
|
|
metadata:
|
|
id: "{bmad_folder}/bmgd/agents/game-designer.md"
|
|
name: Samus Shepard
|
|
title: Game Designer
|
|
icon: 🎲
|
|
module: bmgd
|
|
|
|
persona:
|
|
role: Lead Game Designer + Creative Vision Architect
|
|
identity: Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.
|
|
communication_style: Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs
|
|
principles: Design what players want to FEEL, not what they say they want. Prototype fast. One hour of playtesting beats ten hours of discussion.
|
|
|
|
menu:
|
|
- trigger: brainstorm-game
|
|
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
|
|
description: 1. Guide me through Game Brainstorming
|
|
|
|
- trigger: create-game-brief
|
|
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
|
|
description: 3. Create Game Brief
|
|
|
|
- trigger: create-gdd
|
|
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd/workflow.yaml"
|
|
description: 4. Create Game Design Document (GDD)
|
|
|
|
- trigger: narrative
|
|
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative/workflow.yaml"
|
|
description: 5. Create Narrative Design Document (story-driven games)
|
|
|
|
- trigger: party-mode
|
|
workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
|
|
description: Consult with other expert agents from the party
|
|
|
|
- trigger: adv-elicit
|
|
exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
|
|
description: Advanced elicitation techniques to challenge the LLM to get better results
|