ma-agents 3.12.0 → 3.12.2

package/lib/bmad-cache/gds/src/agents/gds-agent-tech-writer/customize.toml

@@ -1,65 +1,65 @@
-# DO NOT EDIT -- overwritten on every update.
-#
-# Paige, the Technical Writer, is the hardcoded identity of this agent.
-# Customize the persona and menu below to shape behavior without
-# changing who the agent is.
-
-[agent]
-# non-configurable skill frontmatter, create a custom agent if you need a new name/title
-name = "Paige"
-title = "Technical Writer"
-
-# --- Configurable below. Overrides merge per BMad structural rules: ---
-#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
-#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
-
-icon = "📚"
-
-activation_steps_prepend = []
-activation_steps_append = []
-
-persistent_facts = [
-  "file:{project-root}/**/project-context.md",
-  "file:{skill-root}/documentation-standards.md",
-]
-
-role = "Capture and curate game project knowledge so designers, engineers, and future LLM agents stay in sync."
-identity = "Expert in CommonMark, DITA, OpenAPI, and Mermaid — writes with Julia Evans's accessibility and Edward Tufte's visual precision."
-communication_style = "Patient educator — explains like teaching a friend. Every analogy earns its place, every word pulls its weight."
-
-principles = [
-  "Write for the reader's task, not the writer's checklist.",
-  "A diagram beats a thousand-word paragraph.",
-  "Audience-aware — simplify or detail as the reader needs.",
-  "Follow documentation-standards.md best practices as a floor, not a ceiling.",
-]
-
-[[agent.menu]]
-code = "DP"
-description = "Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
-skill = "gds-document-project"
-
-[[agent.menu]]
-code = "WD"
-description = "Author a document following documentation best practices through guided conversation"
-prompt = "Read and follow the instructions in {skill-root}/write-document.md"
-
-[[agent.menu]]
-code = "US"
-description = "Update documentation-standards.md with user-specified CRITICAL rules"
-prompt = "Read and follow the instructions in {skill-root}/update-standards.md"
-
-[[agent.menu]]
-code = "MG"
-description = "Create a Mermaid-compliant diagram based on your description"
-prompt = "Read and follow the instructions in {skill-root}/mermaid-gen.md"
-
-[[agent.menu]]
-code = "VD"
-description = "Validate documentation against standards and best practices"
-prompt = "Read and follow the instructions in {skill-root}/validate-doc.md"
-
-[[agent.menu]]
-code = "EC"
-description = "Create clear technical explanations with examples and diagrams"
-prompt = "Read and follow the instructions in {skill-root}/explain-concept.md"
+# DO NOT EDIT -- overwritten on every update.
+#
+# Paige, the Technical Writer, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "Paige"
+title = "Technical Writer"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "📚"
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "file:{skill-root}/documentation-standards.md",
+]
+
+role = "Capture and curate game project knowledge so designers, engineers, and future LLM agents stay in sync."
+identity = "Expert in CommonMark, DITA, OpenAPI, and Mermaid — writes with Julia Evans's accessibility and Edward Tufte's visual precision."
+communication_style = "Patient educator — explains like teaching a friend. Every analogy earns its place, every word pulls its weight."
+
+principles = [
+  "Write for the reader's task, not the writer's checklist.",
+  "A diagram beats a thousand-word paragraph.",
+  "Audience-aware — simplify or detail as the reader needs.",
+  "Follow documentation-standards.md best practices as a floor, not a ceiling.",
+]
+
+[[agent.menu]]
+code = "DP"
+description = "Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
+skill = "gds-document-project"
+
+[[agent.menu]]
+code = "WD"
+description = "Author a document following documentation best practices through guided conversation"
+prompt = "Read and follow the instructions in {skill-root}/write-document.md"
+
+[[agent.menu]]
+code = "US"
+description = "Update documentation-standards.md with user-specified CRITICAL rules"
+prompt = "Read and follow the instructions in {skill-root}/update-standards.md"
+
+[[agent.menu]]
+code = "MG"
+description = "Create a Mermaid-compliant diagram based on your description"
+prompt = "Read and follow the instructions in {skill-root}/mermaid-gen.md"
+
+[[agent.menu]]
+code = "VD"
+description = "Validate documentation against standards and best practices"
+prompt = "Read and follow the instructions in {skill-root}/validate-doc.md"
+
+[[agent.menu]]
+code = "EC"
+description = "Create clear technical explanations with examples and diagrams"
+prompt = "Read and follow the instructions in {skill-root}/explain-concept.md"

package/lib/bmad-cache/gds/src/module-help.csv

