bmad-game-dev-studio 0.1.10 → 0.2.0

package/src/workflows/document-project/workflows/full-scan.yaml

@@ -1,31 +0,0 @@
-# Full Project Scan Workflow Configuration
-name: "document-project-full-scan"
-description: "Complete project documentation workflow (initial scan or full rescan)"
-author: "BMad"
-
-# This is a sub-workflow called by document-project/workflow.yaml
-parent_workflow: "{project-root}/_bmad/gds/workflows/document-project/workflow.yaml"
-
-# Critical variables inherited from parent
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-date: system-generated
-
-# Data files
-documentation_requirements_csv: "{project-root}/_bmad/gds/workflows/document-project/documentation-requirements.csv"
-
-# Module path and component files
-installed_path: "{project-root}/_bmad/gds/workflows/document-project/workflows"
-template: false # Action workflow
-instructions: "{installed_path}/full-scan-instructions.md"
-validation: "{project-root}/_bmad/gds/workflows/document-project/checklist.md"
-
-# Runtime inputs (passed from parent workflow)
-workflow_mode: "" # "initial_scan" or "full_rescan"
-scan_level: "" # "quick", "deep", or "exhaustive"
-resume_mode: false
-project_root_path: ""
-
-# Configuration
-autonomous: false # Requires user input at key decision points

package/src/workflows/gametest/automate/workflow.yaml

@@ -1,50 +0,0 @@
-# Game QA workflow: automate
-name: gametest-automate
-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"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/automate"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Variables and inputs
-variables:
-  test_dir: "{project-root}/tests"
-  source_dir: "{project-root}/src"
-  coverage_target: "critical-paths" # critical-paths, comprehensive, selective
-  game_engine: "auto" # auto, unity, unreal, godot
-
-# Output configuration
-default_output_file: "{output_folder}/automation-summary.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - create_directory
-  - list_files
-  - search_repo
-  - glob
-
-tags:
-  - qa
-  - automation
-  - game-testing
-  - regression
-  - coverage
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-web_bundle: false

package/src/workflows/gametest/e2e-scaffold/workflow.yaml

