bmad-game-dev-studio 0.1.8 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/workflows/1-preproduction/brainstorm-game/workflow.yaml +1 -1
- package/src/workflows/1-preproduction/game-brief/workflow.yaml +1 -1
- package/src/workflows/2-design/gdd/workflow.yaml +1 -1
- package/src/workflows/2-design/narrative/workflow.yaml +1 -1
- package/src/workflows/3-technical/game-architecture/workflow.yaml +15 -1
- package/src/workflows/4-production/code-review/workflow.yaml +1 -1
- package/src/workflows/4-production/correct-course/workflow.yaml +1 -1
- package/src/workflows/4-production/create-story/workflow.yaml +1 -1
- package/src/workflows/4-production/dev-story/workflow.yaml +1 -1
- package/src/workflows/4-production/retrospective/workflow.yaml +1 -1
- package/src/workflows/4-production/sprint-planning/workflow.yaml +1 -1
- package/src/workflows/4-production/sprint-status/workflow.yaml +1 -1
- package/src/workflows/document-project/workflow.yaml +1 -1
- package/src/workflows/gametest/automate/workflow.yaml +1 -1
- package/src/workflows/gametest/e2e-scaffold/workflow.yaml +1 -1
- package/src/workflows/gametest/performance/workflow.yaml +1 -1
- package/src/workflows/gametest/playtest-plan/workflow.yaml +1 -1
- package/src/workflows/gametest/test-design/workflow.yaml +1 -1
- package/src/workflows/gametest/test-framework/workflow.yaml +1 -1
- package/src/workflows/gametest/test-review/workflow.yaml +1 -1
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://json.schemastore.org/package.json",
|
|
3
3
|
"name": "bmad-game-dev-studio",
|
|
4
|
-
"version": "0.1.
|
|
4
|
+
"version": "0.1.10",
|
|
5
5
|
"description": "A BMad MEthod Core Module that offers a substantial stand alone module for Game Development across multiple supported platforms",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"bmad",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Brainstorm Game Workflow Configuration
|
|
2
2
|
name: "brainstorm-game"
|
|
3
|
-
description:
|
|
3
|
+
description: 'Game concept ideation with guided design techniques. Use when the user says "lets create game design ideas" or "I want to brainstorm game concepts"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game Brief - Interactive Workflow Configuration
|
|
2
2
|
name: game-brief
|
|
3
|
-
description:
|
|
3
|
+
description: 'Game vision definition workflow. Use when the user says "lets create a game brief" or "I want to define my game vision"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game Design Document (GDD) Workflow
|
|
2
2
|
name: gdd
|
|
3
|
-
description:
|
|
3
|
+
description: 'Comprehensive game design document creator. Use when the user says "lets create a game design document" or "I want to create a comprehensive GDD"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Narrative Design Workflow
|
|
2
2
|
name: narrative
|
|
3
|
-
description:
|
|
3
|
+
description: 'Story-driven narrative design documentation. Use when the user says "lets create a narrative design document"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game Architecture Workflow Configuration
|
|
2
2
|
name: game-architecture
|
|
3
|
-
description:
|
|
3
|
+
description: 'Technical game systems architecture design. Use when the user says "lets create a game architecture" or "I want to design technical game systems"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables
|
|
@@ -24,6 +24,15 @@ architecture_patterns: "{installed_path}/architecture-patterns.yaml"
|
|
|
24
24
|
pattern_categories: "{installed_path}/pattern-categories.csv"
|
|
25
25
|
engine_mcps: "{installed_path}/engine-mcps.yaml"
|
|
26
26
|
|
|
27
|
+
# Engine-specific knowledge fragments
|
|
28
|
+
# Steps 4, 6, and 7 should load ONLY the fragment matching the engine selected in Step 3
|
|
29
|
+
# These complement (not replace) decision-catalog.yaml — catalog has relationships, fragments have depth
|
|
30
|
+
knowledge_fragments:
|
|
31
|
+
godot: "{installed_path}/knowledge/godot-engine.md"
|
|
32
|
+
unity: "{installed_path}/knowledge/unity-engine.md"
|
|
33
|
+
unreal: "{installed_path}/knowledge/unreal-engine.md"
|
|
34
|
+
phaser: "{installed_path}/knowledge/phaser-engine.md"
|
|
35
|
+
|
|
27
36
|
# Smart input file references - handles both whole docs and sharded docs
|
|
28
37
|
input_file_patterns:
|
|
29
38
|
gdd:
|
|
@@ -99,3 +108,8 @@ web_bundle:
|
|
|
99
108
|
- "_bmad/gds/workflows/3-technical/game-architecture/architecture-patterns.yaml"
|
|
100
109
|
- "_bmad/gds/workflows/3-technical/game-architecture/pattern-categories.csv"
|
|
101
110
|
- "_bmad/gds/workflows/3-technical/game-architecture/engine-mcps.yaml"
|
|
111
|
+
# Engine knowledge fragments
|
|
112
|
+
- "_bmad/gds/workflows/3-technical/game-architecture/knowledge/godot-engine.md"
|
|
113
|
+
- "_bmad/gds/workflows/3-technical/game-architecture/knowledge/unity-engine.md"
|
|
114
|
+
- "_bmad/gds/workflows/3-technical/game-architecture/knowledge/unreal-engine.md"
|
|
115
|
+
- "_bmad/gds/workflows/3-technical/game-architecture/knowledge/phaser-engine.md"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Review Story Workflow - Game Development
|
|
2
2
|
name: code-review
|
|
3
|
-
description:
|
|
3
|
+
description: 'Adversarial game dev code review. Use when the user says "lets review this code for game dev issues"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Correct Course - Sprint Change Management Workflow
|
|
2
2
|
name: "correct-course"
|
|
3
|
-
description:
|
|
3
|
+
description: 'Sprint change impact analysis and planning. Use when the user says "I want to analyze and plan significant sprint changes"'
|
|
4
4
|
author: "BMad Method"
|
|
5
5
|
|
|
6
6
|
config_source: "{project-root}/_bmad/gds/config.yaml"
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
name: create-story
|
|
2
|
-
description:
|
|
2
|
+
description: 'User story creation from epics. Use when the user says "lets create a user story" or "I want to create a user story"'
|
|
3
3
|
author: "BMad"
|
|
4
4
|
|
|
5
5
|
# Critical variables from config
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
name: dev-story
|
|
2
|
-
description:
|
|
2
|
+
description: 'Story implementation and testing workflow. Use when the user says "lets implement story tasks" or "lets write tests for story"'
|
|
3
3
|
author: "BMad"
|
|
4
4
|
|
|
5
5
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Retrospective - Epic Completion Review Workflow
|
|
2
2
|
name: "retrospective"
|
|
3
|
-
description:
|
|
3
|
+
description: 'Post-epic review and lessons learned. Use when the user says "lets run a retrospective" or "execute epic completion review"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
config_source: "{project-root}/_bmad/gds/config.yaml"
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
name: sprint-planning
|
|
2
|
-
description:
|
|
2
|
+
description: 'Sprint status tracking file generator. Use when the user says "I want to generate sprint status" or "lets create sprint tracking"'
|
|
3
3
|
author: "BMad"
|
|
4
4
|
|
|
5
5
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Sprint Status - Game Development Implementation Tracker
|
|
2
2
|
name: sprint-status
|
|
3
|
-
description:
|
|
3
|
+
description: 'Sprint status summary and risk surfacing. Use when the user says "Summarize sprint-status.yaml for game project and surface risks"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Document Project Workflow Configuration
|
|
2
2
|
name: "document-project"
|
|
3
3
|
version: "1.2.0"
|
|
4
|
-
description:
|
|
4
|
+
description: 'Brownfield project documentation scanner. Use when the user says "lets create project documentation" or "I want to document a brownfield project"'
|
|
5
5
|
author: "BMad"
|
|
6
6
|
|
|
7
7
|
# Critical variables
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: automate
|
|
2
2
|
name: gametest-automate
|
|
3
|
-
description:
|
|
3
|
+
description: 'Automated test scenario generator. Use when the user says "I want to create automated game tests" or "Generate test scenarios for Unity Unreal or Godot"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -8,7 +8,7 @@ workflow:
|
|
|
8
8
|
agent: game-qa
|
|
9
9
|
|
|
10
10
|
description: |
|
|
11
|
-
E2E testing infrastructure scaffolder. Use when the user says
|
|
11
|
+
E2E testing infrastructure scaffolder. Use when the user says "lets scaffold e2e testing infrastructure for game project"
|
|
12
12
|
|
|
13
13
|
triggers:
|
|
14
14
|
- "ES"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: performance
|
|
2
2
|
name: gametest-performance
|
|
3
|
-
description:
|
|
3
|
+
description: 'Performance test strategy designer. Use when the user says "lets create a performance test plan"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: playtest-plan
|
|
2
2
|
name: gametest-playtest-plan
|
|
3
|
-
description:
|
|
3
|
+
description: 'Playtest session planner. Use when the user says "lets create a playtest plan" or "I want to schedule gameplay testing"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: test-design
|
|
2
2
|
name: gametest-test-design
|
|
3
|
-
description:
|
|
3
|
+
description: 'Game test scenario creator. Use when the user says "lets create game test scenarios"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: framework
|
|
2
2
|
name: gametest-framework
|
|
3
|
-
description:
|
|
3
|
+
description: 'Game test framework initializer. Use when the user says "lets create a test framework" or "initialize game testing infrastructure"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Game QA workflow: test-review
|
|
2
2
|
name: gametest-test-review
|
|
3
|
-
description:
|
|
3
|
+
description: 'Game test coverage reviewer. Use when the user says "lets review game tests" or "I want to evaluate test coverage"'
|
|
4
4
|
author: "BMad"
|
|
5
5
|
|
|
6
6
|
# Critical variables from config
|