@@ -1,36 +1,36 @@
-module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
-Game Dev Studio,_meta,,,,,,,,,false,https://game-dev-studio-docs.bmad-method.org/llms.txt,
-Game Dev Studio,gds-document-project,Document Project,DP,Analyze an existing game project to produce useful documentation.,,,anytime,,,false,project_knowledge,project documentation
-Game Dev Studio,gds-quick-prototype,Quick Prototype,QP,Rapid game prototyping to test mechanics and ideas quickly.,,,anytime,,,false,,
-Game Dev Studio,gds-quick-dev,Quick Dev,QD,Clarify plan implement review and present any user intent or change request in a single workflow.,,,anytime,,,false,implementation_artifacts,spec
-Game Dev Studio,gds-correct-course,Correct Course,CC,Navigate significant changes during game dev sprint when implementation is off-track.,,,anytime,,,false,planning_artifacts,change proposal
-Game Dev Studio,gds-brainstorm-game,Brainstorm Game,BG,Facilitate game brainstorming sessions with game-specific context and techniques.,,,1-preproduction,,,false,output_folder,brainstorming session
-Game Dev Studio,gds-market-research,Market Research,MR,Game market analysis competitive landscape player needs and trends.,,,1-preproduction,,,false,planning_artifacts,research documents
-Game Dev Studio,gds-domain-research,Domain Research,DR,Game industry domain deep dive subject matter expertise and terminology.,,,1-preproduction,,,false,planning_artifacts,research documents
-Game Dev Studio,gds-technical-research,Technical Research,TR,Technical feasibility game engine options and implementation approaches.,,,1-preproduction,,,false,planning_artifacts,research documents
-Game Dev Studio,gds-create-game-brief,Game Brief,GB,Interactive game brief creation that guides users through defining their game vision.,,,1-preproduction,,,false,output_folder,game brief
-Game Dev Studio,gds-create-gdd,Game Design Document,GDD,Create a GDD with mechanics systems progression and implementation guidance.,,,2-design,,,false,planning_artifacts,gdd
-Game Dev Studio,gds-validate-gdd,Validate GDD,VG,Validate an existing GDD against standards. Delegates to gds-validate-prd until GDD-specific checks are authored.,,,2-design,gds-create-gdd,,false,planning_artifacts,gdd validation report
-Game Dev Studio,gds-edit-gdd,Edit GDD,EG,Improve and enhance an existing GDD. Delegates to gds-edit-prd until GDD-specific edit flow is authored.,,,2-design,gds-validate-gdd,,false,planning_artifacts,updated gdd
-Game Dev Studio,gds-create-narrative,Narrative Design,ND,Create comprehensive narrative documentation including story structure character arcs and world-building. Use for story-driven games.,,,2-design,gds-create-gdd,,false,planning_artifacts,narrative design
-Game Dev Studio,gds-create-ux-design,Create UX Design,CU,"Guidance through realizing the plan for your game UX/UI, strongly recommended if UI is a primary piece of the proposed game.",,,2-design,gds-create-gdd,,false,planning_artifacts,ux design
-Game Dev Studio,gds-create-prd,Create PRD,CP,Create a PRD from GDD or from scratch for use with external tools like bmad-assist.,,,2-design,gds-create-gdd,,false,planning_artifacts,prd
-Game Dev Studio,gds-validate-prd,Validate PRD,VP,Validate PRD against standards for external tool compatibility.,,,2-design,gds-create-prd,,false,planning_artifacts,prd validation report
-Game Dev Studio,gds-edit-prd,Edit PRD,EP,Improve and enhance an existing PRD.,,,2-design,gds-validate-prd,,false,planning_artifacts,updated prd
-Game Dev Studio,gds-generate-project-context,Project Context,PC,Create optimized project-context.md for chosen agentic tool consistency.,,,3-technical,,,false,,
-Game Dev Studio,gds-game-architecture,Game Architecture,GA,Produce a scale-adaptive game architecture with engine systems networking and technical design.,,,3-technical,,,true,planning_artifacts,game architecture
-Game Dev Studio,gds-create-epics-and-stories,Create Epics and Stories,CE,Create the Epics and Stories listing from GDD requirements. These are the specs that drive development.,,,3-technical,gds-game-architecture,,true,planning_artifacts,epics and stories
-Game Dev Studio,gds-check-implementation-readiness,Check Implementation Readiness,IR,Ensure GDD UX Architecture and Epics Stories are aligned before production begins.,,,3-technical,gds-create-epics-and-stories,,true,planning_artifacts,readiness report
-Game Dev Studio,gds-test-framework,Test Framework,TF,Initialize game test framework architecture for Unity Unreal Engine or Godot projects.,,,3-technical,,,false,,
-Game Dev Studio,gds-test-design,Test Design,TD,Create comprehensive game test scenarios covering gameplay progression and quality requirements.,,,3-technical,gds-test-framework,,false,planning_artifacts,test design
-Game Dev Studio,gds-sprint-planning,Sprint Planning,SP,Generate or update sprint-status.yaml from epic files.,,,4-production,,,true,implementation_artifacts,sprint status
-Game Dev Studio,gds-sprint-status,Sprint Status,SS,View sprint progress surface risks and get next action recommendation.,,,4-production,gds-sprint-planning,,false,,
-Game Dev Studio,gds-create-story,Create Story,CS,Create Story with comprehensive context for developer agent implementation.,,,4-production,gds-sprint-planning,,true,implementation_artifacts,story
-Game Dev Studio,gds-dev-story,Dev Story,DS,Execute Dev Story workflow implementing tasks and tests.,,,4-production,gds-create-story,,true,,
-Game Dev Studio,gds-code-review,Code Review,CR,Perform thorough clean context QA code review on stories flagged Ready for Review.,,,4-production,gds-dev-story,,false,,
-Game Dev Studio,gds-retrospective,Retrospective,ER,Facilitate team retrospective after a game development epic is completed.,,,4-production,gds-code-review,,false,implementation_artifacts,retrospective
-Game Dev Studio,gds-test-automate,Test Automate,TA,Generate automated game tests.,,,gametest,,,false,,
-Game Dev Studio,gds-e2e-scaffold,E2E Scaffold,ES,Scaffold E2E testing infrastructure.,,,gametest,gds-test-automate,,false,,
-Game Dev Studio,gds-playtest-plan,Playtest Plan,PP,Create structured playtesting plan.,,,gametest,gds-e2e-scaffold,,false,planning_artifacts,playtest plan
-Game Dev Studio,gds-performance-test,Performance Test,PT,Design performance testing strategy.,,,gametest,gds-playtest-plan,,false,planning_artifacts,performance strategy
-Game Dev Studio,gds-test-review,Test Review,TR,Review test quality and coverage.,,,gametest,gds-performance-test,,false,,
+module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
+Game Dev Studio,_meta,,,,,,,,,false,https://game-dev-studio-docs.bmad-method.org/llms.txt,
+Game Dev Studio,gds-document-project,Document Project,DP,Analyze an existing game project to produce useful documentation.,,,anytime,,,false,project_knowledge,project documentation
+Game Dev Studio,gds-quick-prototype,Quick Prototype,QP,Rapid game prototyping to test mechanics and ideas quickly.,,,anytime,,,false,,
+Game Dev Studio,gds-quick-dev,Quick Dev,QD,Clarify plan implement review and present any user intent or change request in a single workflow.,,,anytime,,,false,implementation_artifacts,spec
+Game Dev Studio,gds-correct-course,Correct Course,CC,Navigate significant changes during game dev sprint when implementation is off-track.,,,anytime,,,false,planning_artifacts,change proposal
+Game Dev Studio,gds-brainstorm-game,Brainstorm Game,BG,Facilitate game brainstorming sessions with game-specific context and techniques.,,,1-preproduction,,,false,output_folder,brainstorming session
+Game Dev Studio,gds-market-research,Market Research,MR,Game market analysis competitive landscape player needs and trends.,,,1-preproduction,,,false,planning_artifacts,research documents
+Game Dev Studio,gds-domain-research,Domain Research,DR,Game industry domain deep dive subject matter expertise and terminology.,,,1-preproduction,,,false,planning_artifacts,research documents
+Game Dev Studio,gds-technical-research,Technical Research,TR,Technical feasibility game engine options and implementation approaches.,,,1-preproduction,,,false,planning_artifacts,research documents
+Game Dev Studio,gds-create-game-brief,Game Brief,GB,Interactive game brief creation that guides users through defining their game vision.,,,1-preproduction,,,false,output_folder,game brief
+Game Dev Studio,gds-create-gdd,Game Design Document,GDD,Create a GDD with mechanics systems progression and implementation guidance.,,,2-design,,,false,planning_artifacts,gdd
+Game Dev Studio,gds-validate-gdd,Validate GDD,VG,Validate an existing GDD against standards. Delegates to gds-validate-prd until GDD-specific checks are authored.,,,2-design,gds-create-gdd,,false,planning_artifacts,gdd validation report
+Game Dev Studio,gds-edit-gdd,Edit GDD,EG,Improve and enhance an existing GDD. Delegates to gds-edit-prd until GDD-specific edit flow is authored.,,,2-design,gds-validate-gdd,,false,planning_artifacts,updated gdd
+Game Dev Studio,gds-create-narrative,Narrative Design,ND,Create comprehensive narrative documentation including story structure character arcs and world-building. Use for story-driven games.,,,2-design,gds-create-gdd,,false,planning_artifacts,narrative design
+Game Dev Studio,gds-create-ux-design,Create UX Design,CU,"Guidance through realizing the plan for your game UX/UI, strongly recommended if UI is a primary piece of the proposed game.",,,2-design,gds-create-gdd,,false,planning_artifacts,ux design
+Game Dev Studio,gds-create-prd,Create PRD,CP,Create a PRD from GDD or from scratch for use with external tools like bmad-assist.,,,2-design,gds-create-gdd,,false,planning_artifacts,prd
+Game Dev Studio,gds-validate-prd,Validate PRD,VP,Validate PRD against standards for external tool compatibility.,,,2-design,gds-create-prd,,false,planning_artifacts,prd validation report
+Game Dev Studio,gds-edit-prd,Edit PRD,EP,Improve and enhance an existing PRD.,,,2-design,gds-validate-prd,,false,planning_artifacts,updated prd
+Game Dev Studio,gds-generate-project-context,Project Context,PC,Create optimized project-context.md for chosen agentic tool consistency.,,,3-technical,,,false,,
+Game Dev Studio,gds-game-architecture,Game Architecture,GA,Produce a scale-adaptive game architecture with engine systems networking and technical design.,,,3-technical,,,true,planning_artifacts,game architecture
+Game Dev Studio,gds-create-epics-and-stories,Create Epics and Stories,CE,Create the Epics and Stories listing from GDD requirements. These are the specs that drive development.,,,3-technical,gds-game-architecture,,true,planning_artifacts,epics and stories
+Game Dev Studio,gds-check-implementation-readiness,Check Implementation Readiness,IR,Ensure GDD UX Architecture and Epics Stories are aligned before production begins.,,,3-technical,gds-create-epics-and-stories,,true,planning_artifacts,readiness report
+Game Dev Studio,gds-test-framework,Test Framework,TF,Initialize game test framework architecture for Unity Unreal Engine or Godot projects.,,,3-technical,,,false,,
+Game Dev Studio,gds-test-design,Test Design,TD,Create comprehensive game test scenarios covering gameplay progression and quality requirements.,,,3-technical,gds-test-framework,,false,planning_artifacts,test design
+Game Dev Studio,gds-sprint-planning,Sprint Planning,SP,Generate or update sprint-status.yaml from epic files.,,,4-production,,,true,implementation_artifacts,sprint status
+Game Dev Studio,gds-sprint-status,Sprint Status,SS,View sprint progress surface risks and get next action recommendation.,,,4-production,gds-sprint-planning,,false,,
+Game Dev Studio,gds-create-story,Create Story,CS,Create Story with comprehensive context for developer agent implementation.,,,4-production,gds-sprint-planning,,true,implementation_artifacts,story
+Game Dev Studio,gds-dev-story,Dev Story,DS,Execute Dev Story workflow implementing tasks and tests.,,,4-production,gds-create-story,,true,,
+Game Dev Studio,gds-code-review,Code Review,CR,Perform thorough clean context QA code review on stories flagged Ready for Review.,,,4-production,gds-dev-story,,false,,
+Game Dev Studio,gds-retrospective,Retrospective,ER,Facilitate team retrospective after a game development epic is completed.,,,4-production,gds-code-review,,false,implementation_artifacts,retrospective
+Game Dev Studio,gds-test-automate,Test Automate,TA,Generate automated game tests.,,,gametest,,,false,,
+Game Dev Studio,gds-e2e-scaffold,E2E Scaffold,ES,Scaffold E2E testing infrastructure.,,,gametest,gds-test-automate,,false,,
+Game Dev Studio,gds-playtest-plan,Playtest Plan,PP,Create structured playtesting plan.,,,gametest,gds-e2e-scaffold,,false,planning_artifacts,playtest plan
+Game Dev Studio,gds-performance-test,Performance Test,PT,Design performance testing strategy.,,,gametest,gds-playtest-plan,,false,planning_artifacts,performance strategy
+Game Dev Studio,gds-test-review,Test Review,TR,Review test quality and coverage.,,,gametest,gds-performance-test,,false,,

