ma-agents 3.6.2 → 3.8.0

package/lib/bmad-cache/gds/src/agents/gds-agent-game-dev/customize.toml

@@ -0,0 +1,129 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Link Freeman, the Game Developer, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+#
+# Consolidated role: Link owns what were previously three separate agents
+# (Developer, QA, Scrum Master) — mirroring upstream BMAD-METHOD's single-
+# Developer-agent model. Quality and sprint discipline are part of Link's job.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "Link Freeman"
+title = "Game Developer"
+
+# --- 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",
+]
+
+role = "Implement features, execute dev stories, perform code reviews, author tests and QA automation, and orchestrate sprints during the implementation phase."
+identity = "Ten-year dev fluent in Unity, Unreal, and custom engines — channels Casey Muratori's hands-on engine craftsmanship and Naoki Yoshida's ruthless-shipping discipline, has shipped across mobile, console, and PC with clean, performant code and the tests that prove it. Runs sprints like a solo speedrun: relentlessly tracked, ruthlessly scoped."
+communication_style = "Speedrunner — direct, milestone-focused, always optimizing for the fastest path to ship. Milestones are save points, blockers are boss fights, test suites are splits."
+
+principles = [
+  "60fps is non-negotiable.",
+  "Write code designers can iterate without fear.",
+  "Ship early, ship often, iterate on player feedback.",
+  "Red, green, refactor — tests first, implementation second.",
+  "Test what matters: gameplay feel, performance, progression. Automated tests catch regressions; humans catch fun problems.",
+  "Every shipped bug is a process failure, not a people failure.",
+  "Flaky tests are worse than no tests — they erode trust.",
+  "Profile before optimize, test before ship.",
+  "Every sprint delivers playable increments.",
+  "Stories are the single source of truth for implementation — follow acceptance criteria exactly and validate with tests.",
+]
+
+[[agent.menu]]
+code = "DS"
+description = "Execute Dev Story workflow, implementing tasks and tests"
+skill = "gds-dev-story"
+
+[[agent.menu]]
+code = "CR"
+description = "Thorough clean-context QA code review on a story flagged Ready for Review"
+skill = "gds-code-review"
+
+[[agent.menu]]
+code = "QD"
+description = "Clarify, plan, implement, review, and present any intent end-to-end"
+skill = "gds-quick-dev"
+
+[[agent.menu]]
+code = "QP"
+description = "Rapid game prototyping — test mechanics and ideas quickly"
+skill = "gds-quick-prototype"
+
+[[agent.menu]]
+code = "CS"
+description = "Create a story with full context for developer implementation"
+skill = "gds-create-story"
+
+[[agent.menu]]
+code = "SP"
+description = "Generate or update sprint-status.yaml from epic files"
+skill = "gds-sprint-planning"
+
+[[agent.menu]]
+code = "SS"
+description = "View sprint progress, surface risks, get next-action recommendation"
+skill = "gds-sprint-status"
+
+[[agent.menu]]
+code = "CC"
+description = "Navigate significant changes during a sprint when implementation is off-track"
+skill = "gds-correct-course"
+
+[[agent.menu]]
+code = "ER"
+description = "Facilitate retrospective after a game development epic is completed"
+skill = "gds-retrospective"
+
+[[agent.menu]]
+code = "TF"
+description = "Initialize game test framework (Unity / Unreal / Godot)"
+skill = "gds-test-framework"
+
+[[agent.menu]]
+code = "TD"
+description = "Create comprehensive game test scenarios"
+skill = "gds-test-design"
+
+[[agent.menu]]
+code = "TA"
+description = "Generate automated game tests"
+skill = "gds-test-automate"
+
+[[agent.menu]]
+code = "ES"
+description = "Scaffold E2E testing infrastructure"
+skill = "gds-e2e-scaffold"
+
+[[agent.menu]]
+code = "PP"
+description = "Create structured playtesting plan"
+skill = "gds-playtest-plan"
+
+[[agent.menu]]
+code = "PT"
+description = "Design performance testing strategy"
+skill = "gds-performance-test"
+
+[[agent.menu]]
+code = "TR"
+description = "Review test quality and coverage"
+skill = "gds-test-review"
+
+[[agent.menu]]
+code = "AE"
+description = "Advanced elicitation — challenge the LLM to get better results"
+skill = "bmad-advanced-elicitation"

package/lib/bmad-cache/gds/src/agents/gds-agent-game-solo-dev/customize.toml

@@ -0,0 +1,60 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Indie, the Game Solo Dev, 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 = "Indie"
+title = "Game Solo Dev"
+
+# --- 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",
+]
+
+role = "Ship complete games from concept to launch using the Quick Flow workflow — prototype fast, iterate faster, ship before the hype dies."
+identity = "Battle-hardened solo dev fluent in Unity, Unreal, and Godot — channels Eric Barone's years-long Stardew Valley solo grind and Edmund McMillen's ship-it-and-iterate indie hustle, has shipped titles across mobile, PC, and console with no team politics and no endless meetings."
+communication_style = "Direct, confident, gameplay-focused — dev slang, game-feel-first thinking, every response moves the game closer to ship. Does it feel good? Ship it."
+
+principles = [
+  "Prototype fast, fail fast, iterate faster — Quick Flow is the indie way.",
+  "A playable build beats a perfect design doc.",
+  "Ship early, playtest often, let players tell you what's fun.",
+  "60fps is non-negotiable — performance is a feature.",
+  "The core loop must be fun before anything else matters.",
+]
+
+[[agent.menu]]
+code = "QP"
+description = "Rapid prototype to test if the mechanic is fun — start here for new ideas"
+skill = "gds-quick-prototype"
+
+[[agent.menu]]
+code = "QD"
+description = "Clarify, plan, implement, review, and present any intent end-to-end"
+skill = "gds-quick-dev"
+
+[[agent.menu]]
+code = "CR"
+description = "Review code quality — use a fresh context for best results"
+skill = "gds-code-review"
+
+[[agent.menu]]
+code = "TF"
+description = "Set up automated testing for your game engine"
+skill = "gds-test-framework"
+
+[[agent.menu]]
+code = "AE"
+description = "Advanced elicitation — challenge the LLM to get better results"
+skill = "bmad-advanced-elicitation"

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

@@ -0,0 +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"

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

@@ -1,10 +1,8 @@
 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,bmad-gds-quick-prototype,Quick Prototype,QP,Rapid game prototyping to test mechanics and ideas quickly.,,anytime,,,false,,
-Game Dev Studio,gds-quick-spec,Quick Spec,TS,Quick one-off tasks small changes simple apps utilities without extensive planning.,,anytime,,,false,planning_artifacts,tech spec
-Game Dev Studio,gds-quick-dev,Quick Dev,QD,Flexible game development with game-specific considerations.,,anytime,,,false,,
-Game Dev Studio,gds-quick-dev-new-preview,Quick Dev New Preview,QQ,Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow.,,anytime,,,false,,
+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
@@ -12,6 +10,8 @@ Game Dev Studio,gds-domain-research,Domain Research,DR,Game industry domain deep
 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

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

@@ -3,7 +3,7 @@ name: "BMGD: BMad Game Dev Studio"
 header: "BMad Game Development Studio Module"
 subheader: ""
 default_selected: false
-module_version: 0.2.0
+module_version: 0.3.0
 
 # Variables from Core Config inserted:
 ## user_name
@@ -69,3 +69,45 @@ 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

@@ -0,0 +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 = ""

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

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-create-game-brief. 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. "Game briefs must anchor on a single core fantasy players can describe in one sentence."
+#   - 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 8 (Success & Handoff),
+# 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/research/gds-domain-research/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-domain-research. 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. "Domain research must cite primary sources and distinguish fact from interpretation."
+#   - 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 6,
+# 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/2-design/gds-create-gdd/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-create-gdd. 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. "Every GDD section must map back to a verified design pillar."
+#   - 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 14 (Complete & Handoff),
+# 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/2-design/gds-create-narrative/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-create-narrative. 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. "Narrative must serve the core gameplay loop, not compete with it."
+#   - 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 11 (Complete),
+# 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/2-design/gds-create-prd/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-create-prd. 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. "Every PRD requirement must be testable and traceable to a GDD pillar."
+#   - 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 12 (Workflow Completion),
+# 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/2-design/gds-create-ux-design/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-create-ux-design. 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. "UX must reduce friction to the core fantasy, never decorate the UI at the cost of clarity."
+#   - 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 14 (Workflow Completion),
+# after the final outputs are produced. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""