ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: alphabetize agent commands and dependencies for improved organization

Browse Source 
- Alphabetized all commands in agent files while maintaining help first and exit last
- Alphabetized all dependency categories (checklists, data, tasks, templates, utils, workflows)
- Alphabetized items within each dependency category across all 10 core agents:
  - analyst.md: commands and dependencies reorganized
  - architect.md: commands and dependencies reorganized
  - bmad-master.md: commands and dependencies reorganized, fixed YAML parsing issue
  - bmad-orchestrator.md: commands and dependencies reorganized
  - dev.md: commands and dependencies reorganized
  - pm.md: commands and dependencies reorganized
  - po.md: commands and dependencies reorganized
  - qa.md: commands and dependencies reorganized
  - sm.md: commands and dependencies reorganized
  - ux-expert.md: commands and dependencies reorganized
- Fixed YAML parsing error in bmad-master.md by properly quoting activation instructions
- Rebuilt all agent bundles and team bundles successfully
- Updated expansion pack bundles including new creative writing agents

This improves consistency and makes it easier to locate specific commands and dependencies
across all agent configurations.
This commit is contained in:
Brian Madison
2025-08-17 00:30:04 -05:00
parent ac09300075
commit b6fe44b16e
44 changed files with 31314 additions and 17653 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt vendored
View File

@@ -981,8 +981,8 @@ template:
version: 2.0
output:
format: markdown
filename: 'docs/{{game_name}}-game-design-document.md'
title: '{{game_title}} Game Design Document (GDD)'
filename: "docs/{{game_name}}-game-design-document.md"
title: "{{game_title}} Game Design Document (GDD)"
workflow:
mode: interactive
@@ -1019,7 +1019,7 @@ sections:
title: Unique Selling Points
instruction: List 3-5 key features that differentiate this game from competitors
type: numbered-list
template: '{{usp}}'
template: "{{usp}}"
- id: core-gameplay
title: Core Gameplay
@@ -1064,7 +1064,7 @@ sections:
repeatable: true
sections:
- id: mechanic
title: '{{mechanic_name}}'
title: "{{mechanic_name}}"
template: |
**Description:** {{detailed_description}}
@@ -1129,7 +1129,7 @@ sections:
repeatable: true
sections:
- id: level-type
title: '{{level_type_name}}'
title: "{{level_type_name}}"
template: |
**Purpose:** {{gameplay_purpose}}
**Duration:** {{target_time}}
@@ -1230,10 +1230,10 @@ sections:
instruction: Break down the development into phases that can be converted to epics
sections:
- id: phase-1-core-systems
title: 'Phase 1: Core Systems ({{duration}})'
title: "Phase 1: Core Systems ({{duration}})"
sections:
- id: foundation-epic
title: 'Epic: Foundation'
title: "Epic: Foundation"
type: bullet-list
template: |
- Engine setup and configuration
@@ -1241,41 +1241,41 @@ sections:
- Core input handling
- Asset loading pipeline
- id: core-mechanics-epic
title: 'Epic: Core Mechanics'
title: "Epic: Core Mechanics"
type: bullet-list
template: |
- {{primary_mechanic}} implementation
- Basic physics and collision
- Player controller
- id: phase-2-gameplay-features
title: 'Phase 2: Gameplay Features ({{duration}})'
title: "Phase 2: Gameplay Features ({{duration}})"
sections:
- id: game-systems-epic
title: 'Epic: Game Systems'
title: "Epic: Game Systems"
type: bullet-list
template: |
- {{mechanic_2}} implementation
- {{mechanic_3}} implementation
- Game state management
- id: content-creation-epic
title: 'Epic: Content Creation'
title: "Epic: Content Creation"
type: bullet-list
template: |
- Level loading system
- First playable levels
- Basic UI implementation
- id: phase-3-polish-optimization
title: 'Phase 3: Polish & Optimization ({{duration}})'
title: "Phase 3: Polish & Optimization ({{duration}})"
sections:
- id: performance-epic
title: 'Epic: Performance'
title: "Epic: Performance"
type: bullet-list
template: |
- Optimization and profiling
- Mobile platform testing
- Memory management
- id: user-experience-epic
title: 'Epic: User Experience'
title: "Epic: User Experience"
type: bullet-list
template: |
- Audio implementation
@@ -1317,7 +1317,7 @@ sections:
title: References
instruction: List any competitive analysis, inspiration, or research sources
type: bullet-list
template: '{{reference}}'
template: "{{reference}}"
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
@@ -1327,8 +1327,8 @@ template:
version: 2.0
output:
format: markdown
filename: 'docs/{{game_name}}-level-design-document.md'
title: '{{game_title}} Level Design Document'
filename: "docs/{{game_name}}-level-design-document.md"
title: "{{game_title}} Level Design Document"
workflow:
mode: interactive
@@ -1389,7 +1389,7 @@ sections:
repeatable: true
sections:
- id: level-category
title: '{{category_name}} Levels'
title: "{{category_name}} Levels"
template: |
**Purpose:** {{gameplay_purpose}}
@@ -1694,19 +1694,19 @@ sections:
title: Playtesting Checklist
type: checklist
items:
- 'Level completes within target time range'
- 'All mechanics function correctly'
- 'Difficulty feels appropriate for level category'
- 'Player guidance is clear and effective'
- 'No exploits or sequence breaks (unless intended)'
- "Level completes within target time range"
- "All mechanics function correctly"
- "Difficulty feels appropriate for level category"
- "Player guidance is clear and effective"
- "No exploits or sequence breaks (unless intended)"
- id: player-experience-testing
title: Player Experience Testing
type: checklist
items:
- 'Tutorial levels teach effectively'
- 'Challenge feels fair and rewarding'
- 'Flow and pacing maintain engagement'
- 'Audio and visual feedback support gameplay'
- "Tutorial levels teach effectively"
- "Challenge feels fair and rewarding"
- "Flow and pacing maintain engagement"
- "Audio and visual feedback support gameplay"
- id: balance-validation
title: Balance Validation
template: |
@@ -1814,8 +1814,8 @@ template:
version: 2.0
output:
format: markdown
filename: 'docs/{{game_name}}-game-brief.md'
title: '{{game_title}} Game Brief'
filename: "docs/{{game_name}}-game-brief.md"
title: "{{game_title}} Game Brief"
workflow:
mode: interactive
@@ -2101,21 +2101,21 @@ sections:
title: Development Roadmap
sections:
- id: phase-1-preproduction
title: 'Phase 1: Pre-Production ({{duration}})'
title: "Phase 1: Pre-Production ({{duration}})"
type: bullet-list
template: |
- Detailed Game Design Document creation
- Technical architecture planning
- Art style exploration and pipeline setup
- id: phase-2-prototype
title: 'Phase 2: Prototype ({{duration}})'
title: "Phase 2: Prototype ({{duration}})"
type: bullet-list
template: |
- Core mechanic implementation
- Technical proof of concept
- Initial playtesting and iteration
- id: phase-3-production
title: 'Phase 3: Production ({{duration}})'
title: "Phase 3: Production ({{duration}})"
type: bullet-list
template: |
- Full feature development