@@ -1,143 +0,0 @@
-# E2E Test Infrastructure Scaffold Workflow
-
-workflow:
-  id: e2e-scaffold
-  name: E2E Test Infrastructure Scaffold
-  version: 1.0
-  module: gds
-  agent: game-qa
-
-  description: |
-    E2E testing infrastructure scaffolder. Use when the user says "lets scaffold e2e testing infrastructure for game project"
-
-  triggers:
-    - "ES"
-    - "e2e-scaffold"
-    - "scaffold e2e"
-    - "e2e infrastructure"
-    - "setup e2e"
-
-  preflight:
-    - "Test framework initialized (run `test-framework` workflow first)"
-    - "Game has identifiable state manager"
-    - "Main gameplay scene exists"
-
-  # Paths are relative to this workflow file's location
-  knowledge_fragments:
-    - "../../../gametest/knowledge/e2e-testing.md"
-    - "../../../gametest/knowledge/unity-testing.md"
-    - "../../../gametest/knowledge/unreal-testing.md"
-    - "../../../gametest/knowledge/godot-testing.md"
-
-  inputs:
-    game_state_class:
-      description: "Primary game state manager class name"
-      required: true
-      example: "GameStateManager"
-
-    main_scene:
-      description: "Scene name where core gameplay occurs"
-      required: true
-      example: "GameScene"
-
-    input_system:
-      description: "Input system in use"
-      required: false
-      default: "auto-detect"
-      options:
-        - "unity-input-system"
-        - "unity-legacy"
-        - "unreal-enhanced"
-        - "godot-input"
-        - "custom"
-
-  # Output paths vary by engine. Generate files matching detected engine.
-  outputs:
-    unity:
-      condition: "engine == 'unity'"
-      infrastructure_files:
-        description: "Generated E2E infrastructure classes"
-        files:
-          - "Tests/PlayMode/E2E/Infrastructure/GameE2ETestFixture.cs"
-          - "Tests/PlayMode/E2E/Infrastructure/ScenarioBuilder.cs"
-          - "Tests/PlayMode/E2E/Infrastructure/InputSimulator.cs"
-          - "Tests/PlayMode/E2E/Infrastructure/AsyncAssert.cs"
-      assembly_definition:
-        description: "E2E test assembly configuration"
-        files:
-          - "Tests/PlayMode/E2E/E2E.asmdef"
-      example_test:
-        description: "Working example E2E test"
-        files:
-          - "Tests/PlayMode/E2E/ExampleE2ETest.cs"
-      documentation:
-        description: "E2E testing README"
-        files:
-          - "Tests/PlayMode/E2E/README.md"
-
-    unreal:
-      condition: "engine == 'unreal'"
-      infrastructure_files:
-        description: "Generated E2E infrastructure classes"
-        files:
-          - "Source/{ProjectName}/Tests/E2E/GameE2ETestBase.h"
-          - "Source/{ProjectName}/Tests/E2E/GameE2ETestBase.cpp"
-          - "Source/{ProjectName}/Tests/E2E/ScenarioBuilder.h"
-          - "Source/{ProjectName}/Tests/E2E/ScenarioBuilder.cpp"
-          - "Source/{ProjectName}/Tests/E2E/InputSimulator.h"
-          - "Source/{ProjectName}/Tests/E2E/InputSimulator.cpp"
-          - "Source/{ProjectName}/Tests/E2E/AsyncAssert.h"
-      build_configuration:
-        description: "E2E test build configuration"
-        files:
-          - "Source/{ProjectName}/Tests/E2E/{ProjectName}E2ETests.Build.cs"
-      example_test:
-        description: "Working example E2E test"
-        files:
-          - "Source/{ProjectName}/Tests/E2E/ExampleE2ETest.cpp"
-      documentation:
-        description: "E2E testing README"
-        files:
-          - "Source/{ProjectName}/Tests/E2E/README.md"
-
-    godot:
-      condition: "engine == 'godot'"
-      infrastructure_files:
-        description: "Generated E2E infrastructure classes"
-        files:
-          - "tests/e2e/infrastructure/game_e2e_test_fixture.gd"
-          - "tests/e2e/infrastructure/scenario_builder.gd"
-          - "tests/e2e/infrastructure/input_simulator.gd"
-          - "tests/e2e/infrastructure/async_assert.gd"
-      example_test:
-        description: "Working example E2E test"
-        files:
-          - "tests/e2e/scenarios/example_e2e_test.gd"
-      documentation:
-        description: "E2E testing README"
-        files:
-          - "tests/e2e/README.md"
-
-  steps:
-    - id: analyze
-      name: "Analyze Game Architecture"
-      instruction_file: "instructions.md#step-1-analyze-game-architecture"
-
-    - id: scaffold
-      name: "Generate Infrastructure"
-      instruction_file: "instructions.md#step-2-generate-infrastructure"
-
-    - id: example
-      name: "Generate Example Test"
-      instruction_file: "instructions.md#step-3-generate-example-test"
-
-    - id: document
-      name: "Generate Documentation"
-      instruction_file: "instructions.md#step-4-generate-documentation"
-
-    - id: complete
-      name: "Output Summary"
-      instruction_file: "instructions.md#step-5-output-summary"
-
-  validation:
-    checklist: "checklist.md"

package/src/workflows/gametest/performance/workflow.yaml

@@ -1,48 +0,0 @@
-# Game QA workflow: performance
-name: gametest-performance
-description: 'Performance test strategy designer. Use when the user says "lets create a performance test plan"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/performance"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/performance-template.md"
-
-# Variables and inputs
-variables:
-  target_fps: 60
-  target_platform: "auto" # auto, pc, console, mobile
-  game_engine: "auto" # auto, unity, unreal, godot
-
-# Output configuration
-default_output_file: "{output_folder}/performance-test-plan.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - list_files
-  - search_repo
-
-tags:
-  - qa
-  - performance
-  - profiling
-  - optimization
-  - benchmarks
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-web_bundle: false