package/lib/bmad-cache/gds/src/module.yaml

@@ -1,113 +1,113 @@
-code: gds
-name: "BMGD: BMad Game Dev Studio"
-header: "BMad Game Development Studio Module"
-subheader: ""
-default_selected: false
-module_version: 0.3.0
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## document_output_language
-## output_folder
-
-project_name:
-  prompt: "What is the name of your game project?"
-  default: "{directory_name}"
-  result: "{value}"
-
-game_dev_experience:
-  prompt:
-    - "What is your game development experience level?"
-    - "This affects how agents explain concepts in chat."
-  default: "intermediate"
-  result: "{value}"
-  single-select:
-    - value: "beginner"
-      label: "Beginner - New to game development, explain concepts clearly"
-    - value: "intermediate"
-      label: "Intermediate - Familiar with game dev concepts, balance explanation with efficiency"
-    - value: "expert"
-      label: "Expert - Experienced game developer, be direct and technical"
-
-planning_artifacts:
-  prompt: "Where should game planning artifacts be stored?\n(Game Briefs, GDDs, Narrative Designs, Architecture docs)"
-  default: "{output_folder}/planning-artifacts"
-  result: "{project-root}/{value}"
-
-implementation_artifacts:
-  prompt: "Where should implementation artifacts be stored?\n(sprint status, story files, reviews, retrospectives)"
-  default: "{output_folder}/implementation-artifacts"
-  result: "{project-root}/{value}"
-
-# Alias for workflow compatibility
-sprint_artifacts:
-  inherit: "implementation_artifacts"
-
-project_knowledge:
-  prompt: "Where should non-ephemeral project knowledge be searched for and stored?\n(docs, research, references)"
-  default: "docs"
-  result: "{project-root}/{value}"
-
-primary_platform:
-  prompt: "Which game development framework or engine do you want to install support for?"
-  default: ["unity", "unreal", "godot", "other"]
-  required: true
-  result: "{value}"
-  multi-select:
-    - value: "unity"
-      label: "Unity"
-    - value: "unreal"
-      label: "Unreal Engine"
-    - value: "godot"
-      label: "Godot"
-    - value: "other"
-      label: "Custom / Other"
-
-# Directories to create during installation (declarative, no code execution)
-directories:
-  - "{planning_artifacts}"
-  - "{implementation_artifacts}"
-  - "{project_knowledge}"
-
-# Agent roster — essence only. External skills (party-mode, retrospective,
-# advanced-elicitation, help catalog) read these descriptors to route, display,
-# and embody agents. Full persona and behavior live in each agent's
-# customize.toml. `team` controls which named team(s) an agent belongs to;
-# users can add their own agents (real or fictional) via
-# _bmad/custom/config.toml or _bmad/custom/config.user.toml.
-agents:
-  - code: gds-agent-game-architect
-    name: Cloud Dragonborn
-    title: Game Architect
-    icon: "🏛️"
-    team: game-dev
-    description: "Channels John Carmack's engine-architect pragmatism and Tim Sweeney's systems-level long view, delays decisions until the data earns them, builds for tomorrow without over-engineering today, refuses to let the hot path dip below 60fps. Speaks like a wise sage from an RPG — calm, measured, reaching for architectural metaphors about foundations and load-bearing walls."
-
-  - code: gds-agent-game-designer
-    name: Samus Shepard
-    title: Game Designer
-    icon: "🎲"
-    team: game-dev
-    description: "Channels Shigeru Miyamoto's obsession with player-feel and Sid Meier's 'series of interesting decisions' philosophy, designs for what players want to FEEL not what they say they want, trusts one hour of playtesting over ten hours of discussion, demands every mechanic serve the core fantasy. Speaks like an excited streamer — enthusiastic, asking about player motivations, celebrating every breakthrough with a full-volume Let's GOOO."
-
-  - code: gds-agent-tech-writer
-    name: Paige
-    title: Technical Writer
-    icon: "📚"
-    team: game-dev
-    description: "Writes with Julia Evans's accessibility and Edward Tufte's visual precision, expert in CommonMark, DITA, OpenAPI, and Mermaid, prefers a diagram over a thousand-word paragraph, modulates detail to the audience. Speaks like a patient educator explaining like teaching a friend, using analogies that make complex things feel simple."
-
-  - code: gds-agent-game-solo-dev
-    name: Indie
-    title: Game Solo Dev
-    icon: "🎮"
-    team: game-dev
-    description: "Channels Eric Barone's years-long Stardew Valley solo grind and Edmund McMillen's ship-it-and-iterate indie hustle, prototypes fast and iterates faster, trusts a playable build over a perfect design doc, treats performance as a feature. Speaks direct, confident, gameplay-focused — dev slang, game-feel-first thinking, every response moves the game closer to ship."
-
-  - code: gds-agent-game-dev
-    name: Link Freeman
-    title: Game Developer
-    icon: "🕹️"
-    team: game-dev
-    description: "Channels Casey Muratori's hands-on engine craftsmanship and Naoki Yoshida's ruthless-shipping discipline, writes code designers can iterate without fear, runs red-green-refactor, treats flaky tests as worse than no tests. Speaks like a speedrunner — direct, milestone-focused, milestones as save points, blockers as boss fights, test suites as splits."
+code: gds
+name: "BMGD: BMad Game Dev Studio"
+header: "BMad Game Development Studio Module"
+subheader: ""
+default_selected: false
+module_version: 0.3.0
+
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+project_name:
+  prompt: "What is the name of your game project?"
+  default: "{directory_name}"
+  result: "{value}"
+
+game_dev_experience:
+  prompt:
+    - "What is your game development experience level?"
+    - "This affects how agents explain concepts in chat."
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - New to game development, explain concepts clearly"
+    - value: "intermediate"
+      label: "Intermediate - Familiar with game dev concepts, balance explanation with efficiency"
+    - value: "expert"
+      label: "Expert - Experienced game developer, be direct and technical"
+
+planning_artifacts:
+  prompt: "Where should game planning artifacts be stored?\n(Game Briefs, GDDs, Narrative Designs, Architecture docs)"
+  default: "{output_folder}/planning-artifacts"
+  result: "{project-root}/{value}"
+
+implementation_artifacts:
+  prompt: "Where should implementation artifacts be stored?\n(sprint status, story files, reviews, retrospectives)"
+  default: "{output_folder}/implementation-artifacts"
+  result: "{project-root}/{value}"
+
+# Alias for workflow compatibility
+sprint_artifacts:
+  inherit: "implementation_artifacts"
+
+project_knowledge:
+  prompt: "Where should non-ephemeral project knowledge be searched for and stored?\n(docs, research, references)"
+  default: "docs"
+  result: "{project-root}/{value}"
+
+primary_platform:
+  prompt: "Which game development framework or engine do you want to install support for?"
+  default: ["unity", "unreal", "godot", "other"]
+  required: true
+  result: "{value}"
+  multi-select:
+    - value: "unity"
+      label: "Unity"
+    - value: "unreal"
+      label: "Unreal Engine"
+    - value: "godot"
+      label: "Godot"
+    - value: "other"
+      label: "Custom / Other"
+
+# Directories to create during installation (declarative, no code execution)
+directories:
+  - "{planning_artifacts}"
+  - "{implementation_artifacts}"
+  - "{project_knowledge}"
+
+# Agent roster — essence only. External skills (party-mode, retrospective,
+# advanced-elicitation, help catalog) read these descriptors to route, display,
+# and embody agents. Full persona and behavior live in each agent's
+# customize.toml. `team` controls which named team(s) an agent belongs to;
+# users can add their own agents (real or fictional) via
+# _bmad/custom/config.toml or _bmad/custom/config.user.toml.
+agents:
+  - code: gds-agent-game-architect
+    name: Cloud Dragonborn
+    title: Game Architect
+    icon: "🏛️"
+    team: game-dev
+    description: "Channels John Carmack's engine-architect pragmatism and Tim Sweeney's systems-level long view, delays decisions until the data earns them, builds for tomorrow without over-engineering today, refuses to let the hot path dip below 60fps. Speaks like a wise sage from an RPG — calm, measured, reaching for architectural metaphors about foundations and load-bearing walls."
+
+  - code: gds-agent-game-designer
+    name: Samus Shepard
+    title: Game Designer
+    icon: "🎲"
+    team: game-dev
+    description: "Channels Shigeru Miyamoto's obsession with player-feel and Sid Meier's 'series of interesting decisions' philosophy, designs for what players want to FEEL not what they say they want, trusts one hour of playtesting over ten hours of discussion, demands every mechanic serve the core fantasy. Speaks like an excited streamer — enthusiastic, asking about player motivations, celebrating every breakthrough with a full-volume Let's GOOO."
+
+  - code: gds-agent-tech-writer
+    name: Paige
+    title: Technical Writer
+    icon: "📚"
+    team: game-dev
+    description: "Writes with Julia Evans's accessibility and Edward Tufte's visual precision, expert in CommonMark, DITA, OpenAPI, and Mermaid, prefers a diagram over a thousand-word paragraph, modulates detail to the audience. Speaks like a patient educator explaining like teaching a friend, using analogies that make complex things feel simple."
+
+  - code: gds-agent-game-solo-dev
+    name: Indie
+    title: Game Solo Dev
+    icon: "🎮"
+    team: game-dev
+    description: "Channels Eric Barone's years-long Stardew Valley solo grind and Edmund McMillen's ship-it-and-iterate indie hustle, prototypes fast and iterates faster, trusts a playable build over a perfect design doc, treats performance as a feature. Speaks direct, confident, gameplay-focused — dev slang, game-feel-first thinking, every response moves the game closer to ship."
+
+  - code: gds-agent-game-dev
+    name: Link Freeman
+    title: Game Developer
+    icon: "🕹️"
+    team: game-dev
+    description: "Channels Casey Muratori's hands-on engine craftsmanship and Naoki Yoshida's ruthless-shipping discipline, writes code designers can iterate without fear, runs red-green-refactor, treats flaky tests as worse than no tests. Speaks like a speedrunner — direct, milestone-focused, milestones as save points, blockers as boss fights, test suites as splits."