12
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt vendored
View File

@@ -197,8 +197,8 @@ template:
version: 2.0
output:
format: markdown
filename: 'docs/{{game_name}}-game-architecture.md'
title: '{{game_title}} Game Architecture Document'
filename: "docs/{{game_name}}-game-architecture.md"
title: "{{game_title}} Game Architecture Document"
workflow:
mode: interactive
@@ -422,7 +422,7 @@ sections:
repeatable: true
sections:
- id: mechanic-system
title: '{{mechanic_name}} System'
title: "{{mechanic_name}} System"
template: |
**Purpose:** {{system_purpose}}
@@ -719,7 +719,7 @@ sections:
instruction: Break down the architecture implementation into phases that align with the GDD development phases
sections:
- id: phase-1-foundation
title: 'Phase 1: Foundation ({{duration}})'
title: "Phase 1: Foundation ({{duration}})"
sections:
- id: phase-1-core
title: Core Systems
@@ -737,7 +737,7 @@ sections:
- "Basic Scene Management System"
- "Asset Loading Foundation"
- id: phase-2-game-systems
title: 'Phase 2: Game Systems ({{duration}})'
title: "Phase 2: Game Systems ({{duration}})"
sections:
- id: phase-2-gameplay
title: Gameplay Systems
@@ -755,7 +755,7 @@ sections:
- "Physics and Collision Framework"
- "Game State Management System"
- id: phase-3-content-polish
title: 'Phase 3: Content & Polish ({{duration}})'
title: "Phase 3: Content & Polish ({{duration}})"
sections:
- id: phase-3-content
title: Content Systems

38
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt vendored
View File

@@ -402,8 +402,8 @@ template:
version: 2.0
output:
format: markdown
filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md'
title: 'Story: {{story_title}}'
filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md"
title: "Story: {{story_title}}"
workflow:
mode: interactive
@@ -432,7 +432,7 @@ sections:
- id: description
title: Description
instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.
template: '{{clear_description_of_what_needs_to_be_implemented}}'
template: "{{clear_description_of_what_needs_to_be_implemented}}"
- id: acceptance-criteria
title: Acceptance Criteria
@@ -442,22 +442,22 @@ sections:
title: Functional Requirements
type: checklist
items:
- '{{specific_functional_requirement}}'
- "{{specific_functional_requirement}}"
- id: technical-requirements
title: Technical Requirements
type: checklist
items:
- 'Code follows TypeScript strict mode standards'
- 'Maintains 60 FPS on target devices'
- 'No memory leaks or performance degradation'
- '{{specific_technical_requirement}}'
- "Code follows TypeScript strict mode standards"
- "Maintains 60 FPS on target devices"
- "No memory leaks or performance degradation"
- "{{specific_technical_requirement}}"
- id: game-design-requirements
title: Game Design Requirements
type: checklist
items:
- '{{gameplay_requirement_from_gdd}}'
- '{{balance_requirement_if_applicable}}'
- '{{player_experience_requirement}}'
- "{{gameplay_requirement_from_gdd}}"
- "{{balance_requirement_if_applicable}}"
- "{{player_experience_requirement}}"
- id: technical-specifications
title: Technical Specifications
@@ -622,14 +622,14 @@ sections:
instruction: Checklist that must be completed before the story is considered finished
type: checklist
items:
- 'All acceptance criteria met'
- 'Code reviewed and approved'
- 'Unit tests written and passing'
- 'Integration tests passing'
- 'Performance targets met'
- 'No linting errors'
- 'Documentation updated'
- '{{game_specific_dod_item}}'
- "All acceptance criteria met"
- "Code reviewed and approved"
- "Unit tests written and passing"
- "Integration tests passing"
- "Performance targets met"
- "No linting errors"
- "Documentation updated"
- "{{game_specific_dod_item}}"
- id: notes
title: Notes