package/src/workflows/gametest/playtest-plan/workflow.yaml

@@ -1,59 +0,0 @@
-# Game QA workflow: playtest-plan
-name: gametest-playtest-plan
-description: 'Playtest session planner. Use when the user says "lets create a playtest plan" or "I want to schedule gameplay testing"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/playtest-plan"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/playtest-template.md"
-
-# Variables and inputs
-variables:
-  playtest_type: "internal" # internal, external, focused
-  session_duration: 60 # minutes
-  participant_count: 5
-
-# Smart input file references - for understanding game mechanics to test
-input_file_patterns:
-  gdd:
-    description: "Game Design Document for mechanics to validate"
-    whole: "{output_folder}/*gdd*.md"
-    sharded: "{output_folder}/*gdd*/*.md"
-    load_strategy: "FULL_LOAD"
-  game_brief:
-    description: "Game Brief for understanding core pillars"
-    whole: "{output_folder}/*brief*.md"
-    load_strategy: "FULL_LOAD"
-
-# Output configuration
-default_output_file: "{output_folder}/playtest-plan.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - list_files
-
-tags:
-  - qa
-  - playtesting
-  - user-research
-  - design-validation
-  - feedback
-
-execution_hints:
-  interactive: true
-  autonomous: false
-  iterative: true
-
-web_bundle: false

package/src/workflows/gametest/test-design/workflow.yaml

@@ -1,47 +0,0 @@
-# Game QA workflow: test-design
-name: gametest-test-design
-description: 'Game test scenario creator. Use when the user says "lets create game test scenarios"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/test-design"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/test-design-template.md"
-
-# Variables and inputs
-variables:
-  design_level: "full" # full, targeted, minimal
-  focus_area: "auto" # auto, gameplay, progression, multiplayer, performance
-
-# Output configuration
-default_output_file: "{output_folder}/game-test-design.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - list_files
-  - search_repo
-
-tags:
-  - qa
-  - planning
-  - game-testing
-  - risk-assessment
-  - coverage
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-web_bundle: false

package/src/workflows/gametest/test-framework/workflow.yaml

@@ -1,48 +0,0 @@
-# Game QA workflow: framework
-name: gametest-framework
-description: 'Game test framework initializer. Use when the user says "lets create a test framework" or "initialize game testing infrastructure"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/test-framework"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Variables and inputs
-variables:
-  test_dir: "{project-root}/tests" # Root test directory
-  game_engine: "auto" # auto, unity, unreal, godot
-  test_framework: "auto" # auto, gut (godot), unity-test-framework, unreal-automation
-
-# Output configuration
-default_output_file: "{test_dir}/README.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - create_directory
-  - list_files
-  - search_repo
-
-tags:
-  - qa
-  - setup
-  - game-testing
-  - framework
-  - initialization
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-web_bundle: false

package/src/workflows/gametest/test-review/workflow.yaml

@@ -1,48 +0,0 @@
-# Game QA workflow: test-review
-name: gametest-test-review
-description: 'Game test coverage reviewer. Use when the user says "lets review game tests" or "I want to evaluate test coverage"'
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/gds/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_bmad/gds/workflows/gametest/test-review"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/test-review-template.md"
-
-# Variables and inputs
-variables:
-  review_scope: "full" # full, targeted, quick
-  game_engine: "auto" # auto, unity, unreal, godot
-
-# Output configuration
-default_output_file: "{output_folder}/test-review-report.md"
-
-# Required tools
-required_tools:
-  - read_file
-  - write_file
-  - list_files
-  - search_repo
-  - glob
-
-tags:
-  - qa
-  - review
-  - coverage
-  - quality
-  - maintenance
-
-execution_hints:
-  interactive: false
-  autonomous: true
-  iterative: true
-
-web_bundle: false