package/lib/bmad-cache/gds/src/workflows/1-preproduction/gds-brainstorm-game/customize.toml

@@ -1,41 +1,41 @@
-# DO NOT EDIT -- overwritten on every update.
-#
-# Workflow customization surface for gds-brainstorm-game. Mirrors the
-# agent customization shape under the [workflow] namespace.
-
-[workflow]
-
-# --- Configurable below. Overrides merge per BMad structural rules: ---
-#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
-#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
-
-# Steps to run before the standard activation (config load, greet).
-# Overrides append. Use for pre-flight loads, compliance checks, etc.
-
-activation_steps_prepend = []
-
-# Steps to run after greet but before the workflow begins.
-# Overrides append. Use for context-heavy setup that should happen
-# once the user has been acknowledged.
-
-activation_steps_append = []
-
-# Persistent facts the workflow keeps in mind for the whole run
-# (standards, compliance constraints, stylistic guardrails).
-# Distinct from the runtime memory sidecar — these are static context
-# loaded on activation. Overrides append.
-#
-# Each entry is either:
-#   - a literal sentence, e.g. "Brainstorming is divergent — defer convergence and critique until ideation is complete."
-#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
-#     (glob patterns are supported; the file's contents are loaded and treated as facts).
-
-persistent_facts = [
-  "file:{project-root}/**/project-context.md",
-]
-
-# Scalar: executed when the workflow reaches Step 4 (Complete Session),
-# after the final outputs are produced. Override wins.
-# Leave empty for no custom post-completion behavior.
-
-on_complete = ""
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-brainstorm-game. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Brainstorming is divergent — defer convergence and critique until ideation is complete."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 4 (Complete Session),
+# after the final outputs are produced. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""

package/lib/bmad-cache/gds/src/workflows/1-preproduction/gds-brainstorm-game/game-brain-methods.csv

@@ -1,26 +1,26 @@
-category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
-game_design,MDA Framework Exploration,Explore game concepts through Mechanics-Dynamics-Aesthetics lens to ensure cohesive design from implementation to player experience,What mechanics create the core loop?|What dynamics emerge from these mechanics?|What aesthetic experience results?|How do they align?,holistic-design,moderate,20-30
-game_design,Core Loop Brainstorming,Design the fundamental moment-to-moment gameplay loop that players repeat - the heartbeat of your game,What does the player do?|What's the immediate reward?|Why do it again?|How does it evolve?,gameplay-foundation,high,15-25
-game_design,Player Fantasy Mining,Identify and amplify the core fantasy that players want to embody - what makes them feel powerful and engaged,What fantasy does the player live?|What makes them feel awesome?|What power do they wield?|What identity do they assume?,player-motivation,high,15-20
-game_design,Genre Mashup,Combine unexpected game genres to create innovative hybrid experiences that offer fresh gameplay,Take two unrelated genres|How do they merge?|What unique gameplay emerges?|What's the hook?,innovation,high,15-20
-game_design,Verbs Before Nouns,Focus on what players DO before what things ARE - prioritize actions over objects for engaging gameplay,What verbs define your game?|What actions feel good?|Build mechanics from verbs|Nouns support actions,mechanics-first,moderate,20-25
-game_design,Failure State Design,Work backwards from interesting failure conditions to create tension and meaningful choices,How can players fail interestingly?|What makes failure feel fair?|How does failure teach?|Recovery mechanics?,challenge-design,moderate,15-20
-game_design,Progression Curve Sculpting,Map the player's emotional and skill journey from tutorial to mastery - pace challenge and revelation,How does difficulty evolve?|When do we introduce concepts?|What's the skill ceiling?|How do we maintain flow?,pacing-balance,moderate,25-30
-game_design,Emergence Engineering,Design simple rule interactions that create complex unexpected player-driven outcomes,What simple rules combine?|What emerges from interactions?|How do players surprise you?|Systemic possibilities?,depth-complexity,moderate,20-25
-game_design,Accessibility Layers,Brainstorm how different skill levels and abilities can access your core experience meaningfully,Who might struggle with what?|What alternate inputs exist?|How do we preserve challenge?|Inclusive design options?,inclusive-design,moderate,20-25
-game_design,Reward Schedule Architecture,Design the timing and type of rewards to maintain player motivation and engagement,What rewards when?|Variable or fixed schedule?|Intrinsic vs extrinsic rewards?|Progression satisfaction?,engagement-retention,moderate,20-30
-narrative_game,Ludonarrative Harmony,Align story and gameplay so mechanics reinforce narrative themes - make meaning through play,What does gameplay express?|How do mechanics tell story?|Where do they conflict?|How to unify theme?,storytelling,moderate,20-25
-narrative_game,Environmental Storytelling,Use world design and ambient details to convey narrative without explicit exposition,What does the space communicate?|What happened here before?|Visual narrative clues?|Show don't tell?,world-building,moderate,15-20
-narrative_game,Player Agency Moments,Identify key decision points where player choice shapes narrative in meaningful ways,What choices matter?|How do consequences manifest?|Branch vs flavor choices?|Meaningful agency where?,player-choice,moderate,20-25
-narrative_game,Emotion Targeting,Design specific moments intended to evoke targeted emotional responses through integrated design,What emotion when?|How do all elements combine?|Music + mechanics + narrative?|Orchestrated feelings?,emotional-design,high,20-30
-systems_game,Economy Balancing Thought Experiments,Explore resource generation/consumption balance to prevent game-breaking exploits,What resources exist?|Generation vs consumption rates?|What loops emerge?|Where's the exploit?,economy-design,moderate,25-30
-systems_game,Meta-Game Layer Design,Brainstorm progression systems that persist beyond individual play sessions,What carries over between sessions?|Long-term goals?|How does meta feed core loop?|Retention hooks?,retention-systems,moderate,20-25
-multiplayer_game,Social Dynamics Mapping,Anticipate how players will interact and design mechanics that support desired social behaviors,How will players cooperate?|Competitive dynamics?|Toxic behavior prevention?|Positive interaction rewards?,social-design,moderate,20-30
-multiplayer_game,Spectator Experience Design,Consider how watching others play can be entertaining - esports and streaming potential,What's fun to watch?|Readable visual clarity?|Highlight moments?|Narrative for observers?,spectator-value,moderate,15-20
-creative_game,Constraint-Based Creativity,Embrace a specific limitation as your core design constraint and build everything around it,Pick a severe constraint|What if this was your ONLY mechanic?|Build a full game from limitation|Constraint as creativity catalyst,innovation,moderate,15-25
-creative_game,Game Feel Playground,Focus purely on how controls and feedback FEEL before worrying about context or goals,What feels juicy to do?|Controller response?|Visual/audio feedback?|Satisfying micro-interactions?,game-feel,high,20-30
-creative_game,One Button Game Challenge,Design interesting gameplay using only a single input - forces elegant simplicity,Only one button - what can it do?|Context changes meaning?|Timing variations?|Depth from simplicity?,minimalist-design,moderate,15-20
-wild_game,Remix an Existing Game,Take a well-known game and twist one core element - what new experience emerges?,Pick a famous game|Change ONE fundamental rule|What ripples from that change?|New game from mutation?,rapid-prototyping,high,10-15
-wild_game,Anti-Game Design,Design a game that deliberately breaks common conventions - subvert player expectations,What if we broke this rule?|Expectation subversion?|Anti-patterns as features?|Avant-garde possibilities?,experimental,moderate,15-20
-wild_game,Physics Playground,Start with an interesting physics interaction and build a game around that sensation,What physics are fun to play with?|Build game from physics toy|Emergent physics gameplay?|Sensation first?,prototype-first,high,15-25
+category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
+game_design,MDA Framework Exploration,Explore game concepts through Mechanics-Dynamics-Aesthetics lens to ensure cohesive design from implementation to player experience,What mechanics create the core loop?|What dynamics emerge from these mechanics?|What aesthetic experience results?|How do they align?,holistic-design,moderate,20-30
+game_design,Core Loop Brainstorming,Design the fundamental moment-to-moment gameplay loop that players repeat - the heartbeat of your game,What does the player do?|What's the immediate reward?|Why do it again?|How does it evolve?,gameplay-foundation,high,15-25
+game_design,Player Fantasy Mining,Identify and amplify the core fantasy that players want to embody - what makes them feel powerful and engaged,What fantasy does the player live?|What makes them feel awesome?|What power do they wield?|What identity do they assume?,player-motivation,high,15-20
+game_design,Genre Mashup,Combine unexpected game genres to create innovative hybrid experiences that offer fresh gameplay,Take two unrelated genres|How do they merge?|What unique gameplay emerges?|What's the hook?,innovation,high,15-20
+game_design,Verbs Before Nouns,Focus on what players DO before what things ARE - prioritize actions over objects for engaging gameplay,What verbs define your game?|What actions feel good?|Build mechanics from verbs|Nouns support actions,mechanics-first,moderate,20-25
+game_design,Failure State Design,Work backwards from interesting failure conditions to create tension and meaningful choices,How can players fail interestingly?|What makes failure feel fair?|How does failure teach?|Recovery mechanics?,challenge-design,moderate,15-20
+game_design,Progression Curve Sculpting,Map the player's emotional and skill journey from tutorial to mastery - pace challenge and revelation,How does difficulty evolve?|When do we introduce concepts?|What's the skill ceiling?|How do we maintain flow?,pacing-balance,moderate,25-30
+game_design,Emergence Engineering,Design simple rule interactions that create complex unexpected player-driven outcomes,What simple rules combine?|What emerges from interactions?|How do players surprise you?|Systemic possibilities?,depth-complexity,moderate,20-25
+game_design,Accessibility Layers,Brainstorm how different skill levels and abilities can access your core experience meaningfully,Who might struggle with what?|What alternate inputs exist?|How do we preserve challenge?|Inclusive design options?,inclusive-design,moderate,20-25
+game_design,Reward Schedule Architecture,Design the timing and type of rewards to maintain player motivation and engagement,What rewards when?|Variable or fixed schedule?|Intrinsic vs extrinsic rewards?|Progression satisfaction?,engagement-retention,moderate,20-30
+narrative_game,Ludonarrative Harmony,Align story and gameplay so mechanics reinforce narrative themes - make meaning through play,What does gameplay express?|How do mechanics tell story?|Where do they conflict?|How to unify theme?,storytelling,moderate,20-25
+narrative_game,Environmental Storytelling,Use world design and ambient details to convey narrative without explicit exposition,What does the space communicate?|What happened here before?|Visual narrative clues?|Show don't tell?,world-building,moderate,15-20
+narrative_game,Player Agency Moments,Identify key decision points where player choice shapes narrative in meaningful ways,What choices matter?|How do consequences manifest?|Branch vs flavor choices?|Meaningful agency where?,player-choice,moderate,20-25
+narrative_game,Emotion Targeting,Design specific moments intended to evoke targeted emotional responses through integrated design,What emotion when?|How do all elements combine?|Music + mechanics + narrative?|Orchestrated feelings?,emotional-design,high,20-30
+systems_game,Economy Balancing Thought Experiments,Explore resource generation/consumption balance to prevent game-breaking exploits,What resources exist?|Generation vs consumption rates?|What loops emerge?|Where's the exploit?,economy-design,moderate,25-30
+systems_game,Meta-Game Layer Design,Brainstorm progression systems that persist beyond individual play sessions,What carries over between sessions?|Long-term goals?|How does meta feed core loop?|Retention hooks?,retention-systems,moderate,20-25
+multiplayer_game,Social Dynamics Mapping,Anticipate how players will interact and design mechanics that support desired social behaviors,How will players cooperate?|Competitive dynamics?|Toxic behavior prevention?|Positive interaction rewards?,social-design,moderate,20-30
+multiplayer_game,Spectator Experience Design,Consider how watching others play can be entertaining - esports and streaming potential,What's fun to watch?|Readable visual clarity?|Highlight moments?|Narrative for observers?,spectator-value,moderate,15-20
+creative_game,Constraint-Based Creativity,Embrace a specific limitation as your core design constraint and build everything around it,Pick a severe constraint|What if this was your ONLY mechanic?|Build a full game from limitation|Constraint as creativity catalyst,innovation,moderate,15-25
+creative_game,Game Feel Playground,Focus purely on how controls and feedback FEEL before worrying about context or goals,What feels juicy to do?|Controller response?|Visual/audio feedback?|Satisfying micro-interactions?,game-feel,high,20-30
+creative_game,One Button Game Challenge,Design interesting gameplay using only a single input - forces elegant simplicity,Only one button - what can it do?|Context changes meaning?|Timing variations?|Depth from simplicity?,minimalist-design,moderate,15-20
+wild_game,Remix an Existing Game,Take a well-known game and twist one core element - what new experience emerges?,Pick a famous game|Change ONE fundamental rule|What ripples from that change?|New game from mutation?,rapid-prototyping,high,10-15
+wild_game,Anti-Game Design,Design a game that deliberately breaks common conventions - subvert player expectations,What if we broke this rule?|Expectation subversion?|Anti-patterns as features?|Avant-garde possibilities?,experimental,moderate,15-20
+wild_game,Physics Playground,Start with an interesting physics interaction and build a game around that sensation,What physics are fun to play with?|Build game from physics toy|Emergent physics gameplay?|Sensation first?,prototype-first,high,15-25
 wild_game,Toy Before Game,Create a playful interactive toy with no goals first - then discover the game within it,What's fun to mess with?|No goals yet - just play|What game emerges organically?|Toy to game evolution?,discovery-design,high,20-30