The install directory is now configurable, with a few minute issues

This commit is contained in:
Brian Madison
2025-11-08 13:58:43 -06:00
parent a4bbfc4b6e
commit 1728acfb0f
224 changed files with 1303 additions and 1036 deletions

View File

@@ -135,7 +135,7 @@ bmgd/
## Configuration
After installation, configure the module in `bmad/bmgd/config.yaml`
After installation, configure the module in `{bmad_folder}/bmgd/config.yaml`
Key settings:

View File

@@ -16,6 +16,8 @@ prompt:
## document_output_language
## output_folder
## bmad_folder
## install_user_docs
## kb_install
game_project_name:
prompt: "What is the name of your game project?"
@@ -23,18 +25,18 @@ game_project_name:
result: "{value}"
game_design_docs:
prompt: "Where should game design documents (GDD, narrative, etc.) be stored?"
default: "docs/design"
prompt: "Where should game design and planning documents (GDD, narrative, etc.) be stored?"
default: "{output_folder}/design"
result: "{project-root}/{value}"
game_tech_docs:
prompt: "Where should game technical documentation be stored?"
default: "docs/technical"
tech_docs:
prompt: "Where should technical reference documents be stored?"
default: "{output_folder}/technical"
result: "{project-root}/{value}"
game_story_location:
prompt: "Where should game development stories be stored?"
default: "docs/stories"
dev_ephemeral_location:
prompt: "Where should ephemeral development artifacts be stored (stories, epics, temp context, etc...)?"
default: "{bmad_folder}-ephemeral"
result: "{project-root}/{value}"
game_dev_experience:
@@ -51,7 +53,8 @@ game_dev_experience:
specified_framework:
prompt: "Which game development framework or engine do you want to install support for?"
default: "unity"
default: ["unity", "unreal", "godot", "other"]
required: true
result: "{value}"
multi-select:
- value: "unity"
@@ -60,8 +63,8 @@ specified_framework:
label: "Unreal Engine"
- value: "godot"
label: "Godot"
- value: "custom"
- value: "other"
label: "Custom / Other"
data_path:
result: "{project-root}/bmad/bmgd/data"
result: "{project-root}/{bmad_folder}/bmgd/data"

View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmgd/agents/game-architect.md
id: "{bmad_folder}/bmgd/agents/game-architect.md"
name: Cloud Dragonborn
title: Game Architect
icon: 🏛️
@@ -19,10 +19,10 @@ agent:
menu:
- trigger: correct-course
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
description: Course Correction Analysis
- trigger: create-architecture
workflow: "{project-root}/bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
description: Produce a Scale Adaptive Game Architecture

View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmgd/agents/game-designer.md
id: "{bmad_folder}/bmgd/agents/game-designer.md"
name: Samus Shepard
title: Game Designer
icon: 🎲
@@ -19,17 +19,17 @@ agent:
menu:
- trigger: brainstorm-game
workflow: "{project-root}/bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
description: 1. Guide me through Game Brainstorming
- trigger: create-game-brief
workflow: "{project-root}/bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
description: 3. Create Game Brief
- trigger: create-gdd
workflow: "{project-root}/bmad/bmgd/workflows/2-design/gdd/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd/workflow.yaml"
description: 4. Create Game Design Document (GDD)
- trigger: narrative
workflow: "{project-root}/bmad/bmgd/workflows/2-design/narrative/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative/workflow.yaml"
description: 5. Create Narrative Design Document (story-driven games)

View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmgd/agents/game-dev.md
id: "{bmad_folder}/bmgd/agents/game-dev.md"
name: Link Freeman
title: Game Developer
icon: 🕹️
@@ -19,16 +19,16 @@ agent:
menu:
- trigger: develop-story
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/dev-story/workflow.yaml"
description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
- trigger: code-review
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/code-review/workflow.yaml"
description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"
- trigger: story-done
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/story-done/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-done/workflow.yaml"
description: "Mark story done after DoD complete"

View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmgd/agents/game-scrum-master.md
id: "{bmad_folder}/bmgd/agents/game-scrum-master.md"
name: Max
title: Game Dev Scrum Master
icon: 🎯
@@ -22,49 +22,49 @@ agent:
menu:
- trigger: sprint-planning
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
description: Generate or update sprint-status.yaml from epic files
- trigger: epic-tech-context
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
description: (Optional) Use the GDD and Architecture to create an Epic-Tech-Spec for a specific epic
- trigger: validate-epic-tech-context
validate-workflow: "{project-root}/bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
description: (Optional) Validate latest Tech Spec against checklist
- trigger: create-story-draft
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml"
description: Create a Story Draft for a game feature
- trigger: validate-create-story
validate-workflow: "{project-root}/bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml"
description: (Optional) Validate Story Draft with Independent Review
- trigger: story-context
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev
- trigger: validate-story-context
validate-workflow: "{project-root}/bmad/bmgd/workflows/4-production/story-context/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
description: (Optional) Validate latest Story Context XML against checklist
- trigger: story-ready-for-dev
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/story-ready/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-ready/workflow.yaml"
description: (Optional) Mark drafted story ready for dev without generating Story Context
- trigger: epic-retrospective
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/retrospective/workflow.yaml"
data: "{project-root}/bmad/_cfg/agent-manifest.csv"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/retrospective/workflow.yaml"
data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
description: (Optional) Facilitate team retrospective after a game development epic is completed
- trigger: correct-course
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow-install: "{project-root}/bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
description: (Optional) Navigate significant changes during game dev sprint

View File

@@ -1,4 +1,4 @@
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>

View File

@@ -4,7 +4,7 @@ description: "Facilitate game brainstorming sessions by orchestrating the CIS br
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience"
date: system-generated
# Module path and component files
installed_path: "{project-root}/bmad/bmgd/workflows/1-preproduction/brainstorm-game"
installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game"
template: false
instructions: "{installed_path}/instructions.md"
@@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md"
game_brain_methods: "{installed_path}/game-brain-methods.csv"
# CORE brainstorming workflow to invoke
core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
core_brainstorming: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
standalone: true
@@ -30,12 +30,12 @@ web_bundle:
name: "brainstorm-game"
description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."
author: "BMad"
instructions: "bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
template: false
web_bundle_files:
- "bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
- "bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
- "bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
- "bmad/core/workflows/brainstorming/workflow.yaml"
- "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md"
- "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
- "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
- "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
existing_workflows:
- core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"
- core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"

View File

@@ -1,6 +1,6 @@
# Game Brief - Interactive Workflow Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

View File

@@ -4,7 +4,7 @@ description: "Interactive game brief creation workflow that guides users through
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -21,7 +21,7 @@ recommended_inputs:
- reference_games: "List of inspiration games (optional)"
# Module path and component files
installed_path: "{project-root}/bmad/bmgd/workflows/1-preproduction/game-brief"
installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -35,10 +35,10 @@ web_bundle:
name: "game-brief"
description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
author: "BMad"
instructions: "bmad/bmgd/workflows/1-preproduction/game-brief/instructions.md"
validation: "bmad/bmgd/workflows/1-preproduction/game-brief/checklist.md"
template: "bmad/bmgd/workflows/1-preproduction/game-brief/template.md"
instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md"
validation: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md"
template: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md"
web_bundle_files:
- "bmad/bmgd/workflows/1-preproduction/game-brief/instructions.md"
- "bmad/bmgd/workflows/1-preproduction/game-brief/checklist.md"
- "bmad/bmgd/workflows/1-preproduction/game-brief/template.md"
- "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md"
- "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md"
- "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md"

View File

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -34,7 +34,7 @@ This workflow requires: game brief, and may reference market research or brownfi
<step n="0" goal="Validate workflow and extract project configuration">
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: data</param>
<param>data_request: project_config</param>
</invoke-workflow>
@@ -221,7 +221,7 @@ Get core game concept and vision.
<action>Guide user to define the primary game mechanics that players will interact with throughout the game</action>
<template-output>primary_mechanics</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<action>Guide user to describe their control scheme and input method (keyboard/mouse, gamepad, touchscreen, etc.), including key bindings or button layouts if known</action>
@@ -239,7 +239,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
<template-output file="GDD.md">GAME_TYPE_SPECIFIC_SECTIONS</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
@@ -304,7 +304,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
<action>Work with user to translate game features into development epics, following level-appropriate guidelines (Level 1: 1 epic/1-10 stories, Level 2: 1-2 epics/5-15 stories, Level 3: 2-5 epics/12-40 stories, Level 4: 5+ epics/40+ stories)</action>
<template-output>epics</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
@@ -325,7 +325,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
<for-each epic="epic_list">
<template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</for-each>
@@ -403,7 +403,7 @@ Your choice:</ask>
</check>
<check if="user selects option 1 or fuzzy indicates wanting to create the narrative design document">
<invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
<invoke-workflow>{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
<action>Pass GDD context to narrative workflow</action>
<action>Exit current workflow (narrative will hand off to solutioning when done)</action>
@@ -497,7 +497,7 @@ Which would you like to proceed with?</ask>
</check>
<check if="user selects narrative option">
<invoke-workflow>{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
<invoke-workflow>{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml</invoke-workflow>
<action>Pass GDD context to narrative workflow</action>
</check>

View File

@@ -4,7 +4,7 @@ description: "Game Design Document workflow for all game project levels - from s
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmgd/workflows/2-design/gdd"
installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd"
instructions: "{installed_path}/instructions-gdd.md"
template: "{installed_path}/gdd-template.md"
game_types_csv: "{installed_path}/game-types.csv"
@@ -50,32 +50,32 @@ web_bundle:
name: "gdd"
description: "Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance."
author: "BMad"
instructions: "bmad/bmgd/workflows/2-design/gdd/instructions-gdd.md"
instructions: "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md"
web_bundle_files:
- "bmad/bmgd/workflows/2-design/gdd/instructions-gdd.md"
- "bmad/bmgd/workflows/2-design/gdd/gdd-template.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types.csv"
- "bmad/bmgd/workflows/2-design/gdd/game-types/action-platformer.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/adventure.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/card-game.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/fighting.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/horror.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/idle-incremental.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/metroidvania.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/moba.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/party-game.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/puzzle.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/racing.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/rhythm.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/roguelike.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/rpg.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/sandbox.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/shooter.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/simulation.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/sports.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/strategy.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/survival.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/text-based.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/tower-defense.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/turn-based-tactics.md"
- "bmad/bmgd/workflows/2-design/gdd/game-types/visual-novel.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/gdd-template.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types.csv"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/action-platformer.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/adventure.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/card-game.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/fighting.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/horror.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/idle-incremental.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/metroidvania.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/moba.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/party-game.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/puzzle.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/racing.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rhythm.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/roguelike.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rpg.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sandbox.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/shooter.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/simulation.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sports.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/strategy.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/survival.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/text-based.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/tower-defense.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/turn-based-tactics.md"
- "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/visual-novel.md"

View File

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already completed the GDD workflow</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow creates detailed narrative content for story-driven games</critical>
@@ -143,7 +143,7 @@ For 3-Act:
Describe each act/section for your game:</ask>
<template-output>act_breakdown</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
@@ -162,7 +162,7 @@ Format:
Your story beats:</ask>
<template-output>story_beats</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<ask>Describe the pacing and flow of your narrative.
@@ -195,7 +195,7 @@ For each protagonist include:
Your protagonist(s):</ask>
<template-output>protagonists</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
@@ -233,7 +233,7 @@ For each character include:
Your supporting characters:</ask>
<template-output>supporting_characters</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
@@ -281,7 +281,7 @@ Your world:</ask>
Your history:</ask>
<template-output>history_backstory</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>

View File

@@ -4,7 +4,7 @@ description: "Narrative design workflow for story-driven games and applications.
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmgd/workflows/2-design/narrative"
installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative"
instructions: "{installed_path}/instructions-narrative.md"
template: "{installed_path}/narrative-template.md"
@@ -32,7 +32,7 @@ web_bundle:
name: "narrative"
description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."
author: "BMad"
instructions: "bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md"
instructions: "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md"
web_bundle_files:
- "bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md"
- "bmad/bmgd/workflows/2-design/narrative/narrative-template.md"
- "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md"
- "{bmad_folder}/bmgd/workflows/2-design/narrative/narrative-template.md"

View File

@@ -2,7 +2,7 @@
<workflow name="architecture">
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>
@@ -363,7 +363,7 @@ Provided by Starter: {{yes_if_from_starter}}
</action>
<template-output>decision_record</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="5" goal="Address cross-cutting concerns">
@@ -393,7 +393,7 @@ Provided by Starter: {{yes_if_from_starter}}
</action>
<template-output>project_structure</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="7" goal="Design novel architectural patterns" optional="true">
@@ -467,7 +467,7 @@ Provided by Starter: {{yes_if_from_starter}}
</check>
<template-output>novel_pattern_designs</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="8" goal="Define implementation patterns to prevent agent conflicts">
@@ -560,7 +560,7 @@ Enforcement: "All agents MUST follow this pattern"
</action>
<template-output>implementation_patterns</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="9" goal="Validate architectural coherence">
@@ -614,7 +614,7 @@ Enforcement: "All agents MUST follow this pattern"
</action>
<template-output>architecture_document</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="11" goal="Validate document completeness">

View File

@@ -4,7 +4,7 @@ description: "Collaborative game architecture workflow for AI-agent consistency.
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -37,7 +37,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Module path and component files
installed_path: "{project-root}/bmad/bmgd/workflows/3-technical/game-architecture"
installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/architecture-template.md"

View File

@@ -1,7 +1,7 @@
# Senior Developer Review - Workflow Instructions
````xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -376,7 +376,7 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
</step>
<step n="10" goal="Validation and completion">
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<action>Report workflow completion.</action>
<check if="ad_hoc_review_mode == true">

View File

@@ -4,7 +4,7 @@ description: "Perform a Senior Developer code review on a completed story flagge
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/code-review"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -23,7 +23,7 @@ template: false
# Variables (can be provided by caller)
variables:
story_path: "" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
story_dir: "{config_source}:dev_story_location" # Directory containing story files
story_dir: "{config_source}:dev_ephemeral_location" # Directory containing story files
tech_spec_search_dir: "{project-root}/docs"
tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
arch_docs_search_dirs: |

View File

@@ -1,6 +1,6 @@
# Change Navigation Checklist
<critical>This checklist is executed as part of: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>This checklist is executed as part of: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>Work through each section systematically with the user, recording findings and impacts</critical>
<checklist>

View File

@@ -1,7 +1,7 @@
# Correct Course - Sprint Change Management Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

View File

@@ -3,7 +3,7 @@ name: "correct-course"
description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
author: "BMad Method"
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -11,7 +11,7 @@ user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
date: system-generated
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course"
template: false
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

View File

@@ -1,7 +1,7 @@
# Create Story - Workflow Instructions (Spec-compliant, non-interactive by default)
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Generate all documents in {document_output_language}</critical>
<critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
@@ -39,7 +39,7 @@
<workflow>
<step n="1" goal="Load config and initialize">
<action>Resolve variables from config_source: story_dir (dev_story_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
<action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
<action>Create {{story_dir}} if it does not exist</action>
<action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
<action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</action>
@@ -240,7 +240,7 @@ Will update existing story file rather than creating new one.
</step>
<step n="8" goal="Validate, save, and mark story drafted" tag="sprint-status">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<action>Save document unconditionally (non-interactive default). In interactive mode, allow user confirmation.</action>
<!-- Mark story as drafted in sprint status -->

View File

@@ -3,21 +3,21 @@ description: "Create the next user story markdown from epics/PRD and architectur
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/create-story"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
# Variables and inputs
variables:
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
prd_file: "{output_folder}/PRD.md" # Fallback for requirements
architecture_file: "{output_folder}/architecture.md" # Optional architecture context

View File

@@ -26,7 +26,7 @@ The dev-story workflow is well-structured and follows most BMAD v6 standards. Th
The workflow.yaml contains all required standard config variables:
-`config_source: "{project-root}/bmad/bmm/config.yaml"` - Correctly defined
-`config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"` - Correctly defined
-`output_folder: "{config_source}:output_folder"` - Pulls from config_source
-`user_name: "{config_source}:user_name"` - Pulls from config_source
-`communication_language: "{config_source}:communication_language"` - Pulls from config_source
@@ -67,7 +67,7 @@ These variables appear to be pulling from config.yaml but are not explicitly def
### Unused Variables (Bloat)
1. **context_path** - Defined as `"{config_source}:dev_story_location"` but never used. This duplicates `story_dir` functionality.
1. **context_path** - Defined as `"{config_source}:dev_ephemeral_location"` but never used. This duplicates `story_dir` functionality.
---
@@ -140,7 +140,7 @@ The workflow correctly sets `web_bundle: false`. This is the expected configurat
### Unused YAML Fields
1. **context_path** (line 11 in workflow.yaml)
- Defined as: `"{config_source}:dev_story_location"`
- Defined as: `"{config_source}:dev_ephemeral_location"`
- Never referenced in instructions.md
- Duplicates functionality of `story_dir` variable
- **Recommendation:** Remove this variable as `story_dir` serves the same purpose

View File

@@ -1,7 +1,7 @@
# Develop Story - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -227,7 +227,7 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s
</step>
<step n="7" goal="Completion communication and user support">
<action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.xml</action>
<action>Optionally run the workflow validation task against the story using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</action>
<action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
<action>Communicate to {user_name} that story implementation is complete and ready for review</action>

View File

@@ -3,13 +3,13 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
story_dir: "{config_source}:dev_story_location"
story_dir: "{config_source}:dev_ephemeral_location"
run_until_complete: "{config_source}:run_until_complete"
run_tests_command: "{config_source}:run_tests_command"
date: system-generated
@@ -19,7 +19,7 @@ story_file: "" # Explicit story path; auto-discovered if empty
context_file: "{story_dir}/{{story_key}}.context.xml"
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

View File

@@ -1,7 +1,7 @@
# Tech Spec Validation Checklist
```xml
<checklist id="bmad/bmm/workflows/4-implementation/epic-tech-context/checklist">
<checklist id="{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/checklist">
<item>Overview clearly ties to PRD goals</item>
<item>Scope explicitly lists in-scope and out-of-scope</item>
<item>Design lists all services/modules with responsibilities</item>

View File

@@ -1,7 +1,7 @@
<!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
@@ -157,7 +157,7 @@ Continuing to regenerate tech spec...
</step>
<step n="9" goal="Validate and mark epic contexted" tag="sprint-status">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<!-- Mark epic as contexted -->
<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>

View File

@@ -3,7 +3,7 @@ description: "Generate a comprehensive Technical Specification from PRD and Arch
author: "BMAD BMM"
# Critical variables
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -47,7 +47,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

View File

@@ -1,7 +1,7 @@
# Retrospective - Epic Completion Review Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

View File

@@ -3,7 +3,7 @@ name: "retrospective"
description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
author: "BMad"
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -11,7 +11,7 @@ user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
date: system-generated
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective"
template: false
instructions: "{installed_path}/instructions.md"
@@ -19,7 +19,7 @@ mode: interactive
trigger: "Run AFTER completing an epic"
required_inputs:
- agent_manifest: "{project-root}/bmad/_cfg/agent-manifest.csv"
- agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
# Smart input file references - handles both whole docs and sharded docs
# Priority: Whole document first, then sharded version
@@ -46,7 +46,7 @@ input_file_patterns:
# Required files
sprint_status_file: "{output_folder}/sprint-status.yaml"
story_directory: "{config_source}:dev_story_location"
story_directory: "{config_source}:dev_ephemeral_location"
retrospectives_folder: "{output_folder}/retrospectives"
output_artifacts:

View File

@@ -1,7 +1,7 @@
# Sprint Planning - Sprint Status Generator
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>
## 📚 Document Discovery - Full Epic Loading

View File

@@ -3,14 +3,14 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning"
instructions: "{installed_path}/instructions.md"
template: "{installed_path}/sprint-status-template.yaml"
validation: "{installed_path}/checklist.md"
@@ -24,7 +24,7 @@ variables:
# Tracking system configuration
tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
story_location: "{project-root}/docs/stories" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
story_location_absolute: "{config_source}:dev_story_location" # Absolute path for file operations
story_location_absolute: "{config_source}:dev_ephemeral_location" # Absolute path for file operations
# Source files (file-system only)
epics_location: "{output_folder}" # Directory containing epic*.md files

View File

@@ -1,7 +1,7 @@
# Story Context Assembly Checklist
```xml
<checklist id="bmad/bmm/workflows/4-implementation/story-context/checklist">
<checklist id="{bmad_folder}/bmm/workflows/4-implementation/story-context/checklist">
<item>Story fields (asA/iWant/soThat) captured</item>
<item>Acceptance criteria list matches story draft exactly (no invention)</item>
<item>Tasks/subtasks captured as task list</item>

View File

@@ -1,4 +1,4 @@
<story-context id="bmad/bmm/workflows/4-implementation/story-context/template" v="1.0">
<story-context id="{bmad_folder}/bmm/workflows/4-implementation/story-context/template" v="1.0">
<metadata>
<epicId>{{epic_id}}</epicId>
<storyId>{{story_id}}</storyId>

View File

@@ -1,7 +1,7 @@
<!-- BMAD BMM Story Context Assembly Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -181,7 +181,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
<step n="6" goal="Validate and save">
<anchor id="validation_step" />
<action>Validate output context file structure and content</action>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
</step>
<step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">

View File

@@ -4,16 +4,16 @@ description: "Assemble a dynamic Story Context XML by pulling latest documentati
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/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"
story_path: "{config_source}:dev_story_location"
story_path: "{config_source}:dev_ephemeral_location"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-context"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context"
template: "{installed_path}/context-template.xml"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -21,7 +21,7 @@ validation: "{installed_path}/checklist.md"
# Variables and inputs
variables:
story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
story_dir: "{config_source}:dev_story_location"
story_dir: "{config_source}:dev_ephemeral_location"
# Smart input file references - handles both whole docs and sharded docs
# Priority: Whole document first, then sharded version

View File

@@ -1,6 +1,6 @@
# Story Approved Workflow Instructions (DEV Agent)
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>

View File

@@ -4,20 +4,20 @@ description: "Marks a story as done (DoD complete) and moves it from its current
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-done"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done"
instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_path: "" # Explicit path to story file
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
# Output configuration - no output file, just status updates
default_output_file: ""

View File

@@ -1,6 +1,6 @@
# Story Ready Workflow Instructions (SM Agent)
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

View File

@@ -4,20 +4,20 @@ description: "Marks a drafted story as ready for development and moves it from T
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmgd/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready"
instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_path: "" # Explicit path to story file
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
# Output configuration - no output file, just status updates
default_output_file: ""