chore(release): 4.27.2 [skip ci]

## [4.27.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.1...v4.27.2) (2025-07-07)

### Bug Fixes

* improve output ([a5ffe7b](a5ffe7b9b2))

.gitignore

@@ -27,4 +27,4 @@ sample-project/*
 .bmad-creator-tools
 .gemini
 .bmad*/.cursor/
-web-bundles/
+web-bundles/

CHANGELOG.md

@@ -1,3 +1,17 @@
+## [4.27.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.1...v4.27.2) (2025-07-07)
+
+
+### Bug Fixes
+
+* improve output ([a5ffe7b](https://github.com/bmadcode/BMAD-METHOD/commit/a5ffe7b9b209ae02a9d97adf60fe73c0bc9701e4))
+
+## [4.27.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.0...v4.27.1) (2025-07-07)
+
+
+### Bug Fixes
+
+* build web bundles with new file extension includsion ([92201ae](https://github.com/bmadcode/BMAD-METHOD/commit/92201ae7ede620ec09b4764edaed97be42a3b78f))
+
 # [4.27.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.26.0...v4.27.0) (2025-07-06)
 
 

bmad-core/agent-teams/team-all.yaml

@@ -6,9 +6,9 @@ agents:
   - bmad-orchestrator
   - '*'
 workflows:
-  - brownfield-fullstack
-  - brownfield-service
-  - brownfield-ui
-  - greenfield-fullstack
-  - greenfield-service
-  - greenfield-ui
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

bmad-core/agent-teams/team-fullstack.yaml

@@ -10,9 +10,9 @@ agents:
   - architect
   - po
 workflows:
-  - brownfield-fullstack
-  - brownfield-service
-  - brownfield-ui
-  - greenfield-fullstack
-  - greenfield-service
-  - greenfield-ui
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

bmad-core/agent-teams/team-no-ui.yaml

@@ -9,5 +9,5 @@ agents:
   - architect
   - po
 workflows:
-  - greenfield-service
-  - brownfield-service
+  - greenfield-service.yaml
+  - brownfield-service.yaml

bmad-core/agents/analyst.md

@@ -4,13 +4,14 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-  - The customization field ALWAYS takes precedence over any conflicting instructions
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Mary
   id: analyst
@@ -35,35 +36,31 @@ persona:
     - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
     - Integrity of Information - Ensure accurate sourcing and representation
     - Numbered Options Protocol - Always use numbered lists for selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
   - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
+  - yolo: Toggle Yolo Mode
   - doc-out: Output full document to current destination file
   - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
-  - research {topic}: execute task create-deep-research-prompt for architectural decisions
+  - research-prompt {topic}: execute task create-deep-research-prompt for architectural decisions
   - brainstorm {topic}: Facilitate structured brainstorming session
-  - elicit: list the options under output set of information
+  - elicit: run the task advanced-elicitation
   - document-project: Analyze and document existing project structure comprehensively
   - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - facilitate-brainstorming-session
-    - create-deep-research-prompt
-    - create-doc
-    - advanced-elicitation
-    - document-project
+    - facilitate-brainstorming-session.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - advanced-elicitation.md
+    - document-project.md
   templates:
-    - project-brief-tmpl
-    - market-research-tmpl
-    - competitor-analysis-tmpl
-    - brainstorming-output-tmpl
+    - project-brief-tmpl.yaml
+    - market-research-tmpl.yaml
+    - competitor-analysis-tmpl.yaml
+    - brainstorming-output-tmpl.yaml
   data:
-    - bmad-kb
-    - brainstorming-techniques
-  utils:
-    - template-format
+    - bmad-kb.md
+    - brainstorming-techniques.md
 ```

bmad-core/agents/architect.md

@@ -4,13 +4,15 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
+  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
 agent:
   name: Winston
   id: architect
@@ -34,33 +36,28 @@ persona:
     - Data-Centric Design - Let data requirements drive architecture
     - Cost-Conscious Engineering - Balance technical ideals with financial reality
     - Living Architecture - Design for change and adaptation
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
   - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
+  - yolo: Toggle Yolo Mode
   - doc-out: Output full document to current destination file
   - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
   - research {topic}: execute task create-deep-research-prompt for architectural decisions
   - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - create-doc
-    - create-deep-research-prompt
-    - document-project
-    - execute-checklist
+    - create-doc.md
+    - create-deep-research-prompt.md
+    - document-project.md
+    - execute-checklist.md
   templates:
-    - architecture-tmpl
-    - front-end-architecture-tmpl
-    - fullstack-architecture-tmpl
-    - brownfield-architecture-tmpl
+    - architecture-tmpl.yaml
+    - front-end-architecture-tmpl.yaml
+    - fullstack-architecture-tmpl.yaml
+    - brownfield-architecture-tmpl.yaml
   checklists:
-    - architect-checklist
+    - architect-checklist.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
 ```

bmad-core/agents/bmad-master.md

@@ -1,11 +1,18 @@
-# bmad-master
+# BMad Master
 
 CRITICAL: Read the full YAML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+activation-instructions:
+  - Greet the user with your name and role, and inform of the *help command.
+  - Check for active workflow plan using the utils plan-management
+  - If plan exists: Show brief status - Active plan {workflow} in progress
+  - If plan exists: Suggest next step based on plan
+  - CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded
+  - CRITICAL: Do NOT run discovery tasks automatically
 agent:
   name: BMad Master
   id: bmad-master
@@ -24,13 +31,6 @@ persona:
     - Track execution state and guide multi-step plans
     - Use numbered lists for choices
     - Process (*) commands immediately, All commands require * prefix when used (e.g., *help)
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - Check for active workflow plan using the utils plan-management
-  - If plan exists: Show brief status - Active plan {workflow} in progress
-  - If plan exists: Suggest next step based on plan
-  - CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded
-  - CRITICAL: Do NOT run discovery tasks automatically
 
 commands:
   - help: Show these listed commands in a numbered list
@@ -44,7 +44,7 @@ commands:
   - plan: Execute the task Create workflow plan
   - plan-status: Show current workflow plan progress
   - plan-update: Update workflow plan status
-  - yolo: Toggle Yolo Mode off (default) abd on - on will skip doc section confirmations
+  - yolo: Toggle Yolo Mode
   - doc-out: Output full document to current destination file
   - exit: Exit (confirm)
 workflow-guidance:
@@ -59,55 +59,54 @@ execution:
   - Suggest related resources after completion
 dependencies:
   tasks:
-    - advanced-elicitation
-    - facilitate-brainstorming-session
-    - brownfield-create-epic
-    - brownfield-create-story
-    - correct-course
-    - create-deep-research-prompt
-    - create-doc
-    - create-doc2
-    - create-workflow-plan
-    - document-project
-    - create-next-story
-    - execute-checklist
-    - generate-ai-frontend-prompt
-    - index-docs
-    - shard-doc
-    - update-workflow-plan
+    - advanced-elicitation.md
+    - facilitate-brainstorming-session.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
+    - correct-course.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - create-workflow-plan.md
+    - document-project.md
+    - create-next-story.md
+    - execute-checklist.md
+    - generate-ai-frontend-prompt.md
+    - index-docs.md
+    - shard-doc.md
+    - update-workflow-plan.md
   templates:
-    - architecture-tmpl
-    - brownfield-architecture-tmpl
-    - brownfield-prd-tmpl
-    - competitor-analysis-tmpl
-    - front-end-architecture-tmpl
-    - front-end-spec-tmpl
-    - fullstack-architecture-tmpl
-    - market-research-tmpl
-    - prd-tmpl
-    - prd-tmpl2
-    - project-brief-tmpl
-    - story-tmpl
+    - architecture-tmpl.yaml
+    - brownfield-architecture-tmpl.yaml
+    - brownfield-prd-tmpl.yaml
+    - competitor-analysis-tmpl.yaml
+    - front-end-architecture-tmpl.yaml
+    - front-end-spec-tmpl.yaml
+    - fullstack-architecture-tmpl.yaml
+    - market-research-tmpl.yaml
+    - prd-tmpl.yaml
+    - project-brief-tmpl.yaml
+    - story-tmpl.yaml
   data:
-    - bmad-kb
-    - brainstorming-techniques
-    - technical-preferences
+    - bmad-kb.md
+    - brainstorming-techniques.md
+    - elicitation-methods.md
+    - technical-preferences.md
   utils:
-    - plan-management
-    - template-format
-    - workflow-management
+    - plan-management.md
+    - template-format.md
+    - workflow-management.md
   workflows:
-    - brownfield-fullstack
-    - brownfield-service
-    - brownfield-ui
-    - greenfield-fullstack
-    - greenfield-service
-    - greenfield-ui
+    - brownfield-fullstack.md
+    - brownfield-service.md
+    - brownfield-ui.md
+    - greenfield-fullstack.md
+    - greenfield-service.md
+    - greenfield-ui.md
   checklists:
-    - architect-checklist
-    - change-checklist
-    - pm-checklist
-    - po-master-checklist
-    - story-dod-checklist
-    - story-draft-checklist
+    - architect-checklist.md
+    - change-checklist.md
+    - pm-checklist.md
+    - po-master-checklist.md
+    - story-dod-checklist.md
+    - story-draft-checklist.md
 ```

bmad-core/agents/bmad-orchestrator.md

@@ -1,11 +1,22 @@
-# bmad
+# BMad Web Orchestrator
 
 CRITICAL: Read the full YAML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
+activation-instructions:
+  - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
+  - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
+  - Mention *help shows all available commands and options
+  - Check for active workflow plan using {root}/utils/plan-management.md
+  - "If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details."
+  - "If plan exists: Suggest next action based on plan progress"
+  - Assess user goal against available agents and workflows in this bundle
+  - If clear match to an agent's expertise, suggest transformation with *agent command
+  - If project-oriented, suggest *workflow-guidance to explore options
+  - Load resources only when needed - never pre-load
 agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
@@ -27,17 +38,6 @@ persona:
     - Always use numbered lists for choices
     - Process commands starting with * immediately
     - Always remind users that commands require * prefix
-startup:
-  - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
-  - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
-  - Mention *help shows all available commands and options
-  - Check for active workflow plan using {root}/utils/plan-management.md
-  - "If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details."
-  - "If plan exists: Suggest next action based on plan progress"
-  - Assess user goal against available agents and workflows in this bundle
-  - If clear match to an agent's expertise, suggest transformation with *agent command
-  - If project-oriented, suggest *workflow-guidance to explore options
-  - Load resources only when needed - never pre-load
 commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
   help: Show this guide with available agents and workflows
   chat-mode: Start conversational mode for detailed assistance  
@@ -126,15 +126,16 @@ workflow-guidance:
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
 dependencies:
   tasks:
-    - advanced-elicitation
-    - create-doc
-    - create-workflow-plan
-    - kb-mode-interaction
-    - update-workflow-plan
+    - advanced-elicitation.md
+    - create-doc.md
+    - create-workflow-plan.md
+    - kb-mode-interaction.md
+    - update-workflow-plan.md
   data:
-    - bmad-kb
+    - bmad-kb.md
+    - elicitation-methods.md
   utils:
-    - plan-management
-    - workflow-management
-    - template-format
+    - plan-management.md
+    - workflow-management.md
+    - template-format.md
 ```

bmad-core/agents/dev.md

@@ -4,8 +4,13 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
+activation-instructions:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/core-config.yaml devLoadAlwaysFiles list
+  - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
+  - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
 agent:
   name: James
   id: dev
@@ -14,11 +19,6 @@ agent:
   whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
   customization:
 
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/core-config.yaml devLoadAlwaysFiles list
-  - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
-  - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
 
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
@@ -50,8 +50,8 @@ develop-story:
 
 dependencies:
   tasks:
-    - execute-checklist
-    - validate-next-story
+    - execute-checklist.md
+    - validate-next-story.md
   checklists:
-    - story-dod-checklist
+    - story-dod-checklist.md
 ```

bmad-core/agents/pm.md

@@ -4,13 +4,14 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: John
   id: pm
@@ -32,32 +33,28 @@ persona:
     - Collaborative & iterative approach
     - Proactive risk identification
     - Strategic thinking & outcome-oriented
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
-  - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
+  - create-doc {template}: execute task create-doc for template provided, if no template then ONLY list dependencies.templates
+  - yolo: Toggle Yolo Mode
   - doc-out: Output full document to current destination file
   - exit: Exit (confirm)
 dependencies:
   tasks:
-    - create-doc
-    - correct-course
-    - create-deep-research-prompt
-    - brownfield-create-epic
-    - brownfield-create-story
-    - execute-checklist
-    - shard-doc
+    - create-doc.md
+    - correct-course.md
+    - create-deep-research-prompt.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
+    - execute-checklist.md
+    - shard-doc.md
   templates:
-    - prd-tmpl
-    - brownfield-prd-tmpl
+    - prd-tmpl.yaml
+    - brownfield-prd-tmpl.yaml
   checklists:
-    - pm-checklist
-    - change-checklist
+    - pm-checklist.md
+    - change-checklist.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
 ```

bmad-core/agents/po.md

@@ -4,13 +4,14 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Sarah
   id: po
@@ -34,8 +35,6 @@ persona:
     - User Collaboration for Validation - Seek input at critical checkpoints
     - Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
@@ -51,17 +50,15 @@ commands:
   - exit: Exit (confirm)
 dependencies:
   tasks:
-    - execute-checklist
-    - shard-doc
-    - correct-course
-    - brownfield-create-epic
-    - brownfield-create-story
-    - validate-next-story
+    - execute-checklist.md
+    - shard-doc.md
+    - correct-course.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
+    - validate-next-story.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - po-master-checklist
-    - change-checklist
-  utils:
-    - template-format
+    - po-master-checklist.md
+    - change-checklist.md
 ```

bmad-core/agents/qa.md

@@ -4,13 +4,14 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Quinn
   id: qa
@@ -34,8 +35,6 @@ persona:
     - Risk-Based Testing - Prioritize testing based on risk and critical areas
     - Continuous Improvement - Balance perfection with pragmatism
     - Architecture & Design Patterns - Ensure proper patterns and maintainable code structure
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 story-file-permissions:
   - CRITICAL: When reviewing stories, you are ONLY authorized to update the "QA Results" section of story files
   - CRITICAL: DO NOT modify any other sections including Status, Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Testing, Dev Agent Record, Change Log, or any other sections
@@ -48,9 +47,9 @@ commands:
   - exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - review-story
+    - review-story.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
+  templates:
+    - story-tmpl.yaml
 ```

bmad-core/agents/sm.md

@@ -4,12 +4,13 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, fol
 
 ```yaml
 root: .bmad-core
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.yaml), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
 agent:
   name: Bob
   id: sm
@@ -26,10 +27,6 @@ persona:
     - Rigorously follow `create-next-story` procedure to generate the detailed user story
     - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
     - You are NOT allowed to implement stories or modify code EVER!
-startup:
-  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - Offer to help with story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
@@ -39,13 +36,11 @@ commands:
   - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - create-next-story
-    - execute-checklist
-    - correct-course
+    - create-next-story.md
+    - execute-checklist.md
+    - correct-course.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - story-draft-checklist
-  utils:
-    - template-format
+    - story-draft-checklist.md
 ```

bmad-core/agents/ux-expert.md

@@ -11,6 +11,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Sally
   id: ux-expert
@@ -32,9 +33,6 @@ persona:
     - You have a keen eye for detail and a deep empathy for users.
     - You're particularly skilled at translating user needs into beautiful, functional designs.
     - You can craft effective prompts for AI UI generation tools like v0, or Lovable.
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - Always start by understanding the user's context, goals, and constraints before proposing solutions.
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
@@ -45,14 +43,12 @@ commands:
   - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - generate-ai-frontend-prompt
-    - create-deep-research-prompt
-    - create-doc
-    - execute-checklist
+    - generate-ai-frontend-prompt.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - execute-checklist.md
   templates:
-    - front-end-spec-tmpl
+    - front-end-spec-tmpl.yaml
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
 ```

bmad-core/core-config.yaml

@@ -1,4 +1,4 @@
-version: 4.26.0
+version: 4.27.0
 markdownExploder: true
 prd:
   prdFile: docs/prd.md

bmad-core/templates/architecture-tmpl.md

@@ -1,776 +0,0 @@
-# {{Project Name}} Architecture Document
-
-[[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
-
-[[LLM: The default path and filename unless specified is docs/architecture.md]]
-
-## Introduction
-
-[[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
-
-After presenting this section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-This document outlines the overall project architecture for {{Project Name}}, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
-
-**Relationship to Frontend Architecture:**
-If the project includes a significant user interface, a separate Frontend Architecture Document will detail the frontend-specific design and MUST be used in conjunction with this document. Core technology stack choices documented herein (see "Tech Stack") are definitive for the entire project, including any frontend components.
-
-### Starter Template or Existing Project
-
-[[LLM: Before proceeding further with architecture design, check if the project is based on a starter template or existing codebase:
-
-1. Review the PRD and brainstorming brief for any mentions of:
-
-- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
-- Existing projects or codebases being used as a foundation
-- Boilerplate projects or scaffolding tools
-- Previous projects to be cloned or adapted
-
-2. If a starter template or existing project is mentioned:
-
-- Ask the user to provide access via one of these methods:
-  - Link to the starter template documentation
-  - Upload/attach the project files (for small projects)
-  - Share a link to the project repository (GitHub, GitLab, etc.)
-- Analyze the starter/existing project to understand:
-  - Pre-configured technology stack and versions
-  - Project structure and organization patterns
-  - Built-in scripts and tooling
-  - Existing architectural patterns and conventions
-  - Any limitations or constraints imposed by the starter
-- Use this analysis to inform and align your architecture decisions
-
-3. If no starter template is mentioned but this is a greenfield project:
-
-- Suggest appropriate starter templates based on the tech stack preferences
-- Explain the benefits (faster setup, best practices, community support)
-- Let the user decide whether to use one
-
-4. If the user confirms no starter template will be used:
-
-- Proceed with architecture design from scratch
-- Note that manual setup will be required for all tooling and configuration
-
-Document the decision here before proceeding with the architecture design. In none, just say N/A
-
-After presenting this starter template section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## High Level Architecture
-
-[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `{root}/tasks/advanced-elicitation.md` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
-
-### Technical Summary
-
-[[LLM: Provide a brief paragraph (3-5 sentences) overview of:
-
-- The system's overall architecture style
-- Key components and their relationships
-- Primary technology choices
-- Core architectural patterns being used
-- Reference back to the PRD goals and how this architecture supports them]]
-
-### High Level Overview
-
-[[LLM: Based on the PRD's Technical Assumptions section, describe:
-
-1. The main architectural style (e.g., Monolith, Microservices, Serverless, Event-Driven)
-2. Repository structure decision from PRD (Monorepo/Polyrepo)
-3. Service architecture decision from PRD
-4. Primary user interaction flow or data flow at a conceptual level
-5. Key architectural decisions and their rationale
-
-After presenting this section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-### High Level Project Diagram
-
-[[LLM: Create a Mermaid diagram that visualizes the high-level architecture. Consider:
-
-- System boundaries
-- Major components/services
-- Data flow directions
-- External integrations
-- User entry points
-
-Use appropriate Mermaid diagram type (graph TD, C4, sequence) based on what best represents the architecture
-
-After presenting the diagram, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-### Architectural and Design Patterns
-
-[[LLM: List the key high-level patterns that will guide the architecture. For each pattern:
-
-1. Present 2-3 viable options if multiple exist
-2. Provide your recommendation with clear rationale
-3. Get user confirmation before finalizing
-4. These patterns should align with the PRD's technical assumptions and project goals
-
-Common patterns to consider:
-
-- Architectural style patterns (Serverless, Event-Driven, Microservices, CQRS, Hexagonal)
-- Code organization patterns (Dependency Injection, Repository, Module, Factory)
-- Data patterns (Event Sourcing, Saga, Database per Service)
-- Communication patterns (REST, GraphQL, Message Queue, Pub/Sub)]]
-
-<<REPEAT: pattern>>
-
-- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}
-
-<</REPEAT>>
-
-@{example: patterns}
-
-- **Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling
-- **Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility
-- **Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience
-
-@{/example}
-
-[[LLM: After presenting the patterns, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Tech Stack
-
-[[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
-
-1. Review PRD technical assumptions and any preferences from `{root}/data/technical-preferences.yaml` or an attached `technical-preferences`
-2. For each category, present 2-3 viable options with pros/cons
-3. Make a clear recommendation based on project needs
-4. Get explicit user approval for each selection
-5. Document exact versions (avoid "latest" - pin specific versions)
-6. This table is the single source of truth - all other docs must reference these choices
-
-Key decisions to finalize - before displaying the table, ensure you are aware of or ask the user about - let the user know if they are not sure on any that you can also provide suggestions with rationale:
-
-- Starter templates (if any)
-- Languages and runtimes with exact versions
-- Frameworks and libraries / packages
-- Cloud provider and key services choices
-- Database and storage solutions - if unclear suggest sql or nosql or other types depending on the project and depending on cloud provider offer a suggestion
-- Development tools
-
-Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `{root}/tasks/advanced-elicitation.md` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
-
-### Cloud Infrastructure
-
-- **Provider:** {{cloud_provider}}
-- **Key Services:** {{core_services_list}}
-- **Deployment Regions:** {{regions}}
-
-### Technology Stack Table
-
-| Category           | Technology         | Version     | Purpose     | Rationale      |
-| :----------------- | :----------------- | :---------- | :---------- | :------------- |
-| **Language**       | {{language}}       | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Runtime**        | {{runtime}}        | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Framework**      | {{framework}}      | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Database**       | {{database}}       | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Cache**          | {{cache}}          | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Message Queue**  | {{queue}}          | {{version}} | {{purpose}} | {{why_chosen}} |
-| **API Style**      | {{api_style}}      | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Authentication** | {{auth}}           | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Testing**        | {{test_framework}} | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Build Tool**     | {{build_tool}}     | {{version}} | {{purpose}} | {{why_chosen}} |
-| **IaC Tool**       | {{iac_tool}}       | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Monitoring**     | {{monitoring}}     | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Logging**        | {{logging}}        | {{version}} | {{purpose}} | {{why_chosen}} |
-
-@{example: tech_stack_row}
-| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |
-| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |
-| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |
-@{/example}
-
-## Data Models
-
-[[LLM: Define the core data models/entities:
-
-1. Review PRD requirements and identify key business entities
-2. For each model, explain its purpose and relationships
-3. Include key attributes and data types
-4. Show relationships between models
-5. Discuss design decisions with user
-
-Create a clear conceptual model before moving to database schema.
-
-After presenting all data models, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-<<REPEAT: data_model>>
-
-### {{model_name}}
-
-**Purpose:** {{model_purpose}}
-
-**Key Attributes:**
-
-- {{attribute_1}}: {{type_1}} - {{description_1}}
-- {{attribute_2}}: {{type_2}} - {{description_2}}
-
-**Relationships:**
-
-- {{relationship_1}}
-- {{relationship_2}}
-  <</REPEAT>>
-
-## Components
-
-[[LLM: Based on the architectural patterns, tech stack, and data models from above:
-
-1. Identify major logical components/services and their responsibilities
-2. Consider the repository structure (monorepo/polyrepo) from PRD
-3. Define clear boundaries and interfaces between components
-4. For each component, specify:
-
-- Primary responsibility
-- Key interfaces/APIs exposed
-- Dependencies on other components
-- Technology specifics based on tech stack choices
-
-5. Create component diagrams where helpful
-6. After presenting all components, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-<<REPEAT: component>>
-
-### {{component_name}}
-
-**Responsibility:** {{component_description}}
-
-**Key Interfaces:**
-
-- {{interface_1}}
-- {{interface_2}}
-
-**Dependencies:** {{dependencies}}
-
-**Technology Stack:** {{component_tech_details}}
-<</REPEAT>>
-
-### Component Diagrams
-
-[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
-
-- C4 Container diagram for high-level view
-- Component diagram for detailed internal structure
-- Sequence diagrams for complex interactions
-  Choose the most appropriate for clarity
-
-After presenting the diagrams, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## External APIs
-
-[[LLM: For each external service integration:
-
-1. Identify APIs needed based on PRD requirements and component design
-2. If documentation URLs are unknown, ask user for specifics
-3. Document authentication methods and security considerations
-4. List specific endpoints that will be used
-5. Note any rate limits or usage constraints
-
-If no external APIs are needed, state this explicitly and skip to next section.]]
-
-^^CONDITION: has_external_apis^^
-
-<<REPEAT: external_api>>
-
-### {{api_name}} API
-
-- **Purpose:** {{api_purpose}}
-- **Documentation:** {{api_docs_url}}
-- **Base URL(s):** {{api_base_url}}
-- **Authentication:** {{auth_method}}
-- **Rate Limits:** {{rate_limits}}
-
-**Key Endpoints Used:**
-<<REPEAT: endpoint>>
-
-- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
-  <</REPEAT>>
-
-**Integration Notes:** {{integration_considerations}}
-<</REPEAT>>
-
-@{example: external_api}
-
-### Stripe API
-
-- **Purpose:** Payment processing and subscription management
-- **Documentation:** https://stripe.com/docs/api
-- **Base URL(s):** `https://api.stripe.com/v1`
-- **Authentication:** Bearer token with secret key
-- **Rate Limits:** 100 requests per second
-
-**Key Endpoints Used:**
-
-- `POST /customers` - Create customer profiles
-- `POST /payment_intents` - Process payments
-- `POST /subscriptions` - Manage subscriptions
-  @{/example}
-
-^^/CONDITION: has_external_apis^^
-
-[[LLM: After presenting external APIs (or noting their absence), apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Core Workflows
-
-[[LLM: Illustrate key system workflows using sequence diagrams:
-
-1. Identify critical user journeys from PRD
-2. Show component interactions including external APIs
-3. Include error handling paths
-4. Document async operations
-5. Create both high-level and detailed diagrams as needed
-
-Focus on workflows that clarify architecture decisions or complex interactions.
-
-After presenting the workflow diagrams, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## REST API Spec
-
-[[LLM: If the project includes a REST API:
-
-1. Create an OpenAPI 3.0 specification
-2. Include all endpoints from epics/stories
-3. Define request/response schemas based on data models
-4. Document authentication requirements
-5. Include example requests/responses
-
-Use YAML format for better readability. If no REST API, skip this section.]]
-
-^^CONDITION: has_rest_api^^
-
-```yaml
-openapi: 3.0.0
-info:
-  title:
-    '[object Object]': null
-  version:
-    '[object Object]': null
-  description:
-    '[object Object]': null
-servers:
-  - url:
-      '[object Object]': null
-    description:
-      '[object Object]': null
-```
-
-^^/CONDITION: has_rest_api^^
-
-[[LLM: After presenting the REST API spec (or noting its absence if not applicable), apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Database Schema
-
-[[LLM: Transform the conceptual data models into concrete database schemas:
-
-1. Use the database type(s) selected in Tech Stack
-2. Create schema definitions using appropriate notation
-3. Include indexes, constraints, and relationships
-4. Consider performance and scalability
-5. For NoSQL, show document structures
-
-Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
-
-After presenting the database schema, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Source Tree
-
-[[LLM: Create a project folder structure that reflects:
-
-1. The chosen repository structure (monorepo/polyrepo)
-2. The service architecture (monolith/microservices/serverless)
-3. The selected tech stack and languages
-4. Component organization from above
-5. Best practices for the chosen frameworks
-6. Clear separation of concerns
-
-Adapt the structure based on project needs. For monorepos, show service separation. For serverless, show function organization. Include language-specific conventions.
-
-After presenting the structure, apply `{root}/tasks/advanced-elicitation.md` protocol to refine based on user feedback.]]
-
-```plaintext
-{{project-root}}/
-├── .github/                    # CI/CD workflows
-│   └── workflows/
-│       └── main.yaml
-├── .vscode/                    # VSCode settings (optional)
-│   └── settings.json
-├── build/                      # Compiled output (git-ignored)
-├── config/                     # Configuration files
-├── docs/                       # Project documentation
-│   ├── PRD.md
-│   ├── architecture.md
-│   └── ...
-├── infra/                      # Infrastructure as Code
-│   └── {{iac-structure}}
-├── {{dependencies-dir}}/       # Dependencies (git-ignored)
-├── scripts/                    # Utility scripts
-├── src/                        # Application source code
-│   └── {{source-structure}}
-├── tests/                      # Test files
-│   ├── unit/
-│   ├── integration/
-│   └── e2e/
-├── .env.example                # Environment variables template
-├── .gitignore                  # Git ignore rules
-├── {{package-manifest}}        # Dependencies manifest
-├── {{config-files}}            # Language/framework configs
-└── README.md                   # Project documentation
-
-@{example: monorepo-structure}
-project-root/
-├── packages/
-│ ├── api/ # Backend API service
-│ ├── web/ # Frontend application
-│ ├── shared/ # Shared utilities/types
-│ └── infrastructure/ # IaC definitions
-├── scripts/ # Monorepo management scripts
-└── package.json # Root package.json with workspaces
-@{/example}
-```
-
-[[LLM: After presenting the source tree structure, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Infrastructure and Deployment
-
-[[LLM: Define the deployment architecture and practices:
-
-1. Use IaC tool selected in Tech Stack
-2. Choose deployment strategy appropriate for the architecture
-3. Define environments and promotion flow
-4. Establish rollback procedures
-5. Consider security, monitoring, and cost optimization
-
-Get user input on deployment preferences and CI/CD tool choices.]]
-
-### Infrastructure as Code
-
-- **Tool:** {{iac_tool}} {{version}}
-- **Location:** `{{iac_directory}}`
-- **Approach:** {{iac_approach}}
-
-### Deployment Strategy
-
-- **Strategy:** {{deployment_strategy}}
-- **CI/CD Platform:** {{cicd_platform}}
-- **Pipeline Configuration:** `{{pipeline_config_location}}`
-
-### Environments
-
-<<REPEAT: environment>>
-
-- **{{env_name}}:** {{env_purpose}} - {{env_details}}
-  <</REPEAT>>
-
-### Environment Promotion Flow
-
-```text
-{{promotion_flow_diagram}}
-```
-
-### Rollback Strategy
-
-- **Primary Method:** {{rollback_method}}
-- **Trigger Conditions:** {{rollback_triggers}}
-- **Recovery Time Objective:** {{rto}}
-
-[[LLM: After presenting the infrastructure and deployment section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Error Handling Strategy
-
-[[LLM: Define comprehensive error handling approach:
-
-1. Choose appropriate patterns for the language/framework from Tech Stack
-2. Define logging standards and tools
-3. Establish error categories and handling rules
-4. Consider observability and debugging needs
-5. Ensure security (no sensitive data in logs)
-
-This section guides both AI and human developers in consistent error handling.]]
-
-### General Approach
-
-- **Error Model:** {{error_model}}
-- **Exception Hierarchy:** {{exception_structure}}
-- **Error Propagation:** {{propagation_rules}}
-
-### Logging Standards
-
-- **Library:** {{logging_library}} {{version}}
-- **Format:** {{log_format}}
-- **Levels:** {{log_levels_definition}}
-- **Required Context:**
-  - Correlation ID: {{correlation_id_format}}
-  - Service Context: {{service_context}}
-  - User Context: {{user_context_rules}}
-
-### Error Handling Patterns
-
-#### External API Errors
-
-- **Retry Policy:** {{retry_strategy}}
-- **Circuit Breaker:** {{circuit_breaker_config}}
-- **Timeout Configuration:** {{timeout_settings}}
-- **Error Translation:** {{error_mapping_rules}}
-
-#### Business Logic Errors
-
-- **Custom Exceptions:** {{business_exception_types}}
-- **User-Facing Errors:** {{user_error_format}}
-- **Error Codes:** {{error_code_system}}
-
-#### Data Consistency
-
-- **Transaction Strategy:** {{transaction_approach}}
-- **Compensation Logic:** {{compensation_patterns}}
-- **Idempotency:** {{idempotency_approach}}
-
-[[LLM: After presenting the error handling strategy, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Coding Standards
-
-[[LLM: These standards are MANDATORY for AI agents. Work with user to define ONLY the critical rules needed to prevent bad code. Explain that:
-
-1. This section directly controls AI developer behavior
-2. Keep it minimal - assume AI knows general best practices
-3. Focus on project-specific conventions and gotchas
-4. Overly detailed standards bloat context and slow development
-5. Standards will be extracted to separate file for dev agent use
-
-For each standard, get explicit user confirmation it's necessary.]]
-
-### Core Standards
-
-- **Languages & Runtimes:** {{languages_and_versions}}
-- **Style & Linting:** {{linter_config}}
-- **Test Organization:** {{test_file_convention}}
-
-### Naming Conventions
-
-[[LLM: Only include if deviating from language defaults]]
-
-| Element   | Convention           | Example           |
-| :-------- | :------------------- | :---------------- |
-| Variables | {{var_convention}}   | {{var_example}}   |
-| Functions | {{func_convention}}  | {{func_example}}  |
-| Classes   | {{class_convention}} | {{class_example}} |
-| Files     | {{file_convention}}  | {{file_example}}  |
-
-### Critical Rules
-
-[[LLM: List ONLY rules that AI might violate or project-specific requirements. Examples:
-
-- "Never use console.log in production code - use logger"
-- "All API responses must use ApiResponse wrapper type"
-- "Database queries must use repository pattern, never direct ORM"
-
-Avoid obvious rules like "use SOLID principles" or "write clean code"]]
-
-<<REPEAT: critical_rule>>
-
-- **{{rule_name}}:** {{rule_description}}
-  <</REPEAT>>
-
-### Language-Specific Guidelines
-
-[[LLM: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section.]]
-
-^^CONDITION: has_language_specifics^^
-
-#### {{language_name}} Specifics
-
-<<REPEAT: language_rule>>
-
-- **{{rule_topic}}:** {{rule_detail}}
-  <</REPEAT>>
-
-^^/CONDITION: has_language_specifics^^
-
-[[LLM: After presenting the coding standards, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Test Strategy and Standards
-
-[[LLM: Work with user to define comprehensive test strategy:
-
-1. Use test frameworks from Tech Stack
-2. Decide on TDD vs test-after approach
-3. Define test organization and naming
-4. Establish coverage goals
-5. Determine integration test infrastructure
-6. Plan for test data and external dependencies
-
-Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `{root}/tasks/advanced-elicitation.md` after initial draft.]]
-
-### Testing Philosophy
-
-- **Approach:** {{test_approach}}
-- **Coverage Goals:** {{coverage_targets}}
-- **Test Pyramid:** {{test_distribution}}
-
-### Test Types and Organization
-
-#### Unit Tests
-
-- **Framework:** {{unit_test_framework}} {{version}}
-- **File Convention:** {{unit_test_naming}}
-- **Location:** {{unit_test_location}}
-- **Mocking Library:** {{mocking_library}}
-- **Coverage Requirement:** {{unit_coverage}}
-
-**AI Agent Requirements:**
-
-- Generate tests for all public methods
-- Cover edge cases and error conditions
-- Follow AAA pattern (Arrange, Act, Assert)
-- Mock all external dependencies
-
-#### Integration Tests
-
-- **Scope:** {{integration_scope}}
-- **Location:** {{integration_test_location}}
-- **Test Infrastructure:**
-  <<REPEAT: test_dependency>>
-  - **{{dependency_name}}:** {{test_approach}} ({{test_tool}})
-    <</REPEAT>>
-
-@{example: test_dependencies}
-
-- **Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration
-- **Message Queue:** Embedded Kafka for tests
-- **External APIs:** WireMock for stubbing
-  @{/example}
-
-#### End-to-End Tests
-
-- **Framework:** {{e2e_framework}} {{version}}
-- **Scope:** {{e2e_scope}}
-- **Environment:** {{e2e_environment}}
-- **Test Data:** {{e2e_data_strategy}}
-
-### Test Data Management
-
-- **Strategy:** {{test_data_approach}}
-- **Fixtures:** {{fixture_location}}
-- **Factories:** {{factory_pattern}}
-- **Cleanup:** {{cleanup_strategy}}
-
-### Continuous Testing
-
-- **CI Integration:** {{ci_test_stages}}
-- **Performance Tests:** {{perf_test_approach}}
-- **Security Tests:** {{security_test_approach}}
-
-[[LLM: After presenting the test strategy section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Security
-
-[[LLM: Define MANDATORY security requirements for AI and human developers:
-
-1. Focus on implementation-specific rules
-2. Reference security tools from Tech Stack
-3. Define clear patterns for common scenarios
-4. These rules directly impact code generation
-5. Work with user to ensure completeness without redundancy]]
-
-### Input Validation
-
-- **Validation Library:** {{validation_library}}
-- **Validation Location:** {{where_to_validate}}
-- **Required Rules:**
-  - All external inputs MUST be validated
-  - Validation at API boundary before processing
-  - Whitelist approach preferred over blacklist
-
-### Authentication & Authorization
-
-- **Auth Method:** {{auth_implementation}}
-- **Session Management:** {{session_approach}}
-- **Required Patterns:**
-  - {{auth_pattern_1}}
-  - {{auth_pattern_2}}
-
-### Secrets Management
-
-- **Development:** {{dev_secrets_approach}}
-- **Production:** {{prod_secrets_service}}
-- **Code Requirements:**
-  - NEVER hardcode secrets
-  - Access via configuration service only
-  - No secrets in logs or error messages
-
-### API Security
-
-- **Rate Limiting:** {{rate_limit_implementation}}
-- **CORS Policy:** {{cors_configuration}}
-- **Security Headers:** {{required_headers}}
-- **HTTPS Enforcement:** {{https_approach}}
-
-### Data Protection
-
-- **Encryption at Rest:** {{encryption_at_rest}}
-- **Encryption in Transit:** {{encryption_in_transit}}
-- **PII Handling:** {{pii_rules}}
-- **Logging Restrictions:** {{what_not_to_log}}
-
-### Dependency Security
-
-- **Scanning Tool:** {{dependency_scanner}}
-- **Update Policy:** {{update_frequency}}
-- **Approval Process:** {{new_dep_process}}
-
-### Security Testing
-
-- **SAST Tool:** {{static_analysis}}
-- **DAST Tool:** {{dynamic_analysis}}
-- **Penetration Testing:** {{pentest_schedule}}
-
-[[LLM: After presenting the security section, apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-## Checklist Results Report
-
-[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
-
----
-
-## Next Steps
-
-[[LLM: After completing the architecture:
-
-1. If project has UI components:
-
-- Recommend engaging Design Architect agent
-- Use "Frontend Architecture Mode"
-- Provide this document as input
-
-2. For all projects:
-
-- Review with Product Owner
-- Begin story implementation with Dev agent
-- Set up infrastructure with DevOps agent
-
-3. Include specific prompts for next agents if needed]]
-
-^^CONDITION: has_ui^^
-
-### Design Architect Prompt
-
-[[LLM: Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include:
-
-- Reference to this architecture document
-- Key UI requirements from PRD
-- Any frontend-specific decisions made here
-- Request for detailed frontend architecture]]
-
-^^/CONDITION: has_ui^^
-
-### Developer Handoff
-
-[[LLM: Create a brief prompt for developers starting implementation. Include:
-
-- Reference to this architecture and coding standards
-- First epic/story to implement
-- Key technical decisions to follow]]

bmad-core/templates/architecture-tmpl.yaml

@@ -0,0 +1,650 @@
+template:
+  id: architecture-template-v2
+  name: Architecture Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/architecture.md
+    title: "{{project_name}} Architecture Document"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: introduction
+    title: Introduction
+    instruction: |
+      If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot locate docs/prd.md ask the user what docs will provide the basis for the architecture.
+    sections:
+      - id: intro-content
+        content: |
+          This document outlines the overall project architecture for {{project_name}}, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
+          
+          **Relationship to Frontend Architecture:**
+          If the project includes a significant user interface, a separate Frontend Architecture Document will detail the frontend-specific design and MUST be used in conjunction with this document. Core technology stack choices documented herein (see "Tech Stack") are definitive for the entire project, including any frontend components.
+      - id: starter-template
+        title: Starter Template or Existing Project
+        instruction: |
+          Before proceeding further with architecture design, check if the project is based on a starter template or existing codebase:
+          
+          1. Review the PRD and brainstorming brief for any mentions of:
+          - Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
+          - Existing projects or codebases being used as a foundation
+          - Boilerplate projects or scaffolding tools
+          - Previous projects to be cloned or adapted
+          
+          2. If a starter template or existing project is mentioned:
+          - Ask the user to provide access via one of these methods:
+            - Link to the starter template documentation
+            - Upload/attach the project files (for small projects)
+            - Share a link to the project repository (GitHub, GitLab, etc.)
+          - Analyze the starter/existing project to understand:
+            - Pre-configured technology stack and versions
+            - Project structure and organization patterns
+            - Built-in scripts and tooling
+            - Existing architectural patterns and conventions
+            - Any limitations or constraints imposed by the starter
+          - Use this analysis to inform and align your architecture decisions
+          
+          3. If no starter template is mentioned but this is a greenfield project:
+          - Suggest appropriate starter templates based on the tech stack preferences
+          - Explain the benefits (faster setup, best practices, community support)
+          - Let the user decide whether to use one
+          
+          4. If the user confirms no starter template will be used:
+          - Proceed with architecture design from scratch
+          - Note that manual setup will be required for all tooling and configuration
+          
+          Document the decision here before proceeding with the architecture design. If none, just say N/A
+        elicit: true
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: high-level-architecture
+    title: High Level Architecture
+    instruction: |
+      This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together at once.
+    elicit: true
+    sections:
+      - id: technical-summary
+        title: Technical Summary
+        instruction: |
+          Provide a brief paragraph (3-5 sentences) overview of:
+          - The system's overall architecture style
+          - Key components and their relationships
+          - Primary technology choices
+          - Core architectural patterns being used
+          - Reference back to the PRD goals and how this architecture supports them
+      - id: high-level-overview
+        title: High Level Overview
+        instruction: |
+          Based on the PRD's Technical Assumptions section, describe:
+          
+          1. The main architectural style (e.g., Monolith, Microservices, Serverless, Event-Driven)
+          2. Repository structure decision from PRD (Monorepo/Polyrepo)
+          3. Service architecture decision from PRD
+          4. Primary user interaction flow or data flow at a conceptual level
+          5. Key architectural decisions and their rationale
+      - id: project-diagram
+        title: High Level Project Diagram
+        type: mermaid
+        mermaid_type: graph
+        instruction: |
+          Create a Mermaid diagram that visualizes the high-level architecture. Consider:
+          - System boundaries
+          - Major components/services
+          - Data flow directions
+          - External integrations
+          - User entry points
+          
+      - id: architectural-patterns
+        title: Architectural and Design Patterns
+        instruction: |
+          List the key high-level patterns that will guide the architecture. For each pattern:
+          
+          1. Present 2-3 viable options if multiple exist
+          2. Provide your recommendation with clear rationale
+          3. Get user confirmation before finalizing
+          4. These patterns should align with the PRD's technical assumptions and project goals
+          
+          Common patterns to consider:
+          - Architectural style patterns (Serverless, Event-Driven, Microservices, CQRS, Hexagonal)
+          - Code organization patterns (Dependency Injection, Repository, Module, Factory)
+          - Data patterns (Event Sourcing, Saga, Database per Service)
+          - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub)
+        template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}"
+        examples:
+          - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling"
+          - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility"
+          - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience"
+
+  - id: tech-stack
+    title: Tech Stack
+    instruction: |
+      This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
+      
+      1. Review PRD technical assumptions and any preferences from {root}/data/technical-preferences.yaml or an attached technical-preferences
+      2. For each category, present 2-3 viable options with pros/cons
+      3. Make a clear recommendation based on project needs
+      4. Get explicit user approval for each selection
+      5. Document exact versions (avoid "latest" - pin specific versions)
+      6. This table is the single source of truth - all other docs must reference these choices
+      
+      Key decisions to finalize - before displaying the table, ensure you are aware of or ask the user about - let the user know if they are not sure on any that you can also provide suggestions with rationale:
+      
+      - Starter templates (if any)
+      - Languages and runtimes with exact versions
+      - Frameworks and libraries / packages
+      - Cloud provider and key services choices
+      - Database and storage solutions - if unclear suggest sql or nosql or other types depending on the project and depending on cloud provider offer a suggestion
+      - Development tools
+      
+      Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away elicit feedback - this statement and the options should be rendered and then prompt right all before allowing user input.
+    elicit: true
+    sections:
+      - id: cloud-infrastructure
+        title: Cloud Infrastructure
+        template: |
+          - **Provider:** {{cloud_provider}}
+          - **Key Services:** {{core_services_list}}
+          - **Deployment Regions:** {{regions}}
+      - id: technology-stack-table
+        title: Technology Stack Table
+        type: table
+        columns: [Category, Technology, Version, Purpose, Rationale]
+        instruction: Populate the technology stack table with all relevant technologies
+        examples:
+          - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |"
+          - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |"
+          - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |"
+
+  - id: data-models
+    title: Data Models
+    instruction: |
+      Define the core data models/entities:
+      
+      1. Review PRD requirements and identify key business entities
+      2. For each model, explain its purpose and relationships
+      3. Include key attributes and data types
+      4. Show relationships between models
+      5. Discuss design decisions with user
+      
+      Create a clear conceptual model before moving to database schema.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: model
+        title: "{{model_name}}"
+        template: |
+          **Purpose:** {{model_purpose}}
+          
+          **Key Attributes:**
+          - {{attribute_1}}: {{type_1}} - {{description_1}}
+          - {{attribute_2}}: {{type_2}} - {{description_2}}
+          
+          **Relationships:**
+          - {{relationship_1}}
+          - {{relationship_2}}
+
+  - id: components
+    title: Components
+    instruction: |
+      Based on the architectural patterns, tech stack, and data models from above:
+      
+      1. Identify major logical components/services and their responsibilities
+      2. Consider the repository structure (monorepo/polyrepo) from PRD
+      3. Define clear boundaries and interfaces between components
+      4. For each component, specify:
+      - Primary responsibility
+      - Key interfaces/APIs exposed
+      - Dependencies on other components
+      - Technology specifics based on tech stack choices
+      
+      5. Create component diagrams where helpful
+    elicit: true
+    sections:
+      - id: component-list
+        repeatable: true
+        title: "{{component_name}}"
+        template: |
+          **Responsibility:** {{component_description}}
+          
+          **Key Interfaces:**
+          - {{interface_1}}
+          - {{interface_2}}
+          
+          **Dependencies:** {{dependencies}}
+          
+          **Technology Stack:** {{component_tech_details}}
+      - id: component-diagrams
+        title: Component Diagrams
+        type: mermaid
+        instruction: |
+          Create Mermaid diagrams to visualize component relationships. Options:
+          - C4 Container diagram for high-level view
+          - Component diagram for detailed internal structure
+          - Sequence diagrams for complex interactions
+          Choose the most appropriate for clarity
+
+  - id: external-apis
+    title: External APIs
+    condition: Project requires external API integrations
+    instruction: |
+      For each external service integration:
+      
+      1. Identify APIs needed based on PRD requirements and component design
+      2. If documentation URLs are unknown, ask user for specifics
+      3. Document authentication methods and security considerations
+      4. List specific endpoints that will be used
+      5. Note any rate limits or usage constraints
+      
+      If no external APIs are needed, state this explicitly and skip to next section.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: api
+        title: "{{api_name}} API"
+        template: |
+          - **Purpose:** {{api_purpose}}
+          - **Documentation:** {{api_docs_url}}
+          - **Base URL(s):** {{api_base_url}}
+          - **Authentication:** {{auth_method}}
+          - **Rate Limits:** {{rate_limits}}
+          
+          **Key Endpoints Used:**
+          - `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
+          
+          **Integration Notes:** {{integration_considerations}}
+
+  - id: core-workflows
+    title: Core Workflows
+    type: mermaid
+    mermaid_type: sequence
+    instruction: |
+      Illustrate key system workflows using sequence diagrams:
+      
+      1. Identify critical user journeys from PRD
+      2. Show component interactions including external APIs
+      3. Include error handling paths
+      4. Document async operations
+      5. Create both high-level and detailed diagrams as needed
+      
+      Focus on workflows that clarify architecture decisions or complex interactions.
+    elicit: true
+
+  - id: rest-api-spec
+    title: REST API Spec
+    condition: Project includes REST API
+    type: code
+    language: yaml
+    instruction: |
+      If the project includes a REST API:
+      
+      1. Create an OpenAPI 3.0 specification
+      2. Include all endpoints from epics/stories
+      3. Define request/response schemas based on data models
+      4. Document authentication requirements
+      5. Include example requests/responses
+      
+      Use YAML format for better readability. If no REST API, skip this section.
+    elicit: true
+    template: |
+      openapi: 3.0.0
+      info:
+        title: {{api_title}}
+        version: {{api_version}}
+        description: {{api_description}}
+      servers:
+        - url: {{server_url}}
+          description: {{server_description}}
+
+  - id: database-schema
+    title: Database Schema
+    instruction: |
+      Transform the conceptual data models into concrete database schemas:
+      
+      1. Use the database type(s) selected in Tech Stack
+      2. Create schema definitions using appropriate notation
+      3. Include indexes, constraints, and relationships
+      4. Consider performance and scalability
+      5. For NoSQL, show document structures
+      
+      Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
+    elicit: true
+
+  - id: source-tree
+    title: Source Tree
+    type: code
+    language: plaintext
+    instruction: |
+      Create a project folder structure that reflects:
+      
+      1. The chosen repository structure (monorepo/polyrepo)
+      2. The service architecture (monolith/microservices/serverless)
+      3. The selected tech stack and languages
+      4. Component organization from above
+      5. Best practices for the chosen frameworks
+      6. Clear separation of concerns
+      
+      Adapt the structure based on project needs. For monorepos, show service separation. For serverless, show function organization. Include language-specific conventions.
+    elicit: true
+    examples:
+      - |
+        project-root/
+        ├── packages/
+        │   ├── api/                    # Backend API service
+        │   ├── web/                    # Frontend application
+        │   ├── shared/                 # Shared utilities/types
+        │   └── infrastructure/         # IaC definitions
+        ├── scripts/                    # Monorepo management scripts
+        └── package.json                # Root package.json with workspaces
+
+  - id: infrastructure-deployment
+    title: Infrastructure and Deployment
+    instruction: |
+      Define the deployment architecture and practices:
+      
+      1. Use IaC tool selected in Tech Stack
+      2. Choose deployment strategy appropriate for the architecture
+      3. Define environments and promotion flow
+      4. Establish rollback procedures
+      5. Consider security, monitoring, and cost optimization
+      
+      Get user input on deployment preferences and CI/CD tool choices.
+    elicit: true
+    sections:
+      - id: infrastructure-as-code
+        title: Infrastructure as Code
+        template: |
+          - **Tool:** {{iac_tool}} {{version}}
+          - **Location:** `{{iac_directory}}`
+          - **Approach:** {{iac_approach}}
+      - id: deployment-strategy
+        title: Deployment Strategy
+        template: |
+          - **Strategy:** {{deployment_strategy}}
+          - **CI/CD Platform:** {{cicd_platform}}
+          - **Pipeline Configuration:** `{{pipeline_config_location}}`
+      - id: environments
+        title: Environments
+        repeatable: true
+        template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}"
+      - id: promotion-flow
+        title: Environment Promotion Flow
+        type: code
+        language: text
+        template: "{{promotion_flow_diagram}}"
+      - id: rollback-strategy
+        title: Rollback Strategy
+        template: |
+          - **Primary Method:** {{rollback_method}}
+          - **Trigger Conditions:** {{rollback_triggers}}
+          - **Recovery Time Objective:** {{rto}}
+
+  - id: error-handling-strategy
+    title: Error Handling Strategy
+    instruction: |
+      Define comprehensive error handling approach:
+      
+      1. Choose appropriate patterns for the language/framework from Tech Stack
+      2. Define logging standards and tools
+      3. Establish error categories and handling rules
+      4. Consider observability and debugging needs
+      5. Ensure security (no sensitive data in logs)
+      
+      This section guides both AI and human developers in consistent error handling.
+    elicit: true
+    sections:
+      - id: general-approach
+        title: General Approach
+        template: |
+          - **Error Model:** {{error_model}}
+          - **Exception Hierarchy:** {{exception_structure}}
+          - **Error Propagation:** {{propagation_rules}}
+      - id: logging-standards
+        title: Logging Standards
+        template: |
+          - **Library:** {{logging_library}} {{version}}
+          - **Format:** {{log_format}}
+          - **Levels:** {{log_levels_definition}}
+          - **Required Context:**
+            - Correlation ID: {{correlation_id_format}}
+            - Service Context: {{service_context}}
+            - User Context: {{user_context_rules}}
+      - id: error-patterns
+        title: Error Handling Patterns
+        sections:
+          - id: external-api-errors
+            title: External API Errors
+            template: |
+              - **Retry Policy:** {{retry_strategy}}
+              - **Circuit Breaker:** {{circuit_breaker_config}}
+              - **Timeout Configuration:** {{timeout_settings}}
+              - **Error Translation:** {{error_mapping_rules}}
+          - id: business-logic-errors
+            title: Business Logic Errors
+            template: |
+              - **Custom Exceptions:** {{business_exception_types}}
+              - **User-Facing Errors:** {{user_error_format}}
+              - **Error Codes:** {{error_code_system}}
+          - id: data-consistency
+            title: Data Consistency
+            template: |
+              - **Transaction Strategy:** {{transaction_approach}}
+              - **Compensation Logic:** {{compensation_patterns}}
+              - **Idempotency:** {{idempotency_approach}}
+
+  - id: coding-standards
+    title: Coding Standards
+    instruction: |
+      These standards are MANDATORY for AI agents. Work with user to define ONLY the critical rules needed to prevent bad code. Explain that:
+      
+      1. This section directly controls AI developer behavior
+      2. Keep it minimal - assume AI knows general best practices
+      3. Focus on project-specific conventions and gotchas
+      4. Overly detailed standards bloat context and slow development
+      5. Standards will be extracted to separate file for dev agent use
+      
+      For each standard, get explicit user confirmation it's necessary.
+    elicit: true
+    sections:
+      - id: core-standards
+        title: Core Standards
+        template: |
+          - **Languages & Runtimes:** {{languages_and_versions}}
+          - **Style & Linting:** {{linter_config}}
+          - **Test Organization:** {{test_file_convention}}
+      - id: naming-conventions
+        title: Naming Conventions
+        type: table
+        columns: [Element, Convention, Example]
+        instruction: Only include if deviating from language defaults
+      - id: critical-rules
+        title: Critical Rules
+        instruction: |
+          List ONLY rules that AI might violate or project-specific requirements. Examples:
+          - "Never use console.log in production code - use logger"
+          - "All API responses must use ApiResponse wrapper type"
+          - "Database queries must use repository pattern, never direct ORM"
+          
+          Avoid obvious rules like "use SOLID principles" or "write clean code"
+        repeatable: true
+        template: "- **{{rule_name}}:** {{rule_description}}"
+      - id: language-specifics
+        title: Language-Specific Guidelines
+        condition: Critical language-specific rules needed
+        instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section.
+        sections:
+          - id: language-rules
+            title: "{{language_name}} Specifics"
+            repeatable: true
+            template: "- **{{rule_topic}}:** {{rule_detail}}"
+
+  - id: test-strategy
+    title: Test Strategy and Standards
+    instruction: |
+      Work with user to define comprehensive test strategy:
+      
+      1. Use test frameworks from Tech Stack
+      2. Decide on TDD vs test-after approach
+      3. Define test organization and naming
+      4. Establish coverage goals
+      5. Determine integration test infrastructure
+      6. Plan for test data and external dependencies
+      
+      Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference.
+    elicit: true
+    sections:
+      - id: testing-philosophy
+        title: Testing Philosophy
+        template: |
+          - **Approach:** {{test_approach}}
+          - **Coverage Goals:** {{coverage_targets}}
+          - **Test Pyramid:** {{test_distribution}}
+      - id: test-types
+        title: Test Types and Organization
+        sections:
+          - id: unit-tests
+            title: Unit Tests
+            template: |
+              - **Framework:** {{unit_test_framework}} {{version}}
+              - **File Convention:** {{unit_test_naming}}
+              - **Location:** {{unit_test_location}}
+              - **Mocking Library:** {{mocking_library}}
+              - **Coverage Requirement:** {{unit_coverage}}
+              
+              **AI Agent Requirements:**
+              - Generate tests for all public methods
+              - Cover edge cases and error conditions
+              - Follow AAA pattern (Arrange, Act, Assert)
+              - Mock all external dependencies
+          - id: integration-tests
+            title: Integration Tests
+            template: |
+              - **Scope:** {{integration_scope}}
+              - **Location:** {{integration_test_location}}
+              - **Test Infrastructure:**
+                - **{{dependency_name}}:** {{test_approach}} ({{test_tool}})
+            examples:
+              - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration"
+              - "**Message Queue:** Embedded Kafka for tests"
+              - "**External APIs:** WireMock for stubbing"
+          - id: e2e-tests
+            title: End-to-End Tests
+            template: |
+              - **Framework:** {{e2e_framework}} {{version}}
+              - **Scope:** {{e2e_scope}}
+              - **Environment:** {{e2e_environment}}
+              - **Test Data:** {{e2e_data_strategy}}
+      - id: test-data-management
+        title: Test Data Management
+        template: |
+          - **Strategy:** {{test_data_approach}}
+          - **Fixtures:** {{fixture_location}}
+          - **Factories:** {{factory_pattern}}
+          - **Cleanup:** {{cleanup_strategy}}
+      - id: continuous-testing
+        title: Continuous Testing
+        template: |
+          - **CI Integration:** {{ci_test_stages}}
+          - **Performance Tests:** {{perf_test_approach}}
+          - **Security Tests:** {{security_test_approach}}
+
+  - id: security
+    title: Security
+    instruction: |
+      Define MANDATORY security requirements for AI and human developers:
+      
+      1. Focus on implementation-specific rules
+      2. Reference security tools from Tech Stack
+      3. Define clear patterns for common scenarios
+      4. These rules directly impact code generation
+      5. Work with user to ensure completeness without redundancy
+    elicit: true
+    sections:
+      - id: input-validation
+        title: Input Validation
+        template: |
+          - **Validation Library:** {{validation_library}}
+          - **Validation Location:** {{where_to_validate}}
+          - **Required Rules:**
+            - All external inputs MUST be validated
+            - Validation at API boundary before processing
+            - Whitelist approach preferred over blacklist
+      - id: auth-authorization
+        title: Authentication & Authorization
+        template: |
+          - **Auth Method:** {{auth_implementation}}
+          - **Session Management:** {{session_approach}}
+          - **Required Patterns:**
+            - {{auth_pattern_1}}
+            - {{auth_pattern_2}}
+      - id: secrets-management
+        title: Secrets Management
+        template: |
+          - **Development:** {{dev_secrets_approach}}
+          - **Production:** {{prod_secrets_service}}
+          - **Code Requirements:**
+            - NEVER hardcode secrets
+            - Access via configuration service only
+            - No secrets in logs or error messages
+      - id: api-security
+        title: API Security
+        template: |
+          - **Rate Limiting:** {{rate_limit_implementation}}
+          - **CORS Policy:** {{cors_configuration}}
+          - **Security Headers:** {{required_headers}}
+          - **HTTPS Enforcement:** {{https_approach}}
+      - id: data-protection
+        title: Data Protection
+        template: |
+          - **Encryption at Rest:** {{encryption_at_rest}}
+          - **Encryption in Transit:** {{encryption_in_transit}}
+          - **PII Handling:** {{pii_rules}}
+          - **Logging Restrictions:** {{what_not_to_log}}
+      - id: dependency-security
+        title: Dependency Security
+        template: |
+          - **Scanning Tool:** {{dependency_scanner}}
+          - **Update Policy:** {{update_frequency}}
+          - **Approval Process:** {{new_dep_process}}
+      - id: security-testing
+        title: Security Testing
+        template: |
+          - **SAST Tool:** {{static_analysis}}
+          - **DAST Tool:** {{dynamic_analysis}}
+          - **Penetration Testing:** {{pentest_schedule}}
+
+  - id: checklist-results
+    title: Checklist Results Report
+    instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
+
+  - id: next-steps
+    title: Next Steps
+    instruction: |
+      After completing the architecture:
+      
+      1. If project has UI components:
+      - Use "Frontend Architecture Mode"
+      - Provide this document as input
+      
+      2. For all projects:
+      - Review with Product Owner
+      - Begin story implementation with Dev agent
+      - Set up infrastructure with DevOps agent
+      
+      3. Include specific prompts for next agents if needed
+    sections:
+      - id: architect-prompt
+        title: Architect Prompt
+        condition: Project has UI components
+        instruction: |
+          Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include:
+          - Reference to this architecture document
+          - Key UI requirements from PRD
+          - Any frontend-specific decisions made here
+          - Request for detailed frontend architecture

bmad-core/templates/brainstorming-output-tmpl.md

@@ -1,149 +0,0 @@
----
-defaultOutput: docs/brainstorming-session-results.md
----
-
-# Brainstorming Session Results
-
-**Session Date:** [DATE]
-**Facilitator:** [Agent Role] [Agent Name]
-**Participant:** [USER NAME]
-
-## Executive Summary
-
-**Topic:** [SESSION TOPIC]
-
-**Session Goals:** [STATED GOALS]
-
-**Techniques Used:** [LIST OF TECHNIQUES AND DURATION]
-
-**Total Ideas Generated:** [NUMBER]
-
-**Key Themes Identified:**
-
-- [THEME 1]
-- [THEME 2]
-- [THEME 3]
-
----
-
-## Technique Sessions
-
-### [TECHNIQUE NAME 1] - [DURATION]
-
-**Description:** [BRIEF DESCRIPTION OF TECHNIQUE]
-
-**Ideas Generated:**
-
-1. [USER IDEA 1]
-2. [USER IDEA 2]
-3. [USER IDEA 3]
-[etc.]
-
-**Insights Discovered:**
-
-- [INSIGHT 1]
-- [INSIGHT 2]
-
-**Notable Connections:**
-
-- [CONNECTION OR PATTERN IDENTIFIED]
-
----
-
-### [TECHNIQUE NAME 2] - [DURATION]
-
-[Repeat format for each technique used]
-
----
-
-## Idea Categorization
-
-### Immediate Opportunities
-
-*Ideas ready to implement now*
-
-1. **[IDEA NAME]**
-   - Description: [BRIEF DESCRIPTION]
-   - Why immediate: [RATIONALE]
-   - Resources needed: [BASIC REQUIREMENTS]
-
-### Future Innovations
-
-*Ideas requiring development/research*
-
-1. **[IDEA NAME]**
-   - Description: [BRIEF DESCRIPTION]
-   - Development needed: [WHAT'S REQUIRED]
-   - Timeline estimate: [ROUGH TIMEFRAME]
-
-### Moonshots
-
-*Ambitious, transformative concepts*
-
-1. **[IDEA NAME]**
-   - Description: [BRIEF DESCRIPTION]
-   - Transformative potential: [WHY IT'S A MOONSHOT]
-   - Challenges to overcome: [MAJOR OBSTACLES]
-
-### Insights & Learnings
-
-*Key realizations from the session*
-
-- [INSIGHT 1]: [DESCRIPTION AND IMPLICATIONS]
-- [INSIGHT 2]: [DESCRIPTION AND IMPLICATIONS]
-
----
-
-## Action Planning
-
-### Top 3 Priority Ideas
-
-**#1 Priority: [IDEA NAME]**
-
-- Rationale: [WHY THIS IS TOP PRIORITY]
-- Next steps: [SPECIFIC ACTIONS TO TAKE]
-- Resources needed: [WHAT'S REQUIRED]
-- Timeline: [WHEN TO START/COMPLETE]
-
-**#2 Priority: [IDEA NAME]**
-
-- [Same format]
-
-**#3 Priority: [IDEA NAME]**
-
-- [Same format]
-
----
-
-## Reflection & Follow-up
-
-### What Worked Well
-
-- [SUCCESSFUL ASPECT 1]
-- [SUCCESSFUL ASPECT 2]
-
-### Areas for Further Exploration
-
-- [AREA 1]: [WHY IT NEEDS MORE EXPLORATION]
-- [AREA 2]: [WHY IT NEEDS MORE EXPLORATION]
-
-### Recommended Follow-up Techniques
-
-- [TECHNIQUE 1]: [WHY IT WOULD BE HELPFUL]
-- [TECHNIQUE 2]: [WHY IT WOULD BE HELPFUL]
-
-### Questions That Emerged
-
-- [QUESTION 1]
-- [QUESTION 2]
-- [QUESTION 3]
-
-### Next Session Planning
-
-- **Suggested topics:** [FOLLOW-UP TOPICS]
-- **Recommended timeframe:** [WHEN TO RECONVENE]
-- **Preparation needed:** [WHAT TO RESEARCH/PREPARE]
-
----
-
-*Session facilitated using the BMAD-METHOD brainstorming framework*

bmad-core/templates/brainstorming-output-tmpl.yaml

@@ -0,0 +1,156 @@
+template:
+  id: brainstorming-output-template-v2
+  name: Brainstorming Session Results
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/brainstorming-session-results.md
+    title: "Brainstorming Session Results"
+
+workflow:
+  mode: non-interactive
+
+sections:
+  - id: header
+    content: |
+      **Session Date:** {{date}}
+      **Facilitator:** {{agent_role}} {{agent_name}}
+      **Participant:** {{user_name}}
+
+  - id: executive-summary
+    title: Executive Summary
+    sections:
+      - id: summary-details
+        template: |
+          **Topic:** {{session_topic}}
+          
+          **Session Goals:** {{stated_goals}}
+          
+          **Techniques Used:** {{techniques_list}}
+          
+          **Total Ideas Generated:** {{total_ideas}}
+      - id: key-themes
+        title: "Key Themes Identified:"
+        type: bullet-list
+        template: "- {{theme}}"
+
+  - id: technique-sessions
+    title: Technique Sessions
+    repeatable: true
+    sections:
+      - id: technique
+        title: "{{technique_name}} - {{duration}}"
+        sections:
+          - id: description
+            template: "**Description:** {{technique_description}}"
+          - id: ideas-generated
+            title: "Ideas Generated:"
+            type: numbered-list
+            template: "{{idea}}"
+          - id: insights
+            title: "Insights Discovered:"
+            type: bullet-list
+            template: "- {{insight}}"
+          - id: connections
+            title: "Notable Connections:"
+            type: bullet-list
+            template: "- {{connection}}"
+
+  - id: idea-categorization
+    title: Idea Categorization
+    sections:
+      - id: immediate-opportunities
+        title: Immediate Opportunities
+        content: "*Ideas ready to implement now*"
+        repeatable: true
+        type: numbered-list
+        template: |
+          **{{idea_name}}**
+          - Description: {{description}}
+          - Why immediate: {{rationale}}
+          - Resources needed: {{requirements}}
+      - id: future-innovations
+        title: Future Innovations
+        content: "*Ideas requiring development/research*"
+        repeatable: true
+        type: numbered-list
+        template: |
+          **{{idea_name}}**
+          - Description: {{description}}
+          - Development needed: {{development_needed}}
+          - Timeline estimate: {{timeline}}
+      - id: moonshots
+        title: Moonshots
+        content: "*Ambitious, transformative concepts*"
+        repeatable: true
+        type: numbered-list
+        template: |
+          **{{idea_name}}**
+          - Description: {{description}}
+          - Transformative potential: {{potential}}
+          - Challenges to overcome: {{challenges}}
+      - id: insights-learnings
+        title: Insights & Learnings
+        content: "*Key realizations from the session*"
+        type: bullet-list
+        template: "- {{insight}}: {{description_and_implications}}"
+
+  - id: action-planning
+    title: Action Planning
+    sections:
+      - id: top-priorities
+        title: Top 3 Priority Ideas
+        sections:
+          - id: priority-1
+            title: "#1 Priority: {{idea_name}}"
+            template: |
+              - Rationale: {{rationale}}
+              - Next steps: {{next_steps}}
+              - Resources needed: {{resources}}
+              - Timeline: {{timeline}}
+          - id: priority-2
+            title: "#2 Priority: {{idea_name}}"
+            template: |
+              - Rationale: {{rationale}}
+              - Next steps: {{next_steps}}
+              - Resources needed: {{resources}}
+              - Timeline: {{timeline}}
+          - id: priority-3
+            title: "#3 Priority: {{idea_name}}"
+            template: |
+              - Rationale: {{rationale}}
+              - Next steps: {{next_steps}}
+              - Resources needed: {{resources}}
+              - Timeline: {{timeline}}
+
+  - id: reflection-followup
+    title: Reflection & Follow-up
+    sections:
+      - id: what-worked
+        title: What Worked Well
+        type: bullet-list
+        template: "- {{aspect}}"
+      - id: areas-exploration
+        title: Areas for Further Exploration
+        type: bullet-list
+        template: "- {{area}}: {{reason}}"
+      - id: recommended-techniques
+        title: Recommended Follow-up Techniques
+        type: bullet-list
+        template: "- {{technique}}: {{reason}}"
+      - id: questions-emerged
+        title: Questions That Emerged
+        type: bullet-list
+        template: "- {{question}}"
+      - id: next-session
+        title: Next Session Planning
+        template: |
+          - **Suggested topics:** {{followup_topics}}
+          - **Recommended timeframe:** {{timeframe}}
+          - **Preparation needed:** {{preparation}}
+
+  - id: footer
+    content: |
+      ---
+      
+      *Session facilitated using the BMAD-METHOD brainstorming framework*

bmad-core/templates/brownfield-architecture-tmpl.md

@@ -1,544 +0,0 @@
-# {{Project Name}} Brownfield Enhancement Architecture
-
-[[LLM: The default path and filename unless specified is docs/architecture.md]]
-
-[[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
-
-This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
-
-1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
-
-2. **REQUIRED INPUTS**:
-
-   - Completed brownfield-prd.md
-   - Existing project technical documentation (from docs folder or user-provided)
-   - Access to existing project structure (IDE or uploaded files)
-
-3. **DEEP ANALYSIS MANDATE**: You MUST conduct thorough analysis of the existing codebase, architecture patterns, and technical constraints before making ANY architectural recommendations. Every suggestion must be based on actual project analysis, not assumptions.
-
-4. **CONTINUOUS VALIDATION**: Throughout this process, explicitly validate your understanding with the user. For every architectural decision, confirm: "Based on my analysis of your existing system, I recommend [decision] because [evidence from actual project]. Does this align with your system's reality?"
-
-If any required inputs are missing, request them before proceeding.]]
-
-## Introduction
-
-[[LLM: This section establishes the document's purpose and scope for brownfield enhancements. Keep the content below but ensure project name and enhancement details are properly substituted.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-This document outlines the architectural approach for enhancing {{Project Name}} with {{Enhancement Description}}. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development of new features while ensuring seamless integration with the existing system.
-
-**Relationship to Existing Architecture:**
-This document supplements existing project architecture by defining how new components will integrate with current systems. Where conflicts arise between new and existing patterns, this document provides guidance on maintaining consistency while implementing enhancements.
-
-### Existing Project Analysis
-
-[[LLM: Analyze the existing project structure and architecture:
-
-1. Review existing documentation in docs folder
-2. Examine current technology stack and versions
-3. Identify existing architectural patterns and conventions
-4. Note current deployment and infrastructure setup
-5. Document any constraints or limitations
-
-CRITICAL: After your analysis, explicitly validate your findings: "Based on my analysis of your project, I've identified the following about your existing system: [key findings]. Please confirm these observations are accurate before I proceed with architectural recommendations."
-
-Present findings and apply `tasks#advanced-elicitation` protocol]]
-
-**Current Project State:**
-
-- **Primary Purpose:** {{existing_project_purpose}}
-- **Current Tech Stack:** {{existing_tech_summary}}
-- **Architecture Style:** {{existing_architecture_style}}
-- **Deployment Method:** {{existing_deployment_approach}}
-
-**Available Documentation:**
-
-- {{existing_docs_summary}}
-
-**Identified Constraints:**
-
-- {{constraint_1}}
-- {{constraint_2}}
-- {{constraint_3}}
-
-### Change Log
-
-| Change | Date | Version | Description | Author |
-| ------ | ---- | ------- | ----------- | ------ |
-
-## Enhancement Scope and Integration Strategy
-
-[[LLM: Define how the enhancement will integrate with the existing system:
-
-1. Review the brownfield PRD enhancement scope
-2. Identify integration points with existing code
-3. Define boundaries between new and existing functionality
-4. Establish compatibility requirements
-
-VALIDATION CHECKPOINT: Before presenting the integration strategy, confirm: "Based on my analysis, the integration approach I'm proposing takes into account [specific existing system characteristics]. These integration points and boundaries respect your current architecture patterns. Is this assessment accurate?"
-
-Present complete integration strategy and apply `tasks#advanced-elicitation` protocol]]
-
-### Enhancement Overview
-
-**Enhancement Type:** {{enhancement_type}}
-**Scope:** {{enhancement_scope}}
-**Integration Impact:** {{integration_impact_level}}
-
-### Integration Approach
-
-**Code Integration Strategy:** {{code_integration_approach}}
-**Database Integration:** {{database_integration_approach}}
-**API Integration:** {{api_integration_approach}}
-**UI Integration:** {{ui_integration_approach}}
-
-### Compatibility Requirements
-
-- **Existing API Compatibility:** {{api_compatibility}}
-- **Database Schema Compatibility:** {{db_compatibility}}
-- **UI/UX Consistency:** {{ui_compatibility}}
-- **Performance Impact:** {{performance_constraints}}
-
-## Tech Stack Alignment
-
-[[LLM: Ensure new components align with existing technology choices:
-
-1. Use existing technology stack as the foundation
-2. Only introduce new technologies if absolutely necessary
-3. Justify any new additions with clear rationale
-4. Ensure version compatibility with existing dependencies
-
-Present complete tech stack alignment and apply `tasks#advanced-elicitation` protocol]]
-
-### Existing Technology Stack
-
-[[LLM: Document the current stack that must be maintained or integrated with]]
-
-| Category           | Current Technology | Version     | Usage in Enhancement | Notes     |
-| :----------------- | :----------------- | :---------- | :------------------- | :-------- |
-| **Language**       | {{language}}       | {{version}} | {{usage}}            | {{notes}} |
-| **Runtime**        | {{runtime}}        | {{version}} | {{usage}}            | {{notes}} |
-| **Framework**      | {{framework}}      | {{version}} | {{usage}}            | {{notes}} |
-| **Database**       | {{database}}       | {{version}} | {{usage}}            | {{notes}} |
-| **API Style**      | {{api_style}}      | {{version}} | {{usage}}            | {{notes}} |
-| **Authentication** | {{auth}}           | {{version}} | {{usage}}            | {{notes}} |
-| **Testing**        | {{test_framework}} | {{version}} | {{usage}}            | {{notes}} |
-| **Build Tool**     | {{build_tool}}     | {{version}} | {{usage}}            | {{notes}} |
-
-### New Technology Additions
-
-[[LLM: Only include if new technologies are required for the enhancement]]
-
-^^CONDITION: has_new_tech^^
-
-| Technology   | Version     | Purpose     | Rationale     | Integration Method |
-| :----------- | :---------- | :---------- | :------------ | :----------------- |
-| {{new_tech}} | {{version}} | {{purpose}} | {{rationale}} | {{integration}}    |
-
-^^/CONDITION: has_new_tech^^
-
-## Data Models and Schema Changes
-
-[[LLM: Define new data models and how they integrate with existing schema:
-
-1. Identify new entities required for the enhancement
-2. Define relationships with existing data models
-3. Plan database schema changes (additions, modifications)
-4. Ensure backward compatibility
-
-Present data model changes and apply `tasks#advanced-elicitation` protocol]]
-
-### New Data Models
-
-<<REPEAT: new_data_model>>
-
-### {{model_name}}
-
-**Purpose:** {{model_purpose}}
-**Integration:** {{integration_with_existing}}
-
-**Key Attributes:**
-
-- {{attribute_1}}: {{type_1}} - {{description_1}}
-- {{attribute_2}}: {{type_2}} - {{description_2}}
-
-**Relationships:**
-
-- **With Existing:** {{existing_relationships}}
-- **With New:** {{new_relationships}}
-
-<</REPEAT>>
-
-### Schema Integration Strategy
-
-**Database Changes Required:**
-
-- **New Tables:** {{new_tables_list}}
-- **Modified Tables:** {{modified_tables_list}}
-- **New Indexes:** {{new_indexes_list}}
-- **Migration Strategy:** {{migration_approach}}
-
-**Backward Compatibility:**
-
-- {{compatibility_measure_1}}
-- {{compatibility_measure_2}}
-
-## Component Architecture
-
-[[LLM: Define new components and their integration with existing architecture:
-
-1. Identify new components required for the enhancement
-2. Define interfaces with existing components
-3. Establish clear boundaries and responsibilities
-4. Plan integration points and data flow
-
-MANDATORY VALIDATION: Before presenting component architecture, confirm: "The new components I'm proposing follow the existing architectural patterns I identified in your codebase: [specific patterns]. The integration interfaces respect your current component structure and communication patterns. Does this match your project's reality?"
-
-Present component architecture and apply `tasks#advanced-elicitation` protocol]]
-
-### New Components
-
-<<REPEAT: new_component>>
-
-### {{component_name}}
-
-**Responsibility:** {{component_description}}
-**Integration Points:** {{integration_points}}
-
-**Key Interfaces:**
-
-- {{interface_1}}
-- {{interface_2}}
-
-**Dependencies:**
-
-- **Existing Components:** {{existing_dependencies}}
-- **New Components:** {{new_dependencies}}
-
-**Technology Stack:** {{component_tech_details}}
-
-<</REPEAT>>
-
-### Component Interaction Diagram
-
-[[LLM: Create Mermaid diagram showing how new components interact with existing ones]]
-
-```mermaid
-{{component_interaction_diagram}}
-```
-
-## API Design and Integration
-
-[[LLM: Define new API endpoints and integration with existing APIs:
-
-1. Plan new API endpoints required for the enhancement
-2. Ensure consistency with existing API patterns
-3. Define authentication and authorization integration
-4. Plan versioning strategy if needed
-
-Present API design and apply `tasks#advanced-elicitation` protocol]]
-
-### New API Endpoints
-
-^^CONDITION: has_new_api^^
-
-**API Integration Strategy:** {{api_integration_strategy}}
-**Authentication:** {{auth_integration}}
-**Versioning:** {{versioning_approach}}
-
-<<REPEAT: new_endpoint>>
-
-#### {{endpoint_name}}
-
-- **Method:** {{http_method}}
-- **Endpoint:** {{endpoint_path}}
-- **Purpose:** {{endpoint_purpose}}
-- **Integration:** {{integration_with_existing}}
-
-**Request:**
-
-```json
-{{request_schema}}
-```
-
-**Response:**
-
-```json
-{{response_schema}}
-```
-
-<</REPEAT>>
-
-^^/CONDITION: has_new_api^^
-
-## External API Integration
-
-[[LLM: Document new external API integrations required for the enhancement]]
-
-^^CONDITION: has_new_external_apis^^
-
-<<REPEAT: external_api>>
-
-### {{api_name}} API
-
-- **Purpose:** {{api_purpose}}
-- **Documentation:** {{api_docs_url}}
-- **Base URL:** {{api_base_url}}
-- **Authentication:** {{auth_method}}
-- **Integration Method:** {{integration_approach}}
-
-**Key Endpoints Used:**
-
-- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
-
-**Error Handling:** {{error_handling_strategy}}
-
-<</REPEAT>>
-
-^^/CONDITION: has_new_external_apis^^
-
-## Source Tree Integration
-
-[[LLM: Define how new code will integrate with existing project structure:
-
-1. Follow existing project organization patterns
-2. Identify where new files/folders will be placed
-3. Ensure consistency with existing naming conventions
-4. Plan for minimal disruption to existing structure
-
-Present integration plan and apply `tasks#advanced-elicitation` protocol]]
-
-### Existing Project Structure
-
-[[LLM: Document relevant parts of current structure]]
-
-```plaintext
-{{existing_structure_relevant_parts}}
-```
-
-### New File Organization
-
-[[LLM: Show only new additions to existing structure]]
-
-```plaintext
-{{project-root}}/
-├── {{existing_structure_context}}
-│   ├── {{new_folder_1}}/           # {{purpose_1}}
-│   │   ├── {{new_file_1}}
-│   │   └── {{new_file_2}}
-│   ├── {{existing_folder}}/        # Existing folder with additions
-│   │   ├── {{existing_file}}       # Existing file
-│   │   └── {{new_file_3}}          # New addition
-│   └── {{new_folder_2}}/           # {{purpose_2}}
-```
-
-### Integration Guidelines
-
-- **File Naming:** {{file_naming_consistency}}
-- **Folder Organization:** {{folder_organization_approach}}
-- **Import/Export Patterns:** {{import_export_consistency}}
-
-## Infrastructure and Deployment Integration
-
-[[LLM: Define how the enhancement will be deployed alongside existing infrastructure:
-
-1. Use existing deployment pipeline and infrastructure
-2. Identify any infrastructure changes needed
-3. Plan deployment strategy to minimize risk
-4. Define rollback procedures
-
-Present deployment integration and apply `tasks#advanced-elicitation` protocol]]
-
-### Existing Infrastructure
-
-**Current Deployment:** {{existing_deployment_summary}}
-**Infrastructure Tools:** {{existing_infrastructure_tools}}
-**Environments:** {{existing_environments}}
-
-### Enhancement Deployment Strategy
-
-**Deployment Approach:** {{deployment_approach}}
-**Infrastructure Changes:** {{infrastructure_changes}}
-**Pipeline Integration:** {{pipeline_integration}}
-
-### Rollback Strategy
-
-**Rollback Method:** {{rollback_method}}
-**Risk Mitigation:** {{risk_mitigation}}
-**Monitoring:** {{monitoring_approach}}
-
-## Coding Standards and Conventions
-
-[[LLM: Ensure new code follows existing project conventions:
-
-1. Document existing coding standards from project analysis
-2. Identify any enhancement-specific requirements
-3. Ensure consistency with existing codebase patterns
-4. Define standards for new code organization
-
-Present coding standards and apply `tasks#advanced-elicitation` protocol]]
-
-### Existing Standards Compliance
-
-**Code Style:** {{existing_code_style}}
-**Linting Rules:** {{existing_linting}}
-**Testing Patterns:** {{existing_test_patterns}}
-**Documentation Style:** {{existing_doc_style}}
-
-### Enhancement-Specific Standards
-
-[[LLM: Only include if new patterns are needed for the enhancement]]
-
-<<REPEAT: enhancement_standard>>
-
-- **{{standard_name}}:** {{standard_description}}
-
-<</REPEAT>>
-
-### Critical Integration Rules
-
-- **Existing API Compatibility:** {{api_compatibility_rule}}
-- **Database Integration:** {{db_integration_rule}}
-- **Error Handling:** {{error_handling_integration}}
-- **Logging Consistency:** {{logging_consistency}}
-
-## Testing Strategy
-
-[[LLM: Define testing approach for the enhancement:
-
-1. Integrate with existing test suite
-2. Ensure existing functionality remains intact
-3. Plan for testing new features
-4. Define integration testing approach
-
-Present testing strategy and apply `tasks#advanced-elicitation` protocol]]
-
-### Integration with Existing Tests
-
-**Existing Test Framework:** {{existing_test_framework}}
-**Test Organization:** {{existing_test_organization}}
-**Coverage Requirements:** {{existing_coverage_requirements}}
-
-### New Testing Requirements
-
-#### Unit Tests for New Components
-
-- **Framework:** {{test_framework}}
-- **Location:** {{test_location}}
-- **Coverage Target:** {{coverage_target}}
-- **Integration with Existing:** {{test_integration}}
-
-#### Integration Tests
-
-- **Scope:** {{integration_test_scope}}
-- **Existing System Verification:** {{existing_system_verification}}
-- **New Feature Testing:** {{new_feature_testing}}
-
-#### Regression Testing
-
-- **Existing Feature Verification:** {{regression_test_approach}}
-- **Automated Regression Suite:** {{automated_regression}}
-- **Manual Testing Requirements:** {{manual_testing_requirements}}
-
-## Security Integration
-
-[[LLM: Ensure security consistency with existing system:
-
-1. Follow existing security patterns and tools
-2. Ensure new features don't introduce vulnerabilities
-3. Maintain existing security posture
-4. Define security testing for new components
-
-Present security integration and apply `tasks#advanced-elicitation` protocol]]
-
-### Existing Security Measures
-
-**Authentication:** {{existing_auth}}
-**Authorization:** {{existing_authz}}
-**Data Protection:** {{existing_data_protection}}
-**Security Tools:** {{existing_security_tools}}
-
-### Enhancement Security Requirements
-
-**New Security Measures:** {{new_security_measures}}
-**Integration Points:** {{security_integration_points}}
-**Compliance Requirements:** {{compliance_requirements}}
-
-### Security Testing
-
-**Existing Security Tests:** {{existing_security_tests}}
-**New Security Test Requirements:** {{new_security_tests}}
-**Penetration Testing:** {{pentest_requirements}}
-
-## Risk Assessment and Mitigation
-
-[[LLM: Identify and plan for risks specific to brownfield development:
-
-1. Technical integration risks
-2. Deployment and operational risks
-3. User impact and compatibility risks
-4. Mitigation strategies for each risk
-
-Present risk assessment and apply `tasks#advanced-elicitation` protocol]]
-
-### Technical Risks
-
-<<REPEAT: technical_risk>>
-
-**Risk:** {{risk_description}}
-**Impact:** {{impact_level}}
-**Likelihood:** {{likelihood}}
-**Mitigation:** {{mitigation_strategy}}
-
-<</REPEAT>>
-
-### Operational Risks
-
-<<REPEAT: operational_risk>>
-
-**Risk:** {{risk_description}}
-**Impact:** {{impact_level}}
-**Likelihood:** {{likelihood}}
-**Mitigation:** {{mitigation_strategy}}
-
-<</REPEAT>>
-
-### Monitoring and Alerting
-
-**Enhanced Monitoring:** {{monitoring_additions}}
-**New Alerts:** {{new_alerts}}
-**Performance Monitoring:** {{performance_monitoring}}
-
-## Checklist Results Report
-
-[[LLM: Execute the architect-checklist and populate results here, focusing on brownfield-specific validation]]
-
-## Next Steps
-
-[[LLM: After completing the brownfield architecture:
-
-1. Review integration points with existing system
-2. Begin story implementation with Dev agent
-3. Set up deployment pipeline integration
-4. Plan rollback and monitoring procedures]]
-
-### Story Manager Handoff
-
-[[LLM: Create a brief prompt for Story Manager to work with this brownfield enhancement. Include:
-
-- Reference to this architecture document
-- Key integration requirements validated with user
-- Existing system constraints based on actual project analysis
-- First story to implement with clear integration checkpoints
-- Emphasis on maintaining existing system integrity throughout implementation]]
-
-### Developer Handoff
-
-[[LLM: Create a brief prompt for developers starting implementation. Include:
-
-- Reference to this architecture and existing coding standards analyzed from actual project
-- Integration requirements with existing codebase validated with user
-- Key technical decisions based on real project constraints
-- Existing system compatibility requirements with specific verification steps
-- Clear sequencing of implementation to minimize risk to existing functionality]]

bmad-core/templates/brownfield-architecture-tmpl.yaml

@@ -0,0 +1,476 @@
+template:
+  id: brownfield-architecture-template-v2
+  name: Brownfield Enhancement Architecture
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/architecture.md
+    title: "{{project_name}} Brownfield Enhancement Architecture"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: introduction
+    title: Introduction
+    instruction: |
+      IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
+      
+      This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
+      
+      1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
+      
+      2. **REQUIRED INPUTS**:
+         - Completed brownfield-prd.md
+         - Existing project technical documentation (from docs folder or user-provided)
+         - Access to existing project structure (IDE or uploaded files)
+      
+      3. **DEEP ANALYSIS MANDATE**: You MUST conduct thorough analysis of the existing codebase, architecture patterns, and technical constraints before making ANY architectural recommendations. Every suggestion must be based on actual project analysis, not assumptions.
+      
+      4. **CONTINUOUS VALIDATION**: Throughout this process, explicitly validate your understanding with the user. For every architectural decision, confirm: "Based on my analysis of your existing system, I recommend [decision] because [evidence from actual project]. Does this align with your system's reality?"
+      
+      If any required inputs are missing, request them before proceeding.
+    elicit: true
+    sections:
+      - id: intro-content
+        content: |
+          This document outlines the architectural approach for enhancing {{project_name}} with {{enhancement_description}}. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development of new features while ensuring seamless integration with the existing system.
+          
+          **Relationship to Existing Architecture:**
+          This document supplements existing project architecture by defining how new components will integrate with current systems. Where conflicts arise between new and existing patterns, this document provides guidance on maintaining consistency while implementing enhancements.
+      - id: existing-project-analysis
+        title: Existing Project Analysis
+        instruction: |
+          Analyze the existing project structure and architecture:
+          
+          1. Review existing documentation in docs folder
+          2. Examine current technology stack and versions
+          3. Identify existing architectural patterns and conventions
+          4. Note current deployment and infrastructure setup
+          5. Document any constraints or limitations
+          
+          CRITICAL: After your analysis, explicitly validate your findings: "Based on my analysis of your project, I've identified the following about your existing system: [key findings]. Please confirm these observations are accurate before I proceed with architectural recommendations."
+        elicit: true
+        sections:
+          - id: current-state
+            title: Current Project State
+            template: |
+              - **Primary Purpose:** {{existing_project_purpose}}
+              - **Current Tech Stack:** {{existing_tech_summary}}
+              - **Architecture Style:** {{existing_architecture_style}}
+              - **Deployment Method:** {{existing_deployment_approach}}
+          - id: available-docs
+            title: Available Documentation
+            type: bullet-list
+            template: "- {{existing_docs_summary}}"
+          - id: constraints
+            title: Identified Constraints
+            type: bullet-list
+            template: "- {{constraint}}"
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Change, Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: enhancement-scope
+    title: Enhancement Scope and Integration Strategy
+    instruction: |
+      Define how the enhancement will integrate with the existing system:
+      
+      1. Review the brownfield PRD enhancement scope
+      2. Identify integration points with existing code
+      3. Define boundaries between new and existing functionality
+      4. Establish compatibility requirements
+      
+      VALIDATION CHECKPOINT: Before presenting the integration strategy, confirm: "Based on my analysis, the integration approach I'm proposing takes into account [specific existing system characteristics]. These integration points and boundaries respect your current architecture patterns. Is this assessment accurate?"
+    elicit: true
+    sections:
+      - id: enhancement-overview
+        title: Enhancement Overview
+        template: |
+          **Enhancement Type:** {{enhancement_type}}
+          **Scope:** {{enhancement_scope}}
+          **Integration Impact:** {{integration_impact_level}}
+      - id: integration-approach
+        title: Integration Approach
+        template: |
+          **Code Integration Strategy:** {{code_integration_approach}}
+          **Database Integration:** {{database_integration_approach}}
+          **API Integration:** {{api_integration_approach}}
+          **UI Integration:** {{ui_integration_approach}}
+      - id: compatibility-requirements
+        title: Compatibility Requirements
+        template: |
+          - **Existing API Compatibility:** {{api_compatibility}}
+          - **Database Schema Compatibility:** {{db_compatibility}}
+          - **UI/UX Consistency:** {{ui_compatibility}}
+          - **Performance Impact:** {{performance_constraints}}
+
+  - id: tech-stack-alignment
+    title: Tech Stack Alignment
+    instruction: |
+      Ensure new components align with existing technology choices:
+      
+      1. Use existing technology stack as the foundation
+      2. Only introduce new technologies if absolutely necessary
+      3. Justify any new additions with clear rationale
+      4. Ensure version compatibility with existing dependencies
+    elicit: true
+    sections:
+      - id: existing-stack
+        title: Existing Technology Stack
+        type: table
+        columns: [Category, Current Technology, Version, Usage in Enhancement, Notes]
+        instruction: Document the current stack that must be maintained or integrated with
+      - id: new-tech-additions
+        title: New Technology Additions
+        condition: Enhancement requires new technologies
+        type: table
+        columns: [Technology, Version, Purpose, Rationale, Integration Method]
+        instruction: Only include if new technologies are required for the enhancement
+
+  - id: data-models
+    title: Data Models and Schema Changes
+    instruction: |
+      Define new data models and how they integrate with existing schema:
+      
+      1. Identify new entities required for the enhancement
+      2. Define relationships with existing data models
+      3. Plan database schema changes (additions, modifications)
+      4. Ensure backward compatibility
+    elicit: true
+    sections:
+      - id: new-models
+        title: New Data Models
+        repeatable: true
+        sections:
+          - id: model
+            title: "{{model_name}}"
+            template: |
+              **Purpose:** {{model_purpose}}
+              **Integration:** {{integration_with_existing}}
+              
+              **Key Attributes:**
+              - {{attribute_1}}: {{type_1}} - {{description_1}}
+              - {{attribute_2}}: {{type_2}} - {{description_2}}
+              
+              **Relationships:**
+              - **With Existing:** {{existing_relationships}}
+              - **With New:** {{new_relationships}}
+      - id: schema-integration
+        title: Schema Integration Strategy
+        template: |
+          **Database Changes Required:**
+          - **New Tables:** {{new_tables_list}}
+          - **Modified Tables:** {{modified_tables_list}}
+          - **New Indexes:** {{new_indexes_list}}
+          - **Migration Strategy:** {{migration_approach}}
+          
+          **Backward Compatibility:**
+          - {{compatibility_measure_1}}
+          - {{compatibility_measure_2}}
+
+  - id: component-architecture
+    title: Component Architecture
+    instruction: |
+      Define new components and their integration with existing architecture:
+      
+      1. Identify new components required for the enhancement
+      2. Define interfaces with existing components
+      3. Establish clear boundaries and responsibilities
+      4. Plan integration points and data flow
+      
+      MANDATORY VALIDATION: Before presenting component architecture, confirm: "The new components I'm proposing follow the existing architectural patterns I identified in your codebase: [specific patterns]. The integration interfaces respect your current component structure and communication patterns. Does this match your project's reality?"
+    elicit: true
+    sections:
+      - id: new-components
+        title: New Components
+        repeatable: true
+        sections:
+          - id: component
+            title: "{{component_name}}"
+            template: |
+              **Responsibility:** {{component_description}}
+              **Integration Points:** {{integration_points}}
+              
+              **Key Interfaces:**
+              - {{interface_1}}
+              - {{interface_2}}
+              
+              **Dependencies:**
+              - **Existing Components:** {{existing_dependencies}}
+              - **New Components:** {{new_dependencies}}
+              
+              **Technology Stack:** {{component_tech_details}}
+      - id: interaction-diagram
+        title: Component Interaction Diagram
+        type: mermaid
+        mermaid_type: graph
+        instruction: Create Mermaid diagram showing how new components interact with existing ones
+
+  - id: api-design
+    title: API Design and Integration
+    condition: Enhancement requires API changes
+    instruction: |
+      Define new API endpoints and integration with existing APIs:
+      
+      1. Plan new API endpoints required for the enhancement
+      2. Ensure consistency with existing API patterns
+      3. Define authentication and authorization integration
+      4. Plan versioning strategy if needed
+    elicit: true
+    sections:
+      - id: api-strategy
+        title: API Integration Strategy
+        template: |
+          **API Integration Strategy:** {{api_integration_strategy}}
+          **Authentication:** {{auth_integration}}
+          **Versioning:** {{versioning_approach}}
+      - id: new-endpoints
+        title: New API Endpoints
+        repeatable: true
+        sections:
+          - id: endpoint
+            title: "{{endpoint_name}}"
+            template: |
+              - **Method:** {{http_method}}
+              - **Endpoint:** {{endpoint_path}}
+              - **Purpose:** {{endpoint_purpose}}
+              - **Integration:** {{integration_with_existing}}
+            sections:
+              - id: request
+                title: Request
+                type: code
+                language: json
+                template: "{{request_schema}}"
+              - id: response
+                title: Response
+                type: code
+                language: json
+                template: "{{response_schema}}"
+
+  - id: external-api-integration
+    title: External API Integration
+    condition: Enhancement requires new external APIs
+    instruction: Document new external API integrations required for the enhancement
+    repeatable: true
+    sections:
+      - id: external-api
+        title: "{{api_name}} API"
+        template: |
+          - **Purpose:** {{api_purpose}}
+          - **Documentation:** {{api_docs_url}}
+          - **Base URL:** {{api_base_url}}
+          - **Authentication:** {{auth_method}}
+          - **Integration Method:** {{integration_approach}}
+          
+          **Key Endpoints Used:**
+          - `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
+          
+          **Error Handling:** {{error_handling_strategy}}
+
+  - id: source-tree-integration
+    title: Source Tree Integration
+    instruction: |
+      Define how new code will integrate with existing project structure:
+      
+      1. Follow existing project organization patterns
+      2. Identify where new files/folders will be placed
+      3. Ensure consistency with existing naming conventions
+      4. Plan for minimal disruption to existing structure
+    elicit: true
+    sections:
+      - id: existing-structure
+        title: Existing Project Structure
+        type: code
+        language: plaintext
+        instruction: Document relevant parts of current structure
+        template: "{{existing_structure_relevant_parts}}"
+      - id: new-file-organization
+        title: New File Organization
+        type: code
+        language: plaintext
+        instruction: Show only new additions to existing structure
+        template: |
+          {{project-root}}/
+          ├── {{existing_structure_context}}
+          │   ├── {{new_folder_1}}/           # {{purpose_1}}
+          │   │   ├── {{new_file_1}}
+          │   │   └── {{new_file_2}}
+          │   ├── {{existing_folder}}/        # Existing folder with additions
+          │   │   ├── {{existing_file}}       # Existing file
+          │   │   └── {{new_file_3}}          # New addition
+          │   └── {{new_folder_2}}/           # {{purpose_2}}
+      - id: integration-guidelines
+        title: Integration Guidelines
+        template: |
+          - **File Naming:** {{file_naming_consistency}}
+          - **Folder Organization:** {{folder_organization_approach}}
+          - **Import/Export Patterns:** {{import_export_consistency}}
+
+  - id: infrastructure-deployment
+    title: Infrastructure and Deployment Integration
+    instruction: |
+      Define how the enhancement will be deployed alongside existing infrastructure:
+      
+      1. Use existing deployment pipeline and infrastructure
+      2. Identify any infrastructure changes needed
+      3. Plan deployment strategy to minimize risk
+      4. Define rollback procedures
+    elicit: true
+    sections:
+      - id: existing-infrastructure
+        title: Existing Infrastructure
+        template: |
+          **Current Deployment:** {{existing_deployment_summary}}
+          **Infrastructure Tools:** {{existing_infrastructure_tools}}
+          **Environments:** {{existing_environments}}
+      - id: enhancement-deployment
+        title: Enhancement Deployment Strategy
+        template: |
+          **Deployment Approach:** {{deployment_approach}}
+          **Infrastructure Changes:** {{infrastructure_changes}}
+          **Pipeline Integration:** {{pipeline_integration}}
+      - id: rollback-strategy
+        title: Rollback Strategy
+        template: |
+          **Rollback Method:** {{rollback_method}}
+          **Risk Mitigation:** {{risk_mitigation}}
+          **Monitoring:** {{monitoring_approach}}
+
+  - id: coding-standards
+    title: Coding Standards and Conventions
+    instruction: |
+      Ensure new code follows existing project conventions:
+      
+      1. Document existing coding standards from project analysis
+      2. Identify any enhancement-specific requirements
+      3. Ensure consistency with existing codebase patterns
+      4. Define standards for new code organization
+    elicit: true
+    sections:
+      - id: existing-standards
+        title: Existing Standards Compliance
+        template: |
+          **Code Style:** {{existing_code_style}}
+          **Linting Rules:** {{existing_linting}}
+          **Testing Patterns:** {{existing_test_patterns}}
+          **Documentation Style:** {{existing_doc_style}}
+      - id: enhancement-standards
+        title: Enhancement-Specific Standards
+        condition: New patterns needed for enhancement
+        repeatable: true
+        template: "- **{{standard_name}}:** {{standard_description}}"
+      - id: integration-rules
+        title: Critical Integration Rules
+        template: |
+          - **Existing API Compatibility:** {{api_compatibility_rule}}
+          - **Database Integration:** {{db_integration_rule}}
+          - **Error Handling:** {{error_handling_integration}}
+          - **Logging Consistency:** {{logging_consistency}}
+
+  - id: testing-strategy
+    title: Testing Strategy
+    instruction: |
+      Define testing approach for the enhancement:
+      
+      1. Integrate with existing test suite
+      2. Ensure existing functionality remains intact
+      3. Plan for testing new features
+      4. Define integration testing approach
+    elicit: true
+    sections:
+      - id: existing-test-integration
+        title: Integration with Existing Tests
+        template: |
+          **Existing Test Framework:** {{existing_test_framework}}
+          **Test Organization:** {{existing_test_organization}}
+          **Coverage Requirements:** {{existing_coverage_requirements}}
+      - id: new-testing
+        title: New Testing Requirements
+        sections:
+          - id: unit-tests
+            title: Unit Tests for New Components
+            template: |
+              - **Framework:** {{test_framework}}
+              - **Location:** {{test_location}}
+              - **Coverage Target:** {{coverage_target}}
+              - **Integration with Existing:** {{test_integration}}
+          - id: integration-tests
+            title: Integration Tests
+            template: |
+              - **Scope:** {{integration_test_scope}}
+              - **Existing System Verification:** {{existing_system_verification}}
+              - **New Feature Testing:** {{new_feature_testing}}
+          - id: regression-tests
+            title: Regression Testing
+            template: |
+              - **Existing Feature Verification:** {{regression_test_approach}}
+              - **Automated Regression Suite:** {{automated_regression}}
+              - **Manual Testing Requirements:** {{manual_testing_requirements}}
+
+  - id: security-integration
+    title: Security Integration
+    instruction: |
+      Ensure security consistency with existing system:
+      
+      1. Follow existing security patterns and tools
+      2. Ensure new features don't introduce vulnerabilities
+      3. Maintain existing security posture
+      4. Define security testing for new components
+    elicit: true
+    sections:
+      - id: existing-security
+        title: Existing Security Measures
+        template: |
+          **Authentication:** {{existing_auth}}
+          **Authorization:** {{existing_authz}}
+          **Data Protection:** {{existing_data_protection}}
+          **Security Tools:** {{existing_security_tools}}
+      - id: enhancement-security
+        title: Enhancement Security Requirements
+        template: |
+          **New Security Measures:** {{new_security_measures}}
+          **Integration Points:** {{security_integration_points}}
+          **Compliance Requirements:** {{compliance_requirements}}
+      - id: security-testing
+        title: Security Testing
+        template: |
+          **Existing Security Tests:** {{existing_security_tests}}
+          **New Security Test Requirements:** {{new_security_tests}}
+          **Penetration Testing:** {{pentest_requirements}}
+
+  - id: checklist-results
+    title: Checklist Results Report
+    instruction: Execute the architect-checklist and populate results here, focusing on brownfield-specific validation
+
+  - id: next-steps
+    title: Next Steps
+    instruction: |
+      After completing the brownfield architecture:
+      
+      1. Review integration points with existing system
+      2. Begin story implementation with Dev agent
+      3. Set up deployment pipeline integration
+      4. Plan rollback and monitoring procedures
+    sections:
+      - id: story-manager-handoff
+        title: Story Manager Handoff
+        instruction: |
+          Create a brief prompt for Story Manager to work with this brownfield enhancement. Include:
+          - Reference to this architecture document
+          - Key integration requirements validated with user
+          - Existing system constraints based on actual project analysis
+          - First story to implement with clear integration checkpoints
+          - Emphasis on maintaining existing system integrity throughout implementation
+      - id: developer-handoff
+        title: Developer Handoff
+        instruction: |
+          Create a brief prompt for developers starting implementation. Include:
+          - Reference to this architecture and existing coding standards analyzed from actual project
+          - Integration requirements with existing codebase validated with user
+          - Key technical decisions based on real project constraints
+          - Existing system compatibility requirements with specific verification steps
+          - Clear sequencing of implementation to minimize risk to existing functionality

bmad-core/templates/brownfield-prd-tmpl.md

@@ -1,266 +0,0 @@
-# {{Project Name}} Brownfield Enhancement PRD
-
-[[LLM: The default path and filename unless specified is docs/prd.md]]
-
-[[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
-
-This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:
-
-1. **Assess Enhancement Complexity**: If this is a simple feature addition or bug fix that could be completed in 1-2 focused development sessions, STOP and recommend: "For simpler changes, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead. This full PRD process is designed for substantial enhancements that require architectural planning and multiple coordinated stories."
-
-2. **Project Context**: Determine if we're working in an IDE with the project already loaded or if the user needs to provide project information. If project files are available, analyze existing documentation in the docs folder. If insufficient documentation exists, recommend running the document-project task first.
-
-3. **Deep Assessment Requirement**: You MUST thoroughly analyze the existing project structure, patterns, and constraints before making ANY suggestions. Every recommendation must be grounded in actual project analysis, not assumptions.]]
-
-## Intro Project Analysis and Context
-
-[[LLM: Gather comprehensive information about the existing project. This section must be completed before proceeding with requirements.
-
-CRITICAL: Throughout this analysis, explicitly confirm your understanding with the user. For every assumption you make about the existing project, ask: "Based on my analysis, I understand that [assumption]. Is this correct?"
-
-Do not proceed with any recommendations until the user has validated your understanding of the existing system.]]
-
-### Existing Project Overview
-
-[[LLM: Check if document-project analysis was already performed. If yes, reference that output instead of re-analyzing.]]
-
-**Analysis Source**: [[LLM: Indicate one of the following:
-- Document-project output available at: {{path}}
-- IDE-based fresh analysis
-- User-provided information
-]]
-
-**Current Project State**: [[LLM: 
-- If document-project output exists: Extract summary from "High Level Architecture" and "Technical Summary" sections
-- Otherwise: Brief description of what the project currently does and its primary purpose
-]]
-
-### Available Documentation Analysis
-
-[[LLM: 
-If document-project was run:
-- Note: "Document-project analysis available - using existing technical documentation"
-- List key documents created by document-project
-- Skip the missing documentation check below
-
-Otherwise, check for existing documentation:
-]]
-
-**Available Documentation**:
-
-- [ ] Tech Stack Documentation [[LLM: If from document-project, check ✓]]
-- [ ] Source Tree/Architecture [[LLM: If from document-project, check ✓]]
-- [ ] Coding Standards [[LLM: If from document-project, may be partial]]
-- [ ] API Documentation [[LLM: If from document-project, check ✓]]
-- [ ] External API Documentation [[LLM: If from document-project, check ✓]]
-- [ ] UX/UI Guidelines [[LLM: May not be in document-project]]
-- [ ] Technical Debt Documentation [[LLM: If from document-project, check ✓]]
-- [ ] Other: \***\*\_\_\_\*\***
-
-[[LLM: 
-- If document-project was already run: "Using existing project analysis from document-project output."
-- If critical documentation is missing and no document-project: "I recommend running the document-project task first..."
-]]
-
-### Enhancement Scope Definition
-
-[[LLM: Work with user to clearly define what type of enhancement this is. This is critical for scoping and approach.]]
-
-**Enhancement Type**: [[LLM: Determine with user which applies]]
-
-- [ ] New Feature Addition
-- [ ] Major Feature Modification
-- [ ] Integration with New Systems
-- [ ] Performance/Scalability Improvements
-- [ ] UI/UX Overhaul
-- [ ] Technology Stack Upgrade
-- [ ] Bug Fix and Stability Improvements
-- [ ] Other: \***\*\_\_\_\*\***
-
-**Enhancement Description**: [[LLM: 2-3 sentences describing what the user wants to add or change]]
-
-**Impact Assessment**: [[LLM: Assess the scope of impact on existing codebase]]
-
-- [ ] Minimal Impact (isolated additions)
-- [ ] Moderate Impact (some existing code changes)
-- [ ] Significant Impact (substantial existing code changes)
-- [ ] Major Impact (architectural changes required)
-
-### Goals and Background Context
-
-#### Goals
-
-[[LLM: Bullet list of 1-line desired outcomes this enhancement will deliver if successful]]
-
-#### Background Context
-
-[[LLM: 1-2 short paragraphs explaining why this enhancement is needed, what problem it solves, and how it fits with the existing project]]
-
-### Change Log
-
-| Change | Date | Version | Description | Author |
-| ------ | ---- | ------- | ----------- | ------ |
-
-## Requirements
-
-[[LLM: Draft functional and non-functional requirements based on your validated understanding of the existing project. Before presenting requirements, confirm: "These requirements are based on my understanding of your existing system. Please review carefully and confirm they align with your project's reality." Then immediately execute tasks#advanced-elicitation display]]
-
-### Functional
-
-[[LLM: Each Requirement will be a bullet markdown with identifier starting with FR]]
-@{example: - FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.}
-
-### Non Functional
-
-[[LLM: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system]]
-@{example: - NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.}
-
-### Compatibility Requirements
-
-[[LLM: Critical for brownfield - what must remain compatible]]
-
-- CR1: [[LLM: Existing API compatibility requirements]]
-- CR2: [[LLM: Database schema compatibility requirements]]
-- CR3: [[LLM: UI/UX consistency requirements]]
-- CR4: [[LLM: Integration compatibility requirements]]
-
-^^CONDITION: has_ui^^
-
-## User Interface Enhancement Goals
-
-[[LLM: For UI changes, capture how they will integrate with existing UI patterns and design systems]]
-
-### Integration with Existing UI
-
-[[LLM: Describe how new UI elements will fit with existing design patterns, style guides, and component libraries]]
-
-### Modified/New Screens and Views
-
-[[LLM: List only the screens/views that will be modified or added]]
-
-### UI Consistency Requirements
-
-[[LLM: Specific requirements for maintaining visual and interaction consistency with existing application]]
-
-^^/CONDITION: has_ui^^
-
-## Technical Constraints and Integration Requirements
-
-[[LLM: This section replaces separate architecture documentation. Gather detailed technical constraints from existing project analysis.]]
-
-### Existing Technology Stack
-
-[[LLM: 
-If document-project output available:
-- Extract from "Actual Tech Stack" table in High Level Architecture section
-- Include version numbers and any noted constraints
-
-Otherwise, document the current technology stack:
-]]
-
-**Languages**: [[LLM: From document-project or fresh analysis]]
-**Frameworks**: [[LLM: From document-project or fresh analysis]]
-**Database**: [[LLM: From document-project or fresh analysis]]
-**Infrastructure**: [[LLM: From document-project or fresh analysis]]
-**External Dependencies**: [[LLM: From document-project "External Services" section or fresh analysis]]
-
-### Integration Approach
-
-[[LLM: Define how the enhancement will integrate with existing architecture]]
-
-**Database Integration Strategy**: [[LLM: How new features will interact with existing database]]
-**API Integration Strategy**: [[LLM: How new APIs will integrate with existing API structure]]
-**Frontend Integration Strategy**: [[LLM: How new UI components will integrate with existing frontend]]
-**Testing Integration Strategy**: [[LLM: How new tests will integrate with existing test suite]]
-
-### Code Organization and Standards
-
-[[LLM: Based on existing project analysis, define how new code will fit existing patterns]]
-
-**File Structure Approach**: [[LLM: How new files will fit existing project structure]]
-**Naming Conventions**: [[LLM: Existing naming conventions that must be followed]]
-**Coding Standards**: [[LLM: Existing coding standards and linting rules]]
-**Documentation Standards**: [[LLM: How new code documentation will match existing patterns]]
-
-### Deployment and Operations
-
-[[LLM: How the enhancement fits existing deployment pipeline]]
-
-**Build Process Integration**: [[LLM: How enhancement builds with existing process]]
-**Deployment Strategy**: [[LLM: How enhancement will be deployed alongside existing features]]
-**Monitoring and Logging**: [[LLM: How enhancement will integrate with existing monitoring]]
-**Configuration Management**: [[LLM: How new configuration will integrate with existing config]]
-
-### Risk Assessment and Mitigation
-
-[[LLM: 
-If document-project output available:
-- Reference "Technical Debt and Known Issues" section
-- Include "Workarounds and Gotchas" that might impact enhancement
-- Note any identified constraints from "Critical Technical Debt"
-
-Build risk assessment incorporating existing known issues:
-]]
-
-**Technical Risks**: [[LLM: Include risks from document-project + new enhancement risks]]
-**Integration Risks**: [[LLM: Reference integration constraints from document-project]]
-**Deployment Risks**: [[LLM: Include deployment gotchas from document-project]]
-**Mitigation Strategies**: [[LLM: Address both existing and new risks]]
-
-## Epic and Story Structure
-
-[[LLM: For brownfield projects, favor a single comprehensive epic unless the user is clearly requesting multiple unrelated enhancements. Before presenting the epic structure, confirm: "Based on my analysis of your existing project, I believe this enhancement should be structured as [single epic/multiple epics] because [rationale based on actual project analysis]. Does this align with your understanding of the work required?" Then present the epic structure and immediately execute tasks#advanced-elicitation display.]]
-
-### Epic Approach
-
-[[LLM: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features]]
-
-**Epic Structure Decision**: [[LLM: Single Epic or Multiple Epics with rationale]]
-
-## Epic 1: {{enhancement_title}}
-
-[[LLM: Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality]]
-
-**Epic Goal**: [[LLM: 2-3 sentences describing the complete enhancement objective and value]]
-
-**Integration Requirements**: [[LLM: Key integration points with existing system]]
-
-[[LLM: CRITICAL STORY SEQUENCING FOR BROWNFIELD:
-
-- Stories must ensure existing functionality remains intact
-- Each story should include verification that existing features still work
-- Stories should be sequenced to minimize risk to existing system
-- Include rollback considerations for each story
-- Focus on incremental integration rather than big-bang changes
-- Size stories for AI agent execution in existing codebase context
-- MANDATORY: Present the complete story sequence and ask: "This story sequence is designed to minimize risk to your existing system. Does this order make sense given your project's architecture and constraints?"
-- Stories must be logically sequential with clear dependencies identified
-- Each story must deliver value while maintaining system integrity]]
-
-<<REPEAT: story>>
-
-### Story 1.{{story_number}} {{story_title}}
-
-As a {{user_type}},
-I want {{action}},
-so that {{benefit}}.
-
-#### Acceptance Criteria
-
-[[LLM: Define criteria that include both new functionality and existing system integrity]]
-
-<<REPEAT: criteria>>
-
-- {{criterion number}}: {{criteria}}
-
-<</REPEAT>>
-
-#### Integration Verification
-
-[[LLM: Specific verification steps to ensure existing functionality remains intact]]
-
-- IV1: [[LLM: Existing functionality verification requirement]]
-- IV2: [[LLM: Integration point verification requirement]]
-- IV3: [[LLM: Performance impact verification requirement]]
-
-<</REPEAT>>

bmad-core/templates/brownfield-prd-tmpl.yaml

@@ -0,0 +1,280 @@
+template:
+  id: brownfield-prd-template-v2
+  name: Brownfield Enhancement PRD
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/prd.md
+    title: "{{project_name}} Brownfield Enhancement PRD"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: intro-analysis
+    title: Intro Project Analysis and Context
+    instruction: |
+      IMPORTANT - SCOPE ASSESSMENT REQUIRED:
+      
+      This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:
+      
+      1. **Assess Enhancement Complexity**: If this is a simple feature addition or bug fix that could be completed in 1-2 focused development sessions, STOP and recommend: "For simpler changes, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead. This full PRD process is designed for substantial enhancements that require architectural planning and multiple coordinated stories."
+      
+      2. **Project Context**: Determine if we're working in an IDE with the project already loaded or if the user needs to provide project information. If project files are available, analyze existing documentation in the docs folder. If insufficient documentation exists, recommend running the document-project task first.
+      
+      3. **Deep Assessment Requirement**: You MUST thoroughly analyze the existing project structure, patterns, and constraints before making ANY suggestions. Every recommendation must be grounded in actual project analysis, not assumptions.
+      
+      Gather comprehensive information about the existing project. This section must be completed before proceeding with requirements.
+      
+      CRITICAL: Throughout this analysis, explicitly confirm your understanding with the user. For every assumption you make about the existing project, ask: "Based on my analysis, I understand that [assumption]. Is this correct?"
+      
+      Do not proceed with any recommendations until the user has validated your understanding of the existing system.
+    sections:
+      - id: existing-project-overview
+        title: Existing Project Overview
+        instruction: Check if document-project analysis was already performed. If yes, reference that output instead of re-analyzing.
+        sections:
+          - id: analysis-source
+            title: Analysis Source
+            instruction: |
+              Indicate one of the following:
+              - Document-project output available at: {{path}}
+              - IDE-based fresh analysis
+              - User-provided information
+          - id: current-state
+            title: Current Project State
+            instruction: |
+              - If document-project output exists: Extract summary from "High Level Architecture" and "Technical Summary" sections
+              - Otherwise: Brief description of what the project currently does and its primary purpose
+      - id: documentation-analysis
+        title: Available Documentation Analysis
+        instruction: |
+          If document-project was run:
+          - Note: "Document-project analysis available - using existing technical documentation"
+          - List key documents created by document-project
+          - Skip the missing documentation check below
+          
+          Otherwise, check for existing documentation:
+        sections:
+          - id: available-docs
+            title: Available Documentation
+            type: checklist
+            items:
+              - Tech Stack Documentation [[LLM: If from document-project, check ✓]]
+              - Source Tree/Architecture [[LLM: If from document-project, check ✓]]
+              - Coding Standards [[LLM: If from document-project, may be partial]]
+              - API Documentation [[LLM: If from document-project, check ✓]]
+              - External API Documentation [[LLM: If from document-project, check ✓]]
+              - UX/UI Guidelines [[LLM: May not be in document-project]]
+              - Technical Debt Documentation [[LLM: If from document-project, check ✓]]
+              - "Other: {{other_docs}}"
+            instruction: |
+              - If document-project was already run: "Using existing project analysis from document-project output."
+              - If critical documentation is missing and no document-project: "I recommend running the document-project task first..."
+      - id: enhancement-scope
+        title: Enhancement Scope Definition
+        instruction: Work with user to clearly define what type of enhancement this is. This is critical for scoping and approach.
+        sections:
+          - id: enhancement-type
+            title: Enhancement Type
+            type: checklist
+            instruction: Determine with user which applies
+            items:
+              - New Feature Addition
+              - Major Feature Modification
+              - Integration with New Systems
+              - Performance/Scalability Improvements
+              - UI/UX Overhaul
+              - Technology Stack Upgrade
+              - Bug Fix and Stability Improvements
+              - "Other: {{other_type}}"
+          - id: enhancement-description
+            title: Enhancement Description
+            instruction: 2-3 sentences describing what the user wants to add or change
+          - id: impact-assessment
+            title: Impact Assessment
+            type: checklist
+            instruction: Assess the scope of impact on existing codebase
+            items:
+              - Minimal Impact (isolated additions)
+              - Moderate Impact (some existing code changes)
+              - Significant Impact (substantial existing code changes)
+              - Major Impact (architectural changes required)
+      - id: goals-context
+        title: Goals and Background Context
+        sections:
+          - id: goals
+            title: Goals
+            type: bullet-list
+            instruction: Bullet list of 1-line desired outcomes this enhancement will deliver if successful
+          - id: background
+            title: Background Context
+            type: paragraphs
+            instruction: 1-2 short paragraphs explaining why this enhancement is needed, what problem it solves, and how it fits with the existing project
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Change, Date, Version, Description, Author]
+
+  - id: requirements
+    title: Requirements
+    instruction: |
+      Draft functional and non-functional requirements based on your validated understanding of the existing project. Before presenting requirements, confirm: "These requirements are based on my understanding of your existing system. Please review carefully and confirm they align with your project's reality."
+    elicit: true
+    sections:
+      - id: functional
+        title: Functional
+        type: numbered-list
+        prefix: FR
+        instruction: Each Requirement will be a bullet markdown with identifier starting with FR
+        examples:
+          - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality."
+      - id: non-functional
+        title: Non Functional
+        type: numbered-list
+        prefix: NFR
+        instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system
+        examples:
+          - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%."
+      - id: compatibility
+        title: Compatibility Requirements
+        instruction: Critical for brownfield - what must remain compatible
+        type: numbered-list
+        prefix: CR
+        template: "{{requirement}}: {{description}}"
+        items:
+          - id: cr1
+            template: "CR1: {{existing_api_compatibility}}"
+          - id: cr2
+            template: "CR2: {{database_schema_compatibility}}"
+          - id: cr3
+            template: "CR3: {{ui_ux_consistency}}"
+          - id: cr4
+            template: "CR4: {{integration_compatibility}}"
+
+  - id: ui-enhancement-goals
+    title: User Interface Enhancement Goals
+    condition: Enhancement includes UI changes
+    instruction: For UI changes, capture how they will integrate with existing UI patterns and design systems
+    sections:
+      - id: existing-ui-integration
+        title: Integration with Existing UI
+        instruction: Describe how new UI elements will fit with existing design patterns, style guides, and component libraries
+      - id: modified-screens
+        title: Modified/New Screens and Views
+        instruction: List only the screens/views that will be modified or added
+      - id: ui-consistency
+        title: UI Consistency Requirements
+        instruction: Specific requirements for maintaining visual and interaction consistency with existing application
+
+  - id: technical-constraints
+    title: Technical Constraints and Integration Requirements
+    instruction: This section replaces separate architecture documentation. Gather detailed technical constraints from existing project analysis.
+    sections:
+      - id: existing-tech-stack
+        title: Existing Technology Stack
+        instruction: |
+          If document-project output available:
+          - Extract from "Actual Tech Stack" table in High Level Architecture section
+          - Include version numbers and any noted constraints
+          
+          Otherwise, document the current technology stack:
+        template: |
+          **Languages**: {{languages}}
+          **Frameworks**: {{frameworks}}
+          **Database**: {{database}}
+          **Infrastructure**: {{infrastructure}}
+          **External Dependencies**: {{external_dependencies}}
+      - id: integration-approach
+        title: Integration Approach
+        instruction: Define how the enhancement will integrate with existing architecture
+        template: |
+          **Database Integration Strategy**: {{database_integration}}
+          **API Integration Strategy**: {{api_integration}}
+          **Frontend Integration Strategy**: {{frontend_integration}}
+          **Testing Integration Strategy**: {{testing_integration}}
+      - id: code-organization
+        title: Code Organization and Standards
+        instruction: Based on existing project analysis, define how new code will fit existing patterns
+        template: |
+          **File Structure Approach**: {{file_structure}}
+          **Naming Conventions**: {{naming_conventions}}
+          **Coding Standards**: {{coding_standards}}
+          **Documentation Standards**: {{documentation_standards}}
+      - id: deployment-operations
+        title: Deployment and Operations
+        instruction: How the enhancement fits existing deployment pipeline
+        template: |
+          **Build Process Integration**: {{build_integration}}
+          **Deployment Strategy**: {{deployment_strategy}}
+          **Monitoring and Logging**: {{monitoring_logging}}
+          **Configuration Management**: {{config_management}}
+      - id: risk-assessment
+        title: Risk Assessment and Mitigation
+        instruction: |
+          If document-project output available:
+          - Reference "Technical Debt and Known Issues" section
+          - Include "Workarounds and Gotchas" that might impact enhancement
+          - Note any identified constraints from "Critical Technical Debt"
+          
+          Build risk assessment incorporating existing known issues:
+        template: |
+          **Technical Risks**: {{technical_risks}}
+          **Integration Risks**: {{integration_risks}}
+          **Deployment Risks**: {{deployment_risks}}
+          **Mitigation Strategies**: {{mitigation_strategies}}
+
+  - id: epic-structure
+    title: Epic and Story Structure
+    instruction: |
+      For brownfield projects, favor a single comprehensive epic unless the user is clearly requesting multiple unrelated enhancements. Before presenting the epic structure, confirm: "Based on my analysis of your existing project, I believe this enhancement should be structured as [single epic/multiple epics] because [rationale based on actual project analysis]. Does this align with your understanding of the work required?"
+    elicit: true
+    sections:
+      - id: epic-approach
+        title: Epic Approach
+        instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features
+        template: "**Epic Structure Decision**: {{epic_decision}} with rationale"
+
+  - id: epic-details
+    title: "Epic 1: {{enhancement_title}}"
+    instruction: |
+      Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality
+      
+      CRITICAL STORY SEQUENCING FOR BROWNFIELD:
+      - Stories must ensure existing functionality remains intact
+      - Each story should include verification that existing features still work
+      - Stories should be sequenced to minimize risk to existing system
+      - Include rollback considerations for each story
+      - Focus on incremental integration rather than big-bang changes
+      - Size stories for AI agent execution in existing codebase context
+      - MANDATORY: Present the complete story sequence and ask: "This story sequence is designed to minimize risk to your existing system. Does this order make sense given your project's architecture and constraints?"
+      - Stories must be logically sequential with clear dependencies identified
+      - Each story must deliver value while maintaining system integrity
+    template: |
+      **Epic Goal**: {{epic_goal}}
+      
+      **Integration Requirements**: {{integration_requirements}}
+    sections:
+      - id: story
+        title: "Story 1.{{story_number}} {{story_title}}"
+        repeatable: true
+        template: |
+          As a {{user_type}},
+          I want {{action}},
+          so that {{benefit}}.
+        sections:
+          - id: acceptance-criteria
+            title: Acceptance Criteria
+            type: numbered-list
+            instruction: Define criteria that include both new functionality and existing system integrity
+            item_template: "{{criterion_number}}: {{criteria}}"
+          - id: integration-verification
+            title: Integration Verification
+            instruction: Specific verification steps to ensure existing functionality remains intact
+            type: numbered-list
+            prefix: IV
+            items:
+              - template: "IV1: {{existing_functionality_verification}}"
+              - template: "IV2: {{integration_point_verification}}"
+              - template: "IV3: {{performance_impact_verification}}"

bmad-core/templates/competitor-analysis-tmpl.md

@@ -1,291 +0,0 @@
-# Competitive Analysis Report: {{Project/Product Name}}
-
-[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
-
-[[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
-
-## Executive Summary
-
-{{Provide high-level competitive insights, main threats and opportunities, and recommended strategic actions. Write this section LAST after completing all analysis.}}
-
-## Analysis Scope & Methodology
-
-### Analysis Purpose
-
-{{Define the primary purpose:
-
-- New market entry assessment
-- Product positioning strategy
-- Feature gap analysis
-- Pricing strategy development
-- Partnership/acquisition targets
-- Competitive threat assessment}}
-
-### Competitor Categories Analyzed
-
-{{List categories included:
-
-- Direct Competitors: Same product/service, same target market
-- Indirect Competitors: Different product, same need/problem
-- Potential Competitors: Could enter market easily
-- Substitute Products: Alternative solutions
-- Aspirational Competitors: Best-in-class examples}}
-
-### Research Methodology
-
-{{Describe approach:
-
-- Information sources used
-- Analysis timeframe
-- Confidence levels
-- Limitations}}
-
-## Competitive Landscape Overview
-
-### Market Structure
-
-{{Describe the competitive environment:
-
-- Number of active competitors
-- Market concentration (fragmented/consolidated)
-- Competitive dynamics
-- Recent market entries/exits}}
-
-### Competitor Prioritization Matrix
-
-[[LLM: Help categorize competitors by market share and strategic threat level]]
-
-{{Create a 2x2 matrix:
-
-- Priority 1 (Core Competitors): High Market Share + High Threat
-- Priority 2 (Emerging Threats): Low Market Share + High Threat
-- Priority 3 (Established Players): High Market Share + Low Threat
-- Priority 4 (Monitor Only): Low Market Share + Low Threat}}
-
-## Individual Competitor Profiles
-
-[[LLM: Create detailed profiles for each Priority 1 and Priority 2 competitor. For Priority 3 and 4, create condensed profiles.]]
-
-### {{Competitor Name}} - Priority {{1/2/3/4}}
-
-#### Company Overview
-
-- **Founded:** {{Year, founders}}
-- **Headquarters:** {{Location}}
-- **Company Size:** {{Employees, revenue if known}}
-- **Funding:** {{Total raised, key investors}}
-- **Leadership:** {{Key executives}}
-
-#### Business Model & Strategy
-
-- **Revenue Model:** {{How they make money}}
-- **Target Market:** {{Primary customer segments}}
-- **Value Proposition:** {{Core value promise}}
-- **Go-to-Market Strategy:** {{Sales and marketing approach}}
-- **Strategic Focus:** {{Current priorities}}
-
-#### Product/Service Analysis
-
-- **Core Offerings:** {{Main products/services}}
-- **Key Features:** {{Standout capabilities}}
-- **User Experience:** {{UX strengths/weaknesses}}
-- **Technology Stack:** {{If relevant/known}}
-- **Pricing:** {{Model and price points}}
-
-#### Strengths & Weaknesses
-
-**Strengths:**
-
-- {{Strength 1}}
-- {{Strength 2}}
-- {{Strength 3}}
-
-**Weaknesses:**
-
-- {{Weakness 1}}
-- {{Weakness 2}}
-- {{Weakness 3}}
-
-#### Market Position & Performance
-
-- **Market Share:** {{Estimate if available}}
-- **Customer Base:** {{Size, notable clients}}
-- **Growth Trajectory:** {{Trending up/down/stable}}
-- **Recent Developments:** {{Key news, releases}}
-
-<<REPEAT for each priority competitor>>
-
-## Comparative Analysis
-
-### Feature Comparison Matrix
-
-[[LLM: Create a detailed comparison table of key features across competitors]]
-
-| Feature Category            | {{Your Company}}    | {{Competitor 1}}    | {{Competitor 2}}    | {{Competitor 3}}    |
-| --------------------------- | ------------------- | ------------------- | ------------------- | ------------------- |
-| **Core Functionality**      |
-| Feature A                   | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     |
-| Feature B                   | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     | {{✓/✗/Partial}}     |
-| **User Experience**         |
-| Mobile App                  | {{Rating/Status}}   | {{Rating/Status}}   | {{Rating/Status}}   | {{Rating/Status}}   |
-| Onboarding Time             | {{Time}}            | {{Time}}            | {{Time}}            | {{Time}}            |
-| **Integration & Ecosystem** |
-| API Availability            | {{Yes/No/Limited}}  | {{Yes/No/Limited}}  | {{Yes/No/Limited}}  | {{Yes/No/Limited}}  |
-| Third-party Integrations    | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} |
-| **Pricing & Plans**         |
-| Starting Price              | {{$X}}              | {{$X}}              | {{$X}}              | {{$X}}              |
-| Free Tier                   | {{Yes/No}}          | {{Yes/No}}          | {{Yes/No}}          | {{Yes/No}}          |
-
-### SWOT Comparison
-
-[[LLM: Create SWOT analysis for your solution vs. top competitors]]
-
-#### Your Solution
-
-- **Strengths:** {{List key strengths}}
-- **Weaknesses:** {{List key weaknesses}}
-- **Opportunities:** {{List opportunities}}
-- **Threats:** {{List threats}}
-
-#### vs. {{Main Competitor}}
-
-- **Competitive Advantages:** {{Where you're stronger}}
-- **Competitive Disadvantages:** {{Where they're stronger}}
-- **Differentiation Opportunities:** {{How to stand out}}
-
-### Positioning Map
-
-[[LLM: Describe competitor positions on key dimensions]]
-
-{{Create a positioning description using 2 key dimensions relevant to the market, such as:
-
-- Price vs. Features
-- Ease of Use vs. Power
-- Specialization vs. Breadth
-- Self-Serve vs. High-Touch}}
-
-## Strategic Analysis
-
-### Competitive Advantages Assessment
-
-#### Sustainable Advantages
-
-{{Identify moats and defensible positions:
-
-- Network effects
-- Switching costs
-- Brand strength
-- Technology barriers
-- Regulatory advantages}}
-
-#### Vulnerable Points
-
-{{Where competitors could be challenged:
-
-- Weak customer segments
-- Missing features
-- Poor user experience
-- High prices
-- Limited geographic presence}}
-
-### Blue Ocean Opportunities
-
-[[LLM: Identify uncontested market spaces]]
-
-{{List opportunities to create new market space:
-
-- Underserved segments
-- Unaddressed use cases
-- New business models
-- Geographic expansion
-- Different value propositions}}
-
-## Strategic Recommendations
-
-### Differentiation Strategy
-
-{{How to position against competitors:
-
-- Unique value propositions to emphasize
-- Features to prioritize
-- Segments to target
-- Messaging and positioning}}
-
-### Competitive Response Planning
-
-#### Offensive Strategies
-
-{{How to gain market share:
-
-- Target competitor weaknesses
-- Win competitive deals
-- Capture their customers}}
-
-#### Defensive Strategies
-
-{{How to protect your position:
-
-- Strengthen vulnerable areas
-- Build switching costs
-- Deepen customer relationships}}
-
-### Partnership & Ecosystem Strategy
-
-{{Potential collaboration opportunities:
-
-- Complementary players
-- Channel partners
-- Technology integrations
-- Strategic alliances}}
-
-## Monitoring & Intelligence Plan
-
-### Key Competitors to Track
-
-{{Priority list with rationale}}
-
-### Monitoring Metrics
-
-{{What to track:
-
-- Product updates
-- Pricing changes
-- Customer wins/losses
-- Funding/M&A activity
-- Market messaging}}
-
-### Intelligence Sources
-
-{{Where to gather ongoing intelligence:
-
-- Company websites/blogs
-- Customer reviews
-- Industry reports
-- Social media
-- Patent filings}}
-
-### Update Cadence
-
-{{Recommended review schedule:
-
-- Weekly: {{What to check}}
-- Monthly: {{What to review}}
-- Quarterly: {{Deep analysis}}}}
-
----
-
-[[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis:
-
-**Competitive Analysis Elicitation Actions** 0. Deep dive on a specific competitor's strategy
-
-1. Analyze competitive dynamics in a specific segment
-2. War game competitive responses to your moves
-3. Explore partnership vs. competition scenarios
-4. Stress test differentiation claims
-5. Analyze disruption potential (yours or theirs)
-6. Compare to competition in adjacent markets
-7. Generate win/loss analysis insights
-8. If only we had known about [competitor X's plan]...
-9. Proceed to next section
-
-These replace the standard elicitation options when working on competitive analysis documents.]]

bmad-core/templates/competitor-analysis-tmpl.yaml

@@ -0,0 +1,293 @@
+template:
+  id: competitor-analysis-template-v2
+  name: Competitive Analysis Report
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/competitor-analysis.md
+    title: "Competitive Analysis Report: {{project_product_name}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Competitive Analysis Elicitation Actions"
+    options:
+      - "Deep dive on a specific competitor's strategy"
+      - "Analyze competitive dynamics in a specific segment"
+      - "War game competitive responses to your moves"
+      - "Explore partnership vs. competition scenarios"
+      - "Stress test differentiation claims"
+      - "Analyze disruption potential (yours or theirs)"
+      - "Compare to competition in adjacent markets"
+      - "Generate win/loss analysis insights"
+      - "If only we had known about [competitor X's plan]..."
+      - "Proceed to next section"
+
+sections:
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide high-level competitive insights, main threats and opportunities, and recommended strategic actions. Write this section LAST after completing all analysis.
+
+  - id: analysis-scope
+    title: Analysis Scope & Methodology
+    instruction: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.
+    sections:
+      - id: analysis-purpose
+        title: Analysis Purpose
+        instruction: |
+          Define the primary purpose:
+          - New market entry assessment
+          - Product positioning strategy
+          - Feature gap analysis
+          - Pricing strategy development
+          - Partnership/acquisition targets
+          - Competitive threat assessment
+      - id: competitor-categories
+        title: Competitor Categories Analyzed
+        instruction: |
+          List categories included:
+          - Direct Competitors: Same product/service, same target market
+          - Indirect Competitors: Different product, same need/problem
+          - Potential Competitors: Could enter market easily
+          - Substitute Products: Alternative solutions
+          - Aspirational Competitors: Best-in-class examples
+      - id: research-methodology
+        title: Research Methodology
+        instruction: |
+          Describe approach:
+          - Information sources used
+          - Analysis timeframe
+          - Confidence levels
+          - Limitations
+
+  - id: competitive-landscape
+    title: Competitive Landscape Overview
+    sections:
+      - id: market-structure
+        title: Market Structure
+        instruction: |
+          Describe the competitive environment:
+          - Number of active competitors
+          - Market concentration (fragmented/consolidated)
+          - Competitive dynamics
+          - Recent market entries/exits
+      - id: prioritization-matrix
+        title: Competitor Prioritization Matrix
+        instruction: |
+          Help categorize competitors by market share and strategic threat level
+          
+          Create a 2x2 matrix:
+          - Priority 1 (Core Competitors): High Market Share + High Threat
+          - Priority 2 (Emerging Threats): Low Market Share + High Threat
+          - Priority 3 (Established Players): High Market Share + Low Threat
+          - Priority 4 (Monitor Only): Low Market Share + Low Threat
+
+  - id: competitor-profiles
+    title: Individual Competitor Profiles
+    instruction: Create detailed profiles for each Priority 1 and Priority 2 competitor. For Priority 3 and 4, create condensed profiles.
+    repeatable: true
+    sections:
+      - id: competitor
+        title: "{{competitor_name}} - Priority {{priority_level}}"
+        sections:
+          - id: company-overview
+            title: Company Overview
+            template: |
+              - **Founded:** {{year_founders}}
+              - **Headquarters:** {{location}}
+              - **Company Size:** {{employees_revenue}}
+              - **Funding:** {{total_raised_investors}}
+              - **Leadership:** {{key_executives}}
+          - id: business-model
+            title: Business Model & Strategy
+            template: |
+              - **Revenue Model:** {{revenue_model}}
+              - **Target Market:** {{customer_segments}}
+              - **Value Proposition:** {{value_promise}}
+              - **Go-to-Market Strategy:** {{gtm_approach}}
+              - **Strategic Focus:** {{current_priorities}}
+          - id: product-analysis
+            title: Product/Service Analysis
+            template: |
+              - **Core Offerings:** {{main_products}}
+              - **Key Features:** {{standout_capabilities}}
+              - **User Experience:** {{ux_assessment}}
+              - **Technology Stack:** {{tech_stack}}
+              - **Pricing:** {{pricing_model}}
+          - id: strengths-weaknesses
+            title: Strengths & Weaknesses
+            sections:
+              - id: strengths
+                title: Strengths
+                type: bullet-list
+                template: "- {{strength}}"
+              - id: weaknesses
+                title: Weaknesses
+                type: bullet-list
+                template: "- {{weakness}}"
+          - id: market-position
+            title: Market Position & Performance
+            template: |
+              - **Market Share:** {{market_share_estimate}}
+              - **Customer Base:** {{customer_size_notables}}
+              - **Growth Trajectory:** {{growth_trend}}
+              - **Recent Developments:** {{key_news}}
+
+  - id: comparative-analysis
+    title: Comparative Analysis
+    sections:
+      - id: feature-comparison
+        title: Feature Comparison Matrix
+        instruction: Create a detailed comparison table of key features across competitors
+        type: table
+        columns: ["Feature Category", "{{your_company}}", "{{competitor_1}}", "{{competitor_2}}", "{{competitor_3}}"]
+        rows:
+          - category: "Core Functionality"
+            items:
+              - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
+              - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
+          - category: "User Experience"
+            items:
+              - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"]
+              - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"]
+          - category: "Integration & Ecosystem"
+            items:
+              - ["API Availability", "{{availability}}", "{{availability}}", "{{availability}}", "{{availability}}"]
+              - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"]
+          - category: "Pricing & Plans"
+            items:
+              - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"]
+              - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"]
+      - id: swot-comparison
+        title: SWOT Comparison
+        instruction: Create SWOT analysis for your solution vs. top competitors
+        sections:
+          - id: your-solution
+            title: Your Solution
+            template: |
+              - **Strengths:** {{strengths}}
+              - **Weaknesses:** {{weaknesses}}
+              - **Opportunities:** {{opportunities}}
+              - **Threats:** {{threats}}
+          - id: vs-competitor
+            title: "vs. {{main_competitor}}"
+            template: |
+              - **Competitive Advantages:** {{your_advantages}}
+              - **Competitive Disadvantages:** {{their_advantages}}
+              - **Differentiation Opportunities:** {{differentiation}}
+      - id: positioning-map
+        title: Positioning Map
+        instruction: |
+          Describe competitor positions on key dimensions
+          
+          Create a positioning description using 2 key dimensions relevant to the market, such as:
+          - Price vs. Features
+          - Ease of Use vs. Power
+          - Specialization vs. Breadth
+          - Self-Serve vs. High-Touch
+
+  - id: strategic-analysis
+    title: Strategic Analysis
+    sections:
+      - id: competitive-advantages
+        title: Competitive Advantages Assessment
+        sections:
+          - id: sustainable-advantages
+            title: Sustainable Advantages
+            instruction: |
+              Identify moats and defensible positions:
+              - Network effects
+              - Switching costs
+              - Brand strength
+              - Technology barriers
+              - Regulatory advantages
+          - id: vulnerable-points
+            title: Vulnerable Points
+            instruction: |
+              Where competitors could be challenged:
+              - Weak customer segments
+              - Missing features
+              - Poor user experience
+              - High prices
+              - Limited geographic presence
+      - id: blue-ocean
+        title: Blue Ocean Opportunities
+        instruction: |
+          Identify uncontested market spaces
+          
+          List opportunities to create new market space:
+          - Underserved segments
+          - Unaddressed use cases
+          - New business models
+          - Geographic expansion
+          - Different value propositions
+
+  - id: strategic-recommendations
+    title: Strategic Recommendations
+    sections:
+      - id: differentiation-strategy
+        title: Differentiation Strategy
+        instruction: |
+          How to position against competitors:
+          - Unique value propositions to emphasize
+          - Features to prioritize
+          - Segments to target
+          - Messaging and positioning
+      - id: competitive-response
+        title: Competitive Response Planning
+        sections:
+          - id: offensive-strategies
+            title: Offensive Strategies
+            instruction: |
+              How to gain market share:
+              - Target competitor weaknesses
+              - Win competitive deals
+              - Capture their customers
+          - id: defensive-strategies
+            title: Defensive Strategies
+            instruction: |
+              How to protect your position:
+              - Strengthen vulnerable areas
+              - Build switching costs
+              - Deepen customer relationships
+      - id: partnership-ecosystem
+        title: Partnership & Ecosystem Strategy
+        instruction: |
+          Potential collaboration opportunities:
+          - Complementary players
+          - Channel partners
+          - Technology integrations
+          - Strategic alliances
+
+  - id: monitoring-plan
+    title: Monitoring & Intelligence Plan
+    sections:
+      - id: key-competitors
+        title: Key Competitors to Track
+        instruction: Priority list with rationale
+      - id: monitoring-metrics
+        title: Monitoring Metrics
+        instruction: |
+          What to track:
+          - Product updates
+          - Pricing changes
+          - Customer wins/losses
+          - Funding/M&A activity
+          - Market messaging
+      - id: intelligence-sources
+        title: Intelligence Sources
+        instruction: |
+          Where to gather ongoing intelligence:
+          - Company websites/blogs
+          - Customer reviews
+          - Industry reports
+          - Social media
+          - Patent filings
+      - id: update-cadence
+        title: Update Cadence
+        instruction: |
+          Recommended review schedule:
+          - Weekly: {{weekly_items}}
+          - Monthly: {{monthly_items}}
+          - Quarterly: {{quarterly_analysis}}

bmad-core/templates/front-end-architecture-tmpl.md

@@ -1,175 +0,0 @@
-# {{Project Name}} Frontend Architecture Document
-
-[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
-
-[[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
-
-## Template and Framework Selection
-
-[[LLM: Before proceeding with frontend architecture design, check if the project is using a frontend starter template or existing codebase:
-
-1. Review the PRD, main architecture document, and brainstorming brief for mentions of:
-
-   - Frontend starter templates (e.g., Create React App, Next.js, Vite, Vue CLI, Angular CLI, etc.)
-   - UI kit or component library starters
-   - Existing frontend projects being used as a foundation
-   - Admin dashboard templates or other specialized starters
-   - Design system implementations
-
-2. If a frontend starter template or existing project is mentioned:
-
-   - Ask the user to provide access via one of these methods:
-     - Link to the starter template documentation
-     - Upload/attach the project files (for small projects)
-     - Share a link to the project repository
-   - Analyze the starter/existing project to understand:
-     - Pre-installed dependencies and versions
-     - Folder structure and file organization
-     - Built-in components and utilities
-     - Styling approach (CSS modules, styled-components, Tailwind, etc.)
-     - State management setup (if any)
-     - Routing configuration
-     - Testing setup and patterns
-     - Build and development scripts
-
-- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
-
-3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
-
-   - Based on the framework choice, suggest appropriate starters:
-     - React: Create React App, Next.js, Vite + React
-     - Vue: Vue CLI, Nuxt.js, Vite + Vue
-     - Angular: Angular CLI
-     - Or suggest popular UI templates if applicable
-   - Explain benefits specific to frontend development
-
-4. If the user confirms no starter template will be used:
-   - Note that all tooling, bundling, and configuration will need manual setup
-   - Proceed with frontend architecture from scratch
-
-Document the starter template decision and any constraints it imposes before proceeding.]]
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Frontend Tech Stack
-
-[[LLM: Extract from main architecture's Technology Stack Table. This section MUST remain synchronized with the main architecture document. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Technology Stack Table
-
-| Category              | Technology           | Version     | Purpose     | Rationale      |
-| :-------------------- | :------------------- | :---------- | :---------- | :------------- |
-| **Framework**         | {{framework}}        | {{version}} | {{purpose}} | {{why_chosen}} |
-| **UI Library**        | {{ui_library}}       | {{version}} | {{purpose}} | {{why_chosen}} |
-| **State Management**  | {{state_management}} | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Routing**           | {{routing_library}}  | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Build Tool**        | {{build_tool}}       | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Styling**           | {{styling_solution}} | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Testing**           | {{test_framework}}   | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Component Library** | {{component_lib}}    | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Form Handling**     | {{form_library}}     | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Animation**         | {{animation_lib}}    | {{version}} | {{purpose}} | {{why_chosen}} |
-| **Dev Tools**         | {{dev_tools}}        | {{version}} | {{purpose}} | {{why_chosen}} |
-
-[[LLM: Fill in appropriate technology choices based on the selected framework and project requirements.]]
-
-## Project Structure
-
-[[LLM: Define exact directory structure for AI tools based on the chosen framework. Be specific about where each type of file goes. Generate a structure that follows the framework's best practices and conventions. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-## Component Standards
-
-[[LLM: Define exact patterns for component creation based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Component Template
-
-[[LLM: Generate a minimal but complete component template following the framework's best practices. Include TypeScript types, proper imports, and basic structure.]]
-
-### Naming Conventions
-
-[[LLM: Provide naming conventions specific to the chosen framework for components, files, services, state management, and other architectural elements.]]
-
-## State Management
-
-[[LLM: Define state management patterns based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Store Structure
-
-[[LLM: Generate the state management directory structure appropriate for the chosen framework and selected state management solution.]]
-
-### State Management Template
-
-[[LLM: Provide a basic state management template/example following the framework's recommended patterns. Include TypeScript types and common operations like setting, updating, and clearing state.]]
-
-## API Integration
-
-[[LLM: Define API service patterns based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Service Template
-
-[[LLM: Provide an API service template that follows the framework's conventions. Include proper TypeScript types, error handling, and async patterns.]]
-
-### API Client Configuration
-
-[[LLM: Show how to configure the HTTP client for the chosen framework, including authentication interceptors/middleware and error handling.]]
-
-## Routing
-
-[[LLM: Define routing structure and patterns based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Route Configuration
-
-[[LLM: Provide routing configuration appropriate for the chosen framework. Include protected route patterns, lazy loading where applicable, and authentication guards/middleware.]]
-
-## Styling Guidelines
-
-[[LLM: Define styling approach based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Styling Approach
-
-[[LLM: Describe the styling methodology appropriate for the chosen framework (CSS Modules, Styled Components, Tailwind, etc.) and provide basic patterns.]]
-
-### Global Theme Variables
-
-[[LLM: Provide a CSS custom properties (CSS variables) theme system that works across all frameworks. Include colors, spacing, typography, shadows, and dark mode support.]]
-
-## Testing Requirements
-
-[[LLM: Define minimal testing requirements based on the chosen framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Component Test Template
-
-[[LLM: Provide a basic component test template using the framework's recommended testing library. Include examples of rendering tests, user interaction tests, and mocking.]]
-
-### Testing Best Practices
-
-1. **Unit Tests**: Test individual components in isolation
-2. **Integration Tests**: Test component interactions
-3. **E2E Tests**: Test critical user flows (using Cypress/Playwright)
-4. **Coverage Goals**: Aim for 80% code coverage
-5. **Test Structure**: Arrange-Act-Assert pattern
-6. **Mock External Dependencies**: API calls, routing, state management
-
-## Environment Configuration
-
-[[LLM: List required environment variables based on the chosen framework. Show the appropriate format and naming conventions for the framework. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-## Frontend Developer Standards
-
-### Critical Coding Rules
-
-[[LLM: List essential rules that prevent common AI mistakes, including both universal rules and framework-specific ones. After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Quick Reference
-
-[[LLM: Create a framework-specific cheat sheet with:
-
-- Common commands (dev server, build, test)
-- Key import patterns
-- File naming conventions
-- Project-specific patterns and utilities]]

bmad-core/templates/front-end-architecture-tmpl.yaml

@@ -0,0 +1,206 @@
+template:
+  id: frontend-architecture-template-v2
+  name: Frontend Architecture Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/ui-architecture.md
+    title: "{{project_name}} Frontend Architecture Document"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: template-framework-selection
+    title: Template and Framework Selection
+    instruction: |
+      Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.
+      
+      Before proceeding with frontend architecture design, check if the project is using a frontend starter template or existing codebase:
+      
+      1. Review the PRD, main architecture document, and brainstorming brief for mentions of:
+         - Frontend starter templates (e.g., Create React App, Next.js, Vite, Vue CLI, Angular CLI, etc.)
+         - UI kit or component library starters
+         - Existing frontend projects being used as a foundation
+         - Admin dashboard templates or other specialized starters
+         - Design system implementations
+      
+      2. If a frontend starter template or existing project is mentioned:
+         - Ask the user to provide access via one of these methods:
+           - Link to the starter template documentation
+           - Upload/attach the project files (for small projects)
+           - Share a link to the project repository
+         - Analyze the starter/existing project to understand:
+           - Pre-installed dependencies and versions
+           - Folder structure and file organization
+           - Built-in components and utilities
+           - Styling approach (CSS modules, styled-components, Tailwind, etc.)
+           - State management setup (if any)
+           - Routing configuration
+           - Testing setup and patterns
+           - Build and development scripts
+         - Use this analysis to ensure your frontend architecture aligns with the starter's patterns
+      
+      3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
+         - Based on the framework choice, suggest appropriate starters:
+           - React: Create React App, Next.js, Vite + React
+           - Vue: Vue CLI, Nuxt.js, Vite + Vue
+           - Angular: Angular CLI
+           - Or suggest popular UI templates if applicable
+         - Explain benefits specific to frontend development
+      
+      4. If the user confirms no starter template will be used:
+         - Note that all tooling, bundling, and configuration will need manual setup
+         - Proceed with frontend architecture from scratch
+      
+      Document the starter template decision and any constraints it imposes before proceeding.
+    sections:
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: frontend-tech-stack
+    title: Frontend Tech Stack
+    instruction: Extract from main architecture's Technology Stack Table. This section MUST remain synchronized with the main architecture document.
+    elicit: true
+    sections:
+      - id: tech-stack-table
+        title: Technology Stack Table
+        type: table
+        columns: [Category, Technology, Version, Purpose, Rationale]
+        instruction: Fill in appropriate technology choices based on the selected framework and project requirements.
+        rows:
+          - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["State Management", "{{state_management}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Component Library", "{{component_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+
+  - id: project-structure
+    title: Project Structure
+    instruction: Define exact directory structure for AI tools based on the chosen framework. Be specific about where each type of file goes. Generate a structure that follows the framework's best practices and conventions.
+    elicit: true
+    type: code
+    language: plaintext
+
+  - id: component-standards
+    title: Component Standards
+    instruction: Define exact patterns for component creation based on the chosen framework.
+    elicit: true
+    sections:
+      - id: component-template
+        title: Component Template
+        instruction: Generate a minimal but complete component template following the framework's best practices. Include TypeScript types, proper imports, and basic structure.
+        type: code
+        language: typescript
+      - id: naming-conventions
+        title: Naming Conventions
+        instruction: Provide naming conventions specific to the chosen framework for components, files, services, state management, and other architectural elements.
+
+  - id: state-management
+    title: State Management
+    instruction: Define state management patterns based on the chosen framework.
+    elicit: true
+    sections:
+      - id: store-structure
+        title: Store Structure
+        instruction: Generate the state management directory structure appropriate for the chosen framework and selected state management solution.
+        type: code
+        language: plaintext
+      - id: state-template
+        title: State Management Template
+        instruction: Provide a basic state management template/example following the framework's recommended patterns. Include TypeScript types and common operations like setting, updating, and clearing state.
+        type: code
+        language: typescript
+
+  - id: api-integration
+    title: API Integration
+    instruction: Define API service patterns based on the chosen framework.
+    elicit: true
+    sections:
+      - id: service-template
+        title: Service Template
+        instruction: Provide an API service template that follows the framework's conventions. Include proper TypeScript types, error handling, and async patterns.
+        type: code
+        language: typescript
+      - id: api-client-config
+        title: API Client Configuration
+        instruction: Show how to configure the HTTP client for the chosen framework, including authentication interceptors/middleware and error handling.
+        type: code
+        language: typescript
+
+  - id: routing
+    title: Routing
+    instruction: Define routing structure and patterns based on the chosen framework.
+    elicit: true
+    sections:
+      - id: route-configuration
+        title: Route Configuration
+        instruction: Provide routing configuration appropriate for the chosen framework. Include protected route patterns, lazy loading where applicable, and authentication guards/middleware.
+        type: code
+        language: typescript
+
+  - id: styling-guidelines
+    title: Styling Guidelines
+    instruction: Define styling approach based on the chosen framework.
+    elicit: true
+    sections:
+      - id: styling-approach
+        title: Styling Approach
+        instruction: Describe the styling methodology appropriate for the chosen framework (CSS Modules, Styled Components, Tailwind, etc.) and provide basic patterns.
+      - id: global-theme
+        title: Global Theme Variables
+        instruction: Provide a CSS custom properties (CSS variables) theme system that works across all frameworks. Include colors, spacing, typography, shadows, and dark mode support.
+        type: code
+        language: css
+
+  - id: testing-requirements
+    title: Testing Requirements
+    instruction: Define minimal testing requirements based on the chosen framework.
+    elicit: true
+    sections:
+      - id: component-test-template
+        title: Component Test Template
+        instruction: Provide a basic component test template using the framework's recommended testing library. Include examples of rendering tests, user interaction tests, and mocking.
+        type: code
+        language: typescript
+      - id: testing-best-practices
+        title: Testing Best Practices
+        type: numbered-list
+        items:
+          - "**Unit Tests**: Test individual components in isolation"
+          - "**Integration Tests**: Test component interactions"
+          - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)"
+          - "**Coverage Goals**: Aim for 80% code coverage"
+          - "**Test Structure**: Arrange-Act-Assert pattern"
+          - "**Mock External Dependencies**: API calls, routing, state management"
+
+  - id: environment-configuration
+    title: Environment Configuration
+    instruction: List required environment variables based on the chosen framework. Show the appropriate format and naming conventions for the framework.
+    elicit: true
+
+  - id: frontend-developer-standards
+    title: Frontend Developer Standards
+    sections:
+      - id: critical-coding-rules
+        title: Critical Coding Rules
+        instruction: List essential rules that prevent common AI mistakes, including both universal rules and framework-specific ones.
+        elicit: true
+      - id: quick-reference
+        title: Quick Reference
+        instruction: |
+          Create a framework-specific cheat sheet with:
+          - Common commands (dev server, build, test)
+          - Key import patterns
+          - File naming conventions
+          - Project-specific patterns and utilities

bmad-core/templates/front-end-spec-tmpl.md

@@ -1,413 +0,0 @@
-# {{Project Name}} UI/UX Specification
-
-[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
-
-[[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
-
-## Introduction
-
-[[LLM: Establish the document's purpose and scope. Keep the content below but ensure project name is properly substituted.]]
-
-This document defines the user experience goals, information architecture, user flows, and visual design specifications for {{Project Name}}'s user interface. It serves as the foundation for visual design and frontend development, ensuring a cohesive and user-centered experience.
-
-### Overall UX Goals & Principles
-
-[[LLM: Work with the user to establish and document the following. If not already defined, facilitate a discussion to determine:
-
-1. Target User Personas - elicit details or confirm existing ones from PRD
-2. Key Usability Goals - understand what success looks like for users
-3. Core Design Principles - establish 3-5 guiding principles
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Target User Personas
-
-{{persona_descriptions}}
-
-@{example: personas}
-
-- **Power User:** Technical professionals who need advanced features and efficiency
-- **Casual User:** Occasional users who prioritize ease of use and clear guidance
-- **Administrator:** System managers who need control and oversight capabilities
-  @{/example}
-
-### Usability Goals
-
-{{usability_goals}}
-
-@{example: usability_goals}
-
-- Ease of learning: New users can complete core tasks within 5 minutes
-- Efficiency of use: Power users can complete frequent tasks with minimal clicks
-- Error prevention: Clear validation and confirmation for destructive actions
-- Memorability: Infrequent users can return without relearning
-  @{/example}
-
-### Design Principles
-
-{{design_principles}}
-
-@{example: design_principles}
-
-1. **Clarity over cleverness** - Prioritize clear communication over aesthetic innovation
-2. **Progressive disclosure** - Show only what's needed, when it's needed
-3. **Consistent patterns** - Use familiar UI patterns throughout the application
-4. **Immediate feedback** - Every action should have a clear, immediate response
-5. **Accessible by default** - Design for all users from the start
-   @{/example}
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Information Architecture (IA)
-
-[[LLM: Collaborate with the user to create a comprehensive information architecture:
-
-1. Build a Site Map or Screen Inventory showing all major areas
-2. Define the Navigation Structure (primary, secondary, breadcrumbs)
-3. Use Mermaid diagrams for visual representation
-4. Consider user mental models and expected groupings
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Site Map / Screen Inventory
-
-```mermaid
-{{sitemap_diagram}}
-```
-
-@{example: sitemap}
-
-```mermaid
-graph TD
-    A[Homepage] --> B[Dashboard]
-    A --> C[Products]
-    A --> D[Account]
-    B --> B1[Analytics]
-    B --> B2[Recent Activity]
-    C --> C1[Browse]
-    C --> C2[Search]
-    C --> C3[Product Details]
-    D --> D1[Profile]
-    D --> D2[Settings]
-    D --> D3[Billing]
-```
-
-@{/example}
-
-### Navigation Structure
-
-**Primary Navigation:** {{primary_nav_description}}
-
-**Secondary Navigation:** {{secondary_nav_description}}
-
-**Breadcrumb Strategy:** {{breadcrumb_strategy}}
-
-## User Flows
-
-[[LLM: For each critical user task identified in the PRD:
-
-1. Define the user's goal clearly
-2. Map out all steps including decision points
-3. Consider edge cases and error states
-4. Use Mermaid flow diagrams for clarity
-5. Link to external tools (Figma/Miro) if detailed flows exist there
-
-Create subsections for each major flow. After presenting all flows, apply `tasks#advanced-elicitation` protocol]]
-
-<<REPEAT: user_flow>>
-
-### {{flow_name}}
-
-**User Goal:** {{flow_goal}}
-
-**Entry Points:** {{entry_points}}
-
-**Success Criteria:** {{success_criteria}}
-
-#### Flow Diagram
-
-```mermaid
-{{flow_diagram}}
-```
-
-**Edge Cases & Error Handling:**
-
-- {{edge_case_1}}
-- {{edge_case_2}}
-
-**Notes:** {{flow_notes}}
-<</REPEAT>>
-
-@{example: user_flow}
-
-### User Registration
-
-**User Goal:** Create a new account to access the platform
-
-**Entry Points:** Homepage CTA, Login page link, Marketing landing pages
-
-**Success Criteria:** User successfully creates account and reaches dashboard
-
-#### Flow Diagram
-
-```mermaid
-graph TD
-    Start[Landing Page] --> Click[Click Sign Up]
-    Click --> Form[Registration Form]
-    Form --> Fill[Fill Required Fields]
-    Fill --> Submit[Submit Form]
-    Submit --> Validate{Valid?}
-    Validate -->|No| Error[Show Errors]
-    Error --> Form
-    Validate -->|Yes| Verify[Email Verification]
-    Verify --> Complete[Account Created]
-    Complete --> Dashboard[Redirect to Dashboard]
-```
-
-**Edge Cases & Error Handling:**
-
-- Duplicate email: Show inline error with password recovery option
-- Weak password: Real-time feedback on password strength
-- Network error: Preserve form data and show retry option
-  @{/example}
-
-## Wireframes & Mockups
-
-[[LLM: Clarify where detailed visual designs will be created (Figma, Sketch, etc.) and how to reference them. If low-fidelity wireframes are needed, offer to help conceptualize layouts for key screens.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-**Primary Design Files:** {{design_tool_link}}
-
-### Key Screen Layouts
-
-<<REPEAT: screen_layout>>
-
-#### {{screen_name}}
-
-**Purpose:** {{screen_purpose}}
-
-**Key Elements:**
-
-- {{element_1}}
-- {{element_2}}
-- {{element_3}}
-
-**Interaction Notes:** {{interaction_notes}}
-
-**Design File Reference:** {{specific_frame_link}}
-<</REPEAT>>
-
-## Component Library / Design System
-
-[[LLM: Discuss whether to use an existing design system or create a new one. If creating new, identify foundational components and their key states. Note that detailed technical specs belong in front-end-architecture.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-**Design System Approach:** {{design_system_approach}}
-
-### Core Components
-
-<<REPEAT: component>>
-
-#### {{component_name}}
-
-**Purpose:** {{component_purpose}}
-
-**Variants:** {{component_variants}}
-
-**States:** {{component_states}}
-
-**Usage Guidelines:** {{usage_guidelines}}
-<</REPEAT>>
-
-@{example: component}
-
-#### Button
-
-**Purpose:** Primary interaction element for user actions
-
-**Variants:** Primary, Secondary, Tertiary, Destructive
-
-**States:** Default, Hover, Active, Disabled, Loading
-
-**Usage Guidelines:**
-
-- Use Primary for main CTAs (one per view)
-- Secondary for supporting actions
-- Destructive only for permanent deletions with confirmation
-  @{/example}
-
-## Branding & Style Guide
-
-[[LLM: Link to existing style guide or define key brand elements. Ensure consistency with company brand guidelines if they exist.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Visual Identity
-
-**Brand Guidelines:** {{brand_guidelines_link}}
-
-### Color Palette
-
-| Color Type    | Hex Code            | Usage                            |
-| :------------ | :------------------ | :------------------------------- |
-| **Primary**   | {{primary_color}}   | {{primary_usage}}                |
-| **Secondary** | {{secondary_color}} | {{secondary_usage}}              |
-| **Accent**    | {{accent_color}}    | {{accent_usage}}                 |
-| **Success**   | {{success_color}}   | Positive feedback, confirmations |
-| **Warning**   | {{warning_color}}   | Cautions, important notices      |
-| **Error**     | {{error_color}}     | Errors, destructive actions      |
-| **Neutral**   | {{neutral_colors}}  | Text, borders, backgrounds       |
-
-### Typography
-
-**Font Families:**
-
-- **Primary:** {{primary_font}}
-- **Secondary:** {{secondary_font}}
-- **Monospace:** {{mono_font}}
-
-**Type Scale:**
-| Element | Size | Weight | Line Height |
-|:--------|:-----|:-------|:------------|
-| H1 | {{h1_size}} | {{h1_weight}} | {{h1_line}} |
-| H2 | {{h2_size}} | {{h2_weight}} | {{h2_line}} |
-| H3 | {{h3_size}} | {{h3_weight}} | {{h3_line}} |
-| Body | {{body_size}} | {{body_weight}} | {{body_line}} |
-| Small | {{small_size}} | {{small_weight}} | {{small_line}} |
-
-### Iconography
-
-**Icon Library:** {{icon_library}}
-
-**Usage Guidelines:** {{icon_guidelines}}
-
-### Spacing & Layout
-
-**Grid System:** {{grid_system}}
-
-**Spacing Scale:** {{spacing_scale}}
-
-## Accessibility Requirements
-
-[[LLM: Define specific accessibility requirements based on target compliance level and user needs. Be comprehensive but practical.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Compliance Target
-
-**Standard:** {{compliance_standard}}
-
-### Key Requirements
-
-**Visual:**
-
-- Color contrast ratios: {{contrast_requirements}}
-- Focus indicators: {{focus_requirements}}
-- Text sizing: {{text_requirements}}
-
-**Interaction:**
-
-- Keyboard navigation: {{keyboard_requirements}}
-- Screen reader support: {{screen_reader_requirements}}
-- Touch targets: {{touch_requirements}}
-
-**Content:**
-
-- Alternative text: {{alt_text_requirements}}
-- Heading structure: {{heading_requirements}}
-- Form labels: {{form_requirements}}
-
-### Testing Strategy
-
-{{accessibility_testing}}
-
-## Responsiveness Strategy
-
-[[LLM: Define breakpoints and adaptation strategies for different device sizes. Consider both technical constraints and user contexts.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Breakpoints
-
-| Breakpoint | Min Width       | Max Width       | Target Devices      |
-| :--------- | :-------------- | :-------------- | :------------------ |
-| Mobile     | {{mobile_min}}  | {{mobile_max}}  | {{mobile_devices}}  |
-| Tablet     | {{tablet_min}}  | {{tablet_max}}  | {{tablet_devices}}  |
-| Desktop    | {{desktop_min}} | {{desktop_max}} | {{desktop_devices}} |
-| Wide       | {{wide_min}}    | -               | {{wide_devices}}    |
-
-### Adaptation Patterns
-
-**Layout Changes:** {{layout_adaptations}}
-
-**Navigation Changes:** {{nav_adaptations}}
-
-**Content Priority:** {{content_adaptations}}
-
-**Interaction Changes:** {{interaction_adaptations}}
-
-## Animation & Micro-interactions
-
-[[LLM: Define motion design principles and key interactions. Keep performance and accessibility in mind.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Motion Principles
-
-{{motion_principles}}
-
-### Key Animations
-
-<<REPEAT: animation>>
-
-- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})
-  <</REPEAT>>
-
-## Performance Considerations
-
-[[LLM: Define performance goals and strategies that impact UX design decisions.]]
-
-### Performance Goals
-
-- **Page Load:** {{load_time_goal}}
-- **Interaction Response:** {{interaction_goal}}
-- **Animation FPS:** {{animation_goal}}
-
-### Design Strategies
-
-{{performance_strategies}}
-
-## Next Steps
-
-[[LLM: After completing the UI/UX specification:
-
-1. Recommend review with stakeholders
-2. Suggest creating/updating visual designs in design tool
-3. Prepare for handoff to Design Architect for frontend architecture
-4. Note any open questions or decisions needed]]
-
-### Immediate Actions
-
-1. {{next_step_1}}
-2. {{next_step_2}}
-3. {{next_step_3}}
-
-### Design Handoff Checklist
-
-- [ ] All user flows documented
-- [ ] Component inventory complete
-- [ ] Accessibility requirements defined
-- [ ] Responsive strategy clear
-- [ ] Brand guidelines incorporated
-- [ ] Performance goals established
-
-## Checklist Results
-
-[[LLM: If a UI/UX checklist exists, run it against this document and report results here.]]

bmad-core/templates/front-end-spec-tmpl.yaml

@@ -0,0 +1,349 @@
+template:
+  id: frontend-spec-template-v2
+  name: UI/UX Specification
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/front-end-spec.md
+    title: "{{project_name}} UI/UX Specification"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: introduction
+    title: Introduction
+    instruction: |
+      Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.
+      
+      Establish the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
+    content: |
+      This document defines the user experience goals, information architecture, user flows, and visual design specifications for {{project_name}}'s user interface. It serves as the foundation for visual design and frontend development, ensuring a cohesive and user-centered experience.
+    sections:
+      - id: ux-goals-principles
+        title: Overall UX Goals & Principles
+        instruction: |
+          Work with the user to establish and document the following. If not already defined, facilitate a discussion to determine:
+          
+          1. Target User Personas - elicit details or confirm existing ones from PRD
+          2. Key Usability Goals - understand what success looks like for users
+          3. Core Design Principles - establish 3-5 guiding principles
+        elicit: true
+        sections:
+          - id: user-personas
+            title: Target User Personas
+            template: "{{persona_descriptions}}"
+            examples:
+              - "**Power User:** Technical professionals who need advanced features and efficiency"
+              - "**Casual User:** Occasional users who prioritize ease of use and clear guidance"
+              - "**Administrator:** System managers who need control and oversight capabilities"
+          - id: usability-goals
+            title: Usability Goals
+            template: "{{usability_goals}}"
+            examples:
+              - "Ease of learning: New users can complete core tasks within 5 minutes"
+              - "Efficiency of use: Power users can complete frequent tasks with minimal clicks"
+              - "Error prevention: Clear validation and confirmation for destructive actions"
+              - "Memorability: Infrequent users can return without relearning"
+          - id: design-principles
+            title: Design Principles
+            template: "{{design_principles}}"
+            type: numbered-list
+            examples:
+              - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation"
+              - "**Progressive disclosure** - Show only what's needed, when it's needed"
+              - "**Consistent patterns** - Use familiar UI patterns throughout the application"
+              - "**Immediate feedback** - Every action should have a clear, immediate response"
+              - "**Accessible by default** - Design for all users from the start"
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: information-architecture
+    title: Information Architecture (IA)
+    instruction: |
+      Collaborate with the user to create a comprehensive information architecture:
+      
+      1. Build a Site Map or Screen Inventory showing all major areas
+      2. Define the Navigation Structure (primary, secondary, breadcrumbs)
+      3. Use Mermaid diagrams for visual representation
+      4. Consider user mental models and expected groupings
+    elicit: true
+    sections:
+      - id: sitemap
+        title: Site Map / Screen Inventory
+        type: mermaid
+        mermaid_type: graph
+        template: "{{sitemap_diagram}}"
+        examples:
+          - |
+            graph TD
+                A[Homepage] --> B[Dashboard]
+                A --> C[Products]
+                A --> D[Account]
+                B --> B1[Analytics]
+                B --> B2[Recent Activity]
+                C --> C1[Browse]
+                C --> C2[Search]
+                C --> C3[Product Details]
+                D --> D1[Profile]
+                D --> D2[Settings]
+                D --> D3[Billing]
+      - id: navigation-structure
+        title: Navigation Structure
+        template: |
+          **Primary Navigation:** {{primary_nav_description}}
+          
+          **Secondary Navigation:** {{secondary_nav_description}}
+          
+          **Breadcrumb Strategy:** {{breadcrumb_strategy}}
+
+  - id: user-flows
+    title: User Flows
+    instruction: |
+      For each critical user task identified in the PRD:
+      
+      1. Define the user's goal clearly
+      2. Map out all steps including decision points
+      3. Consider edge cases and error states
+      4. Use Mermaid flow diagrams for clarity
+      5. Link to external tools (Figma/Miro) if detailed flows exist there
+      
+      Create subsections for each major flow.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: flow
+        title: "{{flow_name}}"
+        template: |
+          **User Goal:** {{flow_goal}}
+          
+          **Entry Points:** {{entry_points}}
+          
+          **Success Criteria:** {{success_criteria}}
+        sections:
+          - id: flow-diagram
+            title: Flow Diagram
+            type: mermaid
+            mermaid_type: graph
+            template: "{{flow_diagram}}"
+          - id: edge-cases
+            title: "Edge Cases & Error Handling:"
+            type: bullet-list
+            template: "- {{edge_case}}"
+          - id: notes
+            template: "**Notes:** {{flow_notes}}"
+
+  - id: wireframes-mockups
+    title: Wireframes & Mockups
+    instruction: |
+      Clarify where detailed visual designs will be created (Figma, Sketch, etc.) and how to reference them. If low-fidelity wireframes are needed, offer to help conceptualize layouts for key screens.
+    elicit: true
+    sections:
+      - id: design-files
+        template: "**Primary Design Files:** {{design_tool_link}}"
+      - id: key-screen-layouts
+        title: Key Screen Layouts
+        repeatable: true
+        sections:
+          - id: screen
+            title: "{{screen_name}}"
+            template: |
+              **Purpose:** {{screen_purpose}}
+              
+              **Key Elements:**
+              - {{element_1}}
+              - {{element_2}}
+              - {{element_3}}
+              
+              **Interaction Notes:** {{interaction_notes}}
+              
+              **Design File Reference:** {{specific_frame_link}}
+
+  - id: component-library
+    title: Component Library / Design System
+    instruction: |
+      Discuss whether to use an existing design system or create a new one. If creating new, identify foundational components and their key states. Note that detailed technical specs belong in front-end-architecture.
+    elicit: true
+    sections:
+      - id: design-system-approach
+        template: "**Design System Approach:** {{design_system_approach}}"
+      - id: core-components
+        title: Core Components
+        repeatable: true
+        sections:
+          - id: component
+            title: "{{component_name}}"
+            template: |
+              **Purpose:** {{component_purpose}}
+              
+              **Variants:** {{component_variants}}
+              
+              **States:** {{component_states}}
+              
+              **Usage Guidelines:** {{usage_guidelines}}
+
+  - id: branding-style
+    title: Branding & Style Guide
+    instruction: Link to existing style guide or define key brand elements. Ensure consistency with company brand guidelines if they exist.
+    elicit: true
+    sections:
+      - id: visual-identity
+        title: Visual Identity
+        template: "**Brand Guidelines:** {{brand_guidelines_link}}"
+      - id: color-palette
+        title: Color Palette
+        type: table
+        columns: ["Color Type", "Hex Code", "Usage"]
+        rows:
+          - ["Primary", "{{primary_color}}", "{{primary_usage}}"]
+          - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"]
+          - ["Accent", "{{accent_color}}", "{{accent_usage}}"]
+          - ["Success", "{{success_color}}", "Positive feedback, confirmations"]
+          - ["Warning", "{{warning_color}}", "Cautions, important notices"]
+          - ["Error", "{{error_color}}", "Errors, destructive actions"]
+          - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"]
+      - id: typography
+        title: Typography
+        sections:
+          - id: font-families
+            title: Font Families
+            template: |
+              - **Primary:** {{primary_font}}
+              - **Secondary:** {{secondary_font}}
+              - **Monospace:** {{mono_font}}
+          - id: type-scale
+            title: Type Scale
+            type: table
+            columns: ["Element", "Size", "Weight", "Line Height"]
+            rows:
+              - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"]
+              - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"]
+              - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"]
+              - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"]
+              - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"]
+      - id: iconography
+        title: Iconography
+        template: |
+          **Icon Library:** {{icon_library}}
+          
+          **Usage Guidelines:** {{icon_guidelines}}
+      - id: spacing-layout
+        title: Spacing & Layout
+        template: |
+          **Grid System:** {{grid_system}}
+          
+          **Spacing Scale:** {{spacing_scale}}
+
+  - id: accessibility
+    title: Accessibility Requirements
+    instruction: Define specific accessibility requirements based on target compliance level and user needs. Be comprehensive but practical.
+    elicit: true
+    sections:
+      - id: compliance-target
+        title: Compliance Target
+        template: "**Standard:** {{compliance_standard}}"
+      - id: key-requirements
+        title: Key Requirements
+        template: |
+          **Visual:**
+          - Color contrast ratios: {{contrast_requirements}}
+          - Focus indicators: {{focus_requirements}}
+          - Text sizing: {{text_requirements}}
+          
+          **Interaction:**
+          - Keyboard navigation: {{keyboard_requirements}}
+          - Screen reader support: {{screen_reader_requirements}}
+          - Touch targets: {{touch_requirements}}
+          
+          **Content:**
+          - Alternative text: {{alt_text_requirements}}
+          - Heading structure: {{heading_requirements}}
+          - Form labels: {{form_requirements}}
+      - id: testing-strategy
+        title: Testing Strategy
+        template: "{{accessibility_testing}}"
+
+  - id: responsiveness
+    title: Responsiveness Strategy
+    instruction: Define breakpoints and adaptation strategies for different device sizes. Consider both technical constraints and user contexts.
+    elicit: true
+    sections:
+      - id: breakpoints
+        title: Breakpoints
+        type: table
+        columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"]
+        rows:
+          - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"]
+          - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"]
+          - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"]
+          - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"]
+      - id: adaptation-patterns
+        title: Adaptation Patterns
+        template: |
+          **Layout Changes:** {{layout_adaptations}}
+          
+          **Navigation Changes:** {{nav_adaptations}}
+          
+          **Content Priority:** {{content_adaptations}}
+          
+          **Interaction Changes:** {{interaction_adaptations}}
+
+  - id: animation
+    title: Animation & Micro-interactions
+    instruction: Define motion design principles and key interactions. Keep performance and accessibility in mind.
+    elicit: true
+    sections:
+      - id: motion-principles
+        title: Motion Principles
+        template: "{{motion_principles}}"
+      - id: key-animations
+        title: Key Animations
+        repeatable: true
+        template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})"
+
+  - id: performance
+    title: Performance Considerations
+    instruction: Define performance goals and strategies that impact UX design decisions.
+    sections:
+      - id: performance-goals
+        title: Performance Goals
+        template: |
+          - **Page Load:** {{load_time_goal}}
+          - **Interaction Response:** {{interaction_goal}}
+          - **Animation FPS:** {{animation_goal}}
+      - id: design-strategies
+        title: Design Strategies
+        template: "{{performance_strategies}}"
+
+  - id: next-steps
+    title: Next Steps
+    instruction: |
+      After completing the UI/UX specification:
+      
+      1. Recommend review with stakeholders
+      2. Suggest creating/updating visual designs in design tool
+      3. Prepare for handoff to Design Architect for frontend architecture
+      4. Note any open questions or decisions needed
+    sections:
+      - id: immediate-actions
+        title: Immediate Actions
+        type: numbered-list
+        template: "{{action}}"
+      - id: design-handoff-checklist
+        title: Design Handoff Checklist
+        type: checklist
+        items:
+          - "All user flows documented"
+          - "Component inventory complete"
+          - "Accessibility requirements defined"
+          - "Responsive strategy clear"
+          - "Brand guidelines incorporated"
+          - "Performance goals established"
+
+  - id: checklist-results
+    title: Checklist Results
+    instruction: If a UI/UX checklist exists, run it against this document and report results here.

bmad-core/templates/fullstack-architecture-tmpl.yaml

@@ -0,0 +1,805 @@
+template:
+  id: fullstack-architecture-template-v2
+  name: Fullstack Architecture Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/architecture.md
+    title: "{{project_name}} Fullstack Architecture Document"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: introduction
+    title: Introduction
+    instruction: |
+      If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.
+    elicit: true
+    content: |
+      This document outlines the complete fullstack architecture for {{project_name}}, including backend systems, frontend implementation, and their integration. It serves as the single source of truth for AI-driven development, ensuring consistency across the entire technology stack.
+      
+      This unified approach combines what would traditionally be separate backend and frontend architecture documents, streamlining the development process for modern fullstack applications where these concerns are increasingly intertwined.
+    sections:
+      - id: starter-template
+        title: Starter Template or Existing Project
+        instruction: |
+          Before proceeding with architecture design, check if the project is based on any starter templates or existing codebases:
+          
+          1. Review the PRD and other documents for mentions of:
+          - Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
+          - Monorepo templates (e.g., Nx, Turborepo starters)
+          - Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
+          - Existing projects being extended or cloned
+          
+          2. If starter templates or existing projects are mentioned:
+          - Ask the user to provide access (links, repos, or files)
+          - Analyze to understand pre-configured choices and constraints
+          - Note any architectural decisions already made
+          - Identify what can be modified vs what must be retained
+          
+          3. If no starter is mentioned but this is greenfield:
+          - Suggest appropriate fullstack starters based on tech preferences
+          - Consider platform-specific options (Vercel, AWS, etc.)
+          - Let user decide whether to use one
+          
+          4. Document the decision and any constraints it imposes
+          
+          If none, state "N/A - Greenfield project"
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: high-level-architecture
+    title: High Level Architecture
+    instruction: This section contains multiple subsections that establish the foundation. Present all subsections together, then elicit feedback on the complete section.
+    elicit: true
+    sections:
+      - id: technical-summary
+        title: Technical Summary
+        instruction: |
+          Provide a comprehensive overview (4-6 sentences) covering:
+          - Overall architectural style and deployment approach
+          - Frontend framework and backend technology choices
+          - Key integration points between frontend and backend
+          - Infrastructure platform and services
+          - How this architecture achieves PRD goals
+      - id: platform-infrastructure
+        title: Platform and Infrastructure Choice
+        instruction: |
+          Based on PRD requirements and technical assumptions, make a platform recommendation:
+          
+          1. Consider common patterns (not an exhaustive list, use your own best judgement and search the web as needed for emerging trends):
+          - **Vercel + Supabase**: For rapid development with Next.js, built-in auth/storage
+          - **AWS Full Stack**: For enterprise scale with Lambda, API Gateway, S3, Cognito
+          - **Azure**: For .NET ecosystems or enterprise Microsoft environments
+          - **Google Cloud**: For ML/AI heavy applications or Google ecosystem integration
+          
+          2. Present 2-3 viable options with clear pros/cons
+          3. Make a recommendation with rationale
+          4. Get explicit user confirmation
+          
+          Document the choice and key services that will be used.
+        template: |
+          **Platform:** {{selected_platform}}
+          **Key Services:** {{core_services_list}}
+          **Deployment Host and Regions:** {{regions}}
+      - id: repository-structure
+        title: Repository Structure
+        instruction: |
+          Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure:
+          
+          1. For modern fullstack apps, monorepo is often preferred
+          2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces)
+          3. Define package/app boundaries
+          4. Plan for shared code between frontend and backend
+        template: |
+          **Structure:** {{repo_structure_choice}}
+          **Monorepo Tool:** {{monorepo_tool_if_applicable}}
+          **Package Organization:** {{package_strategy}}
+      - id: architecture-diagram
+        title: High Level Architecture Diagram
+        type: mermaid
+        mermaid_type: graph
+        instruction: |
+          Create a Mermaid diagram showing the complete system architecture including:
+          - User entry points (web, mobile)
+          - Frontend application deployment
+          - API layer (REST/GraphQL)
+          - Backend services
+          - Databases and storage
+          - External integrations
+          - CDN and caching layers
+          
+          Use appropriate diagram type for clarity.
+      - id: architectural-patterns
+        title: Architectural Patterns
+        instruction: |
+          List patterns that will guide both frontend and backend development. Include patterns for:
+          - Overall architecture (e.g., Jamstack, Serverless, Microservices)
+          - Frontend patterns (e.g., Component-based, State management)
+          - Backend patterns (e.g., Repository, CQRS, Event-driven)
+          - Integration patterns (e.g., BFF, API Gateway)
+          
+          For each pattern, provide recommendation and rationale.
+        repeatable: true
+        template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}"
+        examples:
+          - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications"
+          - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases"
+          - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility"
+          - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring"
+
+  - id: tech-stack
+    title: Tech Stack
+    instruction: |
+      This is the DEFINITIVE technology selection for the entire project. Work with user to finalize all choices. This table is the single source of truth - all development must use these exact versions.
+      
+      Key areas to cover:
+      - Frontend and backend languages/frameworks
+      - Databases and caching
+      - Authentication and authorization
+      - API approach
+      - Testing tools for both frontend and backend
+      - Build and deployment tools
+      - Monitoring and logging
+      
+      Upon render, elicit feedback immediately.
+    elicit: true
+    sections:
+      - id: tech-stack-table
+        title: Technology Stack Table
+        type: table
+        columns: [Category, Technology, Version, Purpose, Rationale]
+        rows:
+          - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Frontend Framework", "{{fe_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["UI Component Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Backend Framework", "{{be_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+
+  - id: data-models
+    title: Data Models
+    instruction: |
+      Define the core data models/entities that will be shared between frontend and backend:
+      
+      1. Review PRD requirements and identify key business entities
+      2. For each model, explain its purpose and relationships
+      3. Include key attributes and data types
+      4. Show relationships between models
+      5. Create TypeScript interfaces that can be shared
+      6. Discuss design decisions with user
+      
+      Create a clear conceptual model before moving to database schema.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: model
+        title: "{{model_name}}"
+        template: |
+          **Purpose:** {{model_purpose}}
+          
+          **Key Attributes:**
+          - {{attribute_1}}: {{type_1}} - {{description_1}}
+          - {{attribute_2}}: {{type_2}} - {{description_2}}
+        sections:
+          - id: typescript-interface
+            title: TypeScript Interface
+            type: code
+            language: typescript
+            template: "{{model_interface}}"
+          - id: relationships
+            title: Relationships
+            type: bullet-list
+            template: "- {{relationship}}"
+
+  - id: api-spec
+    title: API Specification
+    instruction: |
+      Based on the chosen API style from Tech Stack:
+      
+      1. If REST API, create an OpenAPI 3.0 specification
+      2. If GraphQL, provide the GraphQL schema
+      3. If tRPC, show router definitions
+      4. Include all endpoints from epics/stories
+      5. Define request/response schemas based on data models
+      6. Document authentication requirements
+      7. Include example requests/responses
+      
+      Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.
+    elicit: true
+    sections:
+      - id: rest-api
+        title: REST API Specification
+        condition: API style is REST
+        type: code
+        language: yaml
+        template: |
+          openapi: 3.0.0
+          info:
+            title: {{api_title}}
+            version: {{api_version}}
+            description: {{api_description}}
+          servers:
+            - url: {{server_url}}
+              description: {{server_description}}
+      - id: graphql-api
+        title: GraphQL Schema
+        condition: API style is GraphQL
+        type: code
+        language: graphql
+        template: "{{graphql_schema}}"
+      - id: trpc-api
+        title: tRPC Router Definitions
+        condition: API style is tRPC
+        type: code
+        language: typescript
+        template: "{{trpc_routers}}"
+
+  - id: components
+    title: Components
+    instruction: |
+      Based on the architectural patterns, tech stack, and data models from above:
+      
+      1. Identify major logical components/services across the fullstack
+      2. Consider both frontend and backend components
+      3. Define clear boundaries and interfaces between components
+      4. For each component, specify:
+      - Primary responsibility
+      - Key interfaces/APIs exposed
+      - Dependencies on other components
+      - Technology specifics based on tech stack choices
+      
+      5. Create component diagrams where helpful
+    elicit: true
+    sections:
+      - id: component-list
+        repeatable: true
+        title: "{{component_name}}"
+        template: |
+          **Responsibility:** {{component_description}}
+          
+          **Key Interfaces:**
+          - {{interface_1}}
+          - {{interface_2}}
+          
+          **Dependencies:** {{dependencies}}
+          
+          **Technology Stack:** {{component_tech_details}}
+      - id: component-diagrams
+        title: Component Diagrams
+        type: mermaid
+        instruction: |
+          Create Mermaid diagrams to visualize component relationships. Options:
+          - C4 Container diagram for high-level view
+          - Component diagram for detailed internal structure
+          - Sequence diagrams for complex interactions
+          Choose the most appropriate for clarity
+
+  - id: external-apis
+    title: External APIs
+    condition: Project requires external API integrations
+    instruction: |
+      For each external service integration:
+      
+      1. Identify APIs needed based on PRD requirements and component design
+      2. If documentation URLs are unknown, ask user for specifics
+      3. Document authentication methods and security considerations
+      4. List specific endpoints that will be used
+      5. Note any rate limits or usage constraints
+      
+      If no external APIs are needed, state this explicitly and skip to next section.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: api
+        title: "{{api_name}} API"
+        template: |
+          - **Purpose:** {{api_purpose}}
+          - **Documentation:** {{api_docs_url}}
+          - **Base URL(s):** {{api_base_url}}
+          - **Authentication:** {{auth_method}}
+          - **Rate Limits:** {{rate_limits}}
+          
+          **Key Endpoints Used:**
+          - `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
+          
+          **Integration Notes:** {{integration_considerations}}
+
+  - id: core-workflows
+    title: Core Workflows
+    type: mermaid
+    mermaid_type: sequence
+    instruction: |
+      Illustrate key system workflows using sequence diagrams:
+      
+      1. Identify critical user journeys from PRD
+      2. Show component interactions including external APIs
+      3. Include both frontend and backend flows
+      4. Include error handling paths
+      5. Document async operations
+      6. Create both high-level and detailed diagrams as needed
+      
+      Focus on workflows that clarify architecture decisions or complex interactions.
+    elicit: true
+
+  - id: database-schema
+    title: Database Schema
+    instruction: |
+      Transform the conceptual data models into concrete database schemas:
+      
+      1. Use the database type(s) selected in Tech Stack
+      2. Create schema definitions using appropriate notation
+      3. Include indexes, constraints, and relationships
+      4. Consider performance and scalability
+      5. For NoSQL, show document structures
+      
+      Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
+    elicit: true
+
+  - id: frontend-architecture
+    title: Frontend Architecture
+    instruction: Define frontend-specific architecture details. After each subsection, note if user wants to refine before continuing.
+    elicit: true
+    sections:
+      - id: component-architecture
+        title: Component Architecture
+        instruction: Define component organization and patterns based on chosen framework.
+        sections:
+          - id: component-organization
+            title: Component Organization
+            type: code
+            language: text
+            template: "{{component_structure}}"
+          - id: component-template
+            title: Component Template
+            type: code
+            language: typescript
+            template: "{{component_template}}"
+      - id: state-management
+        title: State Management Architecture
+        instruction: Detail state management approach based on chosen solution.
+        sections:
+          - id: state-structure
+            title: State Structure
+            type: code
+            language: typescript
+            template: "{{state_structure}}"
+          - id: state-patterns
+            title: State Management Patterns
+            type: bullet-list
+            template: "- {{pattern}}"
+      - id: routing-architecture
+        title: Routing Architecture
+        instruction: Define routing structure based on framework choice.
+        sections:
+          - id: route-organization
+            title: Route Organization
+            type: code
+            language: text
+            template: "{{route_structure}}"
+          - id: protected-routes
+            title: Protected Route Pattern
+            type: code
+            language: typescript
+            template: "{{protected_route_example}}"
+      - id: frontend-services
+        title: Frontend Services Layer
+        instruction: Define how frontend communicates with backend.
+        sections:
+          - id: api-client-setup
+            title: API Client Setup
+            type: code
+            language: typescript
+            template: "{{api_client_setup}}"
+          - id: service-example
+            title: Service Example
+            type: code
+            language: typescript
+            template: "{{service_example}}"
+
+  - id: backend-architecture
+    title: Backend Architecture
+    instruction: Define backend-specific architecture details. Consider serverless vs traditional server approaches.
+    elicit: true
+    sections:
+      - id: service-architecture
+        title: Service Architecture
+        instruction: Based on platform choice, define service organization.
+        sections:
+          - id: serverless-architecture
+            condition: Serverless architecture chosen
+            sections:
+              - id: function-organization
+                title: Function Organization
+                type: code
+                language: text
+                template: "{{function_structure}}"
+              - id: function-template
+                title: Function Template
+                type: code
+                language: typescript
+                template: "{{function_template}}"
+          - id: traditional-server
+            condition: Traditional server architecture chosen
+            sections:
+              - id: controller-organization
+                title: Controller/Route Organization
+                type: code
+                language: text
+                template: "{{controller_structure}}"
+              - id: controller-template
+                title: Controller Template
+                type: code
+                language: typescript
+                template: "{{controller_template}}"
+      - id: database-architecture
+        title: Database Architecture
+        instruction: Define database schema and access patterns.
+        sections:
+          - id: schema-design
+            title: Schema Design
+            type: code
+            language: sql
+            template: "{{database_schema}}"
+          - id: data-access-layer
+            title: Data Access Layer
+            type: code
+            language: typescript
+            template: "{{repository_pattern}}"
+      - id: auth-architecture
+        title: Authentication and Authorization
+        instruction: Define auth implementation details.
+        sections:
+          - id: auth-flow
+            title: Auth Flow
+            type: mermaid
+            mermaid_type: sequence
+            template: "{{auth_flow_diagram}}"
+          - id: auth-middleware
+            title: Middleware/Guards
+            type: code
+            language: typescript
+            template: "{{auth_middleware}}"
+
+  - id: unified-project-structure
+    title: Unified Project Structure
+    instruction: Create a monorepo structure that accommodates both frontend and backend. Adapt based on chosen tools and frameworks.
+    elicit: true
+    type: code
+    language: plaintext
+    examples:
+    - |
+      {{project-name}}/
+      ├── .github/                    # CI/CD workflows
+      │   └── workflows/
+      │       ├── ci.yaml
+      │       └── deploy.yaml
+      ├── apps/                       # Application packages
+      │   ├── web/                    # Frontend application
+      │   │   ├── src/
+      │   │   │   ├── components/     # UI components
+      │   │   │   ├── pages/          # Page components/routes
+      │   │   │   ├── hooks/          # Custom React hooks
+      │   │   │   ├── services/       # API client services
+      │   │   │   ├── stores/         # State management
+      │   │   │   ├── styles/         # Global styles/themes
+      │   │   │   └── utils/          # Frontend utilities
+      │   │   ├── public/             # Static assets
+      │   │   ├── tests/              # Frontend tests
+      │   │   └── package.json
+      │   └── api/                    # Backend application
+      │       ├── src/
+      │       │   ├── routes/         # API routes/controllers
+      │       │   ├── services/       # Business logic
+      │       │   ├── models/         # Data models
+      │       │   ├── middleware/     # Express/API middleware
+      │       │   ├── utils/          # Backend utilities
+      │       │   └── {{serverless_or_server_entry}}
+      │       ├── tests/              # Backend tests
+      │       └── package.json
+      ├── packages/                   # Shared packages
+      │   ├── shared/                 # Shared types/utilities
+      │   │   ├── src/
+      │   │   │   ├── types/          # TypeScript interfaces
+      │   │   │   ├── constants/      # Shared constants
+      │   │   │   └── utils/          # Shared utilities
+      │   │   └── package.json
+      │   ├── ui/                     # Shared UI components
+      │   │   ├── src/
+      │   │   └── package.json
+      │   └── config/                 # Shared configuration
+      │       ├── eslint/
+      │       ├── typescript/
+      │       └── jest/
+      ├── infrastructure/             # IaC definitions
+      │   └── {{iac_structure}}
+      ├── scripts/                    # Build/deploy scripts
+      ├── docs/                       # Documentation
+      │   ├── prd.md
+      │   ├── front-end-spec.md
+      │   └── fullstack-architecture.md
+      ├── .env.example                # Environment template
+      ├── package.json                # Root package.json
+      ├── {{monorepo_config}}         # Monorepo configuration
+      └── README.md
+
+  - id: development-workflow
+    title: Development Workflow
+    instruction: Define the development setup and workflow for the fullstack application.
+    elicit: true
+    sections:
+      - id: local-setup
+        title: Local Development Setup
+        sections:
+          - id: prerequisites
+            title: Prerequisites
+            type: code
+            language: bash
+            template: "{{prerequisites_commands}}"
+          - id: initial-setup
+            title: Initial Setup
+            type: code
+            language: bash
+            template: "{{setup_commands}}"
+          - id: dev-commands
+            title: Development Commands
+            type: code
+            language: bash
+            template: |
+              # Start all services
+              {{start_all_command}}
+              
+              # Start frontend only
+              {{start_frontend_command}}
+              
+              # Start backend only
+              {{start_backend_command}}
+              
+              # Run tests
+              {{test_commands}}
+      - id: environment-config
+        title: Environment Configuration
+        sections:
+          - id: env-vars
+            title: Required Environment Variables
+            type: code
+            language: bash
+            template: |
+              # Frontend (.env.local)
+              {{frontend_env_vars}}
+              
+              # Backend (.env)
+              {{backend_env_vars}}
+              
+              # Shared
+              {{shared_env_vars}}
+
+  - id: deployment-architecture
+    title: Deployment Architecture
+    instruction: Define deployment strategy based on platform choice.
+    elicit: true
+    sections:
+      - id: deployment-strategy
+        title: Deployment Strategy
+        template: |
+          **Frontend Deployment:**
+          - **Platform:** {{frontend_deploy_platform}}
+          - **Build Command:** {{frontend_build_command}}
+          - **Output Directory:** {{frontend_output_dir}}
+          - **CDN/Edge:** {{cdn_strategy}}
+          
+          **Backend Deployment:**
+          - **Platform:** {{backend_deploy_platform}}
+          - **Build Command:** {{backend_build_command}}
+          - **Deployment Method:** {{deployment_method}}
+      - id: cicd-pipeline
+        title: CI/CD Pipeline
+        type: code
+        language: yaml
+        template: "{{cicd_pipeline_config}}"
+      - id: environments
+        title: Environments
+        type: table
+        columns: [Environment, Frontend URL, Backend URL, Purpose]
+        rows:
+          - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"]
+          - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"]
+          - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"]
+
+  - id: security-performance
+    title: Security and Performance
+    instruction: Define security and performance considerations for the fullstack application.
+    elicit: true
+    sections:
+      - id: security-requirements
+        title: Security Requirements
+        template: |
+          **Frontend Security:**
+          - CSP Headers: {{csp_policy}}
+          - XSS Prevention: {{xss_strategy}}
+          - Secure Storage: {{storage_strategy}}
+          
+          **Backend Security:**
+          - Input Validation: {{validation_approach}}
+          - Rate Limiting: {{rate_limit_config}}
+          - CORS Policy: {{cors_config}}
+          
+          **Authentication Security:**
+          - Token Storage: {{token_strategy}}
+          - Session Management: {{session_approach}}
+          - Password Policy: {{password_requirements}}
+      - id: performance-optimization
+        title: Performance Optimization
+        template: |
+          **Frontend Performance:**
+          - Bundle Size Target: {{bundle_size}}
+          - Loading Strategy: {{loading_approach}}
+          - Caching Strategy: {{fe_cache_strategy}}
+          
+          **Backend Performance:**
+          - Response Time Target: {{response_target}}
+          - Database Optimization: {{db_optimization}}
+          - Caching Strategy: {{be_cache_strategy}}
+
+  - id: testing-strategy
+    title: Testing Strategy
+    instruction: Define comprehensive testing approach for fullstack application.
+    elicit: true
+    sections:
+      - id: testing-pyramid
+        title: Testing Pyramid
+        type: code
+        language: text
+        template: |
+                  E2E Tests
+                 /        \
+            Integration Tests
+               /            \
+          Frontend Unit  Backend Unit
+      - id: test-organization
+        title: Test Organization
+        sections:
+          - id: frontend-tests
+            title: Frontend Tests
+            type: code
+            language: text
+            template: "{{frontend_test_structure}}"
+          - id: backend-tests
+            title: Backend Tests
+            type: code
+            language: text
+            template: "{{backend_test_structure}}"
+          - id: e2e-tests
+            title: E2E Tests
+            type: code
+            language: text
+            template: "{{e2e_test_structure}}"
+      - id: test-examples
+        title: Test Examples
+        sections:
+          - id: frontend-test
+            title: Frontend Component Test
+            type: code
+            language: typescript
+            template: "{{frontend_test_example}}"
+          - id: backend-test
+            title: Backend API Test
+            type: code
+            language: typescript
+            template: "{{backend_test_example}}"
+          - id: e2e-test
+            title: E2E Test
+            type: code
+            language: typescript
+            template: "{{e2e_test_example}}"
+
+  - id: coding-standards
+    title: Coding Standards
+    instruction: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
+    elicit: true
+    sections:
+      - id: critical-rules
+        title: Critical Fullstack Rules
+        repeatable: true
+        template: "- **{{rule_name}}:** {{rule_description}}"
+        examples:
+          - "**Type Sharing:** Always define types in packages/shared and import from there"
+          - "**API Calls:** Never make direct HTTP calls - use the service layer"
+          - "**Environment Variables:** Access only through config objects, never process.env directly"
+          - "**Error Handling:** All API routes must use the standard error handler"
+          - "**State Updates:** Never mutate state directly - use proper state management patterns"
+      - id: naming-conventions
+        title: Naming Conventions
+        type: table
+        columns: [Element, Frontend, Backend, Example]
+        rows:
+          - ["Components", "PascalCase", "-", "`UserProfile.tsx`"]
+          - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"]
+          - ["API Routes", "-", "kebab-case", "`/api/user-profile`"]
+          - ["Database Tables", "-", "snake_case", "`user_profiles`"]
+
+  - id: error-handling
+    title: Error Handling Strategy
+    instruction: Define unified error handling across frontend and backend.
+    elicit: true
+    sections:
+      - id: error-flow
+        title: Error Flow
+        type: mermaid
+        mermaid_type: sequence
+        template: "{{error_flow_diagram}}"
+      - id: error-format
+        title: Error Response Format
+        type: code
+        language: typescript
+        template: |
+          interface ApiError {
+            error: {
+              code: string;
+              message: string;
+              details?: Record<string, any>;
+              timestamp: string;
+              requestId: string;
+            };
+          }
+      - id: frontend-error-handling
+        title: Frontend Error Handling
+        type: code
+        language: typescript
+        template: "{{frontend_error_handler}}"
+      - id: backend-error-handling
+        title: Backend Error Handling
+        type: code
+        language: typescript
+        template: "{{backend_error_handler}}"
+
+  - id: monitoring
+    title: Monitoring and Observability
+    instruction: Define monitoring strategy for fullstack application.
+    elicit: true
+    sections:
+      - id: monitoring-stack
+        title: Monitoring Stack
+        template: |
+          - **Frontend Monitoring:** {{frontend_monitoring}}
+          - **Backend Monitoring:** {{backend_monitoring}}
+          - **Error Tracking:** {{error_tracking}}
+          - **Performance Monitoring:** {{perf_monitoring}}
+      - id: key-metrics
+        title: Key Metrics
+        template: |
+          **Frontend Metrics:**
+          - Core Web Vitals
+          - JavaScript errors
+          - API response times
+          - User interactions
+          
+          **Backend Metrics:**
+          - Request rate
+          - Error rate
+          - Response time
+          - Database query performance
+
+  - id: checklist-results
+    title: Checklist Results Report
+    instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.

bmad-core/templates/market-research-tmpl.md

@@ -1,263 +0,0 @@
-# Market Research Report: {{Project/Product Name}}
-
-[[LLM: The default path and filename unless specified is docs/market-research.md]]
-
-[[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
-
-## Executive Summary
-
-{{Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.}}
-
-## Research Objectives & Methodology
-
-### Research Objectives
-
-{{List the primary objectives of this market research:
-
-- What decisions will this research inform?
-- What specific questions need to be answered?
-- What are the success criteria for this research?}}
-
-### Research Methodology
-
-{{Describe the research approach:
-
-- Data sources used (primary/secondary)
-- Analysis frameworks applied
-- Data collection timeframe
-- Limitations and assumptions}}
-
-## Market Overview
-
-### Market Definition
-
-{{Define the market being analyzed:
-
-- Product/service category
-- Geographic scope
-- Customer segments included
-- Value chain position}}
-
-### Market Size & Growth
-
-[[LLM: Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
-
-- Top-down: Start with industry data, narrow down
-- Bottom-up: Build from customer/unit economics
-- Value theory: Based on value provided vs. alternatives]]
-
-#### Total Addressable Market (TAM)
-
-{{Calculate and explain the total market opportunity}}
-
-#### Serviceable Addressable Market (SAM)
-
-{{Define the portion of TAM you can realistically reach}}
-
-#### Serviceable Obtainable Market (SOM)
-
-{{Estimate the portion you can realistically capture}}
-
-### Market Trends & Drivers
-
-[[LLM: Analyze key trends shaping the market using appropriate frameworks like PESTEL]]
-
-#### Key Market Trends
-
-{{List and explain 3-5 major trends:
-
-- Trend 1: Description and impact
-- Trend 2: Description and impact
-- etc.}}
-
-#### Growth Drivers
-
-{{Identify primary factors driving market growth}}
-
-#### Market Inhibitors
-
-{{Identify factors constraining market growth}}
-
-## Customer Analysis
-
-### Target Segment Profiles
-
-[[LLM: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay]]
-
-#### Segment 1: {{Segment Name}}
-
-- **Description:** {{Brief overview}}
-- **Size:** {{Number of customers/market value}}
-- **Characteristics:** {{Key demographics/firmographics}}
-- **Needs & Pain Points:** {{Primary problems they face}}
-- **Buying Process:** {{How they make purchasing decisions}}
-- **Willingness to Pay:** {{Price sensitivity and value perception}}
-
-<<REPEAT for each additional segment>>
-
-### Jobs-to-be-Done Analysis
-
-[[LLM: Uncover what customers are really trying to accomplish]]
-
-#### Functional Jobs
-
-{{List practical tasks and objectives customers need to complete}}
-
-#### Emotional Jobs
-
-{{Describe feelings and perceptions customers seek}}
-
-#### Social Jobs
-
-{{Explain how customers want to be perceived by others}}
-
-### Customer Journey Mapping
-
-[[LLM: Map the end-to-end customer experience for primary segments]]
-
-{{For primary customer segment:
-
-1. **Awareness:** How they discover solutions
-2. **Consideration:** Evaluation criteria and process
-3. **Purchase:** Decision triggers and barriers
-4. **Onboarding:** Initial experience expectations
-5. **Usage:** Ongoing interaction patterns
-6. **Advocacy:** Referral and expansion behaviors}}
-
-## Competitive Landscape
-
-### Market Structure
-
-{{Describe the overall competitive environment:
-
-- Number of competitors
-- Market concentration
-- Competitive intensity}}
-
-### Major Players Analysis
-
-{{For top 3-5 competitors:
-
-- Company name and brief description
-- Market share estimate
-- Key strengths and weaknesses
-- Target customer focus
-- Pricing strategy}}
-
-### Competitive Positioning
-
-{{Analyze how competitors are positioned:
-
-- Value propositions
-- Differentiation strategies
-- Market gaps and opportunities}}
-
-## Industry Analysis
-
-### Porter's Five Forces Assessment
-
-[[LLM: Analyze each force with specific evidence and implications]]
-
-#### Supplier Power: {{Low/Medium/High}}
-
-{{Analysis and implications}}
-
-#### Buyer Power: {{Low/Medium/High}}
-
-{{Analysis and implications}}
-
-#### Competitive Rivalry: {{Low/Medium/High}}
-
-{{Analysis and implications}}
-
-#### Threat of New Entry: {{Low/Medium/High}}
-
-{{Analysis and implications}}
-
-#### Threat of Substitutes: {{Low/Medium/High}}
-
-{{Analysis and implications}}
-
-### Technology Adoption Lifecycle Stage
-
-{{Identify where the market is in the adoption curve:
-
-- Current stage and evidence
-- Implications for strategy
-- Expected progression timeline}}
-
-## Opportunity Assessment
-
-### Market Opportunities
-
-[[LLM: Identify specific opportunities based on the analysis]]
-
-#### Opportunity 1: {{Name}}
-
-- **Description:** {{What is the opportunity?}}
-- **Size/Potential:** {{Quantify if possible}}
-- **Requirements:** {{What's needed to capture it?}}
-- **Risks:** {{Key challenges or barriers}}
-
-<<REPEAT for additional opportunities>>
-
-### Strategic Recommendations
-
-#### Go-to-Market Strategy
-
-{{Recommend approach for market entry/expansion:
-
-- Target segment prioritization
-- Positioning strategy
-- Channel strategy
-- Partnership opportunities}}
-
-#### Pricing Strategy
-
-{{Based on willingness to pay analysis and competitive landscape:
-
-- Recommended pricing model
-- Price points/ranges
-- Value metric
-- Competitive positioning}}
-
-#### Risk Mitigation
-
-{{Key risks and mitigation strategies:
-
-- Market risks
-- Competitive risks
-- Execution risks
-- Regulatory/compliance risks}}
-
-## Appendices
-
-### A. Data Sources
-
-{{List all sources used in the research}}
-
-### B. Detailed Calculations
-
-{{Include any complex calculations or models}}
-
-### C. Additional Analysis
-
-{{Any supplementary analysis not included in main body}}
-
----
-
-[[LLM: After completing the document, offer advanced elicitation with these custom options for market research:
-
-**Market Research Elicitation Actions** 0. Expand market sizing calculations with sensitivity analysis
-
-1. Deep dive into a specific customer segment
-2. Analyze an emerging market trend in detail
-3. Compare this market to an analogous market
-4. Stress test market assumptions
-5. Explore adjacent market opportunities
-6. Challenge market definition and boundaries
-7. Generate strategic scenarios (best/base/worst case)
-8. If only we had considered [X market factor]...
-9. Proceed to next section
-
-These replace the standard elicitation options when working on market research documents.]]

bmad-core/templates/market-research-tmpl.yaml

@@ -0,0 +1,252 @@
+template:
+  id: market-research-template-v2
+  name: Market Research Report
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/market-research.md
+    title: "Market Research Report: {{project_product_name}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Market Research Elicitation Actions"
+    options:
+      - "Expand market sizing calculations with sensitivity analysis"
+      - "Deep dive into a specific customer segment"
+      - "Analyze an emerging market trend in detail"
+      - "Compare this market to an analogous market"
+      - "Stress test market assumptions"
+      - "Explore adjacent market opportunities"
+      - "Challenge market definition and boundaries"
+      - "Generate strategic scenarios (best/base/worst case)"
+      - "If only we had considered [X market factor]..."
+      - "Proceed to next section"
+
+sections:
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.
+
+  - id: research-objectives
+    title: Research Objectives & Methodology
+    instruction: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.
+    sections:
+      - id: objectives
+        title: Research Objectives
+        instruction: |
+          List the primary objectives of this market research:
+          - What decisions will this research inform?
+          - What specific questions need to be answered?
+          - What are the success criteria for this research?
+      - id: methodology
+        title: Research Methodology
+        instruction: |
+          Describe the research approach:
+          - Data sources used (primary/secondary)
+          - Analysis frameworks applied
+          - Data collection timeframe
+          - Limitations and assumptions
+
+  - id: market-overview
+    title: Market Overview
+    sections:
+      - id: market-definition
+        title: Market Definition
+        instruction: |
+          Define the market being analyzed:
+          - Product/service category
+          - Geographic scope
+          - Customer segments included
+          - Value chain position
+      - id: market-size-growth
+        title: Market Size & Growth
+        instruction: |
+          Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
+          - Top-down: Start with industry data, narrow down
+          - Bottom-up: Build from customer/unit economics
+          - Value theory: Based on value provided vs. alternatives
+        sections:
+          - id: tam
+            title: Total Addressable Market (TAM)
+            instruction: Calculate and explain the total market opportunity
+          - id: sam
+            title: Serviceable Addressable Market (SAM)
+            instruction: Define the portion of TAM you can realistically reach
+          - id: som
+            title: Serviceable Obtainable Market (SOM)
+            instruction: Estimate the portion you can realistically capture
+      - id: market-trends
+        title: Market Trends & Drivers
+        instruction: Analyze key trends shaping the market using appropriate frameworks like PESTEL
+        sections:
+          - id: key-trends
+            title: Key Market Trends
+            instruction: |
+              List and explain 3-5 major trends:
+              - Trend 1: Description and impact
+              - Trend 2: Description and impact
+              - etc.
+          - id: growth-drivers
+            title: Growth Drivers
+            instruction: Identify primary factors driving market growth
+          - id: market-inhibitors
+            title: Market Inhibitors
+            instruction: Identify factors constraining market growth
+
+  - id: customer-analysis
+    title: Customer Analysis
+    sections:
+      - id: segment-profiles
+        title: Target Segment Profiles
+        instruction: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay
+        repeatable: true
+        sections:
+          - id: segment
+            title: "Segment {{segment_number}}: {{segment_name}}"
+            template: |
+              - **Description:** {{brief_overview}}
+              - **Size:** {{number_of_customers_market_value}}
+              - **Characteristics:** {{key_demographics_firmographics}}
+              - **Needs & Pain Points:** {{primary_problems}}
+              - **Buying Process:** {{purchasing_decisions}}
+              - **Willingness to Pay:** {{price_sensitivity}}
+      - id: jobs-to-be-done
+        title: Jobs-to-be-Done Analysis
+        instruction: Uncover what customers are really trying to accomplish
+        sections:
+          - id: functional-jobs
+            title: Functional Jobs
+            instruction: List practical tasks and objectives customers need to complete
+          - id: emotional-jobs
+            title: Emotional Jobs
+            instruction: Describe feelings and perceptions customers seek
+          - id: social-jobs
+            title: Social Jobs
+            instruction: Explain how customers want to be perceived by others
+      - id: customer-journey
+        title: Customer Journey Mapping
+        instruction: Map the end-to-end customer experience for primary segments
+        template: |
+          For primary customer segment:
+          
+          1. **Awareness:** {{discovery_process}}
+          2. **Consideration:** {{evaluation_criteria}}
+          3. **Purchase:** {{decision_triggers}}
+          4. **Onboarding:** {{initial_expectations}}
+          5. **Usage:** {{interaction_patterns}}
+          6. **Advocacy:** {{referral_behaviors}}
+
+  - id: competitive-landscape
+    title: Competitive Landscape
+    sections:
+      - id: market-structure
+        title: Market Structure
+        instruction: |
+          Describe the overall competitive environment:
+          - Number of competitors
+          - Market concentration
+          - Competitive intensity
+      - id: major-players
+        title: Major Players Analysis
+        instruction: |
+          For top 3-5 competitors:
+          - Company name and brief description
+          - Market share estimate
+          - Key strengths and weaknesses
+          - Target customer focus
+          - Pricing strategy
+      - id: competitive-positioning
+        title: Competitive Positioning
+        instruction: |
+          Analyze how competitors are positioned:
+          - Value propositions
+          - Differentiation strategies
+          - Market gaps and opportunities
+
+  - id: industry-analysis
+    title: Industry Analysis
+    sections:
+      - id: porters-five-forces
+        title: Porter's Five Forces Assessment
+        instruction: Analyze each force with specific evidence and implications
+        sections:
+          - id: supplier-power
+            title: "Supplier Power: {{power_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: buyer-power
+            title: "Buyer Power: {{power_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: competitive-rivalry
+            title: "Competitive Rivalry: {{intensity_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: threat-new-entry
+            title: "Threat of New Entry: {{threat_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: threat-substitutes
+            title: "Threat of Substitutes: {{threat_level}}"
+            template: "{{analysis_and_implications}}"
+      - id: adoption-lifecycle
+        title: Technology Adoption Lifecycle Stage
+        instruction: |
+          Identify where the market is in the adoption curve:
+          - Current stage and evidence
+          - Implications for strategy
+          - Expected progression timeline
+
+  - id: opportunity-assessment
+    title: Opportunity Assessment
+    sections:
+      - id: market-opportunities
+        title: Market Opportunities
+        instruction: Identify specific opportunities based on the analysis
+        repeatable: true
+        sections:
+          - id: opportunity
+            title: "Opportunity {{opportunity_number}}: {{name}}"
+            template: |
+              - **Description:** {{what_is_the_opportunity}}
+              - **Size/Potential:** {{quantified_potential}}
+              - **Requirements:** {{needed_to_capture}}
+              - **Risks:** {{key_challenges}}
+      - id: strategic-recommendations
+        title: Strategic Recommendations
+        sections:
+          - id: go-to-market
+            title: Go-to-Market Strategy
+            instruction: |
+              Recommend approach for market entry/expansion:
+              - Target segment prioritization
+              - Positioning strategy
+              - Channel strategy
+              - Partnership opportunities
+          - id: pricing-strategy
+            title: Pricing Strategy
+            instruction: |
+              Based on willingness to pay analysis and competitive landscape:
+              - Recommended pricing model
+              - Price points/ranges
+              - Value metric
+              - Competitive positioning
+          - id: risk-mitigation
+            title: Risk Mitigation
+            instruction: |
+              Key risks and mitigation strategies:
+              - Market risks
+              - Competitive risks
+              - Execution risks
+              - Regulatory/compliance risks
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: data-sources
+        title: A. Data Sources
+        instruction: List all sources used in the research
+      - id: calculations
+        title: B. Detailed Calculations
+        instruction: Include any complex calculations or models
+      - id: additional-analysis
+        title: C. Additional Analysis
+        instruction: Any supplementary analysis not included in main body

bmad-core/templates/prd-tmpl.md

@@ -1,202 +0,0 @@
-# {{Project Name}} Product Requirements Document (PRD)
-
-[[LLM: The default path and filename unless specified is docs/prd.md]]
-
-[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
-
-## Goals and Background Context
-
-[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
-
-### Goals
-
-[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
-
-### Background Context
-
-[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Requirements
-
-[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute {root}/tasks/advanced-elicitation.md display]]
-
-### Functional
-
-[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
-@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
-
-### Non Functional
-
-[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
-@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
-
-^^CONDITION: has_ui^^
-
-## User Interface Design Goals
-
-[[LLM: Capture high-level UI/UX vision to guide Design Architect and to inform story creation. Steps:
-
-1. Pre-fill all subsections with educated guesses based on project context
-2. Present the complete rendered section to user
-3. Clearly let the user know where assumptions were made
-4. Ask targeted questions for unclear/missing elements or areas needing more specification
-5. This is NOT detailed UI spec - focus on product vision and user goals
-6. After section completion, immediately apply `{root}/tasks/advanced-elicitation.md` protocol]]
-
-### Overall UX Vision
-
-### Key Interaction Paradigms
-
-### Core Screens and Views
-
-[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
-
-@{example}
-
-- Login Screen
-- Main Dashboard
-- Item Detail Page
-- Settings Page
-  @{/example}
-
-### Accessibility: { None, WCAG, etc }
-
-### Branding
-
-[[LLM: Any known branding elements or style guides that must be incorporated?]]
-
-@{example}
-
-- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
-- Attached is the full color pallet and tokens for our corporate branding.
-  @{/example}
-
-### Target Device and Platforms
-
-@{example}
-"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
-@{/example}
-
-^^/CONDITION: has_ui^^
-
-## Technical Assumptions
-
-[[LLM: Gather technical decisions that will guide the Architect. Steps:
-
-1. Check if `{root}/data/technical-preferences.yaml` or an attached `technical-preferences` file exists - use it to pre-populate choices
-2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
-3. For unknowns, offer guidance based on project goals and MVP scope
-4. Document ALL technical choices with rationale (why this choice fits the project)
-5. These become constraints for the Architect - be specific and complete
-6. After section completion, apply `{root}/tasks/advanced-elicitation.md` protocol.]]
-
-### Repository Structure: { Monorepo, Polyrepo, etc...}
-
-### Service Architecture
-
-[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
-
-### Testing requirements
-
-[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
-
-### Additional Technical Assumptions and Requests
-
-[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
-
-## Epics
-
-[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute {root}/tasks/advanced-elicitation.md display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
-
-CRITICAL: Epics MUST be logically sequential following agile best practices:
-
-- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
-- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page - remember this when we produce the stories for the first epic!
-- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
-- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
-- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
-- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
-
-<<REPEAT: epic_list>>
-
-- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
-
-<</REPEAT>>
-
-@{example: epic_list}
-
-1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
-2. Core Business Entities: Create and manage primary domain objects with CRUD operations
-3. User Workflows & Interactions: Enable key user journeys and business processes
-4. Reporting & Analytics: Provide insights and data visualization for users
-
-@{/example}
-
-[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute {root}/tasks/advanced-elicitation.md display, before moving on to the next epic.]]
-
-<<REPEAT: epic_details>>
-
-## Epic {{epic_number}} {{epic_title}}
-
-{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
-
-[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
-
-- Stories within each epic MUST be logically sequential
-- Each story should be a "vertical slice" delivering complete functionality aside from early enabler stories for project foundation
-- No story should depend on work from a later story or epic
-- Identify and note any direct prerequisite stories
-- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
-- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
-- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
-- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
-- If a story seems complex, break it down further as long as it can deliver a vertical slice
-- Each story should result in working, testable code before the agent's context window fills]]
-
-<<REPEAT: story>>
-
-### Story {{epic_number}}.{{story_number}} {{story_title}}
-
-As a {{user_type}},
-I want {{action}},
-so that {{benefit}}.
-
-#### Acceptance Criteria
-
-[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
-
-- Precisely define what "done" means from a functional perspective
-- Are unambiguous and serve as basis for verification
-- Include any critical non-functional requirements from the PRD
-- Consider local testability for backend/data components
-- Specify UI/UX requirements and framework adherence where applicable
-- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
-
-<<REPEAT: criteria>>
-
-- {{criterion number}}: {{criteria}}
-
-<</REPEAT>>
-<</REPEAT>>
-<</REPEAT>>
-
-## Checklist Results Report
-
-[[LLM: Before running the checklist and drafting the prompts, offer to output the full updated PRD. If outputting it, confirm with the user that you will be proceeding to run the checklist and produce the report. Once the user confirms, execute the `pm-checklist` and populate the results in this section.]]
-
-## Next Steps
-
-### Design Architect Prompt
-
-[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
-
-### Architect Prompt
-
-[[LLM: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]

bmad-core/templates/prd-tmpl.yaml

@@ -194,9 +194,9 @@ sections:
   - id: next-steps
     title: Next Steps
     sections:
-      - id: design-architect-prompt
-        title: Design Architect Prompt
-        instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.
+      - id: ux-expert-prompt
+        title: UX Expert Prompt
+        instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input.
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.

bmad-core/templates/project-brief-tmpl.md

@@ -1,232 +0,0 @@
----
-defaultOutput: docs/brief.md
----
-
-# Project Brief: {{Project Name}}
-
-[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
-
-Start by asking the user which mode they prefer:
-
-1. **Interactive Mode** - Work through each section collaboratively
-2. **YOLO Mode** - Generate complete draft for review and refinement
-
-Before beginning, understand what inputs are available (brainstorming results, market research, competitive analysis, initial ideas) and gather project context.]]
-
-## Executive Summary
-
-[[LLM: Create a concise overview that captures the essence of the project. Include:
-
-- Product concept in 1-2 sentences
-- Primary problem being solved
-- Target market identification
-- Key value proposition]]
-
-{{Write executive summary based on information gathered}}
-
-## Problem Statement
-
-[[LLM: Articulate the problem with clarity and evidence. Address:
-
-- Current state and pain points
-- Impact of the problem (quantify if possible)
-- Why existing solutions fall short
-- Urgency and importance of solving this now]]
-
-{{Detailed problem description with supporting evidence}}
-
-## Proposed Solution
-
-[[LLM: Describe the solution approach at a high level. Include:
-
-- Core concept and approach
-- Key differentiators from existing solutions
-- Why this solution will succeed where others haven't
-- High-level vision for the product]]
-
-{{Solution description focusing on the "what" and "why", not implementation details}}
-
-## Target Users
-
-[[LLM: Define and characterize the intended users with specificity. For each user segment include:
-
-- Demographic/firmographic profile
-- Current behaviors and workflows
-- Specific needs and pain points
-- Goals they're trying to achieve]]
-
-### Primary User Segment: {{Segment Name}}
-
-{{Detailed description of primary users}}
-
-### Secondary User Segment: {{Segment Name}}
-
-{{Description of secondary users if applicable}}
-
-## Goals & Success Metrics
-
-[[LLM: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)]]
-
-### Business Objectives
-
-- {{Objective 1 with metric}}
-- {{Objective 2 with metric}}
-- {{Objective 3 with metric}}
-
-### User Success Metrics
-
-- {{How users will measure value}}
-- {{Engagement metrics}}
-- {{Satisfaction indicators}}
-
-### Key Performance Indicators (KPIs)
-
-- {{KPI 1: Definition and target}}
-- {{KPI 2: Definition and target}}
-- {{KPI 3: Definition and target}}
-
-## MVP Scope
-
-[[LLM: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.]]
-
-### Core Features (Must Have)
-
-- **Feature 1:** {{Brief description and why it's essential}}
-- **Feature 2:** {{Brief description and why it's essential}}
-- **Feature 3:** {{Brief description and why it's essential}}
-
-### Out of Scope for MVP
-
-- {{Feature/capability explicitly not in MVP}}
-- {{Feature/capability to be considered post-MVP}}
-
-### MVP Success Criteria
-
-{{Define what constitutes a successful MVP launch}}
-
-## Post-MVP Vision
-
-[[LLM: Outline the longer-term product direction without overcommitting to specifics]]
-
-### Phase 2 Features
-
-{{Next priority features after MVP success}}
-
-### Long-term Vision
-
-{{Where this product could go in 1-2 years}}
-
-### Expansion Opportunities
-
-{{Potential new markets, use cases, or integrations}}
-
-## Technical Considerations
-
-[[LLM: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.]]
-
-### Platform Requirements
-
-- **Target Platforms:** {{Web, mobile, desktop, etc.}}
-- **Browser/OS Support:** {{Specific requirements}}
-- **Performance Requirements:** {{Load times, concurrent users, etc.}}
-
-### Technology Preferences
-
-- **Frontend:** {{If any preferences exist}}
-- **Backend:** {{If any preferences exist}}
-- **Database:** {{If any preferences exist}}
-- **Hosting/Infrastructure:** {{Cloud preferences, on-prem requirements}}
-
-### Architecture Considerations
-
-- **Repository Structure:** {{Initial thoughts on monorepo vs. polyrepo}}
-- **Service Architecture:** {{Initial thoughts on monolith vs. microservices}}
-- **Integration Requirements:** {{Third-party services, APIs}}
-- **Security/Compliance:** {{Any specific requirements}}
-
-## Constraints & Assumptions
-
-[[LLM: Clearly state limitations and assumptions to set realistic expectations]]
-
-### Constraints
-
-- **Budget:** {{If known}}
-- **Timeline:** {{Target launch date or development timeframe}}
-- **Resources:** {{Team size, skill constraints}}
-- **Technical:** {{Legacy systems, required tech stack}}
-
-### Key Assumptions
-
-- {{Assumption about users, market, or technology}}
-- {{Assumption about resources or support}}
-- {{Assumption about external dependencies}}
-
-## Risks & Open Questions
-
-[[LLM: Identify unknowns and potential challenges proactively]]
-
-### Key Risks
-
-- **Risk 1:** {{Description and potential impact}}
-- **Risk 2:** {{Description and potential impact}}
-- **Risk 3:** {{Description and potential impact}}
-
-### Open Questions
-
-- {{Question needing research or decision}}
-- {{Question about technical approach}}
-- {{Question about market or users}}
-
-### Areas Needing Further Research
-
-- {{Topic requiring deeper investigation}}
-- {{Validation needed before proceeding}}
-
-## Appendices
-
-### A. Research Summary
-
-{{If applicable, summarize key findings from:
-
-- Market research
-- Competitive analysis
-- User interviews
-- Technical feasibility studies}}
-
-### B. Stakeholder Input
-
-{{Key feedback or requirements from stakeholders}}
-
-### C. References
-
-{{Links to relevant documents, research, or examples}}
-
-## Next Steps
-
-### Immediate Actions
-
-1. {{First concrete next step}}
-2. {{Second concrete next step}}
-3. {{Third concrete next step}}
-
-### PM Handoff
-
-This Project Brief provides the full context for {{Project Name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-
----
-
-[[LLM: After completing each major section (not subsections), offer advanced elicitation with these custom options for project briefs:
-
-**Project Brief Elicitation Actions** 0. Expand section with more specific details
-
-1. Validate against similar successful products
-2. Stress test assumptions with edge cases
-3. Explore alternative solution approaches
-4. Analyze resource/constraint trade-offs
-5. Generate risk mitigation strategies
-6. Challenge scope from MVP minimalist view
-7. Brainstorm creative feature possibilities
-8. If only we had [resource/capability/time]...
-9. Proceed to next section
-
-These replace the standard elicitation options when working on project brief documents.]]

bmad-core/templates/project-brief-tmpl.yaml

@@ -0,0 +1,221 @@
+template:
+  id: project-brief-template-v2
+  name: Project Brief
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/brief.md
+    title: "Project Brief: {{project_name}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Project Brief Elicitation Actions"
+    options:
+      - "Expand section with more specific details"
+      - "Validate against similar successful products"
+      - "Stress test assumptions with edge cases"
+      - "Explore alternative solution approaches"
+      - "Analyze resource/constraint trade-offs"
+      - "Generate risk mitigation strategies"
+      - "Challenge scope from MVP minimalist view"
+      - "Brainstorm creative feature possibilities"
+      - "If only we had [resource/capability/time]..."
+      - "Proceed to next section"
+
+sections:
+  - id: introduction
+    instruction: |
+      This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
+      
+      Start by asking the user which mode they prefer:
+      
+      1. **Interactive Mode** - Work through each section collaboratively
+      2. **YOLO Mode** - Generate complete draft for review and refinement
+      
+      Before beginning, understand what inputs are available (brainstorming results, market research, competitive analysis, initial ideas) and gather project context.
+
+  - id: executive-summary
+    title: Executive Summary
+    instruction: |
+      Create a concise overview that captures the essence of the project. Include:
+      - Product concept in 1-2 sentences
+      - Primary problem being solved
+      - Target market identification
+      - Key value proposition
+    template: "{{executive_summary_content}}"
+
+  - id: problem-statement
+    title: Problem Statement
+    instruction: |
+      Articulate the problem with clarity and evidence. Address:
+      - Current state and pain points
+      - Impact of the problem (quantify if possible)
+      - Why existing solutions fall short
+      - Urgency and importance of solving this now
+    template: "{{detailed_problem_description}}"
+
+  - id: proposed-solution
+    title: Proposed Solution
+    instruction: |
+      Describe the solution approach at a high level. Include:
+      - Core concept and approach
+      - Key differentiators from existing solutions
+      - Why this solution will succeed where others haven't
+      - High-level vision for the product
+    template: "{{solution_description}}"
+
+  - id: target-users
+    title: Target Users
+    instruction: |
+      Define and characterize the intended users with specificity. For each user segment include:
+      - Demographic/firmographic profile
+      - Current behaviors and workflows
+      - Specific needs and pain points
+      - Goals they're trying to achieve
+    sections:
+      - id: primary-segment
+        title: "Primary User Segment: {{segment_name}}"
+        template: "{{primary_user_description}}"
+      - id: secondary-segment
+        title: "Secondary User Segment: {{segment_name}}"
+        condition: Has secondary user segment
+        template: "{{secondary_user_description}}"
+
+  - id: goals-metrics
+    title: Goals & Success Metrics
+    instruction: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
+    sections:
+      - id: business-objectives
+        title: Business Objectives
+        type: bullet-list
+        template: "- {{objective_with_metric}}"
+      - id: user-success-metrics
+        title: User Success Metrics
+        type: bullet-list
+        template: "- {{user_metric}}"
+      - id: kpis
+        title: Key Performance Indicators (KPIs)
+        type: bullet-list
+        template: "- {{kpi}}: {{definition_and_target}}"
+
+  - id: mvp-scope
+    title: MVP Scope
+    instruction: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.
+    sections:
+      - id: core-features
+        title: Core Features (Must Have)
+        type: bullet-list
+        template: "- **{{feature}}:** {{description_and_rationale}}"
+      - id: out-of-scope
+        title: Out of Scope for MVP
+        type: bullet-list
+        template: "- {{feature_or_capability}}"
+      - id: mvp-success-criteria
+        title: MVP Success Criteria
+        template: "{{mvp_success_definition}}"
+
+  - id: post-mvp-vision
+    title: Post-MVP Vision
+    instruction: Outline the longer-term product direction without overcommitting to specifics
+    sections:
+      - id: phase-2-features
+        title: Phase 2 Features
+        template: "{{next_priority_features}}"
+      - id: long-term-vision
+        title: Long-term Vision
+        template: "{{one_two_year_vision}}"
+      - id: expansion-opportunities
+        title: Expansion Opportunities
+        template: "{{potential_expansions}}"
+
+  - id: technical-considerations
+    title: Technical Considerations
+    instruction: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.
+    sections:
+      - id: platform-requirements
+        title: Platform Requirements
+        template: |
+          - **Target Platforms:** {{platforms}}
+          - **Browser/OS Support:** {{specific_requirements}}
+          - **Performance Requirements:** {{performance_specs}}
+      - id: technology-preferences
+        title: Technology Preferences
+        template: |
+          - **Frontend:** {{frontend_preferences}}
+          - **Backend:** {{backend_preferences}}
+          - **Database:** {{database_preferences}}
+          - **Hosting/Infrastructure:** {{infrastructure_preferences}}
+      - id: architecture-considerations
+        title: Architecture Considerations
+        template: |
+          - **Repository Structure:** {{repo_thoughts}}
+          - **Service Architecture:** {{service_thoughts}}
+          - **Integration Requirements:** {{integration_needs}}
+          - **Security/Compliance:** {{security_requirements}}
+
+  - id: constraints-assumptions
+    title: Constraints & Assumptions
+    instruction: Clearly state limitations and assumptions to set realistic expectations
+    sections:
+      - id: constraints
+        title: Constraints
+        template: |
+          - **Budget:** {{budget_info}}
+          - **Timeline:** {{timeline_info}}
+          - **Resources:** {{resource_info}}
+          - **Technical:** {{technical_constraints}}
+      - id: key-assumptions
+        title: Key Assumptions
+        type: bullet-list
+        template: "- {{assumption}}"
+
+  - id: risks-questions
+    title: Risks & Open Questions
+    instruction: Identify unknowns and potential challenges proactively
+    sections:
+      - id: key-risks
+        title: Key Risks
+        type: bullet-list
+        template: "- **{{risk}}:** {{description_and_impact}}"
+      - id: open-questions
+        title: Open Questions
+        type: bullet-list
+        template: "- {{question}}"
+      - id: research-areas
+        title: Areas Needing Further Research
+        type: bullet-list
+        template: "- {{research_topic}}"
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: research-summary
+        title: A. Research Summary
+        condition: Has research findings
+        instruction: |
+          If applicable, summarize key findings from:
+          - Market research
+          - Competitive analysis
+          - User interviews
+          - Technical feasibility studies
+      - id: stakeholder-input
+        title: B. Stakeholder Input
+        condition: Has stakeholder feedback
+        template: "{{stakeholder_feedback}}"
+      - id: references
+        title: C. References
+        template: "{{relevant_links_and_docs}}"
+
+  - id: next-steps
+    title: Next Steps
+    sections:
+      - id: immediate-actions
+        title: Immediate Actions
+        type: numbered-list
+        template: "{{action_item}}"
+      - id: pm-handoff
+        title: PM Handoff
+        content: |
+          This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.

bmad-core/templates/story-tmpl.md

@@ -1,58 +0,0 @@
----
-defaultOutput: docs/stories/{{EpicNum}}.{{StoryNum}}.{{Short Title Copied from Epic File specific story}}.md
-smAgent:
-  editableSections: Status, Story, Acceptance Criteria, Tasks / Subtasks, Dev Notes, Testing, Change Log
-  sectionSpecificInstructions:
-    "Dev Notes":
-      - Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story
-      - Do not invent information.
-      - If known add Relevant Source Tree info that relates to this story.
-      - If there were important notes from previous story that are relevant to this one, include them here.
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story,  meeting all AC and completing all tasks+subtasks.
-    Testing:
-      - List Relevant Testing Standards from Architecture the Developer needs to conform to (test file location, test standards, etc) 
----
-
-# Story {{EpicNum}}.{{StoryNum}}: {{Short Title Copied from Epic File specific story}}
-
-## Status: {{ Draft | Approved | InProgress | Review | Done }}
-
-## Story
-
-**As a** {{role}},\
-**I want** {{action}},\
-**so that** {{benefit}}
-
-## Acceptance Criteria
-
-{{ Copy of Acceptance Criteria numbered list }}
-
-## Tasks / Subtasks
-
-- [ ] Task 1 (AC: # if applicable)
-  - [ ] Subtask1.1...
-- [ ] Task 2 (AC: # if applicable)
-  - [ ] Subtask 2.1...
-- [ ] Task 3 (AC: # if applicable)
-  - [ ] Subtask 3.1...
-
-## Dev Notes
-
-### Testing
-
-## Change Log
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Dev Agent Record
-
-### Agent Model Used: {{Agent Model Name/Version}}
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List
-
-## QA Results

bmad-core/templates/story-tmpl.yaml

@@ -0,0 +1,137 @@
+template:
+  id: story-template-v2
+  name: Story Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+agent_config:
+  editable_sections: 
+    - Status
+    - Story
+    - Acceptance Criteria
+    - Tasks / Subtasks
+    - Dev Notes
+    - Testing
+    - Change Log
+
+sections:
+  - id: status
+    title: Status
+    type: choice
+    choices: [Draft, Approved, InProgress, Review, Done]
+    instruction: Select the current status of the story
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: story
+    title: Story
+    type: template-text
+    template: |
+      **As a** {{role}},
+      **I want** {{action}},
+      **so that** {{benefit}}
+    instruction: Define the user story using the standard format with role, action, and benefit
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    type: numbered-list
+    instruction: Copy the acceptance criteria numbered list from the epic file
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: tasks-subtasks
+    title: Tasks / Subtasks
+    type: bullet-list
+    instruction: |
+      Break down the story into specific tasks and subtasks needed for implementation.
+      Reference applicable acceptance criteria numbers where relevant.
+    template: |
+      - [ ] Task 1 (AC: # if applicable)
+        - [ ] Subtask1.1...
+      - [ ] Task 2 (AC: # if applicable)
+        - [ ] Subtask 2.1...
+      - [ ] Task 3 (AC: # if applicable)
+        - [ ] Subtask 3.1...
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: dev-notes
+    title: Dev Notes
+    instruction: |
+      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
+      - Do not invent information
+      - If known add Relevant Source Tree info that relates to this story
+      - If there were important notes from previous story that are relevant to this one, include them here
+      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    sections:
+      - id: testing-standards
+        title: Testing
+        instruction: |
+          List Relevant Testing Standards from Architecture the Developer needs to conform to:
+          - Test file location
+          - Test standards
+          - Testing frameworks and patterns to use
+          - Any specific testing requirements for this story
+        elicit: true
+        owner: scrum-master
+        editors: [scrum-master]
+        
+  - id: change-log
+    title: Change Log
+    type: table
+    columns: [Date, Version, Description, Author]
+    instruction: Track changes made to this story document
+    owner: scrum-master
+    editors: [scrum-master, dev-agent, qa-agent]
+    
+  - id: dev-agent-record
+    title: Dev Agent Record
+    instruction: This section is populated by the development agent during implementation
+    owner: dev-agent
+    editors: [dev-agent]
+    sections:
+      - id: agent-model
+        title: Agent Model Used
+        template: "{{agent_model_name_version}}"
+        instruction: Record the specific AI agent model and version used for development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: debug-log-references
+        title: Debug Log References
+        instruction: Reference any debug logs or traces generated during development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: completion-notes
+        title: Completion Notes List
+        instruction: Notes about the completion of tasks and any issues encountered
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: file-list
+        title: File List
+        instruction: List all files created, modified, or affected during story implementation
+        owner: dev-agent
+        editors: [dev-agent]
+        
+  - id: qa-results
+    title: QA Results
+    instruction: Results from QA Agent QA review of the completed story implementation
+    owner: qa-agent
+    editors: [qa-agent]

common/tasks/create-doc.md

@@ -1,91 +1,79 @@
-# Create Document from Template Task
+# Create Document from Template (YAML Driven)
 
-## Purpose
+## CRITICAL: Mandatory Elicitation Format
 
-Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
+**When `elicit: true`, ALWAYS use this exact format:**
 
-## CRITICAL RULES
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. Present numbered options 1-9:
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
 
-1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
-2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
-3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
-4. **WAIT for user input** - At review points and after elicitation tasks
+**NEVER ask yes/no questions or use any other format.**
 
-## Execution Flow
+## Processing Flow
 
-### 0. Check Workflow Plan (if configured)
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
 
-[[LLM: Check if plan tracking is enabled in core-config.yaml]]
+## Detailed Rationale Requirements
 
-- If `workflow.trackProgress: true`, check for active plan using {root}/utils/plan-management.md
-- If plan exists and this document creation is part of the plan:
-  - Verify this is the expected next step
-  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
-  - If out of sequence and `enforceSequence: false`, ask for confirmation
-- Continue with normal execution after plan check
+When presenting section content, ALWAYS include rationale that explains:
 
-### 1. Identify Template
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
 
-- Load from `{root}/templates/*.md` or `{root}/templates directory`
-- Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
+## Elicitation Results Flow
 
-### 2. Ask Interaction Mode
+After user selects elicitation method (2-9):
 
-> 1. **Incremental** - Section by section with reviews
-> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
 
-### 3. Execute Template
+## Agent Permissions
 
-- Replace {{placeholders}} with real content
-- Execute [[LLM:]] instructions as you encounter them
-- Process <<REPEAT>> loops and ^^CONDITIONS^^
-- Use @{examples} for guidance but never output them
+When processing sections with agent permission fields:
 
-### 4. Key Execution Patterns
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
 
-**When you see:** `[[LLM: Draft X and immediately execute {root}/tasks/advanced-elicitation.md]]`
+**For sections with restricted access:**
 
-- Draft the content
-- Present it to user
-- IMMEDIATELY execute the task
-- Wait for completion before continuing
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
 
-**When you see:** `[[LLM: After section completion, apply {root}/tasks/Y.md]]`
+## YOLO Mode
 
-- Finish the section
-- STOP and execute the task
-- Wait for user input
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 
-### 5. Validation & Final Presentation
+## CRITICAL REMINDERS
 
-- Run any specified checklists
-- Present clean, formatted content only
-- No truncation or summarization
-- Begin directly with content (no preamble)
-- Include any handoff prompts from template
+**❌ NEVER:**
 
-### 6. Update Workflow Plan (if applicable)
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
 
-[[LLM: After successful document creation]]
+**✅ ALWAYS:**
 
-- If plan tracking is enabled and document was part of plan:
-  - Call update-workflow-plan task to mark step complete
-  - Parameters: task: create-doc, step_id: {from plan}, status: complete
-  - Show next recommended step from plan
-
-## Common Mistakes to Avoid
-
-❌ Skipping elicitation tasks
-❌ Showing template markup to users
-❌ Continuing past STOP signals
-❌ Combining multiple review points
-
-✅ Execute ALL instructions in sequence
-✅ Present only clean, formatted content
-✅ Stop at every elicitation point
-✅ Wait for user confirmation when instructed
-
-## Remember
-
-Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"

common/tasks/create-doc2.md

@@ -1,65 +0,0 @@
-# Create Document from Template (YAML Driven)
-
-## CRITICAL: Mandatory Elicitation Format
-
-**When `elicit: true`, ALWAYS use this exact format:**
-
-1. Present section content
-2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
-3. Present numbered options 1-9:
-   - **Option 1:** Always "Proceed to next section"
-   - **Options 2-9:** Select 8 methods from data/elicitation-methods
-   - End with: "Select 1-9 or just type your question/feedback:"
-
-**NEVER ask yes/no questions or use any other format.**
-
-## Processing Flow
-
-1. **Parse YAML template** - Load template metadata and sections
-2. **Set preferences** - Show current mode (Interactive), confirm output file
-3. **Process each section:**
-   - Skip if condition unmet
-   - Draft content using section instruction
-   - Present content + detailed rationale
-   - **IF elicit: true** → MANDATORY 1-9 options format
-   - Save to file if possible
-4. **Continue until complete**
-
-## Detailed Rationale Requirements
-
-When presenting section content, ALWAYS include rationale that explains:
-
-- Trade-offs and choices made (what was chosen over alternatives and why)
-- Key assumptions made during drafting
-- Interesting or questionable decisions that need user attention
-- Areas that might need validation
-
-## Elicitation Results Flow
-
-After user selects elicitation method (2-9):
-
-1. Execute method from data/elicitation-methods
-2. Present results with insights
-3. Offer options:
-   - **1. Apply changes and update section**
-   - **2. Return to elicitation menu**
-   - **3. Ask any questions or engage further with this elicitation**
-
-## YOLO Mode
-
-User can type `#yolo` to toggle to YOLO mode (process all sections at once).
-
-## CRITICAL REMINDERS
-
-**❌ NEVER:**
-
-- Ask yes/no questions for elicitation
-- Use any format other than 1-9 numbered options
-- Create new elicitation methods
-
-**✅ ALWAYS:**
-
-- Use exact 1-9 format when elicit: true
-- Select options 2-9 from data/elicitation-methods only
-- Provide detailed rationale explaining decisions
-- End with "Select 1-9 or just type your question/feedback:"

common/utils/bmad-doc-template.md

@@ -67,6 +67,12 @@ sections:
 - **repeatable**: Boolean - Section can be repeated multiple times
 - **condition**: String - Condition for including section (e.g., "has ui requirements")
 
+#### Agent Permissions
+
+- **owner**: String - Agent role that initially creates/populates this section
+- **editors**: Array - List of agent roles allowed to modify this section
+- **readonly**: Boolean - Section cannot be modified after initial creation
+
 #### Content Guidance
 
 - **examples**: Array of example content (not included in output)
@@ -169,6 +175,29 @@ choices:
 - `block` - Block diagrams
 - `kanban` - Kanban boards
 
+### Agent Permissions Example
+
+```yaml
+- id: story-details
+  title: Story
+  owner: scrum-master
+  editors: [scrum-master]
+  readonly: false
+  sections:
+    - id: dev-notes
+      title: Dev Notes
+      owner: dev-agent
+      editors: [dev-agent]
+      readonly: false
+      instruction: Implementation notes and technical details
+    - id: qa-results
+      title: QA Results
+      owner: qa-agent
+      editors: [qa-agent]
+      readonly: true
+      instruction: Quality assurance test results
+```
+
 ### Repeatable Sections
 
 ```yaml

dist/agents/bmad-orchestrator.txt

@@ -45,6 +45,15 @@ These references map directly to bundle sections:
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+activation-instructions:
+  - Mention *help shows all available commands and options
+  - Check for active workflow plan using .bmad-core/utils/plan-management.md
+  - 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
+  - 'If plan exists: Suggest next action based on plan progress'
+  - Assess user goal against available agents and workflows in this bundle
+  - If clear match to an agent's expertise, suggest transformation with *agent command
+  - If project-oriented, suggest *workflow-guidance to explore options
+  - Load resources only when needed - never pre-load
 agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
@@ -66,17 +75,6 @@ persona:
     - Always use numbered lists for choices
     - Process commands starting with * immediately
     - Always remind users that commands require * prefix
-startup:
-  - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
-  - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
-  - Mention *help shows all available commands and options
-  - Check for active workflow plan using .bmad-core/utils/plan-management.md
-  - 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
-  - 'If plan exists: Suggest next action based on plan progress'
-  - Assess user goal against available agents and workflows in this bundle
-  - If clear match to an agent's expertise, suggest transformation with *agent command
-  - If project-oriented, suggest *workflow-guidance to explore options
-  - Load resources only when needed - never pre-load
 commands:
   help: Show this guide with available agents and workflows
   chat-mode: Start conversational mode for detailed assistance
@@ -164,17 +162,18 @@ workflow-guidance:
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
 dependencies:
   tasks:
-    - advanced-elicitation
-    - create-doc
-    - create-workflow-plan
-    - kb-mode-interaction
-    - update-workflow-plan
+    - advanced-elicitation.md
+    - create-doc.md
+    - create-workflow-plan.md
+    - kb-mode-interaction.md
+    - update-workflow-plan.md
   data:
-    - bmad-kb
+    - bmad-kb.md
+    - elicitation-methods.md
   utils:
-    - plan-management
-    - workflow-management
-    - template-format
+    - plan-management.md
+    - workflow-management.md
+    - template-format.md
 ```
 ==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
 
@@ -299,97 +298,85 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-core/tasks/create-doc.md ====================
-# Create Document from Template Task
+# Create Document from Template (YAML Driven)
 
-## Purpose
+## CRITICAL: Mandatory Elicitation Format
 
-Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
+**When `elicit: true`, ALWAYS use this exact format:**
 
-## CRITICAL RULES
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. Present numbered options 1-9:
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
 
-1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
-2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
-3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
-4. **WAIT for user input** - At review points and after elicitation tasks
+**NEVER ask yes/no questions or use any other format.**
 
-## Execution Flow
+## Processing Flow
 
-### 0. Check Workflow Plan (if configured)
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
 
-[[LLM: Check if plan tracking is enabled in core-config.yaml]]
+## Detailed Rationale Requirements
 
-- If `workflow.trackProgress: true`, check for active plan using .bmad-core/utils/plan-management.md
-- If plan exists and this document creation is part of the plan:
-  - Verify this is the expected next step
-  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
-  - If out of sequence and `enforceSequence: false`, ask for confirmation
-- Continue with normal execution after plan check
+When presenting section content, ALWAYS include rationale that explains:
 
-### 1. Identify Template
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
 
-- Load from `.bmad-core/templates/*.md` or `.bmad-core/templates directory`
-- Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
+## Elicitation Results Flow
 
-### 2. Ask Interaction Mode
+After user selects elicitation method (2-9):
 
-> 1. **Incremental** - Section by section with reviews
-> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
 
-### 3. Execute Template
+## Agent Permissions
 
-- Replace {{placeholders}} with real content
-- Execute [[LLM:]] instructions as you encounter them
-- Process <<REPEAT>> loops and ^^CONDITIONS^^
-- Use @{examples} for guidance but never output them
+When processing sections with agent permission fields:
 
-### 4. Key Execution Patterns
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
 
-**When you see:** `[[LLM: Draft X and immediately execute .bmad-core/tasks/advanced-elicitation.md]]`
+**For sections with restricted access:**
 
-- Draft the content
-- Present it to user
-- IMMEDIATELY execute the task
-- Wait for completion before continuing
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
 
-**When you see:** `[[LLM: After section completion, apply .bmad-core/tasks/Y.md]]`
+## YOLO Mode
 
-- Finish the section
-- STOP and execute the task
-- Wait for user input
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 
-### 5. Validation & Final Presentation
+## CRITICAL REMINDERS
 
-- Run any specified checklists
-- Present clean, formatted content only
-- No truncation or summarization
-- Begin directly with content (no preamble)
-- Include any handoff prompts from template
+**❌ NEVER:**
 
-### 6. Update Workflow Plan (if applicable)
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
 
-[[LLM: After successful document creation]]
+**✅ ALWAYS:**
 
-- If plan tracking is enabled and document was part of plan:
-  - Call update-workflow-plan task to mark step complete
-  - Parameters: task: create-doc, step_id: {from plan}, status: complete
-  - Show next recommended step from plan
-
-## Common Mistakes to Avoid
-
-❌ Skipping elicitation tasks
-❌ Showing template markup to users
-❌ Continuing past STOP signals
-❌ Combining multiple review points
-
-✅ Execute ALL instructions in sequence
-✅ Present only clean, formatted content
-✅ Stop at every elicitation point
-✅ Wait for user confirmation when instructed
-
-## Remember
-
-Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"
 ==================== END: .bmad-core/tasks/create-doc.md ====================
 
 ==================== START: .bmad-core/tasks/create-workflow-plan.md ====================
@@ -1821,6 +1808,143 @@ Use the **expansion-creator** pack to build your own:
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
 ==================== END: .bmad-core/data/bmad-kb.md ====================
 
+==================== START: .bmad-core/data/elicitation-methods.md ====================
+# Elicitation Methods Data
+
+## Core Reflective Methods
+
+**Expand or Contract for Audience**
+- Ask whether to 'expand' (add detail, elaborate) or 'contract' (simplify, clarify)
+- Identify specific target audience if relevant
+- Tailor content complexity and depth accordingly
+
+**Explain Reasoning (CoT Step-by-Step)**
+- Walk through the step-by-step thinking process
+- Reveal underlying assumptions and decision points
+- Show how conclusions were reached from current role's perspective
+
+**Critique and Refine**
+- Review output for flaws, inconsistencies, or improvement areas
+- Identify specific weaknesses from role's expertise
+- Suggest refined version reflecting domain knowledge
+
+## Structural Analysis Methods
+
+**Analyze Logical Flow and Dependencies**
+- Examine content structure for logical progression
+- Check internal consistency and coherence
+- Identify and validate dependencies between elements
+- Confirm effective ordering and sequencing
+
+**Assess Alignment with Overall Goals**
+- Evaluate content contribution to stated objectives
+- Identify any misalignments or gaps
+- Interpret alignment from specific role's perspective
+- Suggest adjustments to better serve goals
+
+## Risk and Challenge Methods
+
+**Identify Potential Risks and Unforeseen Issues**
+- Brainstorm potential risks from role's expertise
+- Identify overlooked edge cases or scenarios
+- Anticipate unintended consequences
+- Highlight implementation challenges
+
+**Challenge from Critical Perspective**
+- Adopt critical stance on current content
+- Play devil's advocate from specified viewpoint
+- Argue against proposal highlighting weaknesses
+- Apply YAGNI principles when appropriate (scope trimming)
+
+## Creative Exploration Methods
+
+**Tree of Thoughts Deep Dive**
+- Break problem into discrete "thoughts" or intermediate steps
+- Explore multiple reasoning paths simultaneously
+- Use self-evaluation to classify each path as "sure", "likely", or "impossible"
+- Apply search algorithms (BFS/DFS) to find optimal solution paths
+
+**Hindsight is 20/20: The 'If Only...' Reflection**
+- Imagine retrospective scenario based on current content
+- Identify the one "if only we had known/done X..." insight
+- Describe imagined consequences humorously or dramatically
+- Extract actionable learnings for current context
+
+## Multi-Persona Collaboration Methods
+
+**Agile Team Perspective Shift**
+- Rotate through different Scrum team member viewpoints
+- Product Owner: Focus on user value and business impact
+- Scrum Master: Examine process flow and team dynamics
+- Developer: Assess technical implementation and complexity
+- QA: Identify testing scenarios and quality concerns
+
+**Stakeholder Round Table**
+- Convene virtual meeting with multiple personas
+- Each persona contributes unique perspective on content
+- Identify conflicts and synergies between viewpoints
+- Synthesize insights into actionable recommendations
+
+**Meta-Prompting Analysis**
+- Step back to analyze the structure and logic of current approach
+- Question the format and methodology being used
+- Suggest alternative frameworks or mental models
+- Optimize the elicitation process itself
+
+## Advanced 2025 Techniques
+
+**Self-Consistency Validation**
+- Generate multiple reasoning paths for same problem
+- Compare consistency across different approaches
+- Identify most reliable and robust solution
+- Highlight areas where approaches diverge and why
+
+**ReWOO (Reasoning Without Observation)**
+- Separate parametric reasoning from tool-based actions
+- Create reasoning plan without external dependencies
+- Identify what can be solved through pure reasoning
+- Optimize for efficiency and reduced token usage
+
+**Persona-Pattern Hybrid**
+- Combine specific role expertise with elicitation pattern
+- Architect + Risk Analysis: Deep technical risk assessment
+- UX Expert + User Journey: End-to-end experience critique
+- PM + Stakeholder Analysis: Multi-perspective impact review
+
+**Emergent Collaboration Discovery**
+- Allow multiple perspectives to naturally emerge
+- Identify unexpected insights from persona interactions
+- Explore novel combinations of viewpoints
+- Capture serendipitous discoveries from multi-agent thinking
+
+## Game-Based Elicitation Methods
+
+**Red Team vs Blue Team**
+- Red Team: Attack the proposal, find vulnerabilities
+- Blue Team: Defend and strengthen the approach
+- Competitive analysis reveals blind spots
+- Results in more robust, battle-tested solutions
+
+**Innovation Tournament**
+- Pit multiple alternative approaches against each other
+- Score each approach across different criteria
+- Crowd-source evaluation from different personas
+- Identify winning combination of features
+
+**Escape Room Challenge**
+- Present content as constraints to work within
+- Find creative solutions within tight limitations
+- Identify minimum viable approach
+- Discover innovative workarounds and optimizations
+
+## Process Control
+
+**Proceed / No Further Actions**
+- Acknowledge choice to finalize current work
+- Accept output as-is or move to next step
+- Prepare to continue without additional elicitation
+==================== END: .bmad-core/data/elicitation-methods.md ====================
+
 ==================== START: .bmad-core/utils/plan-management.md ====================
 # Plan Management Utility
 

dist/agents/dev.txt

@@ -45,6 +45,7 @@ These references map directly to bundle sections:
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+activation-instructions: []
 agent:
   name: James
   id: dev
@@ -52,11 +53,6 @@ agent:
   icon: 💻
   whenToUse: Use for code implementation, debugging, refactoring, and development best practices
   customization: null
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - .bmad-core/core-config.yaml devLoadAlwaysFiles list
-  - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
-  - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -83,10 +79,10 @@ develop-story:
   completion: 'All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON''T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: ''Ready for Review''→HALT'
 dependencies:
   tasks:
-    - execute-checklist
-    - validate-next-story
+    - execute-checklist.md
+    - validate-next-story.md
   checklists:
-    - story-dod-checklist
+    - story-dod-checklist.md
 ```
 ==================== END: .bmad-core/agents/dev.md ====================
 

dist/agents/po.txt

@@ -50,6 +50,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Sarah
   id: po
@@ -73,8 +74,6 @@ persona:
     - User Collaboration for Validation - Seek input at critical checkpoints
     - Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 commands:
   - help: Show numbered list of the following commands to allow selection
   - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
@@ -89,19 +88,17 @@ commands:
   - exit: Exit (confirm)
 dependencies:
   tasks:
-    - execute-checklist
-    - shard-doc
-    - correct-course
-    - brownfield-create-epic
-    - brownfield-create-story
-    - validate-next-story
+    - execute-checklist.md
+    - shard-doc.md
+    - correct-course.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
+    - validate-next-story.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - po-master-checklist
-    - change-checklist
-  utils:
-    - template-format
+    - po-master-checklist.md
+    - change-checklist.md
 ```
 ==================== END: .bmad-core/agents/po.md ====================
 
@@ -921,66 +918,145 @@ Provide a structured validation report including:
 - **Confidence Level**: High/Medium/Low for successful implementation
 ==================== END: .bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.md ====================
----
-defaultOutput: docs/stories/{{EpicNum}}.{{StoryNum}}.{{Short Title Copied from Epic File specific story}}.md
-smAgent:
-  editableSections: Status, Story, Acceptance Criteria, Tasks / Subtasks, Dev Notes, Testing, Change Log
-  sectionSpecificInstructions:
-    "Dev Notes":
-      - Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story
-      - Do not invent information.
-      - If known add Relevant Source Tree info that relates to this story.
-      - If there were important notes from previous story that are relevant to this one, include them here.
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story,  meeting all AC and completing all tasks+subtasks.
-    Testing:
-      - List Relevant Testing Standards from Architecture the Developer needs to conform to (test file location, test standards, etc) 
----
+==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+template:
+  id: story-template-v2
+  name: Story Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
 
-# Story {{EpicNum}}.{{StoryNum}}: {{Short Title Copied from Epic File specific story}}
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
 
-## Status: {{ Draft | Approved | InProgress | Review | Done }}
+agent_config:
+  editable_sections: 
+    - Status
+    - Story
+    - Acceptance Criteria
+    - Tasks / Subtasks
+    - Dev Notes
+    - Testing
+    - Change Log
 
-## Story
-
-**As a** {{role}},\
-**I want** {{action}},\
-**so that** {{benefit}}
-
-## Acceptance Criteria
-
-{{ Copy of Acceptance Criteria numbered list }}
-
-## Tasks / Subtasks
-
-- [ ] Task 1 (AC: # if applicable)
-  - [ ] Subtask1.1...
-- [ ] Task 2 (AC: # if applicable)
-  - [ ] Subtask 2.1...
-- [ ] Task 3 (AC: # if applicable)
-  - [ ] Subtask 3.1...
-
-## Dev Notes
-
-### Testing
-
-## Change Log
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Dev Agent Record
-
-### Agent Model Used: {{Agent Model Name/Version}}
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List
-
-## QA Results
-==================== END: .bmad-core/templates/story-tmpl.md ====================
+sections:
+  - id: status
+    title: Status
+    type: choice
+    choices: [Draft, Approved, InProgress, Review, Done]
+    instruction: Select the current status of the story
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: story
+    title: Story
+    type: template-text
+    template: |
+      **As a** {{role}},
+      **I want** {{action}},
+      **so that** {{benefit}}
+    instruction: Define the user story using the standard format with role, action, and benefit
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    type: numbered-list
+    instruction: Copy the acceptance criteria numbered list from the epic file
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: tasks-subtasks
+    title: Tasks / Subtasks
+    type: bullet-list
+    instruction: |
+      Break down the story into specific tasks and subtasks needed for implementation.
+      Reference applicable acceptance criteria numbers where relevant.
+    template: |
+      - [ ] Task 1 (AC: # if applicable)
+        - [ ] Subtask1.1...
+      - [ ] Task 2 (AC: # if applicable)
+        - [ ] Subtask 2.1...
+      - [ ] Task 3 (AC: # if applicable)
+        - [ ] Subtask 3.1...
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: dev-notes
+    title: Dev Notes
+    instruction: |
+      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
+      - Do not invent information
+      - If known add Relevant Source Tree info that relates to this story
+      - If there were important notes from previous story that are relevant to this one, include them here
+      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    sections:
+      - id: testing-standards
+        title: Testing
+        instruction: |
+          List Relevant Testing Standards from Architecture the Developer needs to conform to:
+          - Test file location
+          - Test standards
+          - Testing frameworks and patterns to use
+          - Any specific testing requirements for this story
+        elicit: true
+        owner: scrum-master
+        editors: [scrum-master]
+        
+  - id: change-log
+    title: Change Log
+    type: table
+    columns: [Date, Version, Description, Author]
+    instruction: Track changes made to this story document
+    owner: scrum-master
+    editors: [scrum-master, dev-agent, qa-agent]
+    
+  - id: dev-agent-record
+    title: Dev Agent Record
+    instruction: This section is populated by the development agent during implementation
+    owner: dev-agent
+    editors: [dev-agent]
+    sections:
+      - id: agent-model
+        title: Agent Model Used
+        template: "{{agent_model_name_version}}"
+        instruction: Record the specific AI agent model and version used for development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: debug-log-references
+        title: Debug Log References
+        instruction: Reference any debug logs or traces generated during development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: completion-notes
+        title: Completion Notes List
+        instruction: Notes about the completion of tasks and any issues encountered
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: file-list
+        title: File List
+        instruction: List all files created, modified, or affected during story implementation
+        owner: dev-agent
+        editors: [dev-agent]
+        
+  - id: qa-results
+    title: QA Results
+    instruction: Results from QA Agent QA review of the completed story implementation
+    owner: qa-agent
+    editors: [qa-agent]
+==================== END: .bmad-core/templates/story-tmpl.yaml ====================
 
 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 # Product Owner (PO) Master Validation Checklist
@@ -1610,32 +1686,3 @@ Keep it action-oriented and forward-looking.]]
 
 ---
 ==================== END: .bmad-core/checklists/change-checklist.md ====================
-
-==================== START: .bmad-core/utils/template-format.md ====================
-# Template Format Conventions
-
-Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
-
-## Template Markup Elements
-
-- **{{placeholders}}**: Variables to be replaced with actual content
-- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **REPEAT** sections: Content blocks that may be repeated as needed
-- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
-- **@{examples}**: Example content for guidance (never output to users)
-
-## Processing Rules
-
-- Replace all {{placeholders}} with project-specific content
-- Execute all [[LLM: instructions]] internally without showing users
-- Process conditional and repeat blocks as specified
-- Use examples for guidance but never include them in final output
-- Present only clean, formatted content to users
-
-## Critical Guidelines
-
-- **NEVER display template markup, LLM instructions, or examples to users**
-- Template elements are for AI processing only
-- Focus on faithful template execution and clean output
-- All template-specific instructions are embedded within templates
-==================== END: .bmad-core/utils/template-format.md ====================

dist/agents/qa.txt

@@ -50,6 +50,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Quinn
   id: qa
@@ -73,8 +74,6 @@ persona:
     - Risk-Based Testing - Prioritize testing based on risk and critical areas
     - Continuous Improvement - Balance perfection with pragmatism
     - Architecture & Design Patterns - Ensure proper patterns and maintainable code structure
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 story-file-permissions:
   - CRITICAL: When reviewing stories, you are ONLY authorized to update the "QA Results" section of story files
   - CRITICAL: DO NOT modify any other sections including Status, Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Testing, Dev Agent Record, Change Log, or any other sections
@@ -86,11 +85,11 @@ commands:
   - exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - review-story
+    - review-story.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
+  templates:
+    - story-tmpl.yaml
 ```
 ==================== END: .bmad-core/agents/qa.md ====================
 
@@ -242,37 +241,148 @@ After review:
 3. Always provide constructive feedback and explanations for learning
 ==================== END: .bmad-core/tasks/review-story.md ====================
 
+==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+template:
+  id: story-template-v2
+  name: Story Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+agent_config:
+  editable_sections: 
+    - Status
+    - Story
+    - Acceptance Criteria
+    - Tasks / Subtasks
+    - Dev Notes
+    - Testing
+    - Change Log
+
+sections:
+  - id: status
+    title: Status
+    type: choice
+    choices: [Draft, Approved, InProgress, Review, Done]
+    instruction: Select the current status of the story
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: story
+    title: Story
+    type: template-text
+    template: |
+      **As a** {{role}},
+      **I want** {{action}},
+      **so that** {{benefit}}
+    instruction: Define the user story using the standard format with role, action, and benefit
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    type: numbered-list
+    instruction: Copy the acceptance criteria numbered list from the epic file
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: tasks-subtasks
+    title: Tasks / Subtasks
+    type: bullet-list
+    instruction: |
+      Break down the story into specific tasks and subtasks needed for implementation.
+      Reference applicable acceptance criteria numbers where relevant.
+    template: |
+      - [ ] Task 1 (AC: # if applicable)
+        - [ ] Subtask1.1...
+      - [ ] Task 2 (AC: # if applicable)
+        - [ ] Subtask 2.1...
+      - [ ] Task 3 (AC: # if applicable)
+        - [ ] Subtask 3.1...
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: dev-notes
+    title: Dev Notes
+    instruction: |
+      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
+      - Do not invent information
+      - If known add Relevant Source Tree info that relates to this story
+      - If there were important notes from previous story that are relevant to this one, include them here
+      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    sections:
+      - id: testing-standards
+        title: Testing
+        instruction: |
+          List Relevant Testing Standards from Architecture the Developer needs to conform to:
+          - Test file location
+          - Test standards
+          - Testing frameworks and patterns to use
+          - Any specific testing requirements for this story
+        elicit: true
+        owner: scrum-master
+        editors: [scrum-master]
+        
+  - id: change-log
+    title: Change Log
+    type: table
+    columns: [Date, Version, Description, Author]
+    instruction: Track changes made to this story document
+    owner: scrum-master
+    editors: [scrum-master, dev-agent, qa-agent]
+    
+  - id: dev-agent-record
+    title: Dev Agent Record
+    instruction: This section is populated by the development agent during implementation
+    owner: dev-agent
+    editors: [dev-agent]
+    sections:
+      - id: agent-model
+        title: Agent Model Used
+        template: "{{agent_model_name_version}}"
+        instruction: Record the specific AI agent model and version used for development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: debug-log-references
+        title: Debug Log References
+        instruction: Reference any debug logs or traces generated during development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: completion-notes
+        title: Completion Notes List
+        instruction: Notes about the completion of tasks and any issues encountered
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: file-list
+        title: File List
+        instruction: List all files created, modified, or affected during story implementation
+        owner: dev-agent
+        editors: [dev-agent]
+        
+  - id: qa-results
+    title: QA Results
+    instruction: Results from QA Agent QA review of the completed story implementation
+    owner: qa-agent
+    editors: [qa-agent]
+==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+
 ==================== START: .bmad-core/data/technical-preferences.md ====================
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
 ==================== END: .bmad-core/data/technical-preferences.md ====================
-
-==================== START: .bmad-core/utils/template-format.md ====================
-# Template Format Conventions
-
-Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
-
-## Template Markup Elements
-
-- **{{placeholders}}**: Variables to be replaced with actual content
-- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **REPEAT** sections: Content blocks that may be repeated as needed
-- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
-- **@{examples}**: Example content for guidance (never output to users)
-
-## Processing Rules
-
-- Replace all {{placeholders}} with project-specific content
-- Execute all [[LLM: instructions]] internally without showing users
-- Process conditional and repeat blocks as specified
-- Use examples for guidance but never include them in final output
-- Present only clean, formatted content to users
-
-## Critical Guidelines
-
-- **NEVER display template markup, LLM instructions, or examples to users**
-- Template elements are for AI processing only
-- Focus on faithful template execution and clean output
-- All template-specific instructions are embedded within templates
-==================== END: .bmad-core/utils/template-format.md ====================

dist/agents/sm.txt

@@ -49,6 +49,7 @@ activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
 agent:
   name: Bob
   id: sm
@@ -65,10 +66,6 @@ persona:
     - Rigorously follow `create-next-story` procedure to generate the detailed user story
     - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
     - You are NOT allowed to implement stories or modify code EVER!
-startup:
-  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - Offer to help with story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - help: Show numbered list of the following commands to allow selection
   - draft: Execute task create-next-story
@@ -77,15 +74,13 @@ commands:
   - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - create-next-story
-    - execute-checklist
-    - correct-course
+    - create-next-story.md
+    - execute-checklist.md
+    - correct-course.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - story-draft-checklist
-  utils:
-    - template-format
+    - story-draft-checklist.md
 ```
 ==================== END: .bmad-core/agents/sm.md ====================
 
@@ -378,66 +373,145 @@ The LLM will:
 - **Implicit:** An annotated `change-checklist` (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
 ==================== END: .bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.md ====================
----
-defaultOutput: docs/stories/{{EpicNum}}.{{StoryNum}}.{{Short Title Copied from Epic File specific story}}.md
-smAgent:
-  editableSections: Status, Story, Acceptance Criteria, Tasks / Subtasks, Dev Notes, Testing, Change Log
-  sectionSpecificInstructions:
-    "Dev Notes":
-      - Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story
-      - Do not invent information.
-      - If known add Relevant Source Tree info that relates to this story.
-      - If there were important notes from previous story that are relevant to this one, include them here.
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story,  meeting all AC and completing all tasks+subtasks.
-    Testing:
-      - List Relevant Testing Standards from Architecture the Developer needs to conform to (test file location, test standards, etc) 
----
+==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+template:
+  id: story-template-v2
+  name: Story Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
 
-# Story {{EpicNum}}.{{StoryNum}}: {{Short Title Copied from Epic File specific story}}
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
 
-## Status: {{ Draft | Approved | InProgress | Review | Done }}
+agent_config:
+  editable_sections: 
+    - Status
+    - Story
+    - Acceptance Criteria
+    - Tasks / Subtasks
+    - Dev Notes
+    - Testing
+    - Change Log
 
-## Story
-
-**As a** {{role}},\
-**I want** {{action}},\
-**so that** {{benefit}}
-
-## Acceptance Criteria
-
-{{ Copy of Acceptance Criteria numbered list }}
-
-## Tasks / Subtasks
-
-- [ ] Task 1 (AC: # if applicable)
-  - [ ] Subtask1.1...
-- [ ] Task 2 (AC: # if applicable)
-  - [ ] Subtask 2.1...
-- [ ] Task 3 (AC: # if applicable)
-  - [ ] Subtask 3.1...
-
-## Dev Notes
-
-### Testing
-
-## Change Log
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Dev Agent Record
-
-### Agent Model Used: {{Agent Model Name/Version}}
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List
-
-## QA Results
-==================== END: .bmad-core/templates/story-tmpl.md ====================
+sections:
+  - id: status
+    title: Status
+    type: choice
+    choices: [Draft, Approved, InProgress, Review, Done]
+    instruction: Select the current status of the story
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: story
+    title: Story
+    type: template-text
+    template: |
+      **As a** {{role}},
+      **I want** {{action}},
+      **so that** {{benefit}}
+    instruction: Define the user story using the standard format with role, action, and benefit
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    type: numbered-list
+    instruction: Copy the acceptance criteria numbered list from the epic file
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: tasks-subtasks
+    title: Tasks / Subtasks
+    type: bullet-list
+    instruction: |
+      Break down the story into specific tasks and subtasks needed for implementation.
+      Reference applicable acceptance criteria numbers where relevant.
+    template: |
+      - [ ] Task 1 (AC: # if applicable)
+        - [ ] Subtask1.1...
+      - [ ] Task 2 (AC: # if applicable)
+        - [ ] Subtask 2.1...
+      - [ ] Task 3 (AC: # if applicable)
+        - [ ] Subtask 3.1...
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: dev-notes
+    title: Dev Notes
+    instruction: |
+      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
+      - Do not invent information
+      - If known add Relevant Source Tree info that relates to this story
+      - If there were important notes from previous story that are relevant to this one, include them here
+      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    sections:
+      - id: testing-standards
+        title: Testing
+        instruction: |
+          List Relevant Testing Standards from Architecture the Developer needs to conform to:
+          - Test file location
+          - Test standards
+          - Testing frameworks and patterns to use
+          - Any specific testing requirements for this story
+        elicit: true
+        owner: scrum-master
+        editors: [scrum-master]
+        
+  - id: change-log
+    title: Change Log
+    type: table
+    columns: [Date, Version, Description, Author]
+    instruction: Track changes made to this story document
+    owner: scrum-master
+    editors: [scrum-master, dev-agent, qa-agent]
+    
+  - id: dev-agent-record
+    title: Dev Agent Record
+    instruction: This section is populated by the development agent during implementation
+    owner: dev-agent
+    editors: [dev-agent]
+    sections:
+      - id: agent-model
+        title: Agent Model Used
+        template: "{{agent_model_name_version}}"
+        instruction: Record the specific AI agent model and version used for development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: debug-log-references
+        title: Debug Log References
+        instruction: Reference any debug logs or traces generated during development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: completion-notes
+        title: Completion Notes List
+        instruction: Notes about the completion of tasks and any issues encountered
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: file-list
+        title: File List
+        instruction: List all files created, modified, or affected during story implementation
+        owner: dev-agent
+        editors: [dev-agent]
+        
+  - id: qa-results
+    title: QA Results
+    instruction: Results from QA Agent QA review of the completed story implementation
+    owner: qa-agent
+    editors: [qa-agent]
+==================== END: .bmad-core/templates/story-tmpl.yaml ====================
 
 ==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
 # Story Draft Checklist
@@ -597,32 +671,3 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
 - NEEDS REVISION: The story requires updates (see issues)
 - BLOCKED: External information required (specify what information)
 ==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
-
-==================== START: .bmad-core/utils/template-format.md ====================
-# Template Format Conventions
-
-Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
-
-## Template Markup Elements
-
-- **{{placeholders}}**: Variables to be replaced with actual content
-- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **REPEAT** sections: Content blocks that may be repeated as needed
-- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
-- **@{examples}**: Example content for guidance (never output to users)
-
-## Processing Rules
-
-- Replace all {{placeholders}} with project-specific content
-- Execute all [[LLM: instructions]] internally without showing users
-- Process conditional and repeat blocks as specified
-- Use examples for guidance but never include them in final output
-- Present only clean, formatted content to users
-
-## Critical Guidelines
-
-- **NEVER display template markup, LLM instructions, or examples to users**
-- Template elements are for AI processing only
-- Focus on faithful template execution and clean output
-- All template-specific instructions are embedded within templates
-==================== END: .bmad-core/utils/template-format.md ====================

dist/agents/ux-expert.txt

@@ -50,6 +50,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Sally
   id: ux-expert
@@ -71,9 +72,6 @@ persona:
     - You have a keen eye for detail and a deep empathy for users.
     - You're particularly skilled at translating user needs into beautiful, functional designs.
     - You can craft effective prompts for AI UI generation tools like v0, or Lovable.
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - Always start by understanding the user's context, goals, and constraints before proposing solutions.
 commands:
   - help: Show numbered list of the following commands to allow selection
   - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
@@ -83,16 +81,14 @@ commands:
   - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - generate-ai-frontend-prompt
-    - create-deep-research-prompt
-    - create-doc
-    - execute-checklist
+    - generate-ai-frontend-prompt.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - execute-checklist.md
   templates:
-    - front-end-spec-tmpl
+    - front-end-spec-tmpl.yaml
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
 ```
 ==================== END: .bmad-core/agents/ux-expert.md ====================
 
@@ -455,97 +451,85 @@ Present these numbered options to the user:
 ==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-core/tasks/create-doc.md ====================
-# Create Document from Template Task
+# Create Document from Template (YAML Driven)
 
-## Purpose
+## CRITICAL: Mandatory Elicitation Format
 
-Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
+**When `elicit: true`, ALWAYS use this exact format:**
 
-## CRITICAL RULES
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. Present numbered options 1-9:
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
 
-1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
-2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
-3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
-4. **WAIT for user input** - At review points and after elicitation tasks
+**NEVER ask yes/no questions or use any other format.**
 
-## Execution Flow
+## Processing Flow
 
-### 0. Check Workflow Plan (if configured)
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
 
-[[LLM: Check if plan tracking is enabled in core-config.yaml]]
+## Detailed Rationale Requirements
 
-- If `workflow.trackProgress: true`, check for active plan using .bmad-core/utils/plan-management.md
-- If plan exists and this document creation is part of the plan:
-  - Verify this is the expected next step
-  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
-  - If out of sequence and `enforceSequence: false`, ask for confirmation
-- Continue with normal execution after plan check
+When presenting section content, ALWAYS include rationale that explains:
 
-### 1. Identify Template
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
 
-- Load from `.bmad-core/templates/*.md` or `.bmad-core/templates directory`
-- Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
+## Elicitation Results Flow
 
-### 2. Ask Interaction Mode
+After user selects elicitation method (2-9):
 
-> 1. **Incremental** - Section by section with reviews
-> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
 
-### 3. Execute Template
+## Agent Permissions
 
-- Replace {{placeholders}} with real content
-- Execute [[LLM:]] instructions as you encounter them
-- Process <<REPEAT>> loops and ^^CONDITIONS^^
-- Use @{examples} for guidance but never output them
+When processing sections with agent permission fields:
 
-### 4. Key Execution Patterns
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
 
-**When you see:** `[[LLM: Draft X and immediately execute .bmad-core/tasks/advanced-elicitation.md]]`
+**For sections with restricted access:**
 
-- Draft the content
-- Present it to user
-- IMMEDIATELY execute the task
-- Wait for completion before continuing
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
 
-**When you see:** `[[LLM: After section completion, apply .bmad-core/tasks/Y.md]]`
+## YOLO Mode
 
-- Finish the section
-- STOP and execute the task
-- Wait for user input
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 
-### 5. Validation & Final Presentation
+## CRITICAL REMINDERS
 
-- Run any specified checklists
-- Present clean, formatted content only
-- No truncation or summarization
-- Begin directly with content (no preamble)
-- Include any handoff prompts from template
+**❌ NEVER:**
 
-### 6. Update Workflow Plan (if applicable)
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
 
-[[LLM: After successful document creation]]
+**✅ ALWAYS:**
 
-- If plan tracking is enabled and document was part of plan:
-  - Call update-workflow-plan task to mark step complete
-  - Parameters: task: create-doc, step_id: {from plan}, status: complete
-  - Show next recommended step from plan
-
-## Common Mistakes to Avoid
-
-❌ Skipping elicitation tasks
-❌ Showing template markup to users
-❌ Continuing past STOP signals
-❌ Combining multiple review points
-
-✅ Execute ALL instructions in sequence
-✅ Present only clean, formatted content
-✅ Stop at every elicitation point
-✅ Wait for user confirmation when instructed
-
-## Remember
-
-Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"
 ==================== END: .bmad-core/tasks/create-doc.md ====================
 
 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
@@ -644,453 +628,360 @@ The LLM will:
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
 ==================== END: .bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/templates/front-end-spec-tmpl.md ====================
-# {{Project Name}} UI/UX Specification
-
-[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
-
-[[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
-
-## Introduction
-
-[[LLM: Establish the document's purpose and scope. Keep the content below but ensure project name is properly substituted.]]
-
-This document defines the user experience goals, information architecture, user flows, and visual design specifications for {{Project Name}}'s user interface. It serves as the foundation for visual design and frontend development, ensuring a cohesive and user-centered experience.
-
-### Overall UX Goals & Principles
-
-[[LLM: Work with the user to establish and document the following. If not already defined, facilitate a discussion to determine:
-
-1. Target User Personas - elicit details or confirm existing ones from PRD
-2. Key Usability Goals - understand what success looks like for users
-3. Core Design Principles - establish 3-5 guiding principles
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Target User Personas
-
-{{persona_descriptions}}
-
-@{example: personas}
-
-- **Power User:** Technical professionals who need advanced features and efficiency
-- **Casual User:** Occasional users who prioritize ease of use and clear guidance
-- **Administrator:** System managers who need control and oversight capabilities
-  @{/example}
-
-### Usability Goals
-
-{{usability_goals}}
-
-@{example: usability_goals}
-
-- Ease of learning: New users can complete core tasks within 5 minutes
-- Efficiency of use: Power users can complete frequent tasks with minimal clicks
-- Error prevention: Clear validation and confirmation for destructive actions
-- Memorability: Infrequent users can return without relearning
-  @{/example}
-
-### Design Principles
-
-{{design_principles}}
-
-@{example: design_principles}
-
-1. **Clarity over cleverness** - Prioritize clear communication over aesthetic innovation
-2. **Progressive disclosure** - Show only what's needed, when it's needed
-3. **Consistent patterns** - Use familiar UI patterns throughout the application
-4. **Immediate feedback** - Every action should have a clear, immediate response
-5. **Accessible by default** - Design for all users from the start
-   @{/example}
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Information Architecture (IA)
-
-[[LLM: Collaborate with the user to create a comprehensive information architecture:
-
-1. Build a Site Map or Screen Inventory showing all major areas
-2. Define the Navigation Structure (primary, secondary, breadcrumbs)
-3. Use Mermaid diagrams for visual representation
-4. Consider user mental models and expected groupings
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Site Map / Screen Inventory
-
-```mermaid
-{{sitemap_diagram}}
-```
-
-@{example: sitemap}
-
-```mermaid
-graph TD
-    A[Homepage] --> B[Dashboard]
-    A --> C[Products]
-    A --> D[Account]
-    B --> B1[Analytics]
-    B --> B2[Recent Activity]
-    C --> C1[Browse]
-    C --> C2[Search]
-    C --> C3[Product Details]
-    D --> D1[Profile]
-    D --> D2[Settings]
-    D --> D3[Billing]
-```
-
-@{/example}
-
-### Navigation Structure
-
-**Primary Navigation:** {{primary_nav_description}}
-
-**Secondary Navigation:** {{secondary_nav_description}}
-
-**Breadcrumb Strategy:** {{breadcrumb_strategy}}
-
-## User Flows
-
-[[LLM: For each critical user task identified in the PRD:
-
-1. Define the user's goal clearly
-2. Map out all steps including decision points
-3. Consider edge cases and error states
-4. Use Mermaid flow diagrams for clarity
-5. Link to external tools (Figma/Miro) if detailed flows exist there
-
-Create subsections for each major flow. After presenting all flows, apply `tasks#advanced-elicitation` protocol]]
-
-<<REPEAT: user_flow>>
-
-### {{flow_name}}
-
-**User Goal:** {{flow_goal}}
-
-**Entry Points:** {{entry_points}}
-
-**Success Criteria:** {{success_criteria}}
-
-#### Flow Diagram
-
-```mermaid
-{{flow_diagram}}
-```
-
-**Edge Cases & Error Handling:**
-
-- {{edge_case_1}}
-- {{edge_case_2}}
-
-**Notes:** {{flow_notes}}
-<</REPEAT>>
-
-@{example: user_flow}
-
-### User Registration
-
-**User Goal:** Create a new account to access the platform
-
-**Entry Points:** Homepage CTA, Login page link, Marketing landing pages
-
-**Success Criteria:** User successfully creates account and reaches dashboard
-
-#### Flow Diagram
-
-```mermaid
-graph TD
-    Start[Landing Page] --> Click[Click Sign Up]
-    Click --> Form[Registration Form]
-    Form --> Fill[Fill Required Fields]
-    Fill --> Submit[Submit Form]
-    Submit --> Validate{Valid?}
-    Validate -->|No| Error[Show Errors]
-    Error --> Form
-    Validate -->|Yes| Verify[Email Verification]
-    Verify --> Complete[Account Created]
-    Complete --> Dashboard[Redirect to Dashboard]
-```
-
-**Edge Cases & Error Handling:**
-
-- Duplicate email: Show inline error with password recovery option
-- Weak password: Real-time feedback on password strength
-- Network error: Preserve form data and show retry option
-  @{/example}
-
-## Wireframes & Mockups
-
-[[LLM: Clarify where detailed visual designs will be created (Figma, Sketch, etc.) and how to reference them. If low-fidelity wireframes are needed, offer to help conceptualize layouts for key screens.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-**Primary Design Files:** {{design_tool_link}}
-
-### Key Screen Layouts
-
-<<REPEAT: screen_layout>>
-
-#### {{screen_name}}
-
-**Purpose:** {{screen_purpose}}
-
-**Key Elements:**
-
-- {{element_1}}
-- {{element_2}}
-- {{element_3}}
-
-**Interaction Notes:** {{interaction_notes}}
-
-**Design File Reference:** {{specific_frame_link}}
-<</REPEAT>>
-
-## Component Library / Design System
-
-[[LLM: Discuss whether to use an existing design system or create a new one. If creating new, identify foundational components and their key states. Note that detailed technical specs belong in front-end-architecture.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-**Design System Approach:** {{design_system_approach}}
-
-### Core Components
-
-<<REPEAT: component>>
-
-#### {{component_name}}
-
-**Purpose:** {{component_purpose}}
-
-**Variants:** {{component_variants}}
-
-**States:** {{component_states}}
-
-**Usage Guidelines:** {{usage_guidelines}}
-<</REPEAT>>
-
-@{example: component}
-
-#### Button
-
-**Purpose:** Primary interaction element for user actions
-
-**Variants:** Primary, Secondary, Tertiary, Destructive
-
-**States:** Default, Hover, Active, Disabled, Loading
-
-**Usage Guidelines:**
-
-- Use Primary for main CTAs (one per view)
-- Secondary for supporting actions
-- Destructive only for permanent deletions with confirmation
-  @{/example}
-
-## Branding & Style Guide
-
-[[LLM: Link to existing style guide or define key brand elements. Ensure consistency with company brand guidelines if they exist.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Visual Identity
-
-**Brand Guidelines:** {{brand_guidelines_link}}
-
-### Color Palette
-
-| Color Type    | Hex Code            | Usage                            |
-| :------------ | :------------------ | :------------------------------- |
-| **Primary**   | {{primary_color}}   | {{primary_usage}}                |
-| **Secondary** | {{secondary_color}} | {{secondary_usage}}              |
-| **Accent**    | {{accent_color}}    | {{accent_usage}}                 |
-| **Success**   | {{success_color}}   | Positive feedback, confirmations |
-| **Warning**   | {{warning_color}}   | Cautions, important notices      |
-| **Error**     | {{error_color}}     | Errors, destructive actions      |
-| **Neutral**   | {{neutral_colors}}  | Text, borders, backgrounds       |
-
-### Typography
-
-**Font Families:**
-
-- **Primary:** {{primary_font}}
-- **Secondary:** {{secondary_font}}
-- **Monospace:** {{mono_font}}
-
-**Type Scale:**
-| Element | Size | Weight | Line Height |
-|:--------|:-----|:-------|:------------|
-| H1 | {{h1_size}} | {{h1_weight}} | {{h1_line}} |
-| H2 | {{h2_size}} | {{h2_weight}} | {{h2_line}} |
-| H3 | {{h3_size}} | {{h3_weight}} | {{h3_line}} |
-| Body | {{body_size}} | {{body_weight}} | {{body_line}} |
-| Small | {{small_size}} | {{small_weight}} | {{small_line}} |
-
-### Iconography
-
-**Icon Library:** {{icon_library}}
-
-**Usage Guidelines:** {{icon_guidelines}}
-
-### Spacing & Layout
-
-**Grid System:** {{grid_system}}
-
-**Spacing Scale:** {{spacing_scale}}
-
-## Accessibility Requirements
-
-[[LLM: Define specific accessibility requirements based on target compliance level and user needs. Be comprehensive but practical.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Compliance Target
-
-**Standard:** {{compliance_standard}}
-
-### Key Requirements
-
-**Visual:**
-
-- Color contrast ratios: {{contrast_requirements}}
-- Focus indicators: {{focus_requirements}}
-- Text sizing: {{text_requirements}}
-
-**Interaction:**
-
-- Keyboard navigation: {{keyboard_requirements}}
-- Screen reader support: {{screen_reader_requirements}}
-- Touch targets: {{touch_requirements}}
-
-**Content:**
-
-- Alternative text: {{alt_text_requirements}}
-- Heading structure: {{heading_requirements}}
-- Form labels: {{form_requirements}}
-
-### Testing Strategy
-
-{{accessibility_testing}}
-
-## Responsiveness Strategy
-
-[[LLM: Define breakpoints and adaptation strategies for different device sizes. Consider both technical constraints and user contexts.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Breakpoints
-
-| Breakpoint | Min Width       | Max Width       | Target Devices      |
-| :--------- | :-------------- | :-------------- | :------------------ |
-| Mobile     | {{mobile_min}}  | {{mobile_max}}  | {{mobile_devices}}  |
-| Tablet     | {{tablet_min}}  | {{tablet_max}}  | {{tablet_devices}}  |
-| Desktop    | {{desktop_min}} | {{desktop_max}} | {{desktop_devices}} |
-| Wide       | {{wide_min}}    | -               | {{wide_devices}}    |
-
-### Adaptation Patterns
-
-**Layout Changes:** {{layout_adaptations}}
-
-**Navigation Changes:** {{nav_adaptations}}
-
-**Content Priority:** {{content_adaptations}}
-
-**Interaction Changes:** {{interaction_adaptations}}
-
-## Animation & Micro-interactions
-
-[[LLM: Define motion design principles and key interactions. Keep performance and accessibility in mind.
-
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
-
-### Motion Principles
-
-{{motion_principles}}
-
-### Key Animations
-
-<<REPEAT: animation>>
-
-- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})
-  <</REPEAT>>
-
-## Performance Considerations
-
-[[LLM: Define performance goals and strategies that impact UX design decisions.]]
-
-### Performance Goals
-
-- **Page Load:** {{load_time_goal}}
-- **Interaction Response:** {{interaction_goal}}
-- **Animation FPS:** {{animation_goal}}
-
-### Design Strategies
-
-{{performance_strategies}}
-
-## Next Steps
-
-[[LLM: After completing the UI/UX specification:
-
-1. Recommend review with stakeholders
-2. Suggest creating/updating visual designs in design tool
-3. Prepare for handoff to Design Architect for frontend architecture
-4. Note any open questions or decisions needed]]
-
-### Immediate Actions
-
-1. {{next_step_1}}
-2. {{next_step_2}}
-3. {{next_step_3}}
-
-### Design Handoff Checklist
-
-- [ ] All user flows documented
-- [ ] Component inventory complete
-- [ ] Accessibility requirements defined
-- [ ] Responsive strategy clear
-- [ ] Brand guidelines incorporated
-- [ ] Performance goals established
-
-## Checklist Results
-
-[[LLM: If a UI/UX checklist exists, run it against this document and report results here.]]
-==================== END: .bmad-core/templates/front-end-spec-tmpl.md ====================
+==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+template:
+  id: frontend-spec-template-v2
+  name: UI/UX Specification
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/front-end-spec.md
+    title: "{{project_name}} UI/UX Specification"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: introduction
+    title: Introduction
+    instruction: |
+      Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.
+      
+      Establish the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
+    content: |
+      This document defines the user experience goals, information architecture, user flows, and visual design specifications for {{project_name}}'s user interface. It serves as the foundation for visual design and frontend development, ensuring a cohesive and user-centered experience.
+    sections:
+      - id: ux-goals-principles
+        title: Overall UX Goals & Principles
+        instruction: |
+          Work with the user to establish and document the following. If not already defined, facilitate a discussion to determine:
+          
+          1. Target User Personas - elicit details or confirm existing ones from PRD
+          2. Key Usability Goals - understand what success looks like for users
+          3. Core Design Principles - establish 3-5 guiding principles
+        elicit: true
+        sections:
+          - id: user-personas
+            title: Target User Personas
+            template: "{{persona_descriptions}}"
+            examples:
+              - "**Power User:** Technical professionals who need advanced features and efficiency"
+              - "**Casual User:** Occasional users who prioritize ease of use and clear guidance"
+              - "**Administrator:** System managers who need control and oversight capabilities"
+          - id: usability-goals
+            title: Usability Goals
+            template: "{{usability_goals}}"
+            examples:
+              - "Ease of learning: New users can complete core tasks within 5 minutes"
+              - "Efficiency of use: Power users can complete frequent tasks with minimal clicks"
+              - "Error prevention: Clear validation and confirmation for destructive actions"
+              - "Memorability: Infrequent users can return without relearning"
+          - id: design-principles
+            title: Design Principles
+            template: "{{design_principles}}"
+            type: numbered-list
+            examples:
+              - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation"
+              - "**Progressive disclosure** - Show only what's needed, when it's needed"
+              - "**Consistent patterns** - Use familiar UI patterns throughout the application"
+              - "**Immediate feedback** - Every action should have a clear, immediate response"
+              - "**Accessible by default** - Design for all users from the start"
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+  - id: information-architecture
+    title: Information Architecture (IA)
+    instruction: |
+      Collaborate with the user to create a comprehensive information architecture:
+      
+      1. Build a Site Map or Screen Inventory showing all major areas
+      2. Define the Navigation Structure (primary, secondary, breadcrumbs)
+      3. Use Mermaid diagrams for visual representation
+      4. Consider user mental models and expected groupings
+    elicit: true
+    sections:
+      - id: sitemap
+        title: Site Map / Screen Inventory
+        type: mermaid
+        mermaid_type: graph
+        template: "{{sitemap_diagram}}"
+        examples:
+          - |
+            graph TD
+                A[Homepage] --> B[Dashboard]
+                A --> C[Products]
+                A --> D[Account]
+                B --> B1[Analytics]
+                B --> B2[Recent Activity]
+                C --> C1[Browse]
+                C --> C2[Search]
+                C --> C3[Product Details]
+                D --> D1[Profile]
+                D --> D2[Settings]
+                D --> D3[Billing]
+      - id: navigation-structure
+        title: Navigation Structure
+        template: |
+          **Primary Navigation:** {{primary_nav_description}}
+          
+          **Secondary Navigation:** {{secondary_nav_description}}
+          
+          **Breadcrumb Strategy:** {{breadcrumb_strategy}}
+
+  - id: user-flows
+    title: User Flows
+    instruction: |
+      For each critical user task identified in the PRD:
+      
+      1. Define the user's goal clearly
+      2. Map out all steps including decision points
+      3. Consider edge cases and error states
+      4. Use Mermaid flow diagrams for clarity
+      5. Link to external tools (Figma/Miro) if detailed flows exist there
+      
+      Create subsections for each major flow.
+    elicit: true
+    repeatable: true
+    sections:
+      - id: flow
+        title: "{{flow_name}}"
+        template: |
+          **User Goal:** {{flow_goal}}
+          
+          **Entry Points:** {{entry_points}}
+          
+          **Success Criteria:** {{success_criteria}}
+        sections:
+          - id: flow-diagram
+            title: Flow Diagram
+            type: mermaid
+            mermaid_type: graph
+            template: "{{flow_diagram}}"
+          - id: edge-cases
+            title: "Edge Cases & Error Handling:"
+            type: bullet-list
+            template: "- {{edge_case}}"
+          - id: notes
+            template: "**Notes:** {{flow_notes}}"
+
+  - id: wireframes-mockups
+    title: Wireframes & Mockups
+    instruction: |
+      Clarify where detailed visual designs will be created (Figma, Sketch, etc.) and how to reference them. If low-fidelity wireframes are needed, offer to help conceptualize layouts for key screens.
+    elicit: true
+    sections:
+      - id: design-files
+        template: "**Primary Design Files:** {{design_tool_link}}"
+      - id: key-screen-layouts
+        title: Key Screen Layouts
+        repeatable: true
+        sections:
+          - id: screen
+            title: "{{screen_name}}"
+            template: |
+              **Purpose:** {{screen_purpose}}
+              
+              **Key Elements:**
+              - {{element_1}}
+              - {{element_2}}
+              - {{element_3}}
+              
+              **Interaction Notes:** {{interaction_notes}}
+              
+              **Design File Reference:** {{specific_frame_link}}
+
+  - id: component-library
+    title: Component Library / Design System
+    instruction: |
+      Discuss whether to use an existing design system or create a new one. If creating new, identify foundational components and their key states. Note that detailed technical specs belong in front-end-architecture.
+    elicit: true
+    sections:
+      - id: design-system-approach
+        template: "**Design System Approach:** {{design_system_approach}}"
+      - id: core-components
+        title: Core Components
+        repeatable: true
+        sections:
+          - id: component
+            title: "{{component_name}}"
+            template: |
+              **Purpose:** {{component_purpose}}
+              
+              **Variants:** {{component_variants}}
+              
+              **States:** {{component_states}}
+              
+              **Usage Guidelines:** {{usage_guidelines}}
+
+  - id: branding-style
+    title: Branding & Style Guide
+    instruction: Link to existing style guide or define key brand elements. Ensure consistency with company brand guidelines if they exist.
+    elicit: true
+    sections:
+      - id: visual-identity
+        title: Visual Identity
+        template: "**Brand Guidelines:** {{brand_guidelines_link}}"
+      - id: color-palette
+        title: Color Palette
+        type: table
+        columns: ["Color Type", "Hex Code", "Usage"]
+        rows:
+          - ["Primary", "{{primary_color}}", "{{primary_usage}}"]
+          - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"]
+          - ["Accent", "{{accent_color}}", "{{accent_usage}}"]
+          - ["Success", "{{success_color}}", "Positive feedback, confirmations"]
+          - ["Warning", "{{warning_color}}", "Cautions, important notices"]
+          - ["Error", "{{error_color}}", "Errors, destructive actions"]
+          - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"]
+      - id: typography
+        title: Typography
+        sections:
+          - id: font-families
+            title: Font Families
+            template: |
+              - **Primary:** {{primary_font}}
+              - **Secondary:** {{secondary_font}}
+              - **Monospace:** {{mono_font}}
+          - id: type-scale
+            title: Type Scale
+            type: table
+            columns: ["Element", "Size", "Weight", "Line Height"]
+            rows:
+              - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"]
+              - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"]
+              - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"]
+              - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"]
+              - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"]
+      - id: iconography
+        title: Iconography
+        template: |
+          **Icon Library:** {{icon_library}}
+          
+          **Usage Guidelines:** {{icon_guidelines}}
+      - id: spacing-layout
+        title: Spacing & Layout
+        template: |
+          **Grid System:** {{grid_system}}
+          
+          **Spacing Scale:** {{spacing_scale}}
+
+  - id: accessibility
+    title: Accessibility Requirements
+    instruction: Define specific accessibility requirements based on target compliance level and user needs. Be comprehensive but practical.
+    elicit: true
+    sections:
+      - id: compliance-target
+        title: Compliance Target
+        template: "**Standard:** {{compliance_standard}}"
+      - id: key-requirements
+        title: Key Requirements
+        template: |
+          **Visual:**
+          - Color contrast ratios: {{contrast_requirements}}
+          - Focus indicators: {{focus_requirements}}
+          - Text sizing: {{text_requirements}}
+          
+          **Interaction:**
+          - Keyboard navigation: {{keyboard_requirements}}
+          - Screen reader support: {{screen_reader_requirements}}
+          - Touch targets: {{touch_requirements}}
+          
+          **Content:**
+          - Alternative text: {{alt_text_requirements}}
+          - Heading structure: {{heading_requirements}}
+          - Form labels: {{form_requirements}}
+      - id: testing-strategy
+        title: Testing Strategy
+        template: "{{accessibility_testing}}"
+
+  - id: responsiveness
+    title: Responsiveness Strategy
+    instruction: Define breakpoints and adaptation strategies for different device sizes. Consider both technical constraints and user contexts.
+    elicit: true
+    sections:
+      - id: breakpoints
+        title: Breakpoints
+        type: table
+        columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"]
+        rows:
+          - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"]
+          - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"]
+          - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"]
+          - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"]
+      - id: adaptation-patterns
+        title: Adaptation Patterns
+        template: |
+          **Layout Changes:** {{layout_adaptations}}
+          
+          **Navigation Changes:** {{nav_adaptations}}
+          
+          **Content Priority:** {{content_adaptations}}
+          
+          **Interaction Changes:** {{interaction_adaptations}}
+
+  - id: animation
+    title: Animation & Micro-interactions
+    instruction: Define motion design principles and key interactions. Keep performance and accessibility in mind.
+    elicit: true
+    sections:
+      - id: motion-principles
+        title: Motion Principles
+        template: "{{motion_principles}}"
+      - id: key-animations
+        title: Key Animations
+        repeatable: true
+        template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})"
+
+  - id: performance
+    title: Performance Considerations
+    instruction: Define performance goals and strategies that impact UX design decisions.
+    sections:
+      - id: performance-goals
+        title: Performance Goals
+        template: |
+          - **Page Load:** {{load_time_goal}}
+          - **Interaction Response:** {{interaction_goal}}
+          - **Animation FPS:** {{animation_goal}}
+      - id: design-strategies
+        title: Design Strategies
+        template: "{{performance_strategies}}"
+
+  - id: next-steps
+    title: Next Steps
+    instruction: |
+      After completing the UI/UX specification:
+      
+      1. Recommend review with stakeholders
+      2. Suggest creating/updating visual designs in design tool
+      3. Prepare for handoff to Design Architect for frontend architecture
+      4. Note any open questions or decisions needed
+    sections:
+      - id: immediate-actions
+        title: Immediate Actions
+        type: numbered-list
+        template: "{{action}}"
+      - id: design-handoff-checklist
+        title: Design Handoff Checklist
+        type: checklist
+        items:
+          - "All user flows documented"
+          - "Component inventory complete"
+          - "Accessibility requirements defined"
+          - "Responsive strategy clear"
+          - "Brand guidelines incorporated"
+          - "Performance goals established"
+
+  - id: checklist-results
+    title: Checklist Results
+    instruction: If a UI/UX checklist exists, run it against this document and report results here.
+==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
 
 ==================== START: .bmad-core/data/technical-preferences.md ====================
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
 ==================== END: .bmad-core/data/technical-preferences.md ====================
-
-==================== START: .bmad-core/utils/template-format.md ====================
-# Template Format Conventions
-
-Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
-
-## Template Markup Elements
-
-- **{{placeholders}}**: Variables to be replaced with actual content
-- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **REPEAT** sections: Content blocks that may be repeated as needed
-- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
-- **@{examples}**: Example content for guidance (never output to users)
-
-## Processing Rules
-
-- Replace all {{placeholders}} with project-specific content
-- Execute all [[LLM: instructions]] internally without showing users
-- Process conditional and repeat blocks as specified
-- Use examples for guidance but never include them in final output
-- Present only clean, formatted content to users
-
-## Critical Guidelines
-
-- **NEVER display template markup, LLM instructions, or examples to users**
-- Template elements are for AI processing only
-- Focus on faithful template execution and clean output
-- All template-specific instructions are embedded within templates
-==================== END: .bmad-core/utils/template-format.md ====================

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt

@@ -50,6 +50,10 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - Offer to help with game story preparation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
+  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent'
 agent:
   name: Jordan
   id: game-sm
@@ -69,13 +73,6 @@ core_principles:
   - Focus on One Story at a Time - Complete one before starting next
   - Game-Specific Context - Understand Phaser 3, game mechanics, and performance requirements
   - Numbered Options Protocol - Always use numbered lists for selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically execute create-game-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with game story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
-  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent'
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for game dev advice'
@@ -84,12 +81,12 @@ commands:
   - '*exit" - Say goodbye as the Game Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-game-story
-    - execute-checklist
+    - create-game-story.md
+    - execute-checklist.md
   templates:
-    - game-story-tmpl
+    - game-story-tmpl.yaml
   checklists:
-    - game-story-dod-checklist
+    - game-story-dod-checklist.md
 ```
 ==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
 
@@ -408,243 +405,261 @@ The LLM will:
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
 ==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
-# Story: {{Story Title}}
-
-**Epic:** {{Epic Name}}  
-**Story ID:** {{ID}}  
-**Priority:** {{High|Medium|Low}}  
-**Points:** {{Story Points}}  
-**Status:** Draft
-
-[[LLM: This template creates detailed game development stories that are immediately actionable by game developers. Each story should focus on a single, implementable feature that contributes to the overall game functionality.
-
-Before starting, ensure you have access to:
-
-- Game Design Document (GDD)
-- Game Architecture Document
-- Any existing stories in this epic
-
-The story should be specific enough that a developer can implement it without requiring additional design decisions.]]
-
-## Description
-
-[[LLM: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.]]
-
-{{clear_description_of_what_needs_to_be_implemented}}
-
-## Acceptance Criteria
-
-[[LLM: Define specific, testable conditions that must be met for the story to be considered complete. Each criterion should be verifiable and directly related to gameplay functionality.]]
-
-### Functional Requirements
-
-- [ ] {{specific_functional_requirement_1}}
-- [ ] {{specific_functional_requirement_2}}
-- [ ] {{specific_functional_requirement_3}}
-
-### Technical Requirements
-
-- [ ] Code follows TypeScript strict mode standards
-- [ ] Maintains 60 FPS on target devices
-- [ ] No memory leaks or performance degradation
-- [ ] {{specific_technical_requirement}}
-
-### Game Design Requirements
-
-- [ ] {{gameplay_requirement_from_gdd}}
-- [ ] {{balance_requirement_if_applicable}}
-- [ ] {{player_experience_requirement}}
-
-## Technical Specifications
-
-[[LLM: Provide specific technical details that guide implementation. Include class names, file locations, and integration points based on the game architecture.]]
-
-### Files to Create/Modify
-
-**New Files:**
-
-- `{{file_path_1}}` - {{purpose}}
-- `{{file_path_2}}` - {{purpose}}
-
-**Modified Files:**
-
-- `{{existing_file_1}}` - {{changes_needed}}
-- `{{existing_file_2}}` - {{changes_needed}}
-
-### Class/Interface Definitions
-
-[[LLM: Define specific TypeScript interfaces and class structures needed]]
-
-```typescript
-// {{interface_name}}
-interface {{InterfaceName}} {
-    {{property_1}}: {{type}};
-    {{property_2}}: {{type}};
-    {{method_1}}({{params}}): {{return_type}};
-}
-
-// {{class_name}}
-class {{ClassName}} extends {{PhaseClass}} {
-    private {{property}}: {{type}};
-
-    constructor({{params}}) {
-        // Implementation requirements
-    }
-
-    public {{method}}({{params}}): {{return_type}} {
-        // Method requirements
-    }
-}
-```
-
-### Integration Points
-
-[[LLM: Specify how this feature integrates with existing systems]]
-
-**Scene Integration:**
-
-- {{scene_name}}: {{integration_details}}
-
-**System Dependencies:**
-
-- {{system_name}}: {{dependency_description}}
-
-**Event Communication:**
-
-- Emits: `{{event_name}}` when {{condition}}
-- Listens: `{{event_name}}` to {{response}}
-
-## Implementation Tasks
-
-[[LLM: Break down the implementation into specific, ordered tasks. Each task should be completable in 1-4 hours.]]
-
-### Dev Agent Record
-
-**Tasks:**
-
-- [ ] {{task_1_description}}
-- [ ] {{task_2_description}}
-- [ ] {{task_3_description}}
-- [ ] {{task_4_description}}
-- [ ] Write unit tests for {{component}}
-- [ ] Integration testing with {{related_system}}
-- [ ] Performance testing and optimization
-
-**Debug Log:**
-| Task | File | Change | Reverted? |
-|------|------|--------|-----------|
-| | | | |
-
-**Completion Notes:**
-
-<!-- Only note deviations from requirements, keep under 50 words -->
-
-**Change Log:**
-
-<!-- Only requirement changes during implementation -->
-
-## Game Design Context
-
-[[LLM: Reference the specific sections of the GDD that this story implements]]
-
-**GDD Reference:** {{section_name}} ({{page_or_section_number}})
-
-**Game Mechanic:** {{mechanic_name}}
-
-**Player Experience Goal:** {{experience_description}}
-
-**Balance Parameters:**
-
-- {{parameter_1}}: {{value_or_range}}
-- {{parameter_2}}: {{value_or_range}}
-
-## Testing Requirements
-
-[[LLM: Define specific testing criteria for this game feature]]
-
-### Unit Tests
-
-**Test Files:**
-
-- `tests/{{component_name}}.test.ts`
-
-**Test Scenarios:**
-
-- {{test_scenario_1}}
-- {{test_scenario_2}}
-- {{edge_case_test}}
-
-### Game Testing
-
-**Manual Test Cases:**
-
-1. {{test_case_1_description}}
-
-   - Expected: {{expected_behavior}}
-   - Performance: {{performance_expectation}}
-
-2. {{test_case_2_description}}
-   - Expected: {{expected_behavior}}
-   - Edge Case: {{edge_case_handling}}
-
-### Performance Tests
-
-**Metrics to Verify:**
-
-- Frame rate maintains {{fps_target}} FPS
-- Memory usage stays under {{memory_limit}}MB
-- {{feature_specific_performance_metric}}
-
-## Dependencies
-
-[[LLM: List any dependencies that must be completed before this story can be implemented]]
-
-**Story Dependencies:**
-
-- {{story_id}}: {{dependency_description}}
-
-**Technical Dependencies:**
-
-- {{system_or_file}}: {{requirement}}
-
-**Asset Dependencies:**
-
-- {{asset_type}}: {{asset_description}}
-- Location: `{{asset_path}}`
-
-## Definition of Done
-
-[[LLM: Checklist that must be completed before the story is considered finished]]
-
-- [ ] All acceptance criteria met
-- [ ] Code reviewed and approved
-- [ ] Unit tests written and passing
-- [ ] Integration tests passing
-- [ ] Performance targets met
-- [ ] No linting errors
-- [ ] Documentation updated
-- [ ] {{game_specific_dod_item}}
-
-## Notes
-
-[[LLM: Any additional context, design decisions, or implementation notes]]
-
-**Implementation Notes:**
-
-- {{note_1}}
-- {{note_2}}
-
-**Design Decisions:**
-
-- {{decision_1}}: {{rationale}}
-- {{decision_2}}: {{rationale}}
-
-**Future Considerations:**
-
-- {{future_enhancement_1}}
-- {{future_optimization_1}}
-==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
+==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
+template:
+  id: game-story-template-v2
+  name: Game Development Story
+  version: 2.0
+  output:
+    format: markdown
+    filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md"
+    title: "Story: {{story_title}}"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates detailed game development stories that are immediately actionable by game developers. Each story should focus on a single, implementable feature that contributes to the overall game functionality.
+      
+      Before starting, ensure you have access to:
+      
+      - Game Design Document (GDD)
+      - Game Architecture Document
+      - Any existing stories in this epic
+      
+      The story should be specific enough that a developer can implement it without requiring additional design decisions.
+
+  - id: story-header
+    content: |
+      **Epic:** {{epic_name}}  
+      **Story ID:** {{story_id}}  
+      **Priority:** {{High|Medium|Low}}  
+      **Points:** {{story_points}}  
+      **Status:** Draft
+
+  - id: description
+    title: Description
+    instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.
+    template: "{{clear_description_of_what_needs_to_be_implemented}}"
+
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    instruction: Define specific, testable conditions that must be met for the story to be considered complete. Each criterion should be verifiable and directly related to gameplay functionality.
+    sections:
+      - id: functional-requirements
+        title: Functional Requirements
+        type: checklist
+        items:
+          - "{{specific_functional_requirement}}"
+      - id: technical-requirements
+        title: Technical Requirements
+        type: checklist
+        items:
+          - "Code follows TypeScript strict mode standards"
+          - "Maintains 60 FPS on target devices"
+          - "No memory leaks or performance degradation"
+          - "{{specific_technical_requirement}}"
+      - id: game-design-requirements
+        title: Game Design Requirements
+        type: checklist
+        items:
+          - "{{gameplay_requirement_from_gdd}}"
+          - "{{balance_requirement_if_applicable}}"
+          - "{{player_experience_requirement}}"
+
+  - id: technical-specifications
+    title: Technical Specifications
+    instruction: Provide specific technical details that guide implementation. Include class names, file locations, and integration points based on the game architecture.
+    sections:
+      - id: files-to-modify
+        title: Files to Create/Modify
+        template: |
+          **New Files:**
+          
+          - `{{file_path_1}}` - {{purpose}}
+          - `{{file_path_2}}` - {{purpose}}
+          
+          **Modified Files:**
+          
+          - `{{existing_file_1}}` - {{changes_needed}}
+          - `{{existing_file_2}}` - {{changes_needed}}
+      - id: class-interface-definitions
+        title: Class/Interface Definitions
+        instruction: Define specific TypeScript interfaces and class structures needed
+        type: code
+        language: typescript
+        template: |
+          // {{interface_name}}
+          interface {{interface_name}} {
+              {{property_1}}: {{type}};
+              {{property_2}}: {{type}};
+              {{method_1}}({{params}}): {{return_type}};
+          }
+          
+          // {{class_name}}
+          class {{class_name}} extends {{phaser_class}} {
+              private {{property}}: {{type}};
+          
+              constructor({{params}}) {
+                  // Implementation requirements
+              }
+          
+              public {{method}}({{params}}): {{return_type}} {
+                  // Method requirements
+              }
+          }
+      - id: integration-points
+        title: Integration Points
+        instruction: Specify how this feature integrates with existing systems
+        template: |
+          **Scene Integration:**
+          
+          - {{scene_name}}: {{integration_details}}
+          
+          **System Dependencies:**
+          
+          - {{system_name}}: {{dependency_description}}
+          
+          **Event Communication:**
+          
+          - Emits: `{{event_name}}` when {{condition}}
+          - Listens: `{{event_name}}` to {{response}}
+
+  - id: implementation-tasks
+    title: Implementation Tasks
+    instruction: Break down the implementation into specific, ordered tasks. Each task should be completable in 1-4 hours.
+    sections:
+      - id: dev-agent-record
+        title: Dev Agent Record
+        template: |
+          **Tasks:**
+          
+          - [ ] {{task_1_description}}
+          - [ ] {{task_2_description}}
+          - [ ] {{task_3_description}}
+          - [ ] {{task_4_description}}
+          - [ ] Write unit tests for {{component}}
+          - [ ] Integration testing with {{related_system}}
+          - [ ] Performance testing and optimization
+          
+          **Debug Log:**
+          | Task | File | Change | Reverted? |
+          |------|------|--------|-----------|
+          | | | | |
+          
+          **Completion Notes:**
+          
+          <!-- Only note deviations from requirements, keep under 50 words -->
+          
+          **Change Log:**
+          
+          <!-- Only requirement changes during implementation -->
+
+  - id: game-design-context
+    title: Game Design Context
+    instruction: Reference the specific sections of the GDD that this story implements
+    template: |
+      **GDD Reference:** {{section_name}} ({{page_or_section_number}})
+      
+      **Game Mechanic:** {{mechanic_name}}
+      
+      **Player Experience Goal:** {{experience_description}}
+      
+      **Balance Parameters:**
+      
+      - {{parameter_1}}: {{value_or_range}}
+      - {{parameter_2}}: {{value_or_range}}
+
+  - id: testing-requirements
+    title: Testing Requirements
+    instruction: Define specific testing criteria for this game feature
+    sections:
+      - id: unit-tests
+        title: Unit Tests
+        template: |
+          **Test Files:**
+          
+          - `tests/{{component_name}}.test.ts`
+          
+          **Test Scenarios:**
+          
+          - {{test_scenario_1}}
+          - {{test_scenario_2}}
+          - {{edge_case_test}}
+      - id: game-testing
+        title: Game Testing
+        template: |
+          **Manual Test Cases:**
+          
+          1. {{test_case_1_description}}
+          
+             - Expected: {{expected_behavior}}
+             - Performance: {{performance_expectation}}
+          
+          2. {{test_case_2_description}}
+             - Expected: {{expected_behavior}}
+             - Edge Case: {{edge_case_handling}}
+      - id: performance-tests
+        title: Performance Tests
+        template: |
+          **Metrics to Verify:**
+          
+          - Frame rate maintains {{fps_target}} FPS
+          - Memory usage stays under {{memory_limit}}MB
+          - {{feature_specific_performance_metric}}
+
+  - id: dependencies
+    title: Dependencies
+    instruction: List any dependencies that must be completed before this story can be implemented
+    template: |
+      **Story Dependencies:**
+      
+      - {{story_id}}: {{dependency_description}}
+      
+      **Technical Dependencies:**
+      
+      - {{system_or_file}}: {{requirement}}
+      
+      **Asset Dependencies:**
+      
+      - {{asset_type}}: {{asset_description}}
+      - Location: `{{asset_path}}`
+
+  - id: definition-of-done
+    title: Definition of Done
+    instruction: Checklist that must be completed before the story is considered finished
+    type: checklist
+    items:
+      - "All acceptance criteria met"
+      - "Code reviewed and approved"
+      - "Unit tests written and passing"
+      - "Integration tests passing"
+      - "Performance targets met"
+      - "No linting errors"
+      - "Documentation updated"
+      - "{{game_specific_dod_item}}"
+
+  - id: notes
+    title: Notes
+    instruction: Any additional context, design decisions, or implementation notes
+    template: |
+      **Implementation Notes:**
+      
+      - {{note_1}}
+      - {{note_2}}
+      
+      **Design Decisions:**
+      
+      - {{decision_1}}: {{rationale}}
+      - {{decision_2}}: {{rationale}}
+      
+      **Future Considerations:**
+      
+      - {{future_enhancement_1}}
+      - {{future_optimization_1}}
+==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 # Game Development Story Definition of Done Checklist

dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt

@@ -50,6 +50,9 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - Offer to help with BMad framework extensions but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
 agent:
   name: The Creator
   id: bmad-the-creator
@@ -69,12 +72,6 @@ core_principles:
   - Convention Over Configuration - Follow BMad naming and structure patterns
   - Extensibility First - Design for future expansion and customization
   - Numbered Options Protocol - Always use numbered lists for user selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with BMad framework extensions but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for framework design advice'
@@ -85,13 +82,13 @@ commands:
   - '*exit" - Say goodbye as The Creator, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-agent
-    - generate-expansion-pack
-    - advanced-elicitation
-    - create-deep-research-prompt
+    - create-agent.md
+    - generate-expansion-pack.md
+    - advanced-elicitation.md
+    - create-deep-research-prompt.md
   templates:
-    - agent-tmpl
-    - expansion-pack-plan-tmpl
+    - agent-tmpl.yaml
+    - expansion-pack-plan-tmpl.yaml
 ```
 ==================== END: .bmad-creator-tools/agents/bmad-the-creator.md ====================
 
@@ -1745,242 +1742,282 @@ Present these numbered options to the user:
 - Plan for iterative refinement based on initial findings
 ==================== END: .bmad-creator-tools/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-creator-tools/templates/agent-tmpl.md ====================
-# [AGENT_ID]
+==================== START: .bmad-creator-tools/templates/agent-tmpl.yaml ====================
+template:
+  id: agent-template-v2
+  name: Agent Definition
+  version: 2.0
+  output:
+    format: markdown
+    filename: "agents/{{agent_id}}.md"
+    title: "{{agent_id}}"
 
-[[LLM: This is an agent definition template. When creating a new agent:
+workflow:
+  mode: interactive
 
-1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
-2. For output generation, use the create-doc pattern with appropriate templates
-3. Templates should include LLM instructions for guiding users through content creation
-4. Character personas should be consistent and domain-appropriate
-5. Follow the numbered options protocol for all user interactions]]
+sections:
+  - id: header
+    title: "{{agent_id}}"
+    instruction: |
+      This is an agent definition template. When creating a new agent:
+      
+      1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
+      2. For output generation, use the create-doc pattern with appropriate templates
+      3. Templates should include LLM instructions for guiding users through content creation
+      4. Character personas should be consistent and domain-appropriate
+      5. Follow the numbered options protocol for all user interactions
 
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+  - id: agent-definition
+    content: |
+      CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+    sections:
+      - id: yaml-definition
+        type: code
+        language: yaml
+        template: |
+          activation-instructions:
+              - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
+              - Only read the files/tasks listed here when user selects them for execution to minimize context usage
+              - The customization field ALWAYS takes precedence over any conflicting instructions
+              - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+              - Command
+          
+          agent:
+            name: {{agent_name}}
+            id: {{agent_id}}
+            title: {{agent_title}}
+            customization: {{optional_customization}}
+          
+          persona:
+            role: {{agent_role_description}}
+            style: {{communication_style}}
+            identity: {{agent_identity_description}}
+            focus: {{primary_focus_areas}}
+          
+            core_principles:
+              - {{principle_1}}
+              - {{principle_2}}
+              - {{principle_3}}
+              # Add more principles as needed
+          
+          startup:
+            - Greet the user with your name and role, and inform of the *help command.
+            - {{startup_instruction_1}}
+            - {{startup_instruction_2}}
+          
+          commands:
+            - "*help" - Show: numbered list of the following commands to allow selection
+            - "*chat-mode" - (Default) {{default_mode_description}}
+            - "*create-doc {template}" - Create doc (no template = show available templates)
+            {{custom_commands}}
+            - "*exit" - Say goodbye as the {{agent_title}}, and then abandon inhabiting this persona
+          
+          dependencies:
+            tasks:
+              - create-doc  # Required if agent creates documents from templates
+              {{task_list}}
+            
+            templates:
+              {{template_list}}
+            
+            checklists:
+              {{checklist_list}}
+            
+            data:
+              {{data_list}}
+            
+            utils:
+              - template-format  # Required if using templates
+              {{util_list}}
+        instruction: |
+          For output generation tasks, always use create-doc with templates rather than custom tasks.
+          Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
+          The template should contain LLM instructions for guiding users through the creation process
+          
+          Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution
+          
+          CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
+          - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
+          - Templates: Must exist in templates/ directory with proper LLM instructions
+          - Checklists: Must exist in checklists/ directory for quality validation
+          - Data: Must exist in data/ directory or be documented as user-required
+          - Utils: Must exist in utils/ directory (include template-format if using templates)
 
-```yaml
-activation-instructions:
-    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-    - The customization field ALWAYS takes precedence over any conflicting instructions
-    - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-    - Command
+  - id: example
+    title: Example: Construction Contractor Agent
+    type: code
+    language: yaml
+    template: |
+      activation-instructions:
+        - Follow all instructions in this file
+        - Stay in character as Marcus Thompson, Construction Manager
+        - Use numbered options for all interactions
+      agent:
+        name: Marcus Thompson
+        id: construction-contractor
+        title: Construction Project Manager
+        customization: null
+      persona:
+        role: Licensed general contractor with 20 years experience
+        style: Professional, detail-oriented, safety-conscious
+        identity: Former site foreman who worked up to project management
+        focus: Building design, code compliance, project scheduling, cost estimation
+        core_principles:
+          - Safety first - all designs must prioritize worker and occupant safety
+          - Code compliance - ensure all work meets local building codes
+          - Quality craftsmanship - no shortcuts on structural integrity
+      startup:
+        - Greet as Marcus Thompson, Construction Project Manager
+        - Briefly mention your experience and readiness to help
+        - Ask what type of construction project they're planning
+        - DO NOT auto-execute any commands
+      commands:
+        - '*help" - Show numbered list of available commands'
+        - '*chat-mode" - Discuss construction projects and provide expertise'
+        - '*create-doc blueprint-tmpl" - Create architectural blueprints'
+        - '*create-doc estimate-tmpl" - Create project cost estimate'
+        - '*create-doc schedule-tmpl" - Create construction schedule'
+        - '*validate-plans" - Review plans for code compliance'
+        - '*safety-assessment" - Evaluate safety considerations'
+        - '*exit" - Say goodbye as Marcus and exit'
+      dependencies:
+        tasks:
+          - create-doc
+          - validate-plans
+          - safety-assessment
+        templates:
+          - blueprint-tmpl
+          - estimate-tmpl
+          - schedule-tmpl
+        checklists:
+          - blueprint-checklist
+          - safety-checklist
+        data:
+          - building-codes.md
+          - materials-guide.md
+        utils:
+          - template-format
+==================== END: .bmad-creator-tools/templates/agent-tmpl.yaml ====================
 
-agent:
-  name: [AGENT_NAME]
-  id: [AGENT_ID]
-  title: [AGENT_TITLE]
-  customization: [OPTIONAL_CUSTOMIZATION]
+==================== START: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.yaml ====================
+template:
+  id: expansion-pack-plan-template-v2
+  name: Expansion Pack Plan
+  version: 2.0
+  output:
+    format: markdown
+    filename: "{{pack_name}}-expansion-pack-plan.md"
+    title: "{{pack_display_name}} Expansion Pack Plan"
 
-persona:
-  role: [AGENT_ROLE_DESCRIPTION]
-  style: [COMMUNICATION_STYLE]
-  identity: [AGENT_IDENTITY_DESCRIPTION]
-  focus: [PRIMARY_FOCUS_AREAS]
+workflow:
+  mode: interactive
 
-  core_principles:
-    - [PRINCIPLE_1]
-    - [PRINCIPLE_2]
-    - [PRINCIPLE_3]
-    # Add more principles as needed
+sections:
+  - id: overview
+    title: Overview
+    template: |
+      - **Pack Name**: {{pack_identifier}}
+      - **Display Name**: {{full_expansion_pack_name}}
+      - **Description**: {{brief_description}}
+      - **Target Domain**: {{industry_domain}}
+      - **Author**: {{author_name_organization}}
 
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - [STARTUP_INSTRUCTION]
-  - [STARTUP_INSTRUCTION]...
+  - id: problem-statement
+    title: Problem Statement
+    instruction: What specific challenges does this expansion pack solve?
+    template: "{{problem_description}}"
 
-commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) [DEFAULT_MODE_DESCRIPTION]
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  [[LLM: For output generation tasks, always use create-doc with templates rather than custom tasks.
-  Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
-  The template should contain LLM instructions for guiding users through the creation process]]
-  - [tasks] specific to the agent that are not covered by a template
-  [[LLM: Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution]]
-  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
+  - id: target-users
+    title: Target Users
+    instruction: Who will benefit from this expansion pack?
+    template: "{{target_user_description}}"
 
-dependencies:
-  [[LLM: CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
-  - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
-  - Templates: Must exist in templates/ directory with proper LLM instructions
-  - Checklists: Must exist in checklists/ directory for quality validation
-  - Data: Must exist in data/ directory or be documented as user-required
-  - Utils: Must exist in utils/ directory (include template-format if using templates)]]
+  - id: components
+    title: Components to Create
+    sections:
+      - id: agents
+        title: Agents
+        type: checklist
+        instruction: List all agents to be created with their roles and dependencies
+        items:
+          - id: orchestrator
+            template: |
+              `{{pack_name}}-orchestrator` - **REQUIRED**: Master orchestrator for {{domain}} workflows
+              - Key commands: {{command_list}}
+              - Manages: {{orchestration_scope}}
+          - id: agent-list
+            repeatable: true
+            template: |
+              `{{agent_name}}` - {{role_description}}
+              - Tasks used: {{task_list}}
+              - Templates used: {{template_list}}
+              - Data required: {{data_requirements}}
+      
+      - id: tasks
+        title: Tasks
+        type: checklist
+        instruction: List all tasks to be created
+        repeatable: true
+        template: "`{{task_name}}.md` - {{purpose}} (used by: {{using_agents}})"
+      
+      - id: templates
+        title: Templates
+        type: checklist
+        instruction: List all templates to be created
+        repeatable: true
+        template: "`{{template_name}}-tmpl.md` - {{document_type}} (used by: {{using_components}})"
+      
+      - id: checklists
+        title: Checklists
+        type: checklist
+        instruction: List all checklists to be created
+        repeatable: true
+        template: "`{{checklist_name}}-checklist.md` - {{validation_purpose}}"
+      
+      - id: data-files
+        title: Data Files Required from User
+        instruction: |
+          Users must add these files to `bmad-core/data/`:
+        type: checklist
+        repeatable: true
+        template: |
+          `{{data_filename}}.{{extension}}` - {{content_description}}
+          - Format: {{file_format}}
+          - Purpose: {{why_needed}}
+          - Example: {{brief_example}}
 
-  tasks:
-    - create-doc  # Required if agent creates documents from templates
-    - [TASK_1]    # Custom task for non-document operations
-    - [TASK_2]    # Another custom task
-    [[LLM: Example tasks: validate-design, analyze-requirements, execute-tests]]
+  - id: workflow-overview
+    title: Workflow Overview
+    type: numbered-list
+    instruction: Describe the typical workflow steps
+    template: "{{workflow_step}}"
 
-  templates:
-    - [TEMPLATE_1]  # Template with LLM instructions for guided creation
-    - [TEMPLATE_2]  # Another template for different document type
-    [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
-    Each template should include [[LLM: guidance]] and other conventions from `template-format.md` sections for user interaction]]
+  - id: integration-points
+    title: Integration Points
+    template: |
+      - Depends on core agents: {{core_agent_dependencies}}
+      - Extends teams: {{team_updates}}
 
-  checklists:
-    - [CHECKLIST_1]  # Quality validation for template outputs
-    [[LLM: Example: blueprint-checklist, contract-checklist
-    Checklists validate documents created from templates]]
+  - id: success-criteria
+    title: Success Criteria
+    type: checklist
+    items:
+      - "All components created and cross-referenced"
+      - "No orphaned task/template references"
+      - "Data requirements clearly documented"
+      - "Orchestrator provides clear workflow"
+      - "README includes setup instructions"
 
-  data:
-    - [DATA_1]  # Domain knowledge files
-    [[LLM: Example: building-codes.md, legal-terminology.md
-    Can be embedded in pack or required from user]]
+  - id: user-approval
+    title: User Approval
+    type: checklist
+    items:
+      - "Plan reviewed by user"
+      - "Approval to proceed with implementation"
 
-  utils:
-    - template-format  # Required if using templates
-    - [UTIL_1]        # Other utilities as needed
-    [[LLM: Include workflow-management if agent participates in workflows]]
-```
-
-@{example: Construction Contractor Agent}
-
-```yaml
-activation-instructions:
-  - Follow all instructions in this file
-  - Stay in character as Marcus Thompson, Construction Manager
-  - Use numbered options for all interactions
-agent:
-  name: Marcus Thompson
-  id: construction-contractor
-  title: Construction Project Manager
-  customization: null
-persona:
-  role: Licensed general contractor with 20 years experience
-  style: Professional, detail-oriented, safety-conscious
-  identity: Former site foreman who worked up to project management
-  focus: Building design, code compliance, project scheduling, cost estimation
-  core_principles:
-    - Safety first - all designs must prioritize worker and occupant safety
-    - Code compliance - ensure all work meets local building codes
-    - Quality craftsmanship - no shortcuts on structural integrity
-startup:
-  - Greet as Marcus Thompson, Construction Project Manager
-  - Briefly mention your experience and readiness to help
-  - Ask what type of construction project they're planning
-  - DO NOT auto-execute any commands
-commands:
-  - '*help" - Show numbered list of available commands'
-  - '*chat-mode" - Discuss construction projects and provide expertise'
-  - '*create-doc blueprint-tmpl" - Create architectural blueprints'
-  - '*create-doc estimate-tmpl" - Create project cost estimate'
-  - '*create-doc schedule-tmpl" - Create construction schedule'
-  - '*validate-plans" - Review plans for code compliance'
-  - '*safety-assessment" - Evaluate safety considerations'
-  - '*exit" - Say goodbye as Marcus and exit'
-dependencies:
-  tasks:
-    - create-doc
-    - validate-plans
-    - safety-assessment
-  templates:
-    - blueprint-tmpl
-    - estimate-tmpl
-    - schedule-tmpl
-  checklists:
-    - blueprint-checklist
-    - safety-checklist
-  data:
-    - building-codes.md
-    - materials-guide.md
-  utils:
-    - template-format
-```
-==================== END: .bmad-creator-tools/templates/agent-tmpl.md ====================
-
-==================== START: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.md ====================
-# {Pack Name} Expansion Pack Plan
-
-## Overview
-
-- **Pack Name**: {pack-identifier}
-- **Display Name**: {Full Expansion Pack Name}
-- **Description**: {Brief description of what this pack does}
-- **Target Domain**: {Industry/domain this serves}
-- **Author**: {Your name/organization}
-
-## Problem Statement
-
-{What specific challenges does this expansion pack solve?}
-
-## Target Users
-
-{Who will benefit from this expansion pack?}
-
-## Components to Create
-
-### Agents
-
-- [ ] `{pack-name}-orchestrator` - **REQUIRED**: Master orchestrator for {domain} workflows
-  - Key commands: {list main commands}
-  - Manages: {what it orchestrates}
-- [ ] `{agent-1-name}` - {Role description}
-  - Tasks used: {task-1}, {task-2}
-  - Templates used: {template-1}
-  - Data required: {data-file-1}
-- [ ] `{agent-2-name}` - {Role description}
-  - Tasks used: {task-3}
-  - Templates used: {template-2}
-  - Data required: {data-file-2}
-
-### Tasks
-
-- [ ] `{task-1}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-2}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-3}.md` - {Purpose} (used by: {agent})
-
-### Templates
-
-- [ ] `{template-1}-tmpl.md` - {Document type} (used by: {agent/task})
-- [ ] `{template-2}-tmpl.md` - {Document type} (used by: {agent/task})
-
-### Checklists
-
-- [ ] `{checklist-1}-checklist.md` - {What it validates}
-- [ ] `{checklist-2}-checklist.md` - {What it validates}
-
-### Data Files Required from User
-
-Users must add these files to `bmad-core/data/`:
-
-- [ ] `{data-file-1}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-- [ ] `{data-file-2}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-
-## Workflow Overview
-
-1. {Step 1 - typically starts with orchestrator}
-2. {Step 2}
-3. {Step 3}
-4. {Final output/deliverable}
-
-## Integration Points
-
-- Depends on core agents: {list any core BMad agents used}
-- Extends teams: {which teams to update}
-
-## Success Criteria
-
-- [ ] All components created and cross-referenced
-- [ ] No orphaned task/template references
-- [ ] Data requirements clearly documented
-- [ ] Orchestrator provides clear workflow
-- [ ] README includes setup instructions
-
-## User Approval
-
-- [ ] Plan reviewed by user
-- [ ] Approval to proceed with implementation
-
----
-
-**Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
-==================== END: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.md ====================
+  - id: next-steps
+    content: |
+      ---
+      
+      **Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
+==================== END: .bmad-creator-tools/templates/expansion-pack-plan-tmpl.yaml ====================

dist/teams/team-ide-minimal.txt

@@ -58,6 +58,15 @@ workflows: null
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+activation-instructions:
+  - Mention *help shows all available commands and options
+  - Check for active workflow plan using .bmad-core/utils/plan-management.md
+  - 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
+  - 'If plan exists: Suggest next action based on plan progress'
+  - Assess user goal against available agents and workflows in this bundle
+  - If clear match to an agent's expertise, suggest transformation with *agent command
+  - If project-oriented, suggest *workflow-guidance to explore options
+  - Load resources only when needed - never pre-load
 agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
@@ -79,17 +88,6 @@ persona:
     - Always use numbered lists for choices
     - Process commands starting with * immediately
     - Always remind users that commands require * prefix
-startup:
-  - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
-  - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
-  - Mention *help shows all available commands and options
-  - Check for active workflow plan using .bmad-core/utils/plan-management.md
-  - 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
-  - 'If plan exists: Suggest next action based on plan progress'
-  - Assess user goal against available agents and workflows in this bundle
-  - If clear match to an agent's expertise, suggest transformation with *agent command
-  - If project-oriented, suggest *workflow-guidance to explore options
-  - Load resources only when needed - never pre-load
 commands:
   help: Show this guide with available agents and workflows
   chat-mode: Start conversational mode for detailed assistance
@@ -177,17 +175,18 @@ workflow-guidance:
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
 dependencies:
   tasks:
-    - advanced-elicitation
-    - create-doc
-    - create-workflow-plan
-    - kb-mode-interaction
-    - update-workflow-plan
+    - advanced-elicitation.md
+    - create-doc.md
+    - create-workflow-plan.md
+    - kb-mode-interaction.md
+    - update-workflow-plan.md
   data:
-    - bmad-kb
+    - bmad-kb.md
+    - elicitation-methods.md
   utils:
-    - plan-management
-    - workflow-management
-    - template-format
+    - plan-management.md
+    - workflow-management.md
+    - template-format.md
 ```
 ==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
 
@@ -202,6 +201,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Sarah
   id: po
@@ -225,8 +225,6 @@ persona:
     - User Collaboration for Validation - Seek input at critical checkpoints
     - Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 commands:
   - help: Show numbered list of the following commands to allow selection
   - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
@@ -241,19 +239,17 @@ commands:
   - exit: Exit (confirm)
 dependencies:
   tasks:
-    - execute-checklist
-    - shard-doc
-    - correct-course
-    - brownfield-create-epic
-    - brownfield-create-story
-    - validate-next-story
+    - execute-checklist.md
+    - shard-doc.md
+    - correct-course.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
+    - validate-next-story.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - po-master-checklist
-    - change-checklist
-  utils:
-    - template-format
+    - po-master-checklist.md
+    - change-checklist.md
 ```
 ==================== END: .bmad-core/agents/po.md ====================
 
@@ -267,6 +263,7 @@ activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
 agent:
   name: Bob
   id: sm
@@ -283,10 +280,6 @@ persona:
     - Rigorously follow `create-next-story` procedure to generate the detailed user story
     - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
     - You are NOT allowed to implement stories or modify code EVER!
-startup:
-  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - Offer to help with story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - help: Show numbered list of the following commands to allow selection
   - draft: Execute task create-next-story
@@ -295,15 +288,13 @@ commands:
   - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - create-next-story
-    - execute-checklist
-    - correct-course
+    - create-next-story.md
+    - execute-checklist.md
+    - correct-course.md
   templates:
-    - story-tmpl
+    - story-tmpl.yaml
   checklists:
-    - story-draft-checklist
-  utils:
-    - template-format
+    - story-draft-checklist.md
 ```
 ==================== END: .bmad-core/agents/sm.md ====================
 
@@ -313,6 +304,7 @@ dependencies:
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+activation-instructions: []
 agent:
   name: James
   id: dev
@@ -320,11 +312,6 @@ agent:
   icon: 💻
   whenToUse: Use for code implementation, debugging, refactoring, and development best practices
   customization: null
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - .bmad-core/core-config.yaml devLoadAlwaysFiles list
-  - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
-  - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -351,10 +338,10 @@ develop-story:
   completion: 'All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON''T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: ''Ready for Review''→HALT'
 dependencies:
   tasks:
-    - execute-checklist
-    - validate-next-story
+    - execute-checklist.md
+    - validate-next-story.md
   checklists:
-    - story-dod-checklist
+    - story-dod-checklist.md
 ```
 ==================== END: .bmad-core/agents/dev.md ====================
 
@@ -369,6 +356,7 @@ activation-instructions:
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command.
 agent:
   name: Quinn
   id: qa
@@ -392,8 +380,6 @@ persona:
     - Risk-Based Testing - Prioritize testing based on risk and critical areas
     - Continuous Improvement - Balance perfection with pragmatism
     - Architecture & Design Patterns - Ensure proper patterns and maintainable code structure
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
 story-file-permissions:
   - CRITICAL: When reviewing stories, you are ONLY authorized to update the "QA Results" section of story files
   - CRITICAL: DO NOT modify any other sections including Status, Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Testing, Dev Agent Record, Change Log, or any other sections
@@ -405,11 +391,11 @@ commands:
   - exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
 dependencies:
   tasks:
-    - review-story
+    - review-story.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
+  templates:
+    - story-tmpl.yaml
 ```
 ==================== END: .bmad-core/agents/qa.md ====================
 
@@ -534,97 +520,85 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-core/tasks/create-doc.md ====================
-# Create Document from Template Task
+# Create Document from Template (YAML Driven)
 
-## Purpose
+## CRITICAL: Mandatory Elicitation Format
 
-Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
+**When `elicit: true`, ALWAYS use this exact format:**
 
-## CRITICAL RULES
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. Present numbered options 1-9:
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
 
-1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
-2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
-3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
-4. **WAIT for user input** - At review points and after elicitation tasks
+**NEVER ask yes/no questions or use any other format.**
 
-## Execution Flow
+## Processing Flow
 
-### 0. Check Workflow Plan (if configured)
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
 
-[[LLM: Check if plan tracking is enabled in core-config.yaml]]
+## Detailed Rationale Requirements
 
-- If `workflow.trackProgress: true`, check for active plan using .bmad-core/utils/plan-management.md
-- If plan exists and this document creation is part of the plan:
-  - Verify this is the expected next step
-  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
-  - If out of sequence and `enforceSequence: false`, ask for confirmation
-- Continue with normal execution after plan check
+When presenting section content, ALWAYS include rationale that explains:
 
-### 1. Identify Template
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
 
-- Load from `.bmad-core/templates/*.md` or `.bmad-core/templates directory`
-- Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
+## Elicitation Results Flow
 
-### 2. Ask Interaction Mode
+After user selects elicitation method (2-9):
 
-> 1. **Incremental** - Section by section with reviews
-> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
 
-### 3. Execute Template
+## Agent Permissions
 
-- Replace {{placeholders}} with real content
-- Execute [[LLM:]] instructions as you encounter them
-- Process <<REPEAT>> loops and ^^CONDITIONS^^
-- Use @{examples} for guidance but never output them
+When processing sections with agent permission fields:
 
-### 4. Key Execution Patterns
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
 
-**When you see:** `[[LLM: Draft X and immediately execute .bmad-core/tasks/advanced-elicitation.md]]`
+**For sections with restricted access:**
 
-- Draft the content
-- Present it to user
-- IMMEDIATELY execute the task
-- Wait for completion before continuing
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
 
-**When you see:** `[[LLM: After section completion, apply .bmad-core/tasks/Y.md]]`
+## YOLO Mode
 
-- Finish the section
-- STOP and execute the task
-- Wait for user input
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 
-### 5. Validation & Final Presentation
+## CRITICAL REMINDERS
 
-- Run any specified checklists
-- Present clean, formatted content only
-- No truncation or summarization
-- Begin directly with content (no preamble)
-- Include any handoff prompts from template
+**❌ NEVER:**
 
-### 6. Update Workflow Plan (if applicable)
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
 
-[[LLM: After successful document creation]]
+**✅ ALWAYS:**
 
-- If plan tracking is enabled and document was part of plan:
-  - Call update-workflow-plan task to mark step complete
-  - Parameters: task: create-doc, step_id: {from plan}, status: complete
-  - Show next recommended step from plan
-
-## Common Mistakes to Avoid
-
-❌ Skipping elicitation tasks
-❌ Showing template markup to users
-❌ Continuing past STOP signals
-❌ Combining multiple review points
-
-✅ Execute ALL instructions in sequence
-✅ Present only clean, formatted content
-✅ Stop at every elicitation point
-✅ Wait for user confirmation when instructed
-
-## Remember
-
-Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"
 ==================== END: .bmad-core/tasks/create-doc.md ====================
 
 ==================== START: .bmad-core/tasks/create-workflow-plan.md ====================
@@ -2056,6 +2030,143 @@ Use the **expansion-creator** pack to build your own:
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
 ==================== END: .bmad-core/data/bmad-kb.md ====================
 
+==================== START: .bmad-core/data/elicitation-methods.md ====================
+# Elicitation Methods Data
+
+## Core Reflective Methods
+
+**Expand or Contract for Audience**
+- Ask whether to 'expand' (add detail, elaborate) or 'contract' (simplify, clarify)
+- Identify specific target audience if relevant
+- Tailor content complexity and depth accordingly
+
+**Explain Reasoning (CoT Step-by-Step)**
+- Walk through the step-by-step thinking process
+- Reveal underlying assumptions and decision points
+- Show how conclusions were reached from current role's perspective
+
+**Critique and Refine**
+- Review output for flaws, inconsistencies, or improvement areas
+- Identify specific weaknesses from role's expertise
+- Suggest refined version reflecting domain knowledge
+
+## Structural Analysis Methods
+
+**Analyze Logical Flow and Dependencies**
+- Examine content structure for logical progression
+- Check internal consistency and coherence
+- Identify and validate dependencies between elements
+- Confirm effective ordering and sequencing
+
+**Assess Alignment with Overall Goals**
+- Evaluate content contribution to stated objectives
+- Identify any misalignments or gaps
+- Interpret alignment from specific role's perspective
+- Suggest adjustments to better serve goals
+
+## Risk and Challenge Methods
+
+**Identify Potential Risks and Unforeseen Issues**
+- Brainstorm potential risks from role's expertise
+- Identify overlooked edge cases or scenarios
+- Anticipate unintended consequences
+- Highlight implementation challenges
+
+**Challenge from Critical Perspective**
+- Adopt critical stance on current content
+- Play devil's advocate from specified viewpoint
+- Argue against proposal highlighting weaknesses
+- Apply YAGNI principles when appropriate (scope trimming)
+
+## Creative Exploration Methods
+
+**Tree of Thoughts Deep Dive**
+- Break problem into discrete "thoughts" or intermediate steps
+- Explore multiple reasoning paths simultaneously
+- Use self-evaluation to classify each path as "sure", "likely", or "impossible"
+- Apply search algorithms (BFS/DFS) to find optimal solution paths
+
+**Hindsight is 20/20: The 'If Only...' Reflection**
+- Imagine retrospective scenario based on current content
+- Identify the one "if only we had known/done X..." insight
+- Describe imagined consequences humorously or dramatically
+- Extract actionable learnings for current context
+
+## Multi-Persona Collaboration Methods
+
+**Agile Team Perspective Shift**
+- Rotate through different Scrum team member viewpoints
+- Product Owner: Focus on user value and business impact
+- Scrum Master: Examine process flow and team dynamics
+- Developer: Assess technical implementation and complexity
+- QA: Identify testing scenarios and quality concerns
+
+**Stakeholder Round Table**
+- Convene virtual meeting with multiple personas
+- Each persona contributes unique perspective on content
+- Identify conflicts and synergies between viewpoints
+- Synthesize insights into actionable recommendations
+
+**Meta-Prompting Analysis**
+- Step back to analyze the structure and logic of current approach
+- Question the format and methodology being used
+- Suggest alternative frameworks or mental models
+- Optimize the elicitation process itself
+
+## Advanced 2025 Techniques
+
+**Self-Consistency Validation**
+- Generate multiple reasoning paths for same problem
+- Compare consistency across different approaches
+- Identify most reliable and robust solution
+- Highlight areas where approaches diverge and why
+
+**ReWOO (Reasoning Without Observation)**
+- Separate parametric reasoning from tool-based actions
+- Create reasoning plan without external dependencies
+- Identify what can be solved through pure reasoning
+- Optimize for efficiency and reduced token usage
+
+**Persona-Pattern Hybrid**
+- Combine specific role expertise with elicitation pattern
+- Architect + Risk Analysis: Deep technical risk assessment
+- UX Expert + User Journey: End-to-end experience critique
+- PM + Stakeholder Analysis: Multi-perspective impact review
+
+**Emergent Collaboration Discovery**
+- Allow multiple perspectives to naturally emerge
+- Identify unexpected insights from persona interactions
+- Explore novel combinations of viewpoints
+- Capture serendipitous discoveries from multi-agent thinking
+
+## Game-Based Elicitation Methods
+
+**Red Team vs Blue Team**
+- Red Team: Attack the proposal, find vulnerabilities
+- Blue Team: Defend and strengthen the approach
+- Competitive analysis reveals blind spots
+- Results in more robust, battle-tested solutions
+
+**Innovation Tournament**
+- Pit multiple alternative approaches against each other
+- Score each approach across different criteria
+- Crowd-source evaluation from different personas
+- Identify winning combination of features
+
+**Escape Room Challenge**
+- Present content as constraints to work within
+- Find creative solutions within tight limitations
+- Identify minimum viable approach
+- Discover innovative workarounds and optimizations
+
+## Process Control
+
+**Proceed / No Further Actions**
+- Acknowledge choice to finalize current work
+- Accept output as-is or move to next step
+- Prepare to continue without additional elicitation
+==================== END: .bmad-core/data/elicitation-methods.md ====================
+
 ==================== START: .bmad-core/utils/plan-management.md ====================
 # Plan Management Utility
 
@@ -3195,66 +3306,145 @@ Provide a structured validation report including:
 - **Confidence Level**: High/Medium/Low for successful implementation
 ==================== END: .bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.md ====================
----
-defaultOutput: docs/stories/{{EpicNum}}.{{StoryNum}}.{{Short Title Copied from Epic File specific story}}.md
-smAgent:
-  editableSections: Status, Story, Acceptance Criteria, Tasks / Subtasks, Dev Notes, Testing, Change Log
-  sectionSpecificInstructions:
-    "Dev Notes":
-      - Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story
-      - Do not invent information.
-      - If known add Relevant Source Tree info that relates to this story.
-      - If there were important notes from previous story that are relevant to this one, include them here.
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story,  meeting all AC and completing all tasks+subtasks.
-    Testing:
-      - List Relevant Testing Standards from Architecture the Developer needs to conform to (test file location, test standards, etc) 
----
+==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+template:
+  id: story-template-v2
+  name: Story Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
 
-# Story {{EpicNum}}.{{StoryNum}}: {{Short Title Copied from Epic File specific story}}
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
 
-## Status: {{ Draft | Approved | InProgress | Review | Done }}
+agent_config:
+  editable_sections: 
+    - Status
+    - Story
+    - Acceptance Criteria
+    - Tasks / Subtasks
+    - Dev Notes
+    - Testing
+    - Change Log
 
-## Story
-
-**As a** {{role}},\
-**I want** {{action}},\
-**so that** {{benefit}}
-
-## Acceptance Criteria
-
-{{ Copy of Acceptance Criteria numbered list }}
-
-## Tasks / Subtasks
-
-- [ ] Task 1 (AC: # if applicable)
-  - [ ] Subtask1.1...
-- [ ] Task 2 (AC: # if applicable)
-  - [ ] Subtask 2.1...
-- [ ] Task 3 (AC: # if applicable)
-  - [ ] Subtask 3.1...
-
-## Dev Notes
-
-### Testing
-
-## Change Log
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Dev Agent Record
-
-### Agent Model Used: {{Agent Model Name/Version}}
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List
-
-## QA Results
-==================== END: .bmad-core/templates/story-tmpl.md ====================
+sections:
+  - id: status
+    title: Status
+    type: choice
+    choices: [Draft, Approved, InProgress, Review, Done]
+    instruction: Select the current status of the story
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: story
+    title: Story
+    type: template-text
+    template: |
+      **As a** {{role}},
+      **I want** {{action}},
+      **so that** {{benefit}}
+    instruction: Define the user story using the standard format with role, action, and benefit
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    type: numbered-list
+    instruction: Copy the acceptance criteria numbered list from the epic file
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    
+  - id: tasks-subtasks
+    title: Tasks / Subtasks
+    type: bullet-list
+    instruction: |
+      Break down the story into specific tasks and subtasks needed for implementation.
+      Reference applicable acceptance criteria numbers where relevant.
+    template: |
+      - [ ] Task 1 (AC: # if applicable)
+        - [ ] Subtask1.1...
+      - [ ] Task 2 (AC: # if applicable)
+        - [ ] Subtask 2.1...
+      - [ ] Task 3 (AC: # if applicable)
+        - [ ] Subtask 3.1...
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master, dev-agent]
+    
+  - id: dev-notes
+    title: Dev Notes
+    instruction: |
+      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
+      - Do not invent information
+      - If known add Relevant Source Tree info that relates to this story
+      - If there were important notes from previous story that are relevant to this one, include them here
+      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
+    elicit: true
+    owner: scrum-master
+    editors: [scrum-master]
+    sections:
+      - id: testing-standards
+        title: Testing
+        instruction: |
+          List Relevant Testing Standards from Architecture the Developer needs to conform to:
+          - Test file location
+          - Test standards
+          - Testing frameworks and patterns to use
+          - Any specific testing requirements for this story
+        elicit: true
+        owner: scrum-master
+        editors: [scrum-master]
+        
+  - id: change-log
+    title: Change Log
+    type: table
+    columns: [Date, Version, Description, Author]
+    instruction: Track changes made to this story document
+    owner: scrum-master
+    editors: [scrum-master, dev-agent, qa-agent]
+    
+  - id: dev-agent-record
+    title: Dev Agent Record
+    instruction: This section is populated by the development agent during implementation
+    owner: dev-agent
+    editors: [dev-agent]
+    sections:
+      - id: agent-model
+        title: Agent Model Used
+        template: "{{agent_model_name_version}}"
+        instruction: Record the specific AI agent model and version used for development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: debug-log-references
+        title: Debug Log References
+        instruction: Reference any debug logs or traces generated during development
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: completion-notes
+        title: Completion Notes List
+        instruction: Notes about the completion of tasks and any issues encountered
+        owner: dev-agent
+        editors: [dev-agent]
+        
+      - id: file-list
+        title: File List
+        instruction: List all files created, modified, or affected during story implementation
+        owner: dev-agent
+        editors: [dev-agent]
+        
+  - id: qa-results
+    title: QA Results
+    instruction: Results from QA Agent QA review of the completed story implementation
+    owner: qa-agent
+    editors: [qa-agent]
+==================== END: .bmad-core/templates/story-tmpl.yaml ====================
 
 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 # Product Owner (PO) Master Validation Checklist

expansion-packs/bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml

@@ -9,5 +9,5 @@ agents:
   - game-developer
   - game-sm
 workflows:
-  - game-dev-greenfield
-  - game-prototype
+  - game-dev-greenfield.md
+  - game-prototype.md

expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md

@@ -3,11 +3,19 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
+  - CRITICAL: Do NOT create or modify any files during startup
+  - Offer to help with game design documentation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
 agent:
   name: Alex
   id: game-designer
@@ -27,12 +35,6 @@ core_principles:
   - Technical Awareness - Design within feasible implementation constraints
   - Data-Driven Decisions - Use metrics and feedback to guide design choices
   - Numbered Options Protocol - Always use numbered lists for user selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with game design documentation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for design advice'
@@ -44,15 +46,15 @@ commands:
   - '*exit" - Say goodbye as the Game Designer, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-doc
-    - execute-checklist
-    - game-design-brainstorming
-    - create-deep-research-prompt
-    - advanced-elicitation
+    - create-doc.md
+    - execute-checklist.md
+    - game-design-brainstorming.md
+    - create-deep-research-prompt.md
+    - advanced-elicitation.md
   templates:
-    - game-design-doc-tmpl
-    - level-design-doc-tmpl
-    - game-brief-tmpl
+    - game-design-doc-tmpl.yaml
+    - level-design-doc-tmpl.yaml
+    - game-brief-tmpl.yaml
   checklists:
-    - game-design-checklist
+    - game-design-checklist.md
 ```

expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md

@@ -3,11 +3,20 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - Load development guidelines to ensure consistent coding standards
+  - CRITICAL: Do NOT scan docs/stories/ directory automatically during startup
+  - CRITICAL: Do NOT begin any implementation tasks automatically
+  - Wait for user to specify story or ask for story selection
+  - Only load specific story files when user requests implementation
 agent:
   name: Maya
   id: game-developer
@@ -28,13 +37,6 @@ core_principles:
   - Cross-Platform Optimization - Works seamlessly on desktop and mobile
   - Test-Driven Quality - Comprehensive testing of game logic and systems
   - Numbered Options Protocol - Always use numbered lists for user selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - Load development guidelines to ensure consistent coding standards
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically during startup
-  - CRITICAL: Do NOT begin any implementation tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load specific story files when user requests implementation
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode for technical advice'
@@ -56,11 +58,11 @@ task-execution:
   done: Game feature works + Tests pass + 60 FPS + No lint errors + Follows Phaser 3 best practices
 dependencies:
   tasks:
-    - execute-checklist
+    - execute-checklist.md
   templates:
-    - game-architecture-tmpl
+    - game-architecture-tmpl.yaml
   checklists:
-    - game-story-dod-checklist
+    - game-story-dod-checklist.md
   data:
-    - development-guidelines
+    - development-guidelines.md
 ```

expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md

@@ -3,11 +3,20 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - CRITICAL: Do NOT automatically execute create-game-story tasks during startup
+  - CRITICAL: Do NOT create or modify any files during startup
+  - Offer to help with game story preparation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
+  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
 agent:
   name: Jordan
   id: game-sm
@@ -27,13 +36,6 @@ core_principles:
   - Focus on One Story at a Time - Complete one before starting next
   - Game-Specific Context - Understand Phaser 3, game mechanics, and performance requirements
   - Numbered Options Protocol - Always use numbered lists for selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically execute create-game-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with game story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
-  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for game dev advice'
@@ -42,10 +44,10 @@ commands:
   - '*exit" - Say goodbye as the Game Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-game-story
-    - execute-checklist
+    - create-game-story.md
+    - execute-checklist.md
   templates:
-    - game-story-tmpl
+    - game-story-tmpl.yaml
   checklists:
-    - game-story-dod-checklist
+    - game-story-dod-checklist.md
 ```

expansion-packs/bmad-2d-phaser-game-dev/config.yaml

@@ -1,5 +1,5 @@
 name: bmad-2d-phaser-game-dev
-version: 1.7.0
+version: 1.8.0
 short-title: 2D game development with Phaser 3 & TypeScript
 description: >-
   2D Game Development expansion pack for BMad Method - Phaser 3 & TypeScript

expansion-packs/bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md

@@ -1,560 +0,0 @@
-# {{Game Title}} Game Architecture Document
-
-[[LLM: This template creates a comprehensive game architecture document specifically for Phaser 3 + TypeScript projects. This should provide the technical foundation for all game development stories and epics.
-
-If available, review any provided documents: Game Design Document (GDD), Technical Preferences. This architecture should support all game mechanics defined in the GDD.]]
-
-## Introduction
-
-[[LLM: Establish the document's purpose and scope for game development]]
-
-This document outlines the complete technical architecture for {{Game Title}}, a 2D game built with Phaser 3 and TypeScript. It serves as the technical foundation for AI-driven game development, ensuring consistency and scalability across all game systems.
-
-This architecture is designed to support the gameplay mechanics defined in the Game Design Document while maintaining 60 FPS performance and cross-platform compatibility.
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Technical Overview
-
-[[LLM: Present all subsections together, then apply `tasks#advanced-elicitation` protocol to the complete section.]]
-
-### Architecture Summary
-
-[[LLM: Provide a comprehensive overview covering:
-
-- Game engine choice and configuration
-- Project structure and organization
-- Key systems and their interactions
-- Performance and optimization strategy
-- How this architecture achieves GDD requirements]]
-
-### Platform Targets
-
-[[LLM: Based on GDD requirements, confirm platform support]]
-
-**Primary Platform:** {{primary_platform}}
-**Secondary Platforms:** {{secondary_platforms}}
-**Minimum Requirements:** {{min_specs}}
-**Target Performance:** 60 FPS on {{target_device}}
-
-### Technology Stack
-
-**Core Engine:** Phaser 3.70+
-**Language:** TypeScript 5.0+ (Strict Mode)
-**Build Tool:** {{build_tool}} (Webpack/Vite/Parcel)
-**Package Manager:** {{package_manager}}
-**Testing:** {{test_framework}}
-**Deployment:** {{deployment_platform}}
-
-## Project Structure
-
-[[LLM: Define the complete project organization that developers will follow]]
-
-### Repository Organization
-
-[[LLM: Design a clear folder structure for game development]]
-
-```text
-{{game_name}}/
-├── src/
-│   ├── scenes/          # Game scenes
-│   ├── gameObjects/     # Custom game objects
-│   ├── systems/         # Core game systems
-│   ├── utils/           # Utility functions
-│   ├── types/           # TypeScript type definitions
-│   ├── config/          # Game configuration
-│   └── main.ts          # Entry point
-├── assets/
-│   ├── images/          # Sprite assets
-│   ├── audio/           # Sound files
-│   ├── data/            # JSON data files
-│   └── fonts/           # Font files
-├── public/              # Static web assets
-├── tests/               # Test files
-├── docs/                # Documentation
-│   ├── stories/         # Development stories
-│   └── architecture/    # Technical docs
-└── dist/                # Built game files
-```
-
-### Module Organization
-
-[[LLM: Define how TypeScript modules should be organized]]
-
-**Scene Structure:**
-
-- Each scene in separate file
-- Scene-specific logic contained
-- Clear data passing between scenes
-
-**Game Object Pattern:**
-
-- Component-based architecture
-- Reusable game object classes
-- Type-safe property definitions
-
-**System Architecture:**
-
-- Singleton managers for global systems
-- Event-driven communication
-- Clear separation of concerns
-
-## Core Game Systems
-
-[[LLM: Detail each major system that needs to be implemented. Each system should be specific enough for developers to create implementation stories.]]
-
-### Scene Management System
-
-**Purpose:** Handle game flow and scene transitions
-
-**Key Components:**
-
-- Scene loading and unloading
-- Data passing between scenes
-- Transition effects
-- Memory management
-
-**Implementation Requirements:**
-
-- Preload scene for asset loading
-- Menu system with navigation
-- Gameplay scenes with state management
-- Pause/resume functionality
-
-**Files to Create:**
-
-- `src/scenes/BootScene.ts`
-- `src/scenes/PreloadScene.ts`
-- `src/scenes/MenuScene.ts`
-- `src/scenes/GameScene.ts`
-- `src/systems/SceneManager.ts`
-
-### Game State Management
-
-**Purpose:** Track player progress and game status
-
-**State Categories:**
-
-- Player progress (levels, unlocks)
-- Game settings (audio, controls)
-- Session data (current level, score)
-- Persistent data (achievements, statistics)
-
-**Implementation Requirements:**
-
-- Save/load system with localStorage
-- State validation and error recovery
-- Cross-session data persistence
-- Settings management
-
-**Files to Create:**
-
-- `src/systems/GameState.ts`
-- `src/systems/SaveManager.ts`
-- `src/types/GameData.ts`
-
-### Asset Management System
-
-**Purpose:** Efficient loading and management of game assets
-
-**Asset Categories:**
-
-- Sprite sheets and animations
-- Audio files and music
-- Level data and configurations
-- UI assets and fonts
-
-**Implementation Requirements:**
-
-- Progressive loading strategy
-- Asset caching and optimization
-- Error handling for failed loads
-- Memory management for large assets
-
-**Files to Create:**
-
-- `src/systems/AssetManager.ts`
-- `src/config/AssetConfig.ts`
-- `src/utils/AssetLoader.ts`
-
-### Input Management System
-
-**Purpose:** Handle all player input across platforms
-
-**Input Types:**
-
-- Keyboard controls
-- Mouse/pointer interaction
-- Touch gestures (mobile)
-- Gamepad support (optional)
-
-**Implementation Requirements:**
-
-- Input mapping and configuration
-- Touch-friendly mobile controls
-- Input buffering for responsive gameplay
-- Customizable control schemes
-
-**Files to Create:**
-
-- `src/systems/InputManager.ts`
-- `src/utils/TouchControls.ts`
-- `src/types/InputTypes.ts`
-
-### Game Mechanics Systems
-
-[[LLM: For each major mechanic defined in the GDD, create a system specification]]
-
-<<REPEAT section="mechanic_system" count="based_on_gdd">>
-
-#### {{mechanic_name}} System
-
-**Purpose:** {{system_purpose}}
-
-**Core Functionality:**
-
-- {{feature_1}}
-- {{feature_2}}
-- {{feature_3}}
-
-**Dependencies:** {{required_systems}}
-
-**Performance Considerations:** {{optimization_notes}}
-
-**Files to Create:**
-
-- `src/systems/{{SystemName}}.ts`
-- `src/gameObjects/{{RelatedObject}}.ts`
-- `src/types/{{SystemTypes}}.ts`
-
-<</REPEAT>>
-
-### Physics & Collision System
-
-**Physics Engine:** {{physics_choice}} (Arcade Physics/Matter.js)
-
-**Collision Categories:**
-
-- Player collision
-- Enemy interactions
-- Environmental objects
-- Collectibles and items
-
-**Implementation Requirements:**
-
-- Optimized collision detection
-- Physics body management
-- Collision callbacks and events
-- Performance monitoring
-
-**Files to Create:**
-
-- `src/systems/PhysicsManager.ts`
-- `src/utils/CollisionGroups.ts`
-
-### Audio System
-
-**Audio Requirements:**
-
-- Background music with looping
-- Sound effects for actions
-- Audio settings and volume control
-- Mobile audio optimization
-
-**Implementation Features:**
-
-- Audio sprite management
-- Dynamic music system
-- Spatial audio (if applicable)
-- Audio pooling for performance
-
-**Files to Create:**
-
-- `src/systems/AudioManager.ts`
-- `src/config/AudioConfig.ts`
-
-### UI System
-
-**UI Components:**
-
-- HUD elements (score, health, etc.)
-- Menu navigation
-- Modal dialogs
-- Settings screens
-
-**Implementation Requirements:**
-
-- Responsive layout system
-- Touch-friendly interface
-- Keyboard navigation support
-- Animation and transitions
-
-**Files to Create:**
-
-- `src/systems/UIManager.ts`
-- `src/gameObjects/UI/`
-- `src/types/UITypes.ts`
-
-## Performance Architecture
-
-[[LLM: Define performance requirements and optimization strategies]]
-
-### Performance Targets
-
-**Frame Rate:** 60 FPS sustained, 30 FPS minimum
-**Memory Usage:** <{{memory_limit}}MB total
-**Load Times:** <{{initial_load}}s initial, <{{level_load}}s per level
-**Battery Optimization:** Reduced updates when not visible
-
-### Optimization Strategies
-
-**Object Pooling:**
-
-- Bullets and projectiles
-- Particle effects
-- Enemy objects
-- UI elements
-
-**Asset Optimization:**
-
-- Texture atlases for sprites
-- Audio compression
-- Lazy loading for large assets
-- Progressive enhancement
-
-**Rendering Optimization:**
-
-- Sprite batching
-- Culling off-screen objects
-- Reduced particle counts on mobile
-- Texture resolution scaling
-
-**Files to Create:**
-
-- `src/utils/ObjectPool.ts`
-- `src/utils/PerformanceMonitor.ts`
-- `src/config/OptimizationConfig.ts`
-
-## Game Configuration
-
-[[LLM: Define all configurable aspects of the game]]
-
-### Phaser Configuration
-
-```typescript
-// src/config/GameConfig.ts
-const gameConfig: Phaser.Types.Core.GameConfig = {
-    type: Phaser.AUTO,
-    width: {{game_width}},
-    height: {{game_height}},
-    scale: {
-        mode: {{scale_mode}},
-        autoCenter: Phaser.Scale.CENTER_BOTH
-    },
-    physics: {
-        default: '{{physics_system}}',
-        {{physics_system}}: {
-            gravity: { y: {{gravity}} },
-            debug: false
-        }
-    },
-    // Additional configuration...
-};
-```
-
-### Game Balance Configuration
-
-[[LLM: Based on GDD, define configurable game parameters]]
-
-```typescript
-// src/config/GameBalance.ts
-export const GameBalance = {
-    player: {
-        speed: {{player_speed}},
-        health: {{player_health}},
-        // Additional player parameters...
-    },
-    difficulty: {
-        easy: {{easy_params}},
-        normal: {{normal_params}},
-        hard: {{hard_params}}
-    },
-    // Additional balance parameters...
-};
-```
-
-## Development Guidelines
-
-[[LLM: Provide coding standards specific to game development]]
-
-### TypeScript Standards
-
-**Type Safety:**
-
-- Use strict mode
-- Define interfaces for all data structures
-- Avoid `any` type usage
-- Use enums for game states
-
-**Code Organization:**
-
-- One class per file
-- Clear naming conventions
-- Proper error handling
-- Comprehensive documentation
-
-### Phaser 3 Best Practices
-
-**Scene Management:**
-
-- Clean up resources in shutdown()
-- Use scene data for communication
-- Implement proper event handling
-- Avoid memory leaks
-
-**Game Object Design:**
-
-- Extend Phaser classes appropriately
-- Use component-based architecture
-- Implement object pooling where needed
-- Follow consistent update patterns
-
-### Testing Strategy
-
-**Unit Testing:**
-
-- Test game logic separately from Phaser
-- Mock Phaser dependencies
-- Test utility functions
-- Validate game balance calculations
-
-**Integration Testing:**
-
-- Scene loading and transitions
-- Save/load functionality
-- Input handling
-- Performance benchmarks
-
-**Files to Create:**
-
-- `tests/utils/GameLogic.test.ts`
-- `tests/systems/SaveManager.test.ts`
-- `tests/performance/FrameRate.test.ts`
-
-## Deployment Architecture
-
-[[LLM: Define how the game will be built and deployed]]
-
-### Build Process
-
-**Development Build:**
-
-- Fast compilation
-- Source maps enabled
-- Debug logging active
-- Hot reload support
-
-**Production Build:**
-
-- Minified and optimized
-- Asset compression
-- Performance monitoring
-- Error tracking
-
-### Deployment Strategy
-
-**Web Deployment:**
-
-- Static hosting ({{hosting_platform}})
-- CDN for assets
-- Progressive loading
-- Browser compatibility
-
-**Mobile Packaging:**
-
-- Cordova/Capacitor wrapper
-- Platform-specific optimization
-- App store requirements
-- Performance testing
-
-## Implementation Roadmap
-
-[[LLM: Break down the architecture implementation into phases that align with the GDD development phases]]
-
-### Phase 1: Foundation ({{duration}})
-
-**Core Systems:**
-
-- Project setup and configuration
-- Basic scene management
-- Asset loading pipeline
-- Input handling framework
-
-**Story Epics:**
-
-- "Engine Setup and Configuration"
-- "Basic Scene Management System"
-- "Asset Loading Foundation"
-
-### Phase 2: Game Systems ({{duration}})
-
-**Gameplay Systems:**
-
-- {{primary_mechanic}} implementation
-- Physics and collision system
-- Game state management
-- UI framework
-
-**Story Epics:**
-
-- "{{Primary_Mechanic}} System Implementation"
-- "Physics and Collision Framework"
-- "Game State Management System"
-
-### Phase 3: Content & Polish ({{duration}})
-
-**Content Systems:**
-
-- Level loading and management
-- Audio system integration
-- Performance optimization
-- Final polish and testing
-
-**Story Epics:**
-
-- "Level Management System"
-- "Audio Integration and Optimization"
-- "Performance Optimization and Testing"
-
-## Risk Assessment
-
-[[LLM: Identify potential technical risks and mitigation strategies]]
-
-| Risk                         | Probability | Impact     | Mitigation Strategy |
-| ---------------------------- | ----------- | ---------- | ------------------- |
-| Performance issues on mobile | {{prob}}    | {{impact}} | {{mitigation}}      |
-| Asset loading bottlenecks    | {{prob}}    | {{impact}} | {{mitigation}}      |
-| Cross-platform compatibility | {{prob}}    | {{impact}} | {{mitigation}}      |
-
-## Success Criteria
-
-[[LLM: Define measurable technical success criteria]]
-
-**Technical Metrics:**
-
-- All systems implemented per specification
-- Performance targets met consistently
-- Zero critical bugs in core systems
-- Successful deployment across target platforms
-
-**Code Quality:**
-
-- 90%+ test coverage on game logic
-- Zero TypeScript errors in strict mode
-- Consistent adherence to coding standards
-- Comprehensive documentation coverage

expansion-packs/bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml

@@ -0,0 +1,613 @@
+template:
+  id: game-architecture-template-v2
+  name: Game Architecture Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: "docs/{{game_name}}-game-architecture.md"
+    title: "{{game_title}} Game Architecture Document"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates a comprehensive game architecture document specifically for Phaser 3 + TypeScript projects. This should provide the technical foundation for all game development stories and epics.
+      
+      If available, review any provided documents: Game Design Document (GDD), Technical Preferences. This architecture should support all game mechanics defined in the GDD.
+
+  - id: introduction
+    title: Introduction
+    instruction: Establish the document's purpose and scope for game development
+    content: |
+      This document outlines the complete technical architecture for {{game_title}}, a 2D game built with Phaser 3 and TypeScript. It serves as the technical foundation for AI-driven game development, ensuring consistency and scalability across all game systems.
+      
+      This architecture is designed to support the gameplay mechanics defined in the Game Design Document while maintaining 60 FPS performance and cross-platform compatibility.
+    sections:
+      - id: change-log
+        title: Change Log
+        instruction: Track document versions and changes
+        type: table
+        template: |
+          | Date | Version | Description | Author |
+          | :--- | :------ | :---------- | :----- |
+
+  - id: technical-overview
+    title: Technical Overview
+    instruction: Present all subsections together, then apply `tasks#advanced-elicitation` protocol to the complete section.
+    sections:
+      - id: architecture-summary
+        title: Architecture Summary
+        instruction: |
+          Provide a comprehensive overview covering:
+          
+          - Game engine choice and configuration
+          - Project structure and organization
+          - Key systems and their interactions
+          - Performance and optimization strategy
+          - How this architecture achieves GDD requirements
+      - id: platform-targets
+        title: Platform Targets
+        instruction: Based on GDD requirements, confirm platform support
+        template: |
+          **Primary Platform:** {{primary_platform}}
+          **Secondary Platforms:** {{secondary_platforms}}
+          **Minimum Requirements:** {{min_specs}}
+          **Target Performance:** 60 FPS on {{target_device}}
+      - id: technology-stack
+        title: Technology Stack
+        template: |
+          **Core Engine:** Phaser 3.70+
+          **Language:** TypeScript 5.0+ (Strict Mode)
+          **Build Tool:** {{build_tool}} (Webpack/Vite/Parcel)
+          **Package Manager:** {{package_manager}}
+          **Testing:** {{test_framework}}
+          **Deployment:** {{deployment_platform}}
+
+  - id: project-structure
+    title: Project Structure
+    instruction: Define the complete project organization that developers will follow
+    sections:
+      - id: repository-organization
+        title: Repository Organization
+        instruction: Design a clear folder structure for game development
+        type: code
+        language: text
+        template: |
+          {{game_name}}/
+          ├── src/
+          │   ├── scenes/          # Game scenes
+          │   ├── gameObjects/     # Custom game objects
+          │   ├── systems/         # Core game systems
+          │   ├── utils/           # Utility functions
+          │   ├── types/           # TypeScript type definitions
+          │   ├── config/          # Game configuration
+          │   └── main.ts          # Entry point
+          ├── assets/
+          │   ├── images/          # Sprite assets
+          │   ├── audio/           # Sound files
+          │   ├── data/            # JSON data files
+          │   └── fonts/           # Font files
+          ├── public/              # Static web assets
+          ├── tests/               # Test files
+          ├── docs/                # Documentation
+          │   ├── stories/         # Development stories
+          │   └── architecture/    # Technical docs
+          └── dist/                # Built game files
+      - id: module-organization
+        title: Module Organization
+        instruction: Define how TypeScript modules should be organized
+        sections:
+          - id: scene-structure
+            title: Scene Structure
+            type: bullet-list
+            template: |
+              - Each scene in separate file
+              - Scene-specific logic contained
+              - Clear data passing between scenes
+          - id: game-object-pattern
+            title: Game Object Pattern
+            type: bullet-list
+            template: |
+              - Component-based architecture
+              - Reusable game object classes
+              - Type-safe property definitions
+          - id: system-architecture
+            title: System Architecture
+            type: bullet-list
+            template: |
+              - Singleton managers for global systems
+              - Event-driven communication
+              - Clear separation of concerns
+
+  - id: core-game-systems
+    title: Core Game Systems
+    instruction: Detail each major system that needs to be implemented. Each system should be specific enough for developers to create implementation stories.
+    sections:
+      - id: scene-management
+        title: Scene Management System
+        template: |
+          **Purpose:** Handle game flow and scene transitions
+          
+          **Key Components:**
+          
+          - Scene loading and unloading
+          - Data passing between scenes
+          - Transition effects
+          - Memory management
+          
+          **Implementation Requirements:**
+          
+          - Preload scene for asset loading
+          - Menu system with navigation
+          - Gameplay scenes with state management
+          - Pause/resume functionality
+          
+          **Files to Create:**
+          
+          - `src/scenes/BootScene.ts`
+          - `src/scenes/PreloadScene.ts`
+          - `src/scenes/MenuScene.ts`
+          - `src/scenes/GameScene.ts`
+          - `src/systems/SceneManager.ts`
+      - id: game-state-management
+        title: Game State Management
+        template: |
+          **Purpose:** Track player progress and game status
+          
+          **State Categories:**
+          
+          - Player progress (levels, unlocks)
+          - Game settings (audio, controls)
+          - Session data (current level, score)
+          - Persistent data (achievements, statistics)
+          
+          **Implementation Requirements:**
+          
+          - Save/load system with localStorage
+          - State validation and error recovery
+          - Cross-session data persistence
+          - Settings management
+          
+          **Files to Create:**
+          
+          - `src/systems/GameState.ts`
+          - `src/systems/SaveManager.ts`
+          - `src/types/GameData.ts`
+      - id: asset-management
+        title: Asset Management System
+        template: |
+          **Purpose:** Efficient loading and management of game assets
+          
+          **Asset Categories:**
+          
+          - Sprite sheets and animations
+          - Audio files and music
+          - Level data and configurations
+          - UI assets and fonts
+          
+          **Implementation Requirements:**
+          
+          - Progressive loading strategy
+          - Asset caching and optimization
+          - Error handling for failed loads
+          - Memory management for large assets
+          
+          **Files to Create:**
+          
+          - `src/systems/AssetManager.ts`
+          - `src/config/AssetConfig.ts`
+          - `src/utils/AssetLoader.ts`
+      - id: input-management
+        title: Input Management System
+        template: |
+          **Purpose:** Handle all player input across platforms
+          
+          **Input Types:**
+          
+          - Keyboard controls
+          - Mouse/pointer interaction
+          - Touch gestures (mobile)
+          - Gamepad support (optional)
+          
+          **Implementation Requirements:**
+          
+          - Input mapping and configuration
+          - Touch-friendly mobile controls
+          - Input buffering for responsive gameplay
+          - Customizable control schemes
+          
+          **Files to Create:**
+          
+          - `src/systems/InputManager.ts`
+          - `src/utils/TouchControls.ts`
+          - `src/types/InputTypes.ts`
+      - id: game-mechanics-systems
+        title: Game Mechanics Systems
+        instruction: For each major mechanic defined in the GDD, create a system specification
+        repeatable: true
+        sections:
+          - id: mechanic-system
+            title: "{{mechanic_name}} System"
+            template: |
+              **Purpose:** {{system_purpose}}
+              
+              **Core Functionality:**
+              
+              - {{feature_1}}
+              - {{feature_2}}
+              - {{feature_3}}
+              
+              **Dependencies:** {{required_systems}}
+              
+              **Performance Considerations:** {{optimization_notes}}
+              
+              **Files to Create:**
+              
+              - `src/systems/{{system_name}}.ts`
+              - `src/gameObjects/{{related_object}}.ts`
+              - `src/types/{{system_types}}.ts`
+      - id: physics-collision
+        title: Physics & Collision System
+        template: |
+          **Physics Engine:** {{physics_choice}} (Arcade Physics/Matter.js)
+          
+          **Collision Categories:**
+          
+          - Player collision
+          - Enemy interactions
+          - Environmental objects
+          - Collectibles and items
+          
+          **Implementation Requirements:**
+          
+          - Optimized collision detection
+          - Physics body management
+          - Collision callbacks and events
+          - Performance monitoring
+          
+          **Files to Create:**
+          
+          - `src/systems/PhysicsManager.ts`
+          - `src/utils/CollisionGroups.ts`
+      - id: audio-system
+        title: Audio System
+        template: |
+          **Audio Requirements:**
+          
+          - Background music with looping
+          - Sound effects for actions
+          - Audio settings and volume control
+          - Mobile audio optimization
+          
+          **Implementation Features:**
+          
+          - Audio sprite management
+          - Dynamic music system
+          - Spatial audio (if applicable)
+          - Audio pooling for performance
+          
+          **Files to Create:**
+          
+          - `src/systems/AudioManager.ts`
+          - `src/config/AudioConfig.ts`
+      - id: ui-system
+        title: UI System
+        template: |
+          **UI Components:**
+          
+          - HUD elements (score, health, etc.)
+          - Menu navigation
+          - Modal dialogs
+          - Settings screens
+          
+          **Implementation Requirements:**
+          
+          - Responsive layout system
+          - Touch-friendly interface
+          - Keyboard navigation support
+          - Animation and transitions
+          
+          **Files to Create:**
+          
+          - `src/systems/UIManager.ts`
+          - `src/gameObjects/UI/`
+          - `src/types/UITypes.ts`
+
+  - id: performance-architecture
+    title: Performance Architecture
+    instruction: Define performance requirements and optimization strategies
+    sections:
+      - id: performance-targets
+        title: Performance Targets
+        template: |
+          **Frame Rate:** 60 FPS sustained, 30 FPS minimum
+          **Memory Usage:** <{{memory_limit}}MB total
+          **Load Times:** <{{initial_load}}s initial, <{{level_load}}s per level
+          **Battery Optimization:** Reduced updates when not visible
+      - id: optimization-strategies
+        title: Optimization Strategies
+        sections:
+          - id: object-pooling
+            title: Object Pooling
+            type: bullet-list
+            template: |
+              - Bullets and projectiles
+              - Particle effects
+              - Enemy objects
+              - UI elements
+          - id: asset-optimization
+            title: Asset Optimization
+            type: bullet-list
+            template: |
+              - Texture atlases for sprites
+              - Audio compression
+              - Lazy loading for large assets
+              - Progressive enhancement
+          - id: rendering-optimization
+            title: Rendering Optimization
+            type: bullet-list
+            template: |
+              - Sprite batching
+              - Culling off-screen objects
+              - Reduced particle counts on mobile
+              - Texture resolution scaling
+          - id: optimization-files
+            title: Files to Create
+            type: bullet-list
+            template: |
+              - `src/utils/ObjectPool.ts`
+              - `src/utils/PerformanceMonitor.ts`
+              - `src/config/OptimizationConfig.ts`
+
+  - id: game-configuration
+    title: Game Configuration
+    instruction: Define all configurable aspects of the game
+    sections:
+      - id: phaser-configuration
+        title: Phaser Configuration
+        type: code
+        language: typescript
+        template: |
+          // src/config/GameConfig.ts
+          const gameConfig: Phaser.Types.Core.GameConfig = {
+              type: Phaser.AUTO,
+              width: {{game_width}},
+              height: {{game_height}},
+              scale: {
+                  mode: {{scale_mode}},
+                  autoCenter: Phaser.Scale.CENTER_BOTH
+              },
+              physics: {
+                  default: '{{physics_system}}',
+                  {{physics_system}}: {
+                      gravity: { y: {{gravity}} },
+                      debug: false
+                  }
+              },
+              // Additional configuration...
+          };
+      - id: game-balance-configuration
+        title: Game Balance Configuration
+        instruction: Based on GDD, define configurable game parameters
+        type: code
+        language: typescript
+        template: |
+          // src/config/GameBalance.ts
+          export const GameBalance = {
+              player: {
+                  speed: {{player_speed}},
+                  health: {{player_health}},
+                  // Additional player parameters...
+              },
+              difficulty: {
+                  easy: {{easy_params}},
+                  normal: {{normal_params}},
+                  hard: {{hard_params}}
+              },
+              // Additional balance parameters...
+          };
+
+  - id: development-guidelines
+    title: Development Guidelines
+    instruction: Provide coding standards specific to game development
+    sections:
+      - id: typescript-standards
+        title: TypeScript Standards
+        sections:
+          - id: type-safety
+            title: Type Safety
+            type: bullet-list
+            template: |
+              - Use strict mode
+              - Define interfaces for all data structures
+              - Avoid `any` type usage
+              - Use enums for game states
+          - id: code-organization
+            title: Code Organization
+            type: bullet-list
+            template: |
+              - One class per file
+              - Clear naming conventions
+              - Proper error handling
+              - Comprehensive documentation
+      - id: phaser-best-practices
+        title: Phaser 3 Best Practices
+        sections:
+          - id: scene-management-practices
+            title: Scene Management
+            type: bullet-list
+            template: |
+              - Clean up resources in shutdown()
+              - Use scene data for communication
+              - Implement proper event handling
+              - Avoid memory leaks
+          - id: game-object-design
+            title: Game Object Design
+            type: bullet-list
+            template: |
+              - Extend Phaser classes appropriately
+              - Use component-based architecture
+              - Implement object pooling where needed
+              - Follow consistent update patterns
+      - id: testing-strategy
+        title: Testing Strategy
+        sections:
+          - id: unit-testing
+            title: Unit Testing
+            type: bullet-list
+            template: |
+              - Test game logic separately from Phaser
+              - Mock Phaser dependencies
+              - Test utility functions
+              - Validate game balance calculations
+          - id: integration-testing
+            title: Integration Testing
+            type: bullet-list
+            template: |
+              - Scene loading and transitions
+              - Save/load functionality
+              - Input handling
+              - Performance benchmarks
+          - id: test-files
+            title: Files to Create
+            type: bullet-list
+            template: |
+              - `tests/utils/GameLogic.test.ts`
+              - `tests/systems/SaveManager.test.ts`
+              - `tests/performance/FrameRate.test.ts`
+
+  - id: deployment-architecture
+    title: Deployment Architecture
+    instruction: Define how the game will be built and deployed
+    sections:
+      - id: build-process
+        title: Build Process
+        sections:
+          - id: development-build
+            title: Development Build
+            type: bullet-list
+            template: |
+              - Fast compilation
+              - Source maps enabled
+              - Debug logging active
+              - Hot reload support
+          - id: production-build
+            title: Production Build
+            type: bullet-list
+            template: |
+              - Minified and optimized
+              - Asset compression
+              - Performance monitoring
+              - Error tracking
+      - id: deployment-strategy
+        title: Deployment Strategy
+        sections:
+          - id: web-deployment
+            title: Web Deployment
+            type: bullet-list
+            template: |
+              - Static hosting ({{hosting_platform}})
+              - CDN for assets
+              - Progressive loading
+              - Browser compatibility
+          - id: mobile-packaging
+            title: Mobile Packaging
+            type: bullet-list
+            template: |
+              - Cordova/Capacitor wrapper
+              - Platform-specific optimization
+              - App store requirements
+              - Performance testing
+
+  - id: implementation-roadmap
+    title: Implementation Roadmap
+    instruction: Break down the architecture implementation into phases that align with the GDD development phases
+    sections:
+      - id: phase-1-foundation
+        title: "Phase 1: Foundation ({{duration}})"
+        sections:
+          - id: phase-1-core
+            title: Core Systems
+            type: bullet-list
+            template: |
+              - Project setup and configuration
+              - Basic scene management
+              - Asset loading pipeline
+              - Input handling framework
+          - id: phase-1-epics
+            title: Story Epics
+            type: bullet-list
+            template: |
+              - "Engine Setup and Configuration"
+              - "Basic Scene Management System"
+              - "Asset Loading Foundation"
+      - id: phase-2-game-systems
+        title: "Phase 2: Game Systems ({{duration}})"
+        sections:
+          - id: phase-2-gameplay
+            title: Gameplay Systems
+            type: bullet-list
+            template: |
+              - {{primary_mechanic}} implementation
+              - Physics and collision system
+              - Game state management
+              - UI framework
+          - id: phase-2-epics
+            title: Story Epics
+            type: bullet-list
+            template: |
+              - "{{primary_mechanic}} System Implementation"
+              - "Physics and Collision Framework"
+              - "Game State Management System"
+      - id: phase-3-content-polish
+        title: "Phase 3: Content & Polish ({{duration}})"
+        sections:
+          - id: phase-3-content
+            title: Content Systems
+            type: bullet-list
+            template: |
+              - Level loading and management
+              - Audio system integration
+              - Performance optimization
+              - Final polish and testing
+          - id: phase-3-epics
+            title: Story Epics
+            type: bullet-list
+            template: |
+              - "Level Management System"
+              - "Audio Integration and Optimization"
+              - "Performance Optimization and Testing"
+
+  - id: risk-assessment
+    title: Risk Assessment
+    instruction: Identify potential technical risks and mitigation strategies
+    type: table
+    template: |
+      | Risk                         | Probability | Impact     | Mitigation Strategy |
+      | ---------------------------- | ----------- | ---------- | ------------------- |
+      | Performance issues on mobile | {{prob}}    | {{impact}} | {{mitigation}}      |
+      | Asset loading bottlenecks    | {{prob}}    | {{impact}} | {{mitigation}}      |
+      | Cross-platform compatibility | {{prob}}    | {{impact}} | {{mitigation}}      |
+
+  - id: success-criteria
+    title: Success Criteria
+    instruction: Define measurable technical success criteria
+    sections:
+      - id: technical-metrics
+        title: Technical Metrics
+        type: bullet-list
+        template: |
+          - All systems implemented per specification
+          - Performance targets met consistently
+          - Zero critical bugs in core systems
+          - Successful deployment across target platforms
+      - id: code-quality
+        title: Code Quality
+        type: bullet-list
+        template: |
+          - 90%+ test coverage on game logic
+          - Zero TypeScript errors in strict mode
+          - Consistent adherence to coding standards
+          - Comprehensive documentation coverage

expansion-packs/bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md

@@ -1,345 +0,0 @@
-# {{Game Title}} Game Brief
-
-[[LLM: This template creates a comprehensive game brief that serves as the foundation for all subsequent game development work. The brief should capture the essential vision, scope, and requirements needed to create a detailed Game Design Document.
-
-This brief is typically created early in the ideation process, often after brainstorming sessions, to crystallize the game concept before moving into detailed design.]]
-
-## Game Vision
-
-[[LLM: Establish the core vision and identity of the game. Present each subsection and gather user feedback before proceeding.]]
-
-### Core Concept
-
-[[LLM: 2-3 sentences that clearly capture what the game is and why it will be compelling to players]]
-
-### Elevator Pitch
-
-[[LLM: Single sentence that captures the essence of the game in a memorable way]]
-
-**"{{game_description_in_one_sentence}}"**
-
-### Vision Statement
-
-[[LLM: Inspirational statement about what the game will achieve for players and why it matters]]
-
-## Target Market
-
-[[LLM: Define the audience and market context. Apply `tasks#advanced-elicitation` after presenting this section.]]
-
-### Primary Audience
-
-**Demographics:** {{age_range}}, {{platform_preference}}, {{gaming_experience}}
-**Psychographics:** {{interests}}, {{motivations}}, {{play_patterns}}
-**Gaming Preferences:** {{preferred_genres}}, {{session_length}}, {{difficulty_preference}}
-
-### Secondary Audiences
-
-**Audience 2:** {{description}}
-**Audience 3:** {{description}}
-
-### Market Context
-
-**Genre:** {{primary_genre}} / {{secondary_genre}}
-**Platform Strategy:** {{platform_focus}}
-**Competitive Positioning:** {{differentiation_statement}}
-
-## Game Fundamentals
-
-[[LLM: Define the core gameplay elements. Each subsection should be specific enough to guide detailed design work.]]
-
-### Core Gameplay Pillars
-
-[[LLM: 3-5 fundamental principles that guide all design decisions]]
-
-1. **{{pillar_1}}** - {{description_and_rationale}}
-2. **{{pillar_2}}** - {{description_and_rationale}}
-3. **{{pillar_3}}** - {{description_and_rationale}}
-
-### Primary Mechanics
-
-[[LLM: List the 3-5 most important gameplay mechanics that define the player experience]]
-
-**Core Mechanic 1: {{mechanic_name}}**
-
-- **Description:** {{how_it_works}}
-- **Player Value:** {{why_its_fun}}
-- **Implementation Scope:** {{complexity_estimate}}
-
-**Core Mechanic 2: {{mechanic_name}}**
-
-- **Description:** {{how_it_works}}
-- **Player Value:** {{why_its_fun}}
-- **Implementation Scope:** {{complexity_estimate}}
-
-### Player Experience Goals
-
-[[LLM: Define what emotions and experiences the game should create for players]]
-
-**Primary Experience:** {{main_emotional_goal}}
-**Secondary Experiences:** {{supporting_emotional_goals}}
-**Engagement Pattern:** {{how_player_engagement_evolves}}
-
-## Scope and Constraints
-
-[[LLM: Define the boundaries and limitations that will shape development. Apply `tasks#advanced-elicitation` to clarify any constraints.]]
-
-### Project Scope
-
-**Game Length:** {{estimated_content_hours}}
-**Content Volume:** {{levels_areas_content_amount}}
-**Feature Complexity:** {{simple|moderate|complex}}
-**Scope Comparison:** "Similar to {{reference_game}} but with {{key_differences}}"
-
-### Technical Constraints
-
-**Platform Requirements:**
-
-- Primary: {{platform_1}} - {{requirements}}
-- Secondary: {{platform_2}} - {{requirements}}
-
-**Technical Specifications:**
-
-- Engine: Phaser 3 + TypeScript
-- Performance Target: {{fps_target}} FPS on {{target_device}}
-- Memory Budget: <{{memory_limit}}MB
-- Load Time Goal: <{{load_time_seconds}}s
-
-### Resource Constraints
-
-**Team Size:** {{team_composition}}
-**Timeline:** {{development_duration}}
-**Budget Considerations:** {{budget_constraints_or_targets}}
-**Asset Requirements:** {{art_audio_content_needs}}
-
-### Business Constraints
-
-^^CONDITION: has_business_goals^^
-
-**Monetization Model:** {{free|premium|freemium|subscription}}
-**Revenue Goals:** {{revenue_targets_if_applicable}}
-**Platform Requirements:** {{store_certification_needs}}
-**Launch Timeline:** {{target_launch_window}}
-
-^^/CONDITION: has_business_goals^^
-
-## Reference Framework
-
-[[LLM: Provide context through references and competitive analysis]]
-
-### Inspiration Games
-
-**Primary References:**
-
-1. **{{reference_game_1}}** - {{what_we_learn_from_it}}
-2. **{{reference_game_2}}** - {{what_we_learn_from_it}}
-3. **{{reference_game_3}}** - {{what_we_learn_from_it}}
-
-### Competitive Analysis
-
-**Direct Competitors:**
-
-- {{competitor_1}}: {{strengths_and_weaknesses}}
-- {{competitor_2}}: {{strengths_and_weaknesses}}
-
-**Differentiation Strategy:**
-{{how_we_differ_and_why_thats_valuable}}
-
-### Market Opportunity
-
-**Market Gap:** {{underserved_need_or_opportunity}}
-**Timing Factors:** {{why_now_is_the_right_time}}
-**Success Metrics:** {{how_well_measure_success}}
-
-## Content Framework
-
-[[LLM: Outline the content structure and progression without full design detail]]
-
-### Game Structure
-
-**Overall Flow:** {{linear|hub_world|open_world|procedural}}
-**Progression Model:** {{how_players_advance}}
-**Session Structure:** {{typical_play_session_flow}}
-
-### Content Categories
-
-**Core Content:**
-
-- {{content_type_1}}: {{quantity_and_description}}
-- {{content_type_2}}: {{quantity_and_description}}
-
-**Optional Content:**
-
-- {{optional_content_type}}: {{quantity_and_description}}
-
-**Replay Elements:**
-
-- {{replayability_features}}
-
-### Difficulty and Accessibility
-
-**Difficulty Approach:** {{how_challenge_is_structured}}
-**Accessibility Features:** {{planned_accessibility_support}}
-**Skill Requirements:** {{what_skills_players_need}}
-
-## Art and Audio Direction
-
-[[LLM: Establish the aesthetic vision that will guide asset creation]]
-
-### Visual Style
-
-**Art Direction:** {{style_description}}
-**Reference Materials:** {{visual_inspiration_sources}}
-**Technical Approach:** {{2d_style_pixel_vector_etc}}
-**Color Strategy:** {{color_palette_mood}}
-
-### Audio Direction
-
-**Music Style:** {{genre_and_mood}}
-**Sound Design:** {{audio_personality}}
-**Implementation Needs:** {{technical_audio_requirements}}
-
-### UI/UX Approach
-
-**Interface Style:** {{ui_aesthetic}}
-**User Experience Goals:** {{ux_priorities}}
-**Platform Adaptations:** {{cross_platform_considerations}}
-
-## Risk Assessment
-
-[[LLM: Identify potential challenges and mitigation strategies]]
-
-### Technical Risks
-
-| Risk                 | Probability | Impact | Mitigation Strategy |
-| -------------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{technical_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-| {{technical_risk_2}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-
-### Design Risks
-
-| Risk              | Probability | Impact | Mitigation Strategy |
-| ----------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{design_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-| {{design_risk_2}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-
-### Market Risks
-
-| Risk              | Probability | Impact | Mitigation Strategy |
-| ----------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{market_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-
-## Success Criteria
-
-[[LLM: Define measurable goals for the project]]
-
-### Player Experience Metrics
-
-**Engagement Goals:**
-
-- Tutorial completion rate: >{{percentage}}%
-- Average session length: {{duration}} minutes
-- Player retention: D1 {{d1}}%, D7 {{d7}}%, D30 {{d30}}%
-
-**Quality Benchmarks:**
-
-- Player satisfaction: >{{rating}}/10
-- Completion rate: >{{percentage}}%
-- Technical performance: {{fps_target}} FPS consistent
-
-### Development Metrics
-
-**Technical Targets:**
-
-- Zero critical bugs at launch
-- Performance targets met on all platforms
-- Load times under {{seconds}}s
-
-**Process Goals:**
-
-- Development timeline adherence
-- Feature scope completion
-- Quality assurance standards
-
-^^CONDITION: has_business_goals^^
-
-### Business Metrics
-
-**Commercial Goals:**
-
-- {{revenue_target}} in first {{time_period}}
-- {{user_acquisition_target}} players in first {{time_period}}
-- {{retention_target}} monthly active users
-
-^^/CONDITION: has_business_goals^^
-
-## Next Steps
-
-[[LLM: Define immediate actions following the brief completion]]
-
-### Immediate Actions
-
-1. **Stakeholder Review** - {{review_process_and_timeline}}
-2. **Concept Validation** - {{validation_approach}}
-3. **Resource Planning** - {{team_and_resource_allocation}}
-
-### Development Roadmap
-
-**Phase 1: Pre-Production** ({{duration}})
-
-- Detailed Game Design Document creation
-- Technical architecture planning
-- Art style exploration and pipeline setup
-
-**Phase 2: Prototype** ({{duration}})
-
-- Core mechanic implementation
-- Technical proof of concept
-- Initial playtesting and iteration
-
-**Phase 3: Production** ({{duration}})
-
-- Full feature development
-- Content creation and integration
-- Comprehensive testing and optimization
-
-### Documentation Pipeline
-
-**Required Documents:**
-
-1. Game Design Document (GDD) - {{target_completion}}
-2. Technical Architecture Document - {{target_completion}}
-3. Art Style Guide - {{target_completion}}
-4. Production Plan - {{target_completion}}
-
-### Validation Plan
-
-**Concept Testing:**
-
-- {{validation_method_1}} - {{timeline}}
-- {{validation_method_2}} - {{timeline}}
-
-**Prototype Testing:**
-
-- {{testing_approach}} - {{timeline}}
-- {{feedback_collection_method}} - {{timeline}}
-
-## Appendices
-
-### Research Materials
-
-[[LLM: Include any supporting research, competitive analysis, or market data that informed the brief]]
-
-### Brainstorming Session Notes
-
-[[LLM: Reference any brainstorming sessions that led to this brief]]
-
-### Stakeholder Input
-
-[[LLM: Include key input from stakeholders that shaped the vision]]
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |

expansion-packs/bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml

@@ -0,0 +1,356 @@
+template:
+  id: game-brief-template-v2
+  name: Game Brief
+  version: 2.0
+  output:
+    format: markdown
+    filename: "docs/{{game_name}}-game-brief.md"
+    title: "{{game_title}} Game Brief"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates a comprehensive game brief that serves as the foundation for all subsequent game development work. The brief should capture the essential vision, scope, and requirements needed to create a detailed Game Design Document.
+      
+      This brief is typically created early in the ideation process, often after brainstorming sessions, to crystallize the game concept before moving into detailed design.
+
+  - id: game-vision
+    title: Game Vision
+    instruction: Establish the core vision and identity of the game. Present each subsection and gather user feedback before proceeding.
+    sections:
+      - id: core-concept
+        title: Core Concept
+        instruction: 2-3 sentences that clearly capture what the game is and why it will be compelling to players
+      - id: elevator-pitch
+        title: Elevator Pitch
+        instruction: Single sentence that captures the essence of the game in a memorable way
+        template: |
+          **"{{game_description_in_one_sentence}}"**
+      - id: vision-statement
+        title: Vision Statement
+        instruction: Inspirational statement about what the game will achieve for players and why it matters
+
+  - id: target-market
+    title: Target Market
+    instruction: Define the audience and market context. Apply `tasks#advanced-elicitation` after presenting this section.
+    sections:
+      - id: primary-audience
+        title: Primary Audience
+        template: |
+          **Demographics:** {{age_range}}, {{platform_preference}}, {{gaming_experience}}
+          **Psychographics:** {{interests}}, {{motivations}}, {{play_patterns}}
+          **Gaming Preferences:** {{preferred_genres}}, {{session_length}}, {{difficulty_preference}}
+      - id: secondary-audiences
+        title: Secondary Audiences
+        template: |
+          **Audience 2:** {{description}}
+          **Audience 3:** {{description}}
+      - id: market-context
+        title: Market Context
+        template: |
+          **Genre:** {{primary_genre}} / {{secondary_genre}}
+          **Platform Strategy:** {{platform_focus}}
+          **Competitive Positioning:** {{differentiation_statement}}
+
+  - id: game-fundamentals
+    title: Game Fundamentals
+    instruction: Define the core gameplay elements. Each subsection should be specific enough to guide detailed design work.
+    sections:
+      - id: core-gameplay-pillars
+        title: Core Gameplay Pillars
+        instruction: 3-5 fundamental principles that guide all design decisions
+        type: numbered-list
+        template: |
+          **{{pillar_name}}** - {{description_and_rationale}}
+      - id: primary-mechanics
+        title: Primary Mechanics
+        instruction: List the 3-5 most important gameplay mechanics that define the player experience
+        repeatable: true
+        template: |
+          **Core Mechanic: {{mechanic_name}}**
+          
+          - **Description:** {{how_it_works}}
+          - **Player Value:** {{why_its_fun}}
+          - **Implementation Scope:** {{complexity_estimate}}
+      - id: player-experience-goals
+        title: Player Experience Goals
+        instruction: Define what emotions and experiences the game should create for players
+        template: |
+          **Primary Experience:** {{main_emotional_goal}}
+          **Secondary Experiences:** {{supporting_emotional_goals}}
+          **Engagement Pattern:** {{how_player_engagement_evolves}}
+
+  - id: scope-constraints
+    title: Scope and Constraints
+    instruction: Define the boundaries and limitations that will shape development. Apply `tasks#advanced-elicitation` to clarify any constraints.
+    sections:
+      - id: project-scope
+        title: Project Scope
+        template: |
+          **Game Length:** {{estimated_content_hours}}
+          **Content Volume:** {{levels_areas_content_amount}}
+          **Feature Complexity:** {{simple|moderate|complex}}
+          **Scope Comparison:** "Similar to {{reference_game}} but with {{key_differences}}"
+      - id: technical-constraints
+        title: Technical Constraints
+        template: |
+          **Platform Requirements:**
+          
+          - Primary: {{platform_1}} - {{requirements}}
+          - Secondary: {{platform_2}} - {{requirements}}
+          
+          **Technical Specifications:**
+          
+          - Engine: Phaser 3 + TypeScript
+          - Performance Target: {{fps_target}} FPS on {{target_device}}
+          - Memory Budget: <{{memory_limit}}MB
+          - Load Time Goal: <{{load_time_seconds}}s
+      - id: resource-constraints
+        title: Resource Constraints
+        template: |
+          **Team Size:** {{team_composition}}
+          **Timeline:** {{development_duration}}
+          **Budget Considerations:** {{budget_constraints_or_targets}}
+          **Asset Requirements:** {{art_audio_content_needs}}
+      - id: business-constraints
+        title: Business Constraints
+        condition: has_business_goals
+        template: |
+          **Monetization Model:** {{free|premium|freemium|subscription}}
+          **Revenue Goals:** {{revenue_targets_if_applicable}}
+          **Platform Requirements:** {{store_certification_needs}}
+          **Launch Timeline:** {{target_launch_window}}
+
+  - id: reference-framework
+    title: Reference Framework
+    instruction: Provide context through references and competitive analysis
+    sections:
+      - id: inspiration-games
+        title: Inspiration Games
+        sections:
+          - id: primary-references
+            title: Primary References
+            type: numbered-list
+            repeatable: true
+            template: |
+              **{{reference_game}}** - {{what_we_learn_from_it}}
+      - id: competitive-analysis
+        title: Competitive Analysis
+        template: |
+          **Direct Competitors:**
+          
+          - {{competitor_1}}: {{strengths_and_weaknesses}}
+          - {{competitor_2}}: {{strengths_and_weaknesses}}
+          
+          **Differentiation Strategy:**
+          {{how_we_differ_and_why_thats_valuable}}
+      - id: market-opportunity
+        title: Market Opportunity
+        template: |
+          **Market Gap:** {{underserved_need_or_opportunity}}
+          **Timing Factors:** {{why_now_is_the_right_time}}
+          **Success Metrics:** {{how_well_measure_success}}
+
+  - id: content-framework
+    title: Content Framework
+    instruction: Outline the content structure and progression without full design detail
+    sections:
+      - id: game-structure
+        title: Game Structure
+        template: |
+          **Overall Flow:** {{linear|hub_world|open_world|procedural}}
+          **Progression Model:** {{how_players_advance}}
+          **Session Structure:** {{typical_play_session_flow}}
+      - id: content-categories
+        title: Content Categories
+        template: |
+          **Core Content:**
+          
+          - {{content_type_1}}: {{quantity_and_description}}
+          - {{content_type_2}}: {{quantity_and_description}}
+          
+          **Optional Content:**
+          
+          - {{optional_content_type}}: {{quantity_and_description}}
+          
+          **Replay Elements:**
+          
+          - {{replayability_features}}
+      - id: difficulty-accessibility
+        title: Difficulty and Accessibility
+        template: |
+          **Difficulty Approach:** {{how_challenge_is_structured}}
+          **Accessibility Features:** {{planned_accessibility_support}}
+          **Skill Requirements:** {{what_skills_players_need}}
+
+  - id: art-audio-direction
+    title: Art and Audio Direction
+    instruction: Establish the aesthetic vision that will guide asset creation
+    sections:
+      - id: visual-style
+        title: Visual Style
+        template: |
+          **Art Direction:** {{style_description}}
+          **Reference Materials:** {{visual_inspiration_sources}}
+          **Technical Approach:** {{2d_style_pixel_vector_etc}}
+          **Color Strategy:** {{color_palette_mood}}
+      - id: audio-direction
+        title: Audio Direction
+        template: |
+          **Music Style:** {{genre_and_mood}}
+          **Sound Design:** {{audio_personality}}
+          **Implementation Needs:** {{technical_audio_requirements}}
+      - id: ui-ux-approach
+        title: UI/UX Approach
+        template: |
+          **Interface Style:** {{ui_aesthetic}}
+          **User Experience Goals:** {{ux_priorities}}
+          **Platform Adaptations:** {{cross_platform_considerations}}
+
+  - id: risk-assessment
+    title: Risk Assessment
+    instruction: Identify potential challenges and mitigation strategies
+    sections:
+      - id: technical-risks
+        title: Technical Risks
+        type: table
+        template: |
+          | Risk | Probability | Impact | Mitigation Strategy |
+          | ---- | ----------- | ------ | ------------------- |
+          | {{technical_risk}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+      - id: design-risks
+        title: Design Risks
+        type: table
+        template: |
+          | Risk | Probability | Impact | Mitigation Strategy |
+          | ---- | ----------- | ------ | ------------------- |
+          | {{design_risk}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+      - id: market-risks
+        title: Market Risks
+        type: table
+        template: |
+          | Risk | Probability | Impact | Mitigation Strategy |
+          | ---- | ----------- | ------ | ------------------- |
+          | {{market_risk}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+
+  - id: success-criteria
+    title: Success Criteria
+    instruction: Define measurable goals for the project
+    sections:
+      - id: player-experience-metrics
+        title: Player Experience Metrics
+        template: |
+          **Engagement Goals:**
+          
+          - Tutorial completion rate: >{{percentage}}%
+          - Average session length: {{duration}} minutes
+          - Player retention: D1 {{d1}}%, D7 {{d7}}%, D30 {{d30}}%
+          
+          **Quality Benchmarks:**
+          
+          - Player satisfaction: >{{rating}}/10
+          - Completion rate: >{{percentage}}%
+          - Technical performance: {{fps_target}} FPS consistent
+      - id: development-metrics
+        title: Development Metrics
+        template: |
+          **Technical Targets:**
+          
+          - Zero critical bugs at launch
+          - Performance targets met on all platforms
+          - Load times under {{seconds}}s
+          
+          **Process Goals:**
+          
+          - Development timeline adherence
+          - Feature scope completion
+          - Quality assurance standards
+      - id: business-metrics
+        title: Business Metrics
+        condition: has_business_goals
+        template: |
+          **Commercial Goals:**
+          
+          - {{revenue_target}} in first {{time_period}}
+          - {{user_acquisition_target}} players in first {{time_period}}
+          - {{retention_target}} monthly active users
+
+  - id: next-steps
+    title: Next Steps
+    instruction: Define immediate actions following the brief completion
+    sections:
+      - id: immediate-actions
+        title: Immediate Actions
+        type: numbered-list
+        template: |
+          **{{action_item}}** - {{details_and_timeline}}
+      - id: development-roadmap
+        title: Development Roadmap
+        sections:
+          - id: phase-1-preproduction
+            title: "Phase 1: Pre-Production ({{duration}})"
+            type: bullet-list
+            template: |
+              - Detailed Game Design Document creation
+              - Technical architecture planning
+              - Art style exploration and pipeline setup
+          - id: phase-2-prototype
+            title: "Phase 2: Prototype ({{duration}})"
+            type: bullet-list
+            template: |
+              - Core mechanic implementation
+              - Technical proof of concept
+              - Initial playtesting and iteration
+          - id: phase-3-production
+            title: "Phase 3: Production ({{duration}})"
+            type: bullet-list
+            template: |
+              - Full feature development
+              - Content creation and integration
+              - Comprehensive testing and optimization
+      - id: documentation-pipeline
+        title: Documentation Pipeline
+        sections:
+          - id: required-documents
+            title: Required Documents
+            type: numbered-list
+            template: |
+              Game Design Document (GDD) - {{target_completion}}
+              Technical Architecture Document - {{target_completion}}
+              Art Style Guide - {{target_completion}}
+              Production Plan - {{target_completion}}
+      - id: validation-plan
+        title: Validation Plan
+        template: |
+          **Concept Testing:**
+          
+          - {{validation_method_1}} - {{timeline}}
+          - {{validation_method_2}} - {{timeline}}
+          
+          **Prototype Testing:**
+          
+          - {{testing_approach}} - {{timeline}}
+          - {{feedback_collection_method}} - {{timeline}}
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: research-materials
+        title: Research Materials
+        instruction: Include any supporting research, competitive analysis, or market data that informed the brief
+      - id: brainstorming-notes
+        title: Brainstorming Session Notes
+        instruction: Reference any brainstorming sessions that led to this brief
+      - id: stakeholder-input
+        title: Stakeholder Input
+        instruction: Include key input from stakeholders that shaped the vision
+      - id: change-log
+        title: Change Log
+        instruction: Track document versions and changes
+        type: table
+        template: |
+          | Date | Version | Description | Author |
+          | :--- | :------ | :---------- | :----- |

expansion-packs/bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md

@@ -1,331 +0,0 @@
-# {{Game Title}} Game Design Document (GDD)
-
-[[LLM: This template creates a comprehensive Game Design Document that will serve as the foundation for all game development work. The GDD should be detailed enough that developers can create user stories and epics from it. Focus on gameplay systems, mechanics, and technical requirements that can be broken down into implementable features.
-
-If available, review any provided documents or ask if any are optionally available: Project Brief, Market Research, Competitive Analysis]]
-
-## Executive Summary
-
-[[LLM: Create a compelling overview that captures the essence of the game. Present this section first and get user feedback before proceeding.]]
-
-### Core Concept
-
-[[LLM: 2-3 sentences that clearly describe what the game is and why players will love it]]
-
-### Target Audience
-
-[[LLM: Define the primary and secondary audience with demographics and gaming preferences]]
-
-**Primary:** {{age_range}}, {{player_type}}, {{platform_preference}}
-**Secondary:** {{secondary_audience}}
-
-### Platform & Technical Requirements
-
-[[LLM: Based on the technical preferences or user input, define the target platforms]]
-
-**Primary Platform:** {{platform}}
-**Engine:** Phaser 3 + TypeScript
-**Performance Target:** 60 FPS on {{minimum_device}}
-**Screen Support:** {{resolution_range}}
-
-### Unique Selling Points
-
-[[LLM: List 3-5 key features that differentiate this game from competitors]]
-
-1. {{usp_1}}
-2. {{usp_2}}
-3. {{usp_3}}
-
-## Core Gameplay
-
-[[LLM: This section defines the fundamental game mechanics. After presenting each subsection, apply `tasks#advanced-elicitation` protocol to ensure completeness.]]
-
-### Game Pillars
-
-[[LLM: Define 3-5 core pillars that guide all design decisions. These should be specific and actionable.]]
-
-1. **{{pillar_1}}** - {{description}}
-2. **{{pillar_2}}** - {{description}}
-3. **{{pillar_3}}** - {{description}}
-
-### Core Gameplay Loop
-
-[[LLM: Define the 30-60 second loop that players will repeat. Be specific about timing and player actions.]]
-
-**Primary Loop ({{duration}} seconds):**
-
-1. {{action_1}} ({{time_1}}s)
-2. {{action_2}} ({{time_2}}s)
-3. {{action_3}} ({{time_3}}s)
-4. {{reward_feedback}} ({{time_4}}s)
-
-### Win/Loss Conditions
-
-[[LLM: Clearly define success and failure states]]
-
-**Victory Conditions:**
-
-- {{win_condition_1}}
-- {{win_condition_2}}
-
-**Failure States:**
-
-- {{loss_condition_1}}
-- {{loss_condition_2}}
-
-## Game Mechanics
-
-[[LLM: Detail each major mechanic that will need to be implemented. Each mechanic should be specific enough for developers to create implementation stories.]]
-
-### Primary Mechanics
-
-<<REPEAT section="mechanic" count="3-5">>
-
-#### {{mechanic_name}}
-
-**Description:** {{detailed_description}}
-
-**Player Input:** {{input_method}}
-
-**System Response:** {{game_response}}
-
-**Implementation Notes:**
-
-- {{tech_requirement_1}}
-- {{tech_requirement_2}}
-- {{performance_consideration}}
-
-**Dependencies:** {{other_mechanics_needed}}
-
-<</REPEAT>>
-
-### Controls
-
-[[LLM: Define all input methods for different platforms]]
-
-| Action       | Desktop | Mobile      | Gamepad    |
-| ------------ | ------- | ----------- | ---------- |
-| {{action_1}} | {{key}} | {{gesture}} | {{button}} |
-| {{action_2}} | {{key}} | {{gesture}} | {{button}} |
-
-## Progression & Balance
-
-[[LLM: Define how players advance and how difficulty scales. This section should provide clear parameters for implementation.]]
-
-### Player Progression
-
-**Progression Type:** {{linear|branching|metroidvania}}
-
-**Key Milestones:**
-
-1. **{{milestone_1}}** - {{unlock_description}}
-2. **{{milestone_2}}** - {{unlock_description}}
-3. **{{milestone_3}}** - {{unlock_description}}
-
-### Difficulty Curve
-
-[[LLM: Provide specific parameters for balancing]]
-
-**Tutorial Phase:** {{duration}} - {{difficulty_description}}
-**Early Game:** {{duration}} - {{difficulty_description}}
-**Mid Game:** {{duration}} - {{difficulty_description}}
-**Late Game:** {{duration}} - {{difficulty_description}}
-
-### Economy & Resources
-
-^^CONDITION: has_economy^^
-
-[[LLM: Define any in-game currencies, resources, or collectibles]]
-
-| Resource       | Earn Rate | Spend Rate | Purpose | Cap     |
-| -------------- | --------- | ---------- | ------- | ------- |
-| {{resource_1}} | {{rate}}  | {{rate}}   | {{use}} | {{max}} |
-
-^^/CONDITION: has_economy^^
-
-## Level Design Framework
-
-[[LLM: Provide guidelines for level creation that developers can use to create level implementation stories]]
-
-### Level Types
-
-<<REPEAT section="level_type" count="2-4">>
-
-#### {{level_type_name}}
-
-**Purpose:** {{gameplay_purpose}}
-**Duration:** {{target_time}}
-**Key Elements:** {{required_mechanics}}
-**Difficulty:** {{relative_difficulty}}
-
-**Structure Template:**
-
-- Introduction: {{intro_description}}
-- Challenge: {{main_challenge}}
-- Resolution: {{completion_requirement}}
-
-<</REPEAT>>
-
-### Level Progression
-
-**World Structure:** {{linear|hub|open}}
-**Total Levels:** {{number}}
-**Unlock Pattern:** {{progression_method}}
-
-## Technical Specifications
-
-[[LLM: Define technical requirements that will guide architecture and implementation decisions. Review any existing technical preferences.]]
-
-### Performance Requirements
-
-**Frame Rate:** 60 FPS (minimum 30 FPS on low-end devices)
-**Memory Usage:** <{{memory_limit}}MB
-**Load Times:** <{{load_time}}s initial, <{{level_load}}s between levels
-**Battery Usage:** Optimized for mobile devices
-
-### Platform Specific
-
-**Desktop:**
-
-- Resolution: {{min_resolution}} - {{max_resolution}}
-- Input: Keyboard, Mouse, Gamepad
-- Browser: Chrome 80+, Firefox 75+, Safari 13+
-
-**Mobile:**
-
-- Resolution: {{mobile_min}} - {{mobile_max}}
-- Input: Touch, Tilt (optional)
-- OS: iOS 13+, Android 8+
-
-### Asset Requirements
-
-[[LLM: Define asset specifications for the art and audio teams]]
-
-**Visual Assets:**
-
-- Art Style: {{style_description}}
-- Color Palette: {{color_specification}}
-- Animation: {{animation_requirements}}
-- UI Resolution: {{ui_specs}}
-
-**Audio Assets:**
-
-- Music Style: {{music_genre}}
-- Sound Effects: {{sfx_requirements}}
-- Voice Acting: {{voice_needs}}
-
-## Technical Architecture Requirements
-
-[[LLM: Define high-level technical requirements that the game architecture must support]]
-
-### Engine Configuration
-
-**Phaser 3 Setup:**
-
-- TypeScript: Strict mode enabled
-- Physics: {{physics_system}} (Arcade/Matter)
-- Renderer: WebGL with Canvas fallback
-- Scale Mode: {{scale_mode}}
-
-### Code Architecture
-
-**Required Systems:**
-
-- Scene Management
-- State Management
-- Asset Loading
-- Save/Load System
-- Input Management
-- Audio System
-- Performance Monitoring
-
-### Data Management
-
-**Save Data:**
-
-- Progress tracking
-- Settings persistence
-- Statistics collection
-- {{additional_data}}
-
-## Development Phases
-
-[[LLM: Break down the development into phases that can be converted to epics]]
-
-### Phase 1: Core Systems ({{duration}})
-
-**Epic: Foundation**
-
-- Engine setup and configuration
-- Basic scene management
-- Core input handling
-- Asset loading pipeline
-
-**Epic: Core Mechanics**
-
-- {{primary_mechanic}} implementation
-- Basic physics and collision
-- Player controller
-
-### Phase 2: Gameplay Features ({{duration}})
-
-**Epic: Game Systems**
-
-- {{mechanic_2}} implementation
-- {{mechanic_3}} implementation
-- Game state management
-
-**Epic: Content Creation**
-
-- Level loading system
-- First playable levels
-- Basic UI implementation
-
-### Phase 3: Polish & Optimization ({{duration}})
-
-**Epic: Performance**
-
-- Optimization and profiling
-- Mobile platform testing
-- Memory management
-
-**Epic: User Experience**
-
-- Audio implementation
-- Visual effects and polish
-- Final UI/UX refinement
-
-## Success Metrics
-
-[[LLM: Define measurable goals for the game]]
-
-**Technical Metrics:**
-
-- Frame rate: {{fps_target}}
-- Load time: {{load_target}}
-- Crash rate: <{{crash_threshold}}%
-- Memory usage: <{{memory_target}}MB
-
-**Gameplay Metrics:**
-
-- Tutorial completion: {{completion_rate}}%
-- Average session: {{session_length}} minutes
-- Level completion: {{level_completion}}%
-- Player retention: D1 {{d1}}%, D7 {{d7}}%
-
-## Appendices
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-### References
-
-[[LLM: List any competitive analysis, inspiration, or research sources]]
-
-- {{reference_1}}
-- {{reference_2}}
-- {{reference_3}}

expansion-packs/bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml

@@ -0,0 +1,343 @@
+template:
+  id: game-design-doc-template-v2
+  name: Game Design Document (GDD)
+  version: 2.0
+  output:
+    format: markdown
+    filename: "docs/{{game_name}}-game-design-document.md"
+    title: "{{game_title}} Game Design Document (GDD)"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates a comprehensive Game Design Document that will serve as the foundation for all game development work. The GDD should be detailed enough that developers can create user stories and epics from it. Focus on gameplay systems, mechanics, and technical requirements that can be broken down into implementable features.
+      
+      If available, review any provided documents or ask if any are optionally available: Project Brief, Market Research, Competitive Analysis
+
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Create a compelling overview that captures the essence of the game. Present this section first and get user feedback before proceeding.
+    sections:
+      - id: core-concept
+        title: Core Concept
+        instruction: 2-3 sentences that clearly describe what the game is and why players will love it
+      - id: target-audience
+        title: Target Audience
+        instruction: Define the primary and secondary audience with demographics and gaming preferences
+        template: |
+          **Primary:** {{age_range}}, {{player_type}}, {{platform_preference}}
+          **Secondary:** {{secondary_audience}}
+      - id: platform-technical
+        title: Platform & Technical Requirements
+        instruction: Based on the technical preferences or user input, define the target platforms
+        template: |
+          **Primary Platform:** {{platform}}
+          **Engine:** Phaser 3 + TypeScript
+          **Performance Target:** 60 FPS on {{minimum_device}}
+          **Screen Support:** {{resolution_range}}
+      - id: unique-selling-points
+        title: Unique Selling Points
+        instruction: List 3-5 key features that differentiate this game from competitors
+        type: numbered-list
+        template: "{{usp}}"
+
+  - id: core-gameplay
+    title: Core Gameplay
+    instruction: This section defines the fundamental game mechanics. After presenting each subsection, apply `tasks#advanced-elicitation` protocol to ensure completeness.
+    sections:
+      - id: game-pillars
+        title: Game Pillars
+        instruction: Define 3-5 core pillars that guide all design decisions. These should be specific and actionable.
+        type: numbered-list
+        template: |
+          **{{pillar_name}}** - {{description}}
+      - id: core-gameplay-loop
+        title: Core Gameplay Loop
+        instruction: Define the 30-60 second loop that players will repeat. Be specific about timing and player actions.
+        template: |
+          **Primary Loop ({{duration}} seconds):**
+          
+          1. {{action_1}} ({{time_1}}s)
+          2. {{action_2}} ({{time_2}}s)
+          3. {{action_3}} ({{time_3}}s)
+          4. {{reward_feedback}} ({{time_4}}s)
+      - id: win-loss-conditions
+        title: Win/Loss Conditions
+        instruction: Clearly define success and failure states
+        template: |
+          **Victory Conditions:**
+          
+          - {{win_condition_1}}
+          - {{win_condition_2}}
+          
+          **Failure States:**
+          
+          - {{loss_condition_1}}
+          - {{loss_condition_2}}
+
+  - id: game-mechanics
+    title: Game Mechanics
+    instruction: Detail each major mechanic that will need to be implemented. Each mechanic should be specific enough for developers to create implementation stories.
+    sections:
+      - id: primary-mechanics
+        title: Primary Mechanics
+        repeatable: true
+        sections:
+          - id: mechanic
+            title: "{{mechanic_name}}"
+            template: |
+              **Description:** {{detailed_description}}
+              
+              **Player Input:** {{input_method}}
+              
+              **System Response:** {{game_response}}
+              
+              **Implementation Notes:**
+              
+              - {{tech_requirement_1}}
+              - {{tech_requirement_2}}
+              - {{performance_consideration}}
+              
+              **Dependencies:** {{other_mechanics_needed}}
+      - id: controls
+        title: Controls
+        instruction: Define all input methods for different platforms
+        type: table
+        template: |
+          | Action | Desktop | Mobile | Gamepad |
+          | ------ | ------- | ------ | ------- |
+          | {{action}} | {{key}} | {{gesture}} | {{button}} |
+
+  - id: progression-balance
+    title: Progression & Balance
+    instruction: Define how players advance and how difficulty scales. This section should provide clear parameters for implementation.
+    sections:
+      - id: player-progression
+        title: Player Progression
+        template: |
+          **Progression Type:** {{linear|branching|metroidvania}}
+          
+          **Key Milestones:**
+          
+          1. **{{milestone_1}}** - {{unlock_description}}
+          2. **{{milestone_2}}** - {{unlock_description}}
+          3. **{{milestone_3}}** - {{unlock_description}}
+      - id: difficulty-curve
+        title: Difficulty Curve
+        instruction: Provide specific parameters for balancing
+        template: |
+          **Tutorial Phase:** {{duration}} - {{difficulty_description}}
+          **Early Game:** {{duration}} - {{difficulty_description}}
+          **Mid Game:** {{duration}} - {{difficulty_description}}
+          **Late Game:** {{duration}} - {{difficulty_description}}
+      - id: economy-resources
+        title: Economy & Resources
+        condition: has_economy
+        instruction: Define any in-game currencies, resources, or collectibles
+        type: table
+        template: |
+          | Resource | Earn Rate | Spend Rate | Purpose | Cap |
+          | -------- | --------- | ---------- | ------- | --- |
+          | {{resource}} | {{rate}} | {{rate}} | {{use}} | {{max}} |
+
+  - id: level-design-framework
+    title: Level Design Framework
+    instruction: Provide guidelines for level creation that developers can use to create level implementation stories
+    sections:
+      - id: level-types
+        title: Level Types
+        repeatable: true
+        sections:
+          - id: level-type
+            title: "{{level_type_name}}"
+            template: |
+              **Purpose:** {{gameplay_purpose}}
+              **Duration:** {{target_time}}
+              **Key Elements:** {{required_mechanics}}
+              **Difficulty:** {{relative_difficulty}}
+              
+              **Structure Template:**
+              
+              - Introduction: {{intro_description}}
+              - Challenge: {{main_challenge}}
+              - Resolution: {{completion_requirement}}
+      - id: level-progression
+        title: Level Progression
+        template: |
+          **World Structure:** {{linear|hub|open}}
+          **Total Levels:** {{number}}
+          **Unlock Pattern:** {{progression_method}}
+
+  - id: technical-specifications
+    title: Technical Specifications
+    instruction: Define technical requirements that will guide architecture and implementation decisions. Review any existing technical preferences.
+    sections:
+      - id: performance-requirements
+        title: Performance Requirements
+        template: |
+          **Frame Rate:** 60 FPS (minimum 30 FPS on low-end devices)
+          **Memory Usage:** <{{memory_limit}}MB
+          **Load Times:** <{{load_time}}s initial, <{{level_load}}s between levels
+          **Battery Usage:** Optimized for mobile devices
+      - id: platform-specific
+        title: Platform Specific
+        template: |
+          **Desktop:**
+          
+          - Resolution: {{min_resolution}} - {{max_resolution}}
+          - Input: Keyboard, Mouse, Gamepad
+          - Browser: Chrome 80+, Firefox 75+, Safari 13+
+          
+          **Mobile:**
+          
+          - Resolution: {{mobile_min}} - {{mobile_max}}
+          - Input: Touch, Tilt (optional)
+          - OS: iOS 13+, Android 8+
+      - id: asset-requirements
+        title: Asset Requirements
+        instruction: Define asset specifications for the art and audio teams
+        template: |
+          **Visual Assets:**
+          
+          - Art Style: {{style_description}}
+          - Color Palette: {{color_specification}}
+          - Animation: {{animation_requirements}}
+          - UI Resolution: {{ui_specs}}
+          
+          **Audio Assets:**
+          
+          - Music Style: {{music_genre}}
+          - Sound Effects: {{sfx_requirements}}
+          - Voice Acting: {{voice_needs}}
+
+  - id: technical-architecture-requirements
+    title: Technical Architecture Requirements
+    instruction: Define high-level technical requirements that the game architecture must support
+    sections:
+      - id: engine-configuration
+        title: Engine Configuration
+        template: |
+          **Phaser 3 Setup:**
+          
+          - TypeScript: Strict mode enabled
+          - Physics: {{physics_system}} (Arcade/Matter)
+          - Renderer: WebGL with Canvas fallback
+          - Scale Mode: {{scale_mode}}
+      - id: code-architecture
+        title: Code Architecture
+        template: |
+          **Required Systems:**
+          
+          - Scene Management
+          - State Management
+          - Asset Loading
+          - Save/Load System
+          - Input Management
+          - Audio System
+          - Performance Monitoring
+      - id: data-management
+        title: Data Management
+        template: |
+          **Save Data:**
+          
+          - Progress tracking
+          - Settings persistence
+          - Statistics collection
+          - {{additional_data}}
+
+  - id: development-phases
+    title: Development Phases
+    instruction: Break down the development into phases that can be converted to epics
+    sections:
+      - id: phase-1-core-systems
+        title: "Phase 1: Core Systems ({{duration}})"
+        sections:
+          - id: foundation-epic
+            title: "Epic: Foundation"
+            type: bullet-list
+            template: |
+              - Engine setup and configuration
+              - Basic scene management
+              - Core input handling
+              - Asset loading pipeline
+          - id: core-mechanics-epic
+            title: "Epic: Core Mechanics"
+            type: bullet-list
+            template: |
+              - {{primary_mechanic}} implementation
+              - Basic physics and collision
+              - Player controller
+      - id: phase-2-gameplay-features
+        title: "Phase 2: Gameplay Features ({{duration}})"
+        sections:
+          - id: game-systems-epic
+            title: "Epic: Game Systems"
+            type: bullet-list
+            template: |
+              - {{mechanic_2}} implementation
+              - {{mechanic_3}} implementation
+              - Game state management
+          - id: content-creation-epic
+            title: "Epic: Content Creation"
+            type: bullet-list
+            template: |
+              - Level loading system
+              - First playable levels
+              - Basic UI implementation
+      - id: phase-3-polish-optimization
+        title: "Phase 3: Polish & Optimization ({{duration}})"
+        sections:
+          - id: performance-epic
+            title: "Epic: Performance"
+            type: bullet-list
+            template: |
+              - Optimization and profiling
+              - Mobile platform testing
+              - Memory management
+          - id: user-experience-epic
+            title: "Epic: User Experience"
+            type: bullet-list
+            template: |
+              - Audio implementation
+              - Visual effects and polish
+              - Final UI/UX refinement
+
+  - id: success-metrics
+    title: Success Metrics
+    instruction: Define measurable goals for the game
+    sections:
+      - id: technical-metrics
+        title: Technical Metrics
+        type: bullet-list
+        template: |
+          - Frame rate: {{fps_target}}
+          - Load time: {{load_target}}
+          - Crash rate: <{{crash_threshold}}%
+          - Memory usage: <{{memory_target}}MB
+      - id: gameplay-metrics
+        title: Gameplay Metrics
+        type: bullet-list
+        template: |
+          - Tutorial completion: {{completion_rate}}%
+          - Average session: {{session_length}} minutes
+          - Level completion: {{level_completion}}%
+          - Player retention: D1 {{d1}}%, D7 {{d7}}%
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: change-log
+        title: Change Log
+        instruction: Track document versions and changes
+        type: table
+        template: |
+          | Date | Version | Description | Author |
+          | :--- | :------ | :---------- | :----- |
+      - id: references
+        title: References
+        instruction: List any competitive analysis, inspiration, or research sources
+        type: bullet-list
+        template: "{{reference}}"

expansion-packs/bmad-2d-phaser-game-dev/templates/game-story-tmpl.md

@@ -1,235 +0,0 @@
-# Story: {{Story Title}}
-
-**Epic:** {{Epic Name}}  
-**Story ID:** {{ID}}  
-**Priority:** {{High|Medium|Low}}  
-**Points:** {{Story Points}}  
-**Status:** Draft
-
-[[LLM: This template creates detailed game development stories that are immediately actionable by game developers. Each story should focus on a single, implementable feature that contributes to the overall game functionality.
-
-Before starting, ensure you have access to:
-
-- Game Design Document (GDD)
-- Game Architecture Document
-- Any existing stories in this epic
-
-The story should be specific enough that a developer can implement it without requiring additional design decisions.]]
-
-## Description
-
-[[LLM: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.]]
-
-{{clear_description_of_what_needs_to_be_implemented}}
-
-## Acceptance Criteria
-
-[[LLM: Define specific, testable conditions that must be met for the story to be considered complete. Each criterion should be verifiable and directly related to gameplay functionality.]]
-
-### Functional Requirements
-
-- [ ] {{specific_functional_requirement_1}}
-- [ ] {{specific_functional_requirement_2}}
-- [ ] {{specific_functional_requirement_3}}
-
-### Technical Requirements
-
-- [ ] Code follows TypeScript strict mode standards
-- [ ] Maintains 60 FPS on target devices
-- [ ] No memory leaks or performance degradation
-- [ ] {{specific_technical_requirement}}
-
-### Game Design Requirements
-
-- [ ] {{gameplay_requirement_from_gdd}}
-- [ ] {{balance_requirement_if_applicable}}
-- [ ] {{player_experience_requirement}}
-
-## Technical Specifications
-
-[[LLM: Provide specific technical details that guide implementation. Include class names, file locations, and integration points based on the game architecture.]]
-
-### Files to Create/Modify
-
-**New Files:**
-
-- `{{file_path_1}}` - {{purpose}}
-- `{{file_path_2}}` - {{purpose}}
-
-**Modified Files:**
-
-- `{{existing_file_1}}` - {{changes_needed}}
-- `{{existing_file_2}}` - {{changes_needed}}
-
-### Class/Interface Definitions
-
-[[LLM: Define specific TypeScript interfaces and class structures needed]]
-
-```typescript
-// {{interface_name}}
-interface {{InterfaceName}} {
-    {{property_1}}: {{type}};
-    {{property_2}}: {{type}};
-    {{method_1}}({{params}}): {{return_type}};
-}
-
-// {{class_name}}
-class {{ClassName}} extends {{PhaseClass}} {
-    private {{property}}: {{type}};
-
-    constructor({{params}}) {
-        // Implementation requirements
-    }
-
-    public {{method}}({{params}}): {{return_type}} {
-        // Method requirements
-    }
-}
-```
-
-### Integration Points
-
-[[LLM: Specify how this feature integrates with existing systems]]
-
-**Scene Integration:**
-
-- {{scene_name}}: {{integration_details}}
-
-**System Dependencies:**
-
-- {{system_name}}: {{dependency_description}}
-
-**Event Communication:**
-
-- Emits: `{{event_name}}` when {{condition}}
-- Listens: `{{event_name}}` to {{response}}
-
-## Implementation Tasks
-
-[[LLM: Break down the implementation into specific, ordered tasks. Each task should be completable in 1-4 hours.]]
-
-### Dev Agent Record
-
-**Tasks:**
-
-- [ ] {{task_1_description}}
-- [ ] {{task_2_description}}
-- [ ] {{task_3_description}}
-- [ ] {{task_4_description}}
-- [ ] Write unit tests for {{component}}
-- [ ] Integration testing with {{related_system}}
-- [ ] Performance testing and optimization
-
-**Debug Log:**
-| Task | File | Change | Reverted? |
-|------|------|--------|-----------|
-| | | | |
-
-**Completion Notes:**
-
-<!-- Only note deviations from requirements, keep under 50 words -->
-
-**Change Log:**
-
-<!-- Only requirement changes during implementation -->
-
-## Game Design Context
-
-[[LLM: Reference the specific sections of the GDD that this story implements]]
-
-**GDD Reference:** {{section_name}} ({{page_or_section_number}})
-
-**Game Mechanic:** {{mechanic_name}}
-
-**Player Experience Goal:** {{experience_description}}
-
-**Balance Parameters:**
-
-- {{parameter_1}}: {{value_or_range}}
-- {{parameter_2}}: {{value_or_range}}
-
-## Testing Requirements
-
-[[LLM: Define specific testing criteria for this game feature]]
-
-### Unit Tests
-
-**Test Files:**
-
-- `tests/{{component_name}}.test.ts`
-
-**Test Scenarios:**
-
-- {{test_scenario_1}}
-- {{test_scenario_2}}
-- {{edge_case_test}}
-
-### Game Testing
-
-**Manual Test Cases:**
-
-1. {{test_case_1_description}}
-
-   - Expected: {{expected_behavior}}
-   - Performance: {{performance_expectation}}
-
-2. {{test_case_2_description}}
-   - Expected: {{expected_behavior}}
-   - Edge Case: {{edge_case_handling}}
-
-### Performance Tests
-
-**Metrics to Verify:**
-
-- Frame rate maintains {{fps_target}} FPS
-- Memory usage stays under {{memory_limit}}MB
-- {{feature_specific_performance_metric}}
-
-## Dependencies
-
-[[LLM: List any dependencies that must be completed before this story can be implemented]]
-
-**Story Dependencies:**
-
-- {{story_id}}: {{dependency_description}}
-
-**Technical Dependencies:**
-
-- {{system_or_file}}: {{requirement}}
-
-**Asset Dependencies:**
-
-- {{asset_type}}: {{asset_description}}
-- Location: `{{asset_path}}`
-
-## Definition of Done
-
-[[LLM: Checklist that must be completed before the story is considered finished]]
-
-- [ ] All acceptance criteria met
-- [ ] Code reviewed and approved
-- [ ] Unit tests written and passing
-- [ ] Integration tests passing
-- [ ] Performance targets met
-- [ ] No linting errors
-- [ ] Documentation updated
-- [ ] {{game_specific_dod_item}}
-
-## Notes
-
-[[LLM: Any additional context, design decisions, or implementation notes]]
-
-**Implementation Notes:**
-
-- {{note_1}}
-- {{note_2}}
-
-**Design Decisions:**
-
-- {{decision_1}}: {{rationale}}
-- {{decision_2}}: {{rationale}}
-
-**Future Considerations:**
-
-- {{future_enhancement_1}}
-- {{future_optimization_1}}

expansion-packs/bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml

@@ -0,0 +1,253 @@
+template:
+  id: game-story-template-v2
+  name: Game Development Story
+  version: 2.0
+  output:
+    format: markdown
+    filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md"
+    title: "Story: {{story_title}}"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates detailed game development stories that are immediately actionable by game developers. Each story should focus on a single, implementable feature that contributes to the overall game functionality.
+      
+      Before starting, ensure you have access to:
+      
+      - Game Design Document (GDD)
+      - Game Architecture Document
+      - Any existing stories in this epic
+      
+      The story should be specific enough that a developer can implement it without requiring additional design decisions.
+
+  - id: story-header
+    content: |
+      **Epic:** {{epic_name}}  
+      **Story ID:** {{story_id}}  
+      **Priority:** {{High|Medium|Low}}  
+      **Points:** {{story_points}}  
+      **Status:** Draft
+
+  - id: description
+    title: Description
+    instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.
+    template: "{{clear_description_of_what_needs_to_be_implemented}}"
+
+  - id: acceptance-criteria
+    title: Acceptance Criteria
+    instruction: Define specific, testable conditions that must be met for the story to be considered complete. Each criterion should be verifiable and directly related to gameplay functionality.
+    sections:
+      - id: functional-requirements
+        title: Functional Requirements
+        type: checklist
+        items:
+          - "{{specific_functional_requirement}}"
+      - id: technical-requirements
+        title: Technical Requirements
+        type: checklist
+        items:
+          - "Code follows TypeScript strict mode standards"
+          - "Maintains 60 FPS on target devices"
+          - "No memory leaks or performance degradation"
+          - "{{specific_technical_requirement}}"
+      - id: game-design-requirements
+        title: Game Design Requirements
+        type: checklist
+        items:
+          - "{{gameplay_requirement_from_gdd}}"
+          - "{{balance_requirement_if_applicable}}"
+          - "{{player_experience_requirement}}"
+
+  - id: technical-specifications
+    title: Technical Specifications
+    instruction: Provide specific technical details that guide implementation. Include class names, file locations, and integration points based on the game architecture.
+    sections:
+      - id: files-to-modify
+        title: Files to Create/Modify
+        template: |
+          **New Files:**
+          
+          - `{{file_path_1}}` - {{purpose}}
+          - `{{file_path_2}}` - {{purpose}}
+          
+          **Modified Files:**
+          
+          - `{{existing_file_1}}` - {{changes_needed}}
+          - `{{existing_file_2}}` - {{changes_needed}}
+      - id: class-interface-definitions
+        title: Class/Interface Definitions
+        instruction: Define specific TypeScript interfaces and class structures needed
+        type: code
+        language: typescript
+        template: |
+          // {{interface_name}}
+          interface {{interface_name}} {
+              {{property_1}}: {{type}};
+              {{property_2}}: {{type}};
+              {{method_1}}({{params}}): {{return_type}};
+          }
+          
+          // {{class_name}}
+          class {{class_name}} extends {{phaser_class}} {
+              private {{property}}: {{type}};
+          
+              constructor({{params}}) {
+                  // Implementation requirements
+              }
+          
+              public {{method}}({{params}}): {{return_type}} {
+                  // Method requirements
+              }
+          }
+      - id: integration-points
+        title: Integration Points
+        instruction: Specify how this feature integrates with existing systems
+        template: |
+          **Scene Integration:**
+          
+          - {{scene_name}}: {{integration_details}}
+          
+          **System Dependencies:**
+          
+          - {{system_name}}: {{dependency_description}}
+          
+          **Event Communication:**
+          
+          - Emits: `{{event_name}}` when {{condition}}
+          - Listens: `{{event_name}}` to {{response}}
+
+  - id: implementation-tasks
+    title: Implementation Tasks
+    instruction: Break down the implementation into specific, ordered tasks. Each task should be completable in 1-4 hours.
+    sections:
+      - id: dev-agent-record
+        title: Dev Agent Record
+        template: |
+          **Tasks:**
+          
+          - [ ] {{task_1_description}}
+          - [ ] {{task_2_description}}
+          - [ ] {{task_3_description}}
+          - [ ] {{task_4_description}}
+          - [ ] Write unit tests for {{component}}
+          - [ ] Integration testing with {{related_system}}
+          - [ ] Performance testing and optimization
+          
+          **Debug Log:**
+          | Task | File | Change | Reverted? |
+          |------|------|--------|-----------|
+          | | | | |
+          
+          **Completion Notes:**
+          
+          <!-- Only note deviations from requirements, keep under 50 words -->
+          
+          **Change Log:**
+          
+          <!-- Only requirement changes during implementation -->
+
+  - id: game-design-context
+    title: Game Design Context
+    instruction: Reference the specific sections of the GDD that this story implements
+    template: |
+      **GDD Reference:** {{section_name}} ({{page_or_section_number}})
+      
+      **Game Mechanic:** {{mechanic_name}}
+      
+      **Player Experience Goal:** {{experience_description}}
+      
+      **Balance Parameters:**
+      
+      - {{parameter_1}}: {{value_or_range}}
+      - {{parameter_2}}: {{value_or_range}}
+
+  - id: testing-requirements
+    title: Testing Requirements
+    instruction: Define specific testing criteria for this game feature
+    sections:
+      - id: unit-tests
+        title: Unit Tests
+        template: |
+          **Test Files:**
+          
+          - `tests/{{component_name}}.test.ts`
+          
+          **Test Scenarios:**
+          
+          - {{test_scenario_1}}
+          - {{test_scenario_2}}
+          - {{edge_case_test}}
+      - id: game-testing
+        title: Game Testing
+        template: |
+          **Manual Test Cases:**
+          
+          1. {{test_case_1_description}}
+          
+             - Expected: {{expected_behavior}}
+             - Performance: {{performance_expectation}}
+          
+          2. {{test_case_2_description}}
+             - Expected: {{expected_behavior}}
+             - Edge Case: {{edge_case_handling}}
+      - id: performance-tests
+        title: Performance Tests
+        template: |
+          **Metrics to Verify:**
+          
+          - Frame rate maintains {{fps_target}} FPS
+          - Memory usage stays under {{memory_limit}}MB
+          - {{feature_specific_performance_metric}}
+
+  - id: dependencies
+    title: Dependencies
+    instruction: List any dependencies that must be completed before this story can be implemented
+    template: |
+      **Story Dependencies:**
+      
+      - {{story_id}}: {{dependency_description}}
+      
+      **Technical Dependencies:**
+      
+      - {{system_or_file}}: {{requirement}}
+      
+      **Asset Dependencies:**
+      
+      - {{asset_type}}: {{asset_description}}
+      - Location: `{{asset_path}}`
+
+  - id: definition-of-done
+    title: Definition of Done
+    instruction: Checklist that must be completed before the story is considered finished
+    type: checklist
+    items:
+      - "All acceptance criteria met"
+      - "Code reviewed and approved"
+      - "Unit tests written and passing"
+      - "Integration tests passing"
+      - "Performance targets met"
+      - "No linting errors"
+      - "Documentation updated"
+      - "{{game_specific_dod_item}}"
+
+  - id: notes
+    title: Notes
+    instruction: Any additional context, design decisions, or implementation notes
+    template: |
+      **Implementation Notes:**
+      
+      - {{note_1}}
+      - {{note_2}}
+      
+      **Design Decisions:**
+      
+      - {{decision_1}}: {{rationale}}
+      - {{decision_2}}: {{rationale}}
+      
+      **Future Considerations:**
+      
+      - {{future_enhancement_1}}
+      - {{future_optimization_1}}

expansion-packs/bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md

@@ -1,470 +0,0 @@
-# {{Game Title}} Level Design Document
-
-[[LLM: This template creates comprehensive level design documentation that guides both content creation and technical implementation. This document should provide enough detail for developers to create level loading systems and for designers to create specific levels.
-
-If available, review: Game Design Document (GDD), Game Architecture Document. This document should align with the game mechanics and technical systems defined in those documents.]]
-
-## Introduction
-
-[[LLM: Establish the purpose and scope of level design for this game]]
-
-This document defines the level design framework for {{Game Title}}, providing guidelines for creating engaging, balanced levels that support the core gameplay mechanics defined in the Game Design Document.
-
-This framework ensures consistency across all levels while providing flexibility for creative level design within established technical and design constraints.
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Level Design Philosophy
-
-[[LLM: Establish the overall approach to level design based on the game's core pillars and mechanics. Apply `tasks#advanced-elicitation` after presenting this section.]]
-
-### Design Principles
-
-[[LLM: Define 3-5 core principles that guide all level design decisions]]
-
-1. **{{principle_1}}** - {{description}}
-2. **{{principle_2}}** - {{description}}
-3. **{{principle_3}}** - {{description}}
-
-### Player Experience Goals
-
-[[LLM: Define what players should feel and learn in each level category]]
-
-**Tutorial Levels:** {{experience_description}}
-**Standard Levels:** {{experience_description}}
-**Challenge Levels:** {{experience_description}}
-**Boss Levels:** {{experience_description}}
-
-### Level Flow Framework
-
-[[LLM: Define the standard structure for level progression]]
-
-**Introduction Phase:** {{duration}} - {{purpose}}
-**Development Phase:** {{duration}} - {{purpose}}
-**Climax Phase:** {{duration}} - {{purpose}}
-**Resolution Phase:** {{duration}} - {{purpose}}
-
-## Level Categories
-
-[[LLM: Define different types of levels based on the GDD requirements. Each category should be specific enough for implementation.]]
-
-<<REPEAT section="level_category" count="based_on_gdd">>
-
-### {{category_name}} Levels
-
-**Purpose:** {{gameplay_purpose}}
-
-**Target Duration:** {{min_time}} - {{max_time}} minutes
-
-**Difficulty Range:** {{difficulty_scale}}
-
-**Key Mechanics Featured:**
-
-- {{mechanic_1}} - {{usage_description}}
-- {{mechanic_2}} - {{usage_description}}
-
-**Player Objectives:**
-
-- Primary: {{primary_objective}}
-- Secondary: {{secondary_objective}}
-- Hidden: {{secret_objective}}
-
-**Success Criteria:**
-
-- {{completion_requirement_1}}
-- {{completion_requirement_2}}
-
-**Technical Requirements:**
-
-- Maximum entities: {{entity_limit}}
-- Performance target: {{fps_target}} FPS
-- Memory budget: {{memory_limit}}MB
-- Asset requirements: {{asset_needs}}
-
-<</REPEAT>>
-
-## Level Progression System
-
-[[LLM: Define how players move through levels and how difficulty scales]]
-
-### World Structure
-
-[[LLM: Based on GDD requirements, define the overall level organization]]
-
-**Organization Type:** {{linear|hub_world|open_world}}
-
-**Total Level Count:** {{number}}
-
-**World Breakdown:**
-
-- World 1: {{level_count}} levels - {{theme}} - {{difficulty_range}}
-- World 2: {{level_count}} levels - {{theme}} - {{difficulty_range}}
-- World 3: {{level_count}} levels - {{theme}} - {{difficulty_range}}
-
-### Difficulty Progression
-
-[[LLM: Define how challenge increases across the game]]
-
-**Progression Curve:**
-
-````text
-Difficulty
-    ^     ___/```
-    |    /
-    |   /     ___/```
-    |  /     /
-    | /     /
-    |/     /
-    +-----------> Level Number
-   Tutorial  Early  Mid  Late
-````
-
-**Scaling Parameters:**
-
-- Enemy count: {{start_count}} → {{end_count}}
-- Enemy difficulty: {{start_diff}} → {{end_diff}}
-- Level complexity: {{start_complex}} → {{end_complex}}
-- Time pressure: {{start_time}} → {{end_time}}
-
-### Unlock Requirements
-
-[[LLM: Define how players access new levels]]
-
-**Progression Gates:**
-
-- Linear progression: Complete previous level
-- Star requirements: {{star_count}} stars to unlock
-- Skill gates: Demonstrate {{skill_requirement}}
-- Optional content: {{unlock_condition}}
-
-## Level Design Components
-
-[[LLM: Define the building blocks used to create levels]]
-
-### Environmental Elements
-
-[[LLM: Define all environmental components that can be used in levels]]
-
-**Terrain Types:**
-
-- {{terrain_1}}: {{properties_and_usage}}
-- {{terrain_2}}: {{properties_and_usage}}
-
-**Interactive Objects:**
-
-- {{object_1}}: {{behavior_and_purpose}}
-- {{object_2}}: {{behavior_and_purpose}}
-
-**Hazards and Obstacles:**
-
-- {{hazard_1}}: {{damage_and_behavior}}
-- {{hazard_2}}: {{damage_and_behavior}}
-
-### Collectibles and Rewards
-
-[[LLM: Define all collectible items and their placement rules]]
-
-**Collectible Types:**
-
-- {{collectible_1}}: {{value_and_purpose}}
-- {{collectible_2}}: {{value_and_purpose}}
-
-**Placement Guidelines:**
-
-- Mandatory collectibles: {{placement_rules}}
-- Optional collectibles: {{placement_rules}}
-- Secret collectibles: {{placement_rules}}
-
-**Reward Distribution:**
-
-- Easy to find: {{percentage}}%
-- Moderate challenge: {{percentage}}%
-- High skill required: {{percentage}}%
-
-### Enemy Placement Framework
-
-[[LLM: Define how enemies should be placed and balanced in levels]]
-
-**Enemy Categories:**
-
-- {{enemy_type_1}}: {{behavior_and_usage}}
-- {{enemy_type_2}}: {{behavior_and_usage}}
-
-**Placement Principles:**
-
-- Introduction encounters: {{guideline}}
-- Standard encounters: {{guideline}}
-- Challenge encounters: {{guideline}}
-
-**Difficulty Scaling:**
-
-- Enemy count progression: {{scaling_rule}}
-- Enemy type introduction: {{pacing_rule}}
-- Encounter complexity: {{complexity_rule}}
-
-## Level Creation Guidelines
-
-[[LLM: Provide specific guidelines for creating individual levels]]
-
-### Level Layout Principles
-
-**Spatial Design:**
-
-- Grid size: {{grid_dimensions}}
-- Minimum path width: {{width_units}}
-- Maximum vertical distance: {{height_units}}
-- Safe zones placement: {{safety_guidelines}}
-
-**Navigation Design:**
-
-- Clear path indication: {{visual_cues}}
-- Landmark placement: {{landmark_rules}}
-- Dead end avoidance: {{dead_end_policy}}
-- Multiple path options: {{branching_rules}}
-
-### Pacing and Flow
-
-[[LLM: Define how to control the rhythm and pace of gameplay within levels]]
-
-**Action Sequences:**
-
-- High intensity duration: {{max_duration}}
-- Rest period requirement: {{min_rest_time}}
-- Intensity variation: {{pacing_pattern}}
-
-**Learning Sequences:**
-
-- New mechanic introduction: {{teaching_method}}
-- Practice opportunity: {{practice_duration}}
-- Skill application: {{application_context}}
-
-### Challenge Design
-
-[[LLM: Define how to create appropriate challenges for each level type]]
-
-**Challenge Types:**
-
-- Execution challenges: {{skill_requirements}}
-- Puzzle challenges: {{complexity_guidelines}}
-- Time challenges: {{time_pressure_rules}}
-- Resource challenges: {{resource_management}}
-
-**Difficulty Calibration:**
-
-- Skill check frequency: {{frequency_guidelines}}
-- Failure recovery: {{retry_mechanics}}
-- Hint system integration: {{help_system}}
-
-## Technical Implementation
-
-[[LLM: Define technical requirements for level implementation]]
-
-### Level Data Structure
-
-[[LLM: Define how level data should be structured for implementation]]
-
-**Level File Format:**
-
-- Data format: {{json|yaml|custom}}
-- File naming: `level_{{world}}_{{number}}.{{extension}}`
-- Data organization: {{structure_description}}
-
-**Required Data Fields:**
-
-```json
-{
-  "levelId": "{{unique_identifier}}",
-  "worldId": "{{world_identifier}}",
-  "difficulty": {{difficulty_value}},
-  "targetTime": {{completion_time_seconds}},
-  "objectives": {
-    "primary": "{{primary_objective}}",
-    "secondary": ["{{secondary_objectives}}"],
-    "hidden": ["{{secret_objectives}}"]
-  },
-  "layout": {
-    "width": {{grid_width}},
-    "height": {{grid_height}},
-    "tilemap": "{{tilemap_reference}}"
-  },
-  "entities": [
-    {
-      "type": "{{entity_type}}",
-      "position": {"x": {{x}}, "y": {{y}}},
-      "properties": {{entity_properties}}
-    }
-  ]
-}
-```
-
-### Asset Integration
-
-[[LLM: Define how level assets are organized and loaded]]
-
-**Tilemap Requirements:**
-
-- Tile size: {{tile_dimensions}}px
-- Tileset organization: {{tileset_structure}}
-- Layer organization: {{layer_system}}
-- Collision data: {{collision_format}}
-
-**Audio Integration:**
-
-- Background music: {{music_requirements}}
-- Ambient sounds: {{ambient_system}}
-- Dynamic audio: {{dynamic_audio_rules}}
-
-### Performance Optimization
-
-[[LLM: Define performance requirements for level systems]]
-
-**Entity Limits:**
-
-- Maximum active entities: {{entity_limit}}
-- Maximum particles: {{particle_limit}}
-- Maximum audio sources: {{audio_limit}}
-
-**Memory Management:**
-
-- Texture memory budget: {{texture_memory}}MB
-- Audio memory budget: {{audio_memory}}MB
-- Level loading time: <{{load_time}}s
-
-**Culling and LOD:**
-
-- Off-screen culling: {{culling_distance}}
-- Level-of-detail rules: {{lod_system}}
-- Asset streaming: {{streaming_requirements}}
-
-## Level Testing Framework
-
-[[LLM: Define how levels should be tested and validated]]
-
-### Automated Testing
-
-**Performance Testing:**
-
-- Frame rate validation: Maintain {{fps_target}} FPS
-- Memory usage monitoring: Stay under {{memory_limit}}MB
-- Loading time verification: Complete in <{{load_time}}s
-
-**Gameplay Testing:**
-
-- Completion path validation: All objectives achievable
-- Collectible accessibility: All items reachable
-- Softlock prevention: No unwinnable states
-
-### Manual Testing Protocol
-
-**Playtesting Checklist:**
-
-- [ ] Level completes within target time range
-- [ ] All mechanics function correctly
-- [ ] Difficulty feels appropriate for level category
-- [ ] Player guidance is clear and effective
-- [ ] No exploits or sequence breaks (unless intended)
-
-**Player Experience Testing:**
-
-- [ ] Tutorial levels teach effectively
-- [ ] Challenge feels fair and rewarding
-- [ ] Flow and pacing maintain engagement
-- [ ] Audio and visual feedback support gameplay
-
-### Balance Validation
-
-**Metrics Collection:**
-
-- Completion rate: Target {{completion_percentage}}%
-- Average completion time: {{target_time}} ± {{variance}}
-- Death count per level: <{{max_deaths}}
-- Collectible discovery rate: {{discovery_percentage}}%
-
-**Iteration Guidelines:**
-
-- Adjustment criteria: {{criteria_for_changes}}
-- Testing sample size: {{minimum_testers}}
-- Validation period: {{testing_duration}}
-
-## Content Creation Pipeline
-
-[[LLM: Define the workflow for creating new levels]]
-
-### Design Phase
-
-**Concept Development:**
-
-1. Define level purpose and goals
-2. Create rough layout sketch
-3. Identify key mechanics and challenges
-4. Estimate difficulty and duration
-
-**Documentation Requirements:**
-
-- Level design brief
-- Layout diagrams
-- Mechanic integration notes
-- Asset requirement list
-
-### Implementation Phase
-
-**Technical Implementation:**
-
-1. Create level data file
-2. Build tilemap and layout
-3. Place entities and objects
-4. Configure level logic and triggers
-5. Integrate audio and visual effects
-
-**Quality Assurance:**
-
-1. Automated testing execution
-2. Internal playtesting
-3. Performance validation
-4. Bug fixing and polish
-
-### Integration Phase
-
-**Game Integration:**
-
-1. Level progression integration
-2. Save system compatibility
-3. Analytics integration
-4. Achievement system integration
-
-**Final Validation:**
-
-1. Full game context testing
-2. Performance regression testing
-3. Platform compatibility verification
-4. Final approval and release
-
-## Success Metrics
-
-[[LLM: Define how to measure level design success]]
-
-**Player Engagement:**
-
-- Level completion rate: {{target_rate}}%
-- Replay rate: {{replay_target}}%
-- Time spent per level: {{engagement_time}}
-- Player satisfaction scores: {{satisfaction_target}}/10
-
-**Technical Performance:**
-
-- Frame rate consistency: {{fps_consistency}}%
-- Loading time compliance: {{load_compliance}}%
-- Memory usage efficiency: {{memory_efficiency}}%
-- Crash rate: <{{crash_threshold}}%
-
-**Design Quality:**
-
-- Difficulty curve adherence: {{curve_accuracy}}
-- Mechanic integration effectiveness: {{integration_score}}
-- Player guidance clarity: {{guidance_score}}
-- Content accessibility: {{accessibility_rate}}%

expansion-packs/bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml

@@ -0,0 +1,484 @@
+template:
+  id: level-design-doc-template-v2
+  name: Level Design Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: "docs/{{game_name}}-level-design-document.md"
+    title: "{{game_title}} Level Design Document"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: initial-setup
+    instruction: |
+      This template creates comprehensive level design documentation that guides both content creation and technical implementation. This document should provide enough detail for developers to create level loading systems and for designers to create specific levels.
+      
+      If available, review: Game Design Document (GDD), Game Architecture Document. This document should align with the game mechanics and technical systems defined in those documents.
+
+  - id: introduction
+    title: Introduction
+    instruction: Establish the purpose and scope of level design for this game
+    content: |
+      This document defines the level design framework for {{game_title}}, providing guidelines for creating engaging, balanced levels that support the core gameplay mechanics defined in the Game Design Document.
+      
+      This framework ensures consistency across all levels while providing flexibility for creative level design within established technical and design constraints.
+    sections:
+      - id: change-log
+        title: Change Log
+        instruction: Track document versions and changes
+        type: table
+        template: |
+          | Date | Version | Description | Author |
+          | :--- | :------ | :---------- | :----- |
+
+  - id: level-design-philosophy
+    title: Level Design Philosophy
+    instruction: Establish the overall approach to level design based on the game's core pillars and mechanics. Apply `tasks#advanced-elicitation` after presenting this section.
+    sections:
+      - id: design-principles
+        title: Design Principles
+        instruction: Define 3-5 core principles that guide all level design decisions
+        type: numbered-list
+        template: |
+          **{{principle_name}}** - {{description}}
+      - id: player-experience-goals
+        title: Player Experience Goals
+        instruction: Define what players should feel and learn in each level category
+        template: |
+          **Tutorial Levels:** {{experience_description}}
+          **Standard Levels:** {{experience_description}}
+          **Challenge Levels:** {{experience_description}}
+          **Boss Levels:** {{experience_description}}
+      - id: level-flow-framework
+        title: Level Flow Framework
+        instruction: Define the standard structure for level progression
+        template: |
+          **Introduction Phase:** {{duration}} - {{purpose}}
+          **Development Phase:** {{duration}} - {{purpose}}
+          **Climax Phase:** {{duration}} - {{purpose}}
+          **Resolution Phase:** {{duration}} - {{purpose}}
+
+  - id: level-categories
+    title: Level Categories
+    instruction: Define different types of levels based on the GDD requirements. Each category should be specific enough for implementation.
+    repeatable: true
+    sections:
+      - id: level-category
+        title: "{{category_name}} Levels"
+        template: |
+          **Purpose:** {{gameplay_purpose}}
+          
+          **Target Duration:** {{min_time}} - {{max_time}} minutes
+          
+          **Difficulty Range:** {{difficulty_scale}}
+          
+          **Key Mechanics Featured:**
+          
+          - {{mechanic_1}} - {{usage_description}}
+          - {{mechanic_2}} - {{usage_description}}
+          
+          **Player Objectives:**
+          
+          - Primary: {{primary_objective}}
+          - Secondary: {{secondary_objective}}
+          - Hidden: {{secret_objective}}
+          
+          **Success Criteria:**
+          
+          - {{completion_requirement_1}}
+          - {{completion_requirement_2}}
+          
+          **Technical Requirements:**
+          
+          - Maximum entities: {{entity_limit}}
+          - Performance target: {{fps_target}} FPS
+          - Memory budget: {{memory_limit}}MB
+          - Asset requirements: {{asset_needs}}
+
+  - id: level-progression-system
+    title: Level Progression System
+    instruction: Define how players move through levels and how difficulty scales
+    sections:
+      - id: world-structure
+        title: World Structure
+        instruction: Based on GDD requirements, define the overall level organization
+        template: |
+          **Organization Type:** {{linear|hub_world|open_world}}
+          
+          **Total Level Count:** {{number}}
+          
+          **World Breakdown:**
+          
+          - World 1: {{level_count}} levels - {{theme}} - {{difficulty_range}}
+          - World 2: {{level_count}} levels - {{theme}} - {{difficulty_range}}
+          - World 3: {{level_count}} levels - {{theme}} - {{difficulty_range}}
+      - id: difficulty-progression
+        title: Difficulty Progression
+        instruction: Define how challenge increases across the game
+        sections:
+          - id: progression-curve
+            title: Progression Curve
+            type: code
+            language: text
+            template: |
+              Difficulty
+                  ^     ___/```
+                  |    /
+                  |   /     ___/```
+                  |  /     /
+                  | /     /
+                  |/     /
+                  +-----------> Level Number
+                 Tutorial  Early  Mid  Late
+          - id: scaling-parameters
+            title: Scaling Parameters
+            type: bullet-list
+            template: |
+              - Enemy count: {{start_count}} → {{end_count}}
+              - Enemy difficulty: {{start_diff}} → {{end_diff}}
+              - Level complexity: {{start_complex}} → {{end_complex}}
+              - Time pressure: {{start_time}} → {{end_time}}
+      - id: unlock-requirements
+        title: Unlock Requirements
+        instruction: Define how players access new levels
+        template: |
+          **Progression Gates:**
+          
+          - Linear progression: Complete previous level
+          - Star requirements: {{star_count}} stars to unlock
+          - Skill gates: Demonstrate {{skill_requirement}}
+          - Optional content: {{unlock_condition}}
+
+  - id: level-design-components
+    title: Level Design Components
+    instruction: Define the building blocks used to create levels
+    sections:
+      - id: environmental-elements
+        title: Environmental Elements
+        instruction: Define all environmental components that can be used in levels
+        template: |
+          **Terrain Types:**
+          
+          - {{terrain_1}}: {{properties_and_usage}}
+          - {{terrain_2}}: {{properties_and_usage}}
+          
+          **Interactive Objects:**
+          
+          - {{object_1}}: {{behavior_and_purpose}}
+          - {{object_2}}: {{behavior_and_purpose}}
+          
+          **Hazards and Obstacles:**
+          
+          - {{hazard_1}}: {{damage_and_behavior}}
+          - {{hazard_2}}: {{damage_and_behavior}}
+      - id: collectibles-rewards
+        title: Collectibles and Rewards
+        instruction: Define all collectible items and their placement rules
+        template: |
+          **Collectible Types:**
+          
+          - {{collectible_1}}: {{value_and_purpose}}
+          - {{collectible_2}}: {{value_and_purpose}}
+          
+          **Placement Guidelines:**
+          
+          - Mandatory collectibles: {{placement_rules}}
+          - Optional collectibles: {{placement_rules}}
+          - Secret collectibles: {{placement_rules}}
+          
+          **Reward Distribution:**
+          
+          - Easy to find: {{percentage}}%
+          - Moderate challenge: {{percentage}}%
+          - High skill required: {{percentage}}%
+      - id: enemy-placement-framework
+        title: Enemy Placement Framework
+        instruction: Define how enemies should be placed and balanced in levels
+        template: |
+          **Enemy Categories:**
+          
+          - {{enemy_type_1}}: {{behavior_and_usage}}
+          - {{enemy_type_2}}: {{behavior_and_usage}}
+          
+          **Placement Principles:**
+          
+          - Introduction encounters: {{guideline}}
+          - Standard encounters: {{guideline}}
+          - Challenge encounters: {{guideline}}
+          
+          **Difficulty Scaling:**
+          
+          - Enemy count progression: {{scaling_rule}}
+          - Enemy type introduction: {{pacing_rule}}
+          - Encounter complexity: {{complexity_rule}}
+
+  - id: level-creation-guidelines
+    title: Level Creation Guidelines
+    instruction: Provide specific guidelines for creating individual levels
+    sections:
+      - id: level-layout-principles
+        title: Level Layout Principles
+        template: |
+          **Spatial Design:**
+          
+          - Grid size: {{grid_dimensions}}
+          - Minimum path width: {{width_units}}
+          - Maximum vertical distance: {{height_units}}
+          - Safe zones placement: {{safety_guidelines}}
+          
+          **Navigation Design:**
+          
+          - Clear path indication: {{visual_cues}}
+          - Landmark placement: {{landmark_rules}}
+          - Dead end avoidance: {{dead_end_policy}}
+          - Multiple path options: {{branching_rules}}
+      - id: pacing-and-flow
+        title: Pacing and Flow
+        instruction: Define how to control the rhythm and pace of gameplay within levels
+        template: |
+          **Action Sequences:**
+          
+          - High intensity duration: {{max_duration}}
+          - Rest period requirement: {{min_rest_time}}
+          - Intensity variation: {{pacing_pattern}}
+          
+          **Learning Sequences:**
+          
+          - New mechanic introduction: {{teaching_method}}
+          - Practice opportunity: {{practice_duration}}
+          - Skill application: {{application_context}}
+      - id: challenge-design
+        title: Challenge Design
+        instruction: Define how to create appropriate challenges for each level type
+        template: |
+          **Challenge Types:**
+          
+          - Execution challenges: {{skill_requirements}}
+          - Puzzle challenges: {{complexity_guidelines}}
+          - Time challenges: {{time_pressure_rules}}
+          - Resource challenges: {{resource_management}}
+          
+          **Difficulty Calibration:**
+          
+          - Skill check frequency: {{frequency_guidelines}}
+          - Failure recovery: {{retry_mechanics}}
+          - Hint system integration: {{help_system}}
+
+  - id: technical-implementation
+    title: Technical Implementation
+    instruction: Define technical requirements for level implementation
+    sections:
+      - id: level-data-structure
+        title: Level Data Structure
+        instruction: Define how level data should be structured for implementation
+        template: |
+          **Level File Format:**
+          
+          - Data format: {{json|yaml|custom}}
+          - File naming: `level_{{world}}_{{number}}.{{extension}}`
+          - Data organization: {{structure_description}}
+        sections:
+          - id: required-data-fields
+            title: Required Data Fields
+            type: code
+            language: json
+            template: |
+              {
+                "levelId": "{{unique_identifier}}",
+                "worldId": "{{world_identifier}}",
+                "difficulty": {{difficulty_value}},
+                "targetTime": {{completion_time_seconds}},
+                "objectives": {
+                  "primary": "{{primary_objective}}",
+                  "secondary": ["{{secondary_objectives}}"],
+                  "hidden": ["{{secret_objectives}}"]
+                },
+                "layout": {
+                  "width": {{grid_width}},
+                  "height": {{grid_height}},
+                  "tilemap": "{{tilemap_reference}}"
+                },
+                "entities": [
+                  {
+                    "type": "{{entity_type}}",
+                    "position": {"x": {{x}}, "y": {{y}}},
+                    "properties": {{entity_properties}}
+                  }
+                ]
+              }
+      - id: asset-integration
+        title: Asset Integration
+        instruction: Define how level assets are organized and loaded
+        template: |
+          **Tilemap Requirements:**
+          
+          - Tile size: {{tile_dimensions}}px
+          - Tileset organization: {{tileset_structure}}
+          - Layer organization: {{layer_system}}
+          - Collision data: {{collision_format}}
+          
+          **Audio Integration:**
+          
+          - Background music: {{music_requirements}}
+          - Ambient sounds: {{ambient_system}}
+          - Dynamic audio: {{dynamic_audio_rules}}
+      - id: performance-optimization
+        title: Performance Optimization
+        instruction: Define performance requirements for level systems
+        template: |
+          **Entity Limits:**
+          
+          - Maximum active entities: {{entity_limit}}
+          - Maximum particles: {{particle_limit}}
+          - Maximum audio sources: {{audio_limit}}
+          
+          **Memory Management:**
+          
+          - Texture memory budget: {{texture_memory}}MB
+          - Audio memory budget: {{audio_memory}}MB
+          - Level loading time: <{{load_time}}s
+          
+          **Culling and LOD:**
+          
+          - Off-screen culling: {{culling_distance}}
+          - Level-of-detail rules: {{lod_system}}
+          - Asset streaming: {{streaming_requirements}}
+
+  - id: level-testing-framework
+    title: Level Testing Framework
+    instruction: Define how levels should be tested and validated
+    sections:
+      - id: automated-testing
+        title: Automated Testing
+        template: |
+          **Performance Testing:**
+          
+          - Frame rate validation: Maintain {{fps_target}} FPS
+          - Memory usage monitoring: Stay under {{memory_limit}}MB
+          - Loading time verification: Complete in <{{load_time}}s
+          
+          **Gameplay Testing:**
+          
+          - Completion path validation: All objectives achievable
+          - Collectible accessibility: All items reachable
+          - Softlock prevention: No unwinnable states
+      - id: manual-testing-protocol
+        title: Manual Testing Protocol
+        sections:
+          - id: playtesting-checklist
+            title: Playtesting Checklist
+            type: checklist
+            items:
+              - "Level completes within target time range"
+              - "All mechanics function correctly"
+              - "Difficulty feels appropriate for level category"
+              - "Player guidance is clear and effective"
+              - "No exploits or sequence breaks (unless intended)"
+          - id: player-experience-testing
+            title: Player Experience Testing
+            type: checklist
+            items:
+              - "Tutorial levels teach effectively"
+              - "Challenge feels fair and rewarding"
+              - "Flow and pacing maintain engagement"
+              - "Audio and visual feedback support gameplay"
+      - id: balance-validation
+        title: Balance Validation
+        template: |
+          **Metrics Collection:**
+          
+          - Completion rate: Target {{completion_percentage}}%
+          - Average completion time: {{target_time}} ± {{variance}}
+          - Death count per level: <{{max_deaths}}
+          - Collectible discovery rate: {{discovery_percentage}}%
+          
+          **Iteration Guidelines:**
+          
+          - Adjustment criteria: {{criteria_for_changes}}
+          - Testing sample size: {{minimum_testers}}
+          - Validation period: {{testing_duration}}
+
+  - id: content-creation-pipeline
+    title: Content Creation Pipeline
+    instruction: Define the workflow for creating new levels
+    sections:
+      - id: design-phase
+        title: Design Phase
+        template: |
+          **Concept Development:**
+          
+          1. Define level purpose and goals
+          2. Create rough layout sketch
+          3. Identify key mechanics and challenges
+          4. Estimate difficulty and duration
+          
+          **Documentation Requirements:**
+          
+          - Level design brief
+          - Layout diagrams
+          - Mechanic integration notes
+          - Asset requirement list
+      - id: implementation-phase
+        title: Implementation Phase
+        template: |
+          **Technical Implementation:**
+          
+          1. Create level data file
+          2. Build tilemap and layout
+          3. Place entities and objects
+          4. Configure level logic and triggers
+          5. Integrate audio and visual effects
+          
+          **Quality Assurance:**
+          
+          1. Automated testing execution
+          2. Internal playtesting
+          3. Performance validation
+          4. Bug fixing and polish
+      - id: integration-phase
+        title: Integration Phase
+        template: |
+          **Game Integration:**
+          
+          1. Level progression integration
+          2. Save system compatibility
+          3. Analytics integration
+          4. Achievement system integration
+          
+          **Final Validation:**
+          
+          1. Full game context testing
+          2. Performance regression testing
+          3. Platform compatibility verification
+          4. Final approval and release
+
+  - id: success-metrics
+    title: Success Metrics
+    instruction: Define how to measure level design success
+    sections:
+      - id: player-engagement
+        title: Player Engagement
+        type: bullet-list
+        template: |
+          - Level completion rate: {{target_rate}}%
+          - Replay rate: {{replay_target}}%
+          - Time spent per level: {{engagement_time}}
+          - Player satisfaction scores: {{satisfaction_target}}/10
+      - id: technical-performance
+        title: Technical Performance
+        type: bullet-list
+        template: |
+          - Frame rate consistency: {{fps_consistency}}%
+          - Loading time compliance: {{load_compliance}}%
+          - Memory usage efficiency: {{memory_efficiency}}%
+          - Crash rate: <{{crash_threshold}}%
+      - id: design-quality
+        title: Design Quality
+        type: bullet-list
+        template: |
+          - Difficulty curve adherence: {{curve_accuracy}}
+          - Mechanic integration effectiveness: {{integration_score}}
+          - Player guidance clarity: {{guidance_score}}
+          - Content accessibility: {{accessibility_rate}}%

expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md

@@ -3,11 +3,19 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-creator-tools
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Greet the user with your name and role, and inform of the *help command
+  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
+  - CRITICAL: Do NOT create or modify any files during startup
+  - Offer to help with BMad framework extensions but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
 agent:
   name: The Creator
   id: bmad-the-creator
@@ -27,12 +35,6 @@ core_principles:
   - Convention Over Configuration - Follow BMad naming and structure patterns
   - Extensibility First - Design for future expansion and customization
   - Numbered Options Protocol - Always use numbered lists for user selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically create documents or execute tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with BMad framework extensions but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for framework design advice'
@@ -43,11 +45,11 @@ commands:
   - '*exit" - Say goodbye as The Creator, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-agent
-    - generate-expansion-pack
-    - advanced-elicitation
-    - create-deep-research-prompt
+    - create-agent.md
+    - generate-expansion-pack.md
+    - advanced-elicitation.md
+    - create-deep-research-prompt.md
   templates:
-    - agent-tmpl
-    - expansion-pack-plan-tmpl
+    - agent-tmpl.yaml
+    - expansion-pack-plan-tmpl.yaml
 ```

expansion-packs/bmad-creator-tools/config.yaml

@@ -1,5 +1,5 @@
 name: bmad-creator-tools
-version: 1.6.0
+version: 1.7.0
 short-title: Tools for creating BMad framework components
 description: Tools for creating and extending BMad framework components.
 author: Brian (BMad)

expansion-packs/bmad-creator-tools/templates/agent-teams-tmpl.md

@@ -1,154 +0,0 @@
-# Agent Team Configuration Template
-
-[[LLM: This template is for creating agent team configurations in YAML format. Follow the structure carefully and replace all placeholders with appropriate values. The team name should reflect the team's purpose and domain focus.]]
-
-```yaml
-bundle:
-  name: {{team-display-name}}
-  [[LLM: Use format "Team [Descriptor]" for generic teams or "[Domain] Team" for specialized teams. Examples: "Team Fullstack", "Healthcare Team", "Legal Team"]]
-
-  icon: {{team-emoji}}
-  [[LLM: Choose a single emoji that best represents the team's function or name]]
-
-  description: {{team-description}}
-  [[LLM: Write a concise description (1 sentence) that explains:
-  1. The team's primary purpose
-  2. What types of projects they handle
-  3. Any special capabilities or focus areas
-  4. Keep it short as its displayed in menus
-  Example: "Full Stack Ideation Web App Team." or "Startup Business Coaching team"]]
-
-agents:
-  [[LLM: List the agents that make up this team. Guidelines:
-  - Use shortened agent names (e.g., 'analyst' not 'business-analyst')
-  - Include 'bmad-orchestrator' for bmad-core teams as the coordinator
-  - Only use '*' for an all-inclusive team (rare)
-  - Order agents logically by workflow (analysis → design → development → testing)
-  - For expansion packs, include both core agents and custom agents]]
-
-  ^^CONDITION: standard-team^^
-  # Core workflow agents
-  - bmad-orchestrator  # Team coordinator
-  - analyst            # Requirements and analysis
-  - pm                 # Product management
-  - architect          # System design
-  - dev                # Development
-  - qa                 # Quality assurance
-  ^^/CONDITION: standard-team^^
-
-  ^^CONDITION: minimal-team^^
-  # Minimal team for quick iterations
-  - bmad-orchestrator  # Team coordinator
-  - architect          # Design and planning
-  - dev                # Implementation
-  ^^/CONDITION: minimal-team^^
-
-  ^^CONDITION: specialized-team^^
-  # Domain-specific team composition
-  - {{domain}}-orchestrator  # Domain coordinator
-  <<REPEAT section="specialist-agents" count="{{agent-count}}">>
-  - {{agent-short-name}}     # {{agent-role-description}}
-  <</REPEAT>>
-  ^^/CONDITION: specialized-team^^
-
-  ^^CONDITION: include-all-agents^^
-  - '*'  # Include all available agents
-  ^^/CONDITION: include-all-agents^^
-
-workflows:
-  [[LLM: Define the workflows this team can execute that will guide the user through a multi-step multi agent process. Guidelines:
-  - Use null if the team doesn't have predefined workflows
-  - Workflow names should be descriptive
-  - use domain-specific workflow names]]
-
-  ^^CONDITION: no-workflows^^
-  null  # No predefined workflows
-  ^^/CONDITION: no-workflows^^
-
-  ^^CONDITION: standard-workflows^^
-  # New project workflows
-  - greenfield-fullstack  # New full-stack application
-  - greenfield-service    # New backend service
-  - greenfield-ui         # New frontend application
-
-  # Existing project workflows
-  - brownfield-fullstack  # Enhance existing full-stack app
-  - brownfield-service    # Enhance existing service
-  - brownfield-ui         # Enhance existing UI
-  ^^/CONDITION: standard-workflows^^
-
-  ^^CONDITION: domain-workflows^^
-  # Domain-specific workflows
-  <<REPEAT section="workflows" count="{{workflow-count}}">>
-  - {{workflow-name}}  # {{workflow-description}}
-  <</REPEAT>>
-  ^^/CONDITION: domain-workflows^^
-```
-
-@{example-1: Standard fullstack team}
-
-```yaml
-bundle:
-  name: Team Fullstack
-  icon: 🚀
-  description: Complete agile team for full-stack web applications. Handles everything from requirements to deployment.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - architect
-  - dev
-  - qa
-  - ux-expert
-workflows:
-  - greenfield-fullstack
-  - greenfield-service
-  - greenfield-ui
-  - brownfield-fullstack
-  - brownfield-service
-  - brownfield-ui
-```
-
-@{example-2: Healthcare expansion pack team}
-
-```yaml
-bundle:
-  name: Healthcare Compliance Team
-  icon: ⚕️
-  description: Specialized team for healthcare applications with HIPAA compliance focus. Manages clinical workflows and regulatory requirements.
-agents:
-  - healthcare-orchestrator
-  - clinical-analyst
-  - compliance-officer
-  - architect
-  - dev
-  - qa
-workflows:
-  - healthcare-patient-portal
-  - healthcare-compliance-audit
-  - clinical-trial-management
-```
-
-@{example-3: Minimal IDE team}
-
-```yaml
-bundle:
-  name: Team IDE Minimal
-  icon: ⚡
-  description: Minimal team for IDE usage. Just the essentials for quick development.
-agents:
-  - bmad-orchestrator
-  - architect
-  - dev
-workflows: null
-```
-
-[[LLM: When creating a new team configuration:
-
-1. Choose the most appropriate condition block based on team type
-2. Remove all unused condition blocks
-3. Replace all placeholders with actual values
-4. Ensure agent names match available agents in the system
-5. Verify workflow names match available workflows
-6. Save as team-[descriptor].yaml or [domain]-team.yaml
-7. Place in the agent-teams directory of the appropriate location]]

expansion-packs/bmad-creator-tools/templates/agent-teams-tmpl.yaml

@@ -0,0 +1,178 @@
+template:
+  id: agent-teams-template-v2
+  name: Agent Team Configuration
+  version: 2.0
+  output:
+    format: yaml
+    filename: "agent-teams/{{team_name}}.yaml"
+    title: "{{team_name}}"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: header
+    title: Agent Team Configuration Template
+    instruction: |
+      This template is for creating agent team configurations in YAML format. Follow the structure carefully and replace all placeholders with appropriate values. The team name should reflect the team's purpose and domain focus.
+
+  - id: yaml-configuration
+    type: code
+    language: yaml
+    template: |
+      bundle:
+        name: {{team_display_name}}
+        icon: {{team_emoji}}
+        description: {{team_description}}
+      
+      agents:
+        {{agent_list}}
+      
+      workflows:
+        {{workflow_list}}
+    instruction: |
+      Use format "Team [Descriptor]" for generic teams or "[Domain] Team" for specialized teams. Examples: "Team Fullstack", "Healthcare Team", "Legal Team"
+      
+      Choose a single emoji that best represents the team's function or name
+      
+      Write a concise description (1 sentence) that explains:
+      1. The team's primary purpose
+      2. What types of projects they handle
+      3. Any special capabilities or focus areas
+      4. Keep it short as its displayed in menus
+      Example: "Full Stack Ideation Web App Team." or "Startup Business Coaching team"
+      
+      List the agents that make up this team. Guidelines:
+      - Use shortened agent names (e.g., 'analyst' not 'business-analyst')
+      - Include 'bmad-orchestrator' for bmad-core teams as the coordinator
+      - Only use '*' for an all-inclusive team (rare)
+      - Order agents logically by workflow (analysis → design → development → testing)
+      - For expansion packs, include both core agents and custom agents
+      
+      Define the workflows this team can execute that will guide the user through a multi-step multi agent process. Guidelines:
+      - Use null if the team doesn't have predefined workflows
+      - Workflow names should be descriptive
+      - use domain-specific workflow names
+    sections:
+      - id: standard-team
+        condition: Standard team configuration
+        template: |
+          # Core workflow agents
+          - bmad-orchestrator  # Team coordinator
+          - analyst            # Requirements and analysis
+          - pm                 # Product management
+          - architect          # System design
+          - dev                # Development
+          - qa                 # Quality assurance
+      - id: minimal-team
+        condition: Minimal team configuration
+        template: |
+          # Minimal team for quick iterations
+          - bmad-orchestrator  # Team coordinator
+          - architect          # Design and planning
+          - dev                # Implementation
+      - id: specialized-team
+        condition: Domain-specific team
+        template: |
+          # Domain-specific team composition
+          - {{domain}}-orchestrator  # Domain coordinator
+          - {{agent_short_name}}     # {{agent_role_description}}
+      - id: all-agents
+        condition: Include all available agents
+        template: |
+          - '*'  # Include all available agents
+      - id: no-workflows
+        condition: No predefined workflows
+        template: |
+          null  # No predefined workflows
+      - id: standard-workflows
+        condition: Standard project workflows
+        template: |
+          # New project workflows
+          - greenfield-fullstack  # New full-stack application
+          - greenfield-service    # New backend service
+          - greenfield-ui         # New frontend application
+          
+          # Existing project workflows
+          - brownfield-fullstack  # Enhance existing full-stack app
+          - brownfield-service    # Enhance existing service
+          - brownfield-ui         # Enhance existing UI
+      - id: domain-workflows
+        condition: Domain-specific workflows
+        template: |
+          # Domain-specific workflows
+          - {{workflow_name}}  # {{workflow_description}}
+
+  - id: examples
+    title: Examples
+    sections:
+      - id: example-1
+        title: "Example 1: Standard fullstack team"
+        type: code
+        language: yaml
+        template: |
+          bundle:
+            name: Team Fullstack
+            icon: 🚀
+            description: Complete agile team for full-stack web applications. Handles everything from requirements to deployment.
+          agents:
+            - bmad-orchestrator
+            - analyst
+            - pm
+            - architect
+            - dev
+            - qa
+            - ux-expert
+          workflows:
+            - greenfield-fullstack
+            - greenfield-service
+            - greenfield-ui
+            - brownfield-fullstack
+            - brownfield-service
+            - brownfield-ui
+      - id: example-2
+        title: "Example 2: Healthcare expansion pack team"
+        type: code
+        language: yaml
+        template: |
+          bundle:
+            name: Healthcare Compliance Team
+            icon: ⚕️
+            description: Specialized team for healthcare applications with HIPAA compliance focus. Manages clinical workflows and regulatory requirements.
+          agents:
+            - healthcare-orchestrator
+            - clinical-analyst
+            - compliance-officer
+            - architect
+            - dev
+            - qa
+          workflows:
+            - healthcare-patient-portal
+            - healthcare-compliance-audit
+            - clinical-trial-management
+      - id: example-3
+        title: "Example 3: Minimal IDE team"
+        type: code
+        language: yaml
+        template: |
+          bundle:
+            name: Team IDE Minimal
+            icon: ⚡
+            description: Minimal team for IDE usage. Just the essentials for quick development.
+          agents:
+            - bmad-orchestrator
+            - architect
+            - dev
+          workflows: null
+
+  - id: creation-instructions
+    instruction: |
+      When creating a new team configuration:
+      
+      1. Choose the most appropriate condition block based on team type
+      2. Remove all unused condition blocks
+      3. Replace all placeholders with actual values
+      4. Ensure agent names match available agents in the system
+      5. Verify workflow names match available workflows
+      6. Save as team-[descriptor].yaml or [domain]-team.yaml
+      7. Place in the agent-teams directory of the appropriate location

expansion-packs/bmad-creator-tools/templates/agent-tmpl.md

@@ -1,143 +0,0 @@
-# [AGENT_ID]
-
-[[LLM: This is an agent definition template. When creating a new agent:
-
-1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
-2. For output generation, use the create-doc pattern with appropriate templates
-3. Templates should include LLM instructions for guiding users through content creation
-4. Character personas should be consistent and domain-appropriate
-5. Follow the numbered options protocol for all user interactions]]
-
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yaml
-activation-instructions:
-    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-    - The customization field ALWAYS takes precedence over any conflicting instructions
-    - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-    - Command
-
-agent:
-  name: [AGENT_NAME]
-  id: [AGENT_ID]
-  title: [AGENT_TITLE]
-  customization: [OPTIONAL_CUSTOMIZATION]
-
-persona:
-  role: [AGENT_ROLE_DESCRIPTION]
-  style: [COMMUNICATION_STYLE]
-  identity: [AGENT_IDENTITY_DESCRIPTION]
-  focus: [PRIMARY_FOCUS_AREAS]
-
-  core_principles:
-    - [PRINCIPLE_1]
-    - [PRINCIPLE_2]
-    - [PRINCIPLE_3]
-    # Add more principles as needed
-
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - [STARTUP_INSTRUCTION]
-  - [STARTUP_INSTRUCTION]...
-
-commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) [DEFAULT_MODE_DESCRIPTION]
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  [[LLM: For output generation tasks, always use create-doc with templates rather than custom tasks.
-  Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
-  The template should contain LLM instructions for guiding users through the creation process]]
-  - [tasks] specific to the agent that are not covered by a template
-  [[LLM: Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution]]
-  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
-
-dependencies:
-  [[LLM: CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
-  - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
-  - Templates: Must exist in templates/ directory with proper LLM instructions
-  - Checklists: Must exist in checklists/ directory for quality validation
-  - Data: Must exist in data/ directory or be documented as user-required
-  - Utils: Must exist in utils/ directory (include template-format if using templates)]]
-
-  tasks:
-    - create-doc  # Required if agent creates documents from templates
-    - [TASK_1]    # Custom task for non-document operations
-    - [TASK_2]    # Another custom task
-    [[LLM: Example tasks: validate-design, analyze-requirements, execute-tests]]
-
-  templates:
-    - [TEMPLATE_1]  # Template with LLM instructions for guided creation
-    - [TEMPLATE_2]  # Another template for different document type
-    [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
-    Each template should include [[LLM: guidance]] and other conventions from `template-format.md` sections for user interaction]]
-
-  checklists:
-    - [CHECKLIST_1]  # Quality validation for template outputs
-    [[LLM: Example: blueprint-checklist, contract-checklist
-    Checklists validate documents created from templates]]
-
-  data:
-    - [DATA_1]  # Domain knowledge files
-    [[LLM: Example: building-codes.md, legal-terminology.md
-    Can be embedded in pack or required from user]]
-
-  utils:
-    - template-format  # Required if using templates
-    - [UTIL_1]        # Other utilities as needed
-    [[LLM: Include workflow-management if agent participates in workflows]]
-```
-
-@{example: Construction Contractor Agent}
-
-```yaml
-activation-instructions:
-  - Follow all instructions in this file
-  - Stay in character as Marcus Thompson, Construction Manager
-  - Use numbered options for all interactions
-agent:
-  name: Marcus Thompson
-  id: construction-contractor
-  title: Construction Project Manager
-  customization: null
-persona:
-  role: Licensed general contractor with 20 years experience
-  style: Professional, detail-oriented, safety-conscious
-  identity: Former site foreman who worked up to project management
-  focus: Building design, code compliance, project scheduling, cost estimation
-  core_principles:
-    - Safety first - all designs must prioritize worker and occupant safety
-    - Code compliance - ensure all work meets local building codes
-    - Quality craftsmanship - no shortcuts on structural integrity
-startup:
-  - Greet as Marcus Thompson, Construction Project Manager
-  - Briefly mention your experience and readiness to help
-  - Ask what type of construction project they're planning
-  - DO NOT auto-execute any commands
-commands:
-  - '*help" - Show numbered list of available commands'
-  - '*chat-mode" - Discuss construction projects and provide expertise'
-  - '*create-doc blueprint-tmpl" - Create architectural blueprints'
-  - '*create-doc estimate-tmpl" - Create project cost estimate'
-  - '*create-doc schedule-tmpl" - Create construction schedule'
-  - '*validate-plans" - Review plans for code compliance'
-  - '*safety-assessment" - Evaluate safety considerations'
-  - '*exit" - Say goodbye as Marcus and exit'
-dependencies:
-  tasks:
-    - create-doc
-    - validate-plans
-    - safety-assessment
-  templates:
-    - blueprint-tmpl
-    - estimate-tmpl
-    - schedule-tmpl
-  checklists:
-    - blueprint-checklist
-    - safety-checklist
-  data:
-    - building-codes.md
-    - materials-guide.md
-  utils:
-    - template-format
-```

expansion-packs/bmad-creator-tools/templates/agent-tmpl.yaml

@@ -0,0 +1,154 @@
+template:
+  id: agent-template-v2
+  name: Agent Definition
+  version: 2.0
+  output:
+    format: markdown
+    filename: "agents/{{agent_id}}.md"
+    title: "{{agent_id}}"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: header
+    title: "{{agent_id}}"
+    instruction: |
+      This is an agent definition template. When creating a new agent:
+      
+      1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
+      2. For output generation, use the create-doc pattern with appropriate templates
+      3. Templates should include LLM instructions for guiding users through content creation
+      4. Character personas should be consistent and domain-appropriate
+      5. Follow the numbered options protocol for all user interactions
+
+  - id: agent-definition
+    content: |
+      CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+    sections:
+      - id: yaml-definition
+        type: code
+        language: yaml
+        template: |
+          activation-instructions:
+              - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
+              - Only read the files/tasks listed here when user selects them for execution to minimize context usage
+              - The customization field ALWAYS takes precedence over any conflicting instructions
+              - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+              - Command
+          
+          agent:
+            name: {{agent_name}}
+            id: {{agent_id}}
+            title: {{agent_title}}
+            customization: {{optional_customization}}
+          
+          persona:
+            role: {{agent_role_description}}
+            style: {{communication_style}}
+            identity: {{agent_identity_description}}
+            focus: {{primary_focus_areas}}
+          
+            core_principles:
+              - {{principle_1}}
+              - {{principle_2}}
+              - {{principle_3}}
+              # Add more principles as needed
+          
+          startup:
+            - Greet the user with your name and role, and inform of the *help command.
+            - {{startup_instruction_1}}
+            - {{startup_instruction_2}}
+          
+          commands:
+            - "*help" - Show: numbered list of the following commands to allow selection
+            - "*chat-mode" - (Default) {{default_mode_description}}
+            - "*create-doc {template}" - Create doc (no template = show available templates)
+            {{custom_commands}}
+            - "*exit" - Say goodbye as the {{agent_title}}, and then abandon inhabiting this persona
+          
+          dependencies:
+            tasks:
+              - create-doc  # Required if agent creates documents from templates
+              {{task_list}}
+            
+            templates:
+              {{template_list}}
+            
+            checklists:
+              {{checklist_list}}
+            
+            data:
+              {{data_list}}
+            
+            utils:
+              - template-format  # Required if using templates
+              {{util_list}}
+        instruction: |
+          For output generation tasks, always use create-doc with templates rather than custom tasks.
+          Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
+          The template should contain LLM instructions for guiding users through the creation process
+          
+          Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution
+          
+          CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
+          - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
+          - Templates: Must exist in templates/ directory with proper LLM instructions
+          - Checklists: Must exist in checklists/ directory for quality validation
+          - Data: Must exist in data/ directory or be documented as user-required
+          - Utils: Must exist in utils/ directory (include template-format if using templates)
+
+  - id: example
+    title: Example: Construction Contractor Agent
+    type: code
+    language: yaml
+    template: |
+      activation-instructions:
+        - Follow all instructions in this file
+        - Stay in character as Marcus Thompson, Construction Manager
+        - Use numbered options for all interactions
+      agent:
+        name: Marcus Thompson
+        id: construction-contractor
+        title: Construction Project Manager
+        customization: null
+      persona:
+        role: Licensed general contractor with 20 years experience
+        style: Professional, detail-oriented, safety-conscious
+        identity: Former site foreman who worked up to project management
+        focus: Building design, code compliance, project scheduling, cost estimation
+        core_principles:
+          - Safety first - all designs must prioritize worker and occupant safety
+          - Code compliance - ensure all work meets local building codes
+          - Quality craftsmanship - no shortcuts on structural integrity
+      startup:
+        - Greet as Marcus Thompson, Construction Project Manager
+        - Briefly mention your experience and readiness to help
+        - Ask what type of construction project they're planning
+        - DO NOT auto-execute any commands
+      commands:
+        - '*help" - Show numbered list of available commands'
+        - '*chat-mode" - Discuss construction projects and provide expertise'
+        - '*create-doc blueprint-tmpl" - Create architectural blueprints'
+        - '*create-doc estimate-tmpl" - Create project cost estimate'
+        - '*create-doc schedule-tmpl" - Create construction schedule'
+        - '*validate-plans" - Review plans for code compliance'
+        - '*safety-assessment" - Evaluate safety considerations'
+        - '*exit" - Say goodbye as Marcus and exit'
+      dependencies:
+        tasks:
+          - create-doc
+          - validate-plans
+          - safety-assessment
+        templates:
+          - blueprint-tmpl
+          - estimate-tmpl
+          - schedule-tmpl
+        checklists:
+          - blueprint-checklist
+          - safety-checklist
+        data:
+          - building-codes.md
+          - materials-guide.md
+        utils:
+          - template-format

expansion-packs/bmad-creator-tools/templates/expansion-pack-plan-tmpl.md

@@ -1,91 +0,0 @@
-# {Pack Name} Expansion Pack Plan
-
-## Overview
-
-- **Pack Name**: {pack-identifier}
-- **Display Name**: {Full Expansion Pack Name}
-- **Description**: {Brief description of what this pack does}
-- **Target Domain**: {Industry/domain this serves}
-- **Author**: {Your name/organization}
-
-## Problem Statement
-
-{What specific challenges does this expansion pack solve?}
-
-## Target Users
-
-{Who will benefit from this expansion pack?}
-
-## Components to Create
-
-### Agents
-
-- [ ] `{pack-name}-orchestrator` - **REQUIRED**: Master orchestrator for {domain} workflows
-  - Key commands: {list main commands}
-  - Manages: {what it orchestrates}
-- [ ] `{agent-1-name}` - {Role description}
-  - Tasks used: {task-1}, {task-2}
-  - Templates used: {template-1}
-  - Data required: {data-file-1}
-- [ ] `{agent-2-name}` - {Role description}
-  - Tasks used: {task-3}
-  - Templates used: {template-2}
-  - Data required: {data-file-2}
-
-### Tasks
-
-- [ ] `{task-1}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-2}.md` - {Purpose} (used by: {agent})
-- [ ] `{task-3}.md` - {Purpose} (used by: {agent})
-
-### Templates
-
-- [ ] `{template-1}-tmpl.md` - {Document type} (used by: {agent/task})
-- [ ] `{template-2}-tmpl.md` - {Document type} (used by: {agent/task})
-
-### Checklists
-
-- [ ] `{checklist-1}-checklist.md` - {What it validates}
-- [ ] `{checklist-2}-checklist.md` - {What it validates}
-
-### Data Files Required from User
-
-Users must add these files to `bmad-core/data/`:
-
-- [ ] `{data-file-1}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-- [ ] `{data-file-2}.{ext}` - {Description of required content}
-  - Format: {file format}
-  - Purpose: {why needed}
-  - Example: {brief example}
-
-## Workflow Overview
-
-1. {Step 1 - typically starts with orchestrator}
-2. {Step 2}
-3. {Step 3}
-4. {Final output/deliverable}
-
-## Integration Points
-
-- Depends on core agents: {list any core BMad agents used}
-- Extends teams: {which teams to update}
-
-## Success Criteria
-
-- [ ] All components created and cross-referenced
-- [ ] No orphaned task/template references
-- [ ] Data requirements clearly documented
-- [ ] Orchestrator provides clear workflow
-- [ ] README includes setup instructions
-
-## User Approval
-
-- [ ] Plan reviewed by user
-- [ ] Approval to proceed with implementation
-
----
-
-**Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.

expansion-packs/bmad-creator-tools/templates/expansion-pack-plan-tmpl.yaml

@@ -0,0 +1,120 @@
+template:
+  id: expansion-pack-plan-template-v2
+  name: Expansion Pack Plan
+  version: 2.0
+  output:
+    format: markdown
+    filename: "{{pack_name}}-expansion-pack-plan.md"
+    title: "{{pack_display_name}} Expansion Pack Plan"
+
+workflow:
+  mode: interactive
+
+sections:
+  - id: overview
+    title: Overview
+    template: |
+      - **Pack Name**: {{pack_identifier}}
+      - **Display Name**: {{full_expansion_pack_name}}
+      - **Description**: {{brief_description}}
+      - **Target Domain**: {{industry_domain}}
+      - **Author**: {{author_name_organization}}
+
+  - id: problem-statement
+    title: Problem Statement
+    instruction: What specific challenges does this expansion pack solve?
+    template: "{{problem_description}}"
+
+  - id: target-users
+    title: Target Users
+    instruction: Who will benefit from this expansion pack?
+    template: "{{target_user_description}}"
+
+  - id: components
+    title: Components to Create
+    sections:
+      - id: agents
+        title: Agents
+        type: checklist
+        instruction: List all agents to be created with their roles and dependencies
+        items:
+          - id: orchestrator
+            template: |
+              `{{pack_name}}-orchestrator` - **REQUIRED**: Master orchestrator for {{domain}} workflows
+              - Key commands: {{command_list}}
+              - Manages: {{orchestration_scope}}
+          - id: agent-list
+            repeatable: true
+            template: |
+              `{{agent_name}}` - {{role_description}}
+              - Tasks used: {{task_list}}
+              - Templates used: {{template_list}}
+              - Data required: {{data_requirements}}
+      
+      - id: tasks
+        title: Tasks
+        type: checklist
+        instruction: List all tasks to be created
+        repeatable: true
+        template: "`{{task_name}}.md` - {{purpose}} (used by: {{using_agents}})"
+      
+      - id: templates
+        title: Templates
+        type: checklist
+        instruction: List all templates to be created
+        repeatable: true
+        template: "`{{template_name}}-tmpl.md` - {{document_type}} (used by: {{using_components}})"
+      
+      - id: checklists
+        title: Checklists
+        type: checklist
+        instruction: List all checklists to be created
+        repeatable: true
+        template: "`{{checklist_name}}-checklist.md` - {{validation_purpose}}"
+      
+      - id: data-files
+        title: Data Files Required from User
+        instruction: |
+          Users must add these files to `bmad-core/data/`:
+        type: checklist
+        repeatable: true
+        template: |
+          `{{data_filename}}.{{extension}}` - {{content_description}}
+          - Format: {{file_format}}
+          - Purpose: {{why_needed}}
+          - Example: {{brief_example}}
+
+  - id: workflow-overview
+    title: Workflow Overview
+    type: numbered-list
+    instruction: Describe the typical workflow steps
+    template: "{{workflow_step}}"
+
+  - id: integration-points
+    title: Integration Points
+    template: |
+      - Depends on core agents: {{core_agent_dependencies}}
+      - Extends teams: {{team_updates}}
+
+  - id: success-criteria
+    title: Success Criteria
+    type: checklist
+    items:
+      - "All components created and cross-referenced"
+      - "No orphaned task/template references"
+      - "Data requirements clearly documented"
+      - "Orchestrator provides clear workflow"
+      - "README includes setup instructions"
+
+  - id: user-approval
+    title: User Approval
+    type: checklist
+    items:
+      - "Plan reviewed by user"
+      - "Approval to proceed with implementation"
+
+  - id: next-steps
+    content: |
+      ---
+      
+      **Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.

expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md

@@ -3,11 +3,18 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-infrastructure-devops
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
+  - "List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation"
+  - "List available templates: infrastructure-architecture, infrastructure-platform-from-arch"
+  - Execute selected task or stay in persona to help guided by Core DevOps Principles
 agent:
   name: Alex
   id: infra-devops-platform
@@ -29,11 +36,6 @@ persona:
     - CI/CD Excellence - Build robust pipelines for fast, safe, reliable software delivery through automation and testing
     - Disaster Recovery - Plan for worst-case scenarios with backup strategies and regularly tested recovery procedures
     - Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
-startup:
-  - Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
-  - "List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation"
-  - "List available templates: infrastructure-architecture, infrastructure-platform-from-arch"
-  - Execute selected task or stay in persona to help guided by Core DevOps Principles
 commands:
   - '*help" - Show: numbered list of the following commands to allow selection'
   - '*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance'
@@ -44,16 +46,14 @@ commands:
   - '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-doc
-    - review-infrastructure
-    - validate-infrastructure
+    - create-doc.md
+    - review-infrastructure.md
+    - validate-infrastructure.md
   templates:
-    - infrastructure-architecture-tmpl
-    - infrastructure-platform-from-arch-tmpl
+    - infrastructure-architecture-tmpl.yaml
+    - infrastructure-platform-from-arch-tmpl.yaml
   checklists:
-    - infrastructure-checklist
+    - infrastructure-checklist.md
   data:
-    - technical-preferences
-  utils:
-    - template-format
+    - technical-preferences.md
 ```

expansion-packs/bmad-infrastructure-devops/config.yaml

@@ -1,5 +1,5 @@
 name: bmad-infrastructure-devops
-version: 1.6.0
+version: 1.7.0
 short-title: Infrastructure and DevOps capabilities
 description: >-
   This expansion pack extends BMad Method with comprehensive infrastructure and

expansion-packs/bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.md

@@ -1,415 +0,0 @@
-# {{Project Name}} Infrastructure Architecture
-
-[[LLM: Initial Setup
-
-1. Replace {{Project Name}} with the actual project name throughout the document
-2. Gather and review required inputs:
-   - Product Requirements Document (PRD) - Required for business needs and scale requirements
-   - Main System Architecture - Required for infrastructure dependencies
-   - Technical Preferences/Tech Stack Document - Required for technology choices
-   - PRD Technical Assumptions - Required for cross-referencing repository and service architecture
-
-If any required documents are missing, ask user: "I need the following documents to create a comprehensive infrastructure architecture: [list missing]. Would you like to proceed with available information or provide the missing documents first?"
-
-3. <critical_rule>Cross-reference with PRD Technical Assumptions to ensure infrastructure decisions align with repository and service architecture decisions made in the system architecture.</critical_rule>
-
-Output file location: `docs/infrastructure-architecture.md`]]
-
-## Infrastructure Overview
-
-[[LLM: Review the product requirements document to understand business needs and scale requirements. Analyze the main system architecture to identify infrastructure dependencies. Document non-functional requirements (performance, scalability, reliability, security). Cross-reference with PRD Technical Assumptions to ensure alignment with repository and service architecture decisions.]]
-
-- Cloud Provider(s)
-- Core Services & Resources
-- Regional Architecture
-- Multi-environment Strategy
-
-@{example: cloud_strategy}
-
-- **Cloud Provider:** AWS (primary), with multi-cloud capability for critical services
-- **Core Services:** EKS for container orchestration, RDS for databases, S3 for storage, CloudFront for CDN
-- **Regional Architecture:** Multi-region active-passive with primary in us-east-1, DR in us-west-2
-- **Multi-environment Strategy:** Development, Staging, UAT, Production with identical infrastructure patterns
-
-@{/example}
-
-[[LLM: Infrastructure Elicitation Options
-Present user with domain-specific elicitation options:
-"For the Infrastructure Overview section, I can explore:
-
-1. **Multi-Cloud Strategy Analysis** - Evaluate cloud provider options and vendor lock-in considerations
-2. **Regional Distribution Planning** - Analyze latency requirements and data residency needs
-3. **Environment Isolation Strategy** - Design security boundaries and resource segregation
-4. **Scalability Patterns Review** - Assess auto-scaling needs and traffic patterns
-5. **Compliance Requirements Analysis** - Review regulatory and security compliance needs
-6. **Cost-Benefit Analysis** - Compare infrastructure options and TCO
-7. **Proceed to next section**
-
-Select an option (1-7):"]]
-
-## Infrastructure as Code (IaC)
-
-[[LLM: Define IaC approach based on technical preferences and existing patterns. Consider team expertise, tooling ecosystem, and maintenance requirements.]]
-
-- Tools & Frameworks
-- Repository Structure
-- State Management
-- Dependency Management
-
-<critical_rule>All infrastructure must be defined as code. No manual resource creation in production environments.</critical_rule>
-
-## Environment Configuration
-
-[[LLM: Design environment strategy that supports the development workflow while maintaining security and cost efficiency. Reference the Environment Transition Strategy section for promotion details.]]
-
-- Environment Promotion Strategy
-- Configuration Management
-- Secret Management
-- Feature Flag Integration
-
-<<REPEAT: environment>>
-
-### {{environment_name}} Environment
-
-- **Purpose:** {{environment_purpose}}
-- **Resources:** {{environment_resources}}
-- **Access Control:** {{environment_access}}
-- **Data Classification:** {{environment_data_class}}
-
-<</REPEAT>>
-
-## Environment Transition Strategy
-
-[[LLM: Detail the complete lifecycle of code and configuration changes from development to production. Include governance, testing gates, and rollback procedures.]]
-
-- Development to Production Pipeline
-- Deployment Stages and Gates
-- Approval Workflows and Authorities
-- Rollback Procedures
-- Change Cadence and Release Windows
-- Environment-Specific Configuration Management
-
-## Network Architecture
-
-[[LLM: Design network topology considering security zones, traffic patterns, and compliance requirements. Reference main architecture for service communication patterns.
-
-Create Mermaid diagram showing:
-
-- VPC/Network structure
-- Security zones and boundaries
-- Traffic flow patterns
-- Load balancer placement
-- Service mesh topology (if applicable)]]
-
-- VPC/VNET Design
-- Subnet Strategy
-- Security Groups & NACLs
-- Load Balancers & API Gateways
-- Service Mesh (if applicable)
-
-```mermaid
-graph TB
-    subgraph "Production VPC"
-        subgraph "Public Subnets"
-            ALB[Application Load Balancer]
-        end
-        subgraph "Private Subnets"
-            EKS[EKS Cluster]
-            RDS[(RDS Database)]
-        end
-    end
-    Internet((Internet)) --> ALB
-    ALB --> EKS
-    EKS --> RDS
-```
-
-^^CONDITION: uses_service_mesh^^
-
-### Service Mesh Architecture
-
-- **Mesh Technology:** {{service_mesh_tech}}
-- **Traffic Management:** {{traffic_policies}}
-- **Security Policies:** {{mesh_security}}
-- **Observability Integration:** {{mesh_observability}}
-
-^^/CONDITION: uses_service_mesh^^
-
-## Compute Resources
-
-[[LLM: Select compute strategy based on application architecture (microservices, serverless, monolithic). Consider cost, scalability, and operational complexity.]]
-
-- Container Strategy
-- Serverless Architecture
-- VM/Instance Configuration
-- Auto-scaling Approach
-
-^^CONDITION: uses_kubernetes^^
-
-### Kubernetes Architecture
-
-- **Cluster Configuration:** {{k8s_cluster_config}}
-- **Node Groups:** {{k8s_node_groups}}
-- **Networking:** {{k8s_networking}}
-- **Storage Classes:** {{k8s_storage}}
-- **Security Policies:** {{k8s_security}}
-
-^^/CONDITION: uses_kubernetes^^
-
-## Data Resources
-
-[[LLM: Design data infrastructure based on data architecture from main system design. Consider data volumes, access patterns, compliance, and recovery requirements.
-
-Create data flow diagram showing:
-
-- Database topology
-- Replication patterns
-- Backup flows
-- Data migration paths]]
-
-- Database Deployment Strategy
-- Backup & Recovery
-- Replication & Failover
-- Data Migration Strategy
-
-## Security Architecture
-
-[[LLM: Implement defense-in-depth strategy. Reference security requirements from PRD and compliance needs. Consider zero-trust principles where applicable.]]
-
-- IAM & Authentication
-- Network Security
-- Data Encryption
-- Compliance Controls
-- Security Scanning & Monitoring
-
-<critical_rule>Apply principle of least privilege for all access controls. Document all security exceptions with business justification.</critical_rule>
-
-## Shared Responsibility Model
-
-[[LLM: Clearly define boundaries between cloud provider, platform team, development team, and security team responsibilities. This is critical for operational success.]]
-
-- Cloud Provider Responsibilities
-- Platform Team Responsibilities
-- Development Team Responsibilities
-- Security Team Responsibilities
-- Operational Monitoring Ownership
-- Incident Response Accountability Matrix
-
-@{example: responsibility_matrix}
-
-| Component            | Cloud Provider | Platform Team | Dev Team       | Security Team |
-| -------------------- | -------------- | ------------- | -------------- | ------------- |
-| Physical Security    | ✓              | -             | -              | Audit         |
-| Network Security     | Partial        | ✓             | Config         | Audit         |
-| Application Security | -              | Tools         | ✓              | Review        |
-| Data Encryption      | Engine         | Config        | Implementation | Standards     |
-
-@{/example}
-
-## Monitoring & Observability
-
-[[LLM: Design comprehensive observability strategy covering metrics, logs, traces, and business KPIs. Ensure alignment with SLA/SLO requirements.]]
-
-- Metrics Collection
-- Logging Strategy
-- Tracing Implementation
-- Alerting & Incident Response
-- Dashboards & Visualization
-
-## CI/CD Pipeline
-
-[[LLM: Design deployment pipeline that balances speed with safety. Include progressive deployment strategies and automated quality gates.
-
-Create pipeline diagram showing:
-
-- Build stages
-- Test gates
-- Deployment stages
-- Approval points
-- Rollback triggers]]
-
-- Pipeline Architecture
-- Build Process
-- Deployment Strategy
-- Rollback Procedures
-- Approval Gates
-
-^^CONDITION: uses_progressive_deployment^^
-
-### Progressive Deployment Strategy
-
-- **Canary Deployment:** {{canary_config}}
-- **Blue-Green Deployment:** {{blue_green_config}}
-- **Feature Flags:** {{feature_flag_integration}}
-- **Traffic Splitting:** {{traffic_split_rules}}
-
-^^/CONDITION: uses_progressive_deployment^^
-
-## Disaster Recovery
-
-[[LLM: Design DR strategy based on business continuity requirements. Define clear RTO/RPO targets and ensure they align with business needs.]]
-
-- Backup Strategy
-- Recovery Procedures
-- RTO & RPO Targets
-- DR Testing Approach
-
-<critical_rule>DR procedures must be tested at least quarterly. Document test results and improvement actions.</critical_rule>
-
-## Cost Optimization
-
-[[LLM: Balance cost efficiency with performance and reliability requirements. Include both immediate optimizations and long-term strategies.]]
-
-- Resource Sizing Strategy
-- Reserved Instances/Commitments
-- Cost Monitoring & Reporting
-- Optimization Recommendations
-
-## BMad Integration Architecture
-
-[[LLM: Design infrastructure to specifically support other BMad agents and their workflows. This ensures the infrastructure enables the entire BMad methodology.]]
-
-### Development Agent Support
-
-- Container platform for development environments
-- GitOps workflows for application deployment
-- Service mesh integration for development testing
-- Developer self-service platform capabilities
-
-### Product & Architecture Alignment
-
-- Infrastructure implementing PRD scalability requirements
-- Deployment automation supporting product iteration speed
-- Service reliability meeting product SLAs
-- Architecture patterns properly implemented in infrastructure
-
-### Cross-Agent Integration Points
-
-- CI/CD pipelines supporting Frontend, Backend, and Full Stack development workflows
-- Monitoring and observability data accessible to QA and DevOps agents
-- Infrastructure enabling Design Architect's UI/UX performance requirements
-- Platform supporting Analyst's data collection and analysis needs
-
-## DevOps/Platform Feasibility Review
-
-[[LLM: CRITICAL STEP - Present architectural blueprint summary to DevOps/Platform Engineering Agent for feasibility review. Request specific feedback on:
-
-- **Operational Complexity:** Are the proposed patterns implementable with current tooling and expertise?
-- **Resource Constraints:** Do infrastructure requirements align with available resources and budgets?
-- **Security Implementation:** Are security patterns achievable with current security toolchain?
-- **Operational Overhead:** Will the proposed architecture create excessive operational burden?
-- **Technology Constraints:** Are selected technologies compatible with existing infrastructure?
-
-Document all feasibility feedback and concerns raised. Iterate on architectural decisions based on operational constraints and feedback.
-
-<critical_rule>Address all critical feasibility concerns before proceeding to final architecture documentation. If critical blockers identified, revise architecture before continuing.</critical_rule>]]
-
-### Feasibility Assessment Results
-
-- **Green Light Items:** {{feasible_items}}
-- **Yellow Light Items:** {{items_needing_adjustment}}
-- **Red Light Items:** {{items_requiring_redesign}}
-- **Mitigation Strategies:** {{mitigation_plans}}
-
-## Infrastructure Verification
-
-### Validation Framework
-
-This infrastructure architecture will be validated using the comprehensive `infrastructure-checklist.md`, with particular focus on Section 12: Architecture Documentation Validation. The checklist ensures:
-
-- Completeness of architecture documentation
-- Consistency with broader system architecture
-- Appropriate level of detail for different stakeholders
-- Clear implementation guidance
-- Future evolution considerations
-
-### Validation Process
-
-The architecture documentation validation should be performed:
-
-- After initial architecture development
-- After significant architecture changes
-- Before major implementation phases
-- During periodic architecture reviews
-
-The Platform Engineer should use the infrastructure checklist to systematically validate all aspects of this architecture document.
-
-## Implementation Handoff
-
-[[LLM: Create structured handoff documentation for implementation team. This ensures architecture decisions are properly communicated and implemented.]]
-
-### Architecture Decision Records (ADRs)
-
-Create ADRs for key infrastructure decisions:
-
-- Cloud provider selection rationale
-- Container orchestration platform choice
-- Networking architecture decisions
-- Security implementation choices
-- Cost optimization trade-offs
-
-### Implementation Validation Criteria
-
-Define specific criteria for validating correct implementation:
-
-- Infrastructure as Code quality gates
-- Security compliance checkpoints
-- Performance benchmarks
-- Cost targets
-- Operational readiness criteria
-
-### Knowledge Transfer Requirements
-
-- Technical documentation for operations team
-- Runbook creation requirements
-- Training needs for platform team
-- Handoff meeting agenda items
-
-## Infrastructure Evolution
-
-[[LLM: Document the long-term vision and evolution path for the infrastructure. Consider technology trends, anticipated growth, and technical debt management.]]
-
-- Technical Debt Inventory
-- Planned Upgrades and Migrations
-- Deprecation Schedule
-- Technology Roadmap
-- Capacity Planning
-- Scalability Considerations
-
-## Integration with Application Architecture
-
-[[LLM: Map infrastructure components to application services. Ensure infrastructure design supports application requirements and patterns defined in main architecture.]]
-
-- Service-to-Infrastructure Mapping
-- Application Dependency Matrix
-- Performance Requirements Implementation
-- Security Requirements Implementation
-- Data Flow to Infrastructure Correlation
-- API Gateway and Service Mesh Integration
-
-## Cross-Team Collaboration
-
-[[LLM: Define clear interfaces and communication patterns between teams. This section is critical for operational success and should include specific touchpoints and escalation paths.]]
-
-- Platform Engineer and Developer Touchpoints
-- Frontend/Backend Integration Requirements
-- Product Requirements to Infrastructure Mapping
-- Architecture Decision Impact Analysis
-- Design Architect UI/UX Infrastructure Requirements
-- Analyst Research Integration
-
-## Infrastructure Change Management
-
-[[LLM: Define structured process for infrastructure changes. Include risk assessment, testing requirements, and rollback procedures.]]
-
-- Change Request Process
-- Risk Assessment
-- Testing Strategy
-- Validation Procedures
-
-[[LLM: Final Review - Ensure all sections are complete and consistent. Verify feasibility review was conducted and all concerns addressed. Apply final validation against infrastructure checklist.]]
-
----
-
-_Document Version: 1.0_
-_Last Updated: {{current_date}}_
-_Next Review: {{review_date}}_

expansion-packs/bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.yaml

@@ -0,0 +1,424 @@
+template:
+  id: infrastructure-architecture-template-v2
+  name: Infrastructure Architecture
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/infrastructure-architecture.md
+    title: "{{project_name}} Infrastructure Architecture"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Infrastructure Architecture Elicitation Actions"
+    sections:
+      - id: infrastructure-overview
+        options:
+          - "Multi-Cloud Strategy Analysis - Evaluate cloud provider options and vendor lock-in considerations"
+          - "Regional Distribution Planning - Analyze latency requirements and data residency needs"
+          - "Environment Isolation Strategy - Design security boundaries and resource segregation"
+          - "Scalability Patterns Review - Assess auto-scaling needs and traffic patterns"
+          - "Compliance Requirements Analysis - Review regulatory and security compliance needs"
+          - "Cost-Benefit Analysis - Compare infrastructure options and TCO"
+          - "Proceed to next section"
+
+sections:
+  - id: initial-setup
+    instruction: |
+      Initial Setup
+      
+      1. Replace {{project_name}} with the actual project name throughout the document
+      2. Gather and review required inputs:
+         - Product Requirements Document (PRD) - Required for business needs and scale requirements
+         - Main System Architecture - Required for infrastructure dependencies
+         - Technical Preferences/Tech Stack Document - Required for technology choices
+         - PRD Technical Assumptions - Required for cross-referencing repository and service architecture
+      
+      If any required documents are missing, ask user: "I need the following documents to create a comprehensive infrastructure architecture: [list missing]. Would you like to proceed with available information or provide the missing documents first?"
+      
+      3. <critical_rule>Cross-reference with PRD Technical Assumptions to ensure infrastructure decisions align with repository and service architecture decisions made in the system architecture.</critical_rule>
+      
+      Output file location: `docs/infrastructure-architecture.md`
+
+  - id: infrastructure-overview
+    title: Infrastructure Overview
+    instruction: |
+      Review the product requirements document to understand business needs and scale requirements. Analyze the main system architecture to identify infrastructure dependencies. Document non-functional requirements (performance, scalability, reliability, security). Cross-reference with PRD Technical Assumptions to ensure alignment with repository and service architecture decisions.
+    elicit: true
+    custom_elicitation: infrastructure-overview
+    template: |
+      - Cloud Provider(s)
+      - Core Services & Resources
+      - Regional Architecture
+      - Multi-environment Strategy
+    examples:
+      - |
+        - **Cloud Provider:** AWS (primary), with multi-cloud capability for critical services
+        - **Core Services:** EKS for container orchestration, RDS for databases, S3 for storage, CloudFront for CDN
+        - **Regional Architecture:** Multi-region active-passive with primary in us-east-1, DR in us-west-2
+        - **Multi-environment Strategy:** Development, Staging, UAT, Production with identical infrastructure patterns
+
+  - id: iac
+    title: Infrastructure as Code (IaC)
+    instruction: Define IaC approach based on technical preferences and existing patterns. Consider team expertise, tooling ecosystem, and maintenance requirements.
+    template: |
+      - Tools & Frameworks
+      - Repository Structure
+      - State Management
+      - Dependency Management
+      
+      <critical_rule>All infrastructure must be defined as code. No manual resource creation in production environments.</critical_rule>
+
+  - id: environment-configuration
+    title: Environment Configuration
+    instruction: Design environment strategy that supports the development workflow while maintaining security and cost efficiency. Reference the Environment Transition Strategy section for promotion details.
+    template: |
+      - Environment Promotion Strategy
+      - Configuration Management
+      - Secret Management
+      - Feature Flag Integration
+    sections:
+      - id: environments
+        repeatable: true
+        title: "{{environment_name}} Environment"
+        template: |
+          - **Purpose:** {{environment_purpose}}
+          - **Resources:** {{environment_resources}}
+          - **Access Control:** {{environment_access}}
+          - **Data Classification:** {{environment_data_class}}
+
+  - id: environment-transition
+    title: Environment Transition Strategy
+    instruction: Detail the complete lifecycle of code and configuration changes from development to production. Include governance, testing gates, and rollback procedures.
+    template: |
+      - Development to Production Pipeline
+      - Deployment Stages and Gates
+      - Approval Workflows and Authorities
+      - Rollback Procedures
+      - Change Cadence and Release Windows
+      - Environment-Specific Configuration Management
+
+  - id: network-architecture
+    title: Network Architecture
+    instruction: |
+      Design network topology considering security zones, traffic patterns, and compliance requirements. Reference main architecture for service communication patterns.
+      
+      Create Mermaid diagram showing:
+      - VPC/Network structure
+      - Security zones and boundaries
+      - Traffic flow patterns
+      - Load balancer placement
+      - Service mesh topology (if applicable)
+    template: |
+      - VPC/VNET Design
+      - Subnet Strategy
+      - Security Groups & NACLs
+      - Load Balancers & API Gateways
+      - Service Mesh (if applicable)
+    sections:
+      - id: network-diagram
+        type: mermaid
+        mermaid_type: graph
+        template: |
+          graph TB
+              subgraph "Production VPC"
+                  subgraph "Public Subnets"
+                      ALB[Application Load Balancer]
+                  end
+                  subgraph "Private Subnets"
+                      EKS[EKS Cluster]
+                      RDS[(RDS Database)]
+                  end
+              end
+              Internet((Internet)) --> ALB
+              ALB --> EKS
+              EKS --> RDS
+      - id: service-mesh
+        title: Service Mesh Architecture
+        condition: Uses service mesh
+        template: |
+          - **Mesh Technology:** {{service_mesh_tech}}
+          - **Traffic Management:** {{traffic_policies}}
+          - **Security Policies:** {{mesh_security}}
+          - **Observability Integration:** {{mesh_observability}}
+
+  - id: compute-resources
+    title: Compute Resources
+    instruction: Select compute strategy based on application architecture (microservices, serverless, monolithic). Consider cost, scalability, and operational complexity.
+    template: |
+      - Container Strategy
+      - Serverless Architecture
+      - VM/Instance Configuration
+      - Auto-scaling Approach
+    sections:
+      - id: kubernetes
+        title: Kubernetes Architecture
+        condition: Uses Kubernetes
+        template: |
+          - **Cluster Configuration:** {{k8s_cluster_config}}
+          - **Node Groups:** {{k8s_node_groups}}
+          - **Networking:** {{k8s_networking}}
+          - **Storage Classes:** {{k8s_storage}}
+          - **Security Policies:** {{k8s_security}}
+
+  - id: data-resources
+    title: Data Resources
+    instruction: |
+      Design data infrastructure based on data architecture from main system design. Consider data volumes, access patterns, compliance, and recovery requirements.
+      
+      Create data flow diagram showing:
+      - Database topology
+      - Replication patterns
+      - Backup flows
+      - Data migration paths
+    template: |
+      - Database Deployment Strategy
+      - Backup & Recovery
+      - Replication & Failover
+      - Data Migration Strategy
+
+  - id: security-architecture
+    title: Security Architecture
+    instruction: Implement defense-in-depth strategy. Reference security requirements from PRD and compliance needs. Consider zero-trust principles where applicable.
+    template: |
+      - IAM & Authentication
+      - Network Security
+      - Data Encryption
+      - Compliance Controls
+      - Security Scanning & Monitoring
+      
+      <critical_rule>Apply principle of least privilege for all access controls. Document all security exceptions with business justification.</critical_rule>
+
+  - id: shared-responsibility
+    title: Shared Responsibility Model
+    instruction: Clearly define boundaries between cloud provider, platform team, development team, and security team responsibilities. This is critical for operational success.
+    template: |
+      - Cloud Provider Responsibilities
+      - Platform Team Responsibilities
+      - Development Team Responsibilities
+      - Security Team Responsibilities
+      - Operational Monitoring Ownership
+      - Incident Response Accountability Matrix
+    examples:
+      - |
+        | Component            | Cloud Provider | Platform Team | Dev Team       | Security Team |
+        | -------------------- | -------------- | ------------- | -------------- | ------------- |
+        | Physical Security    | ✓              | -             | -              | Audit         |
+        | Network Security     | Partial        | ✓             | Config         | Audit         |
+        | Application Security | -              | Tools         | ✓              | Review        |
+        | Data Encryption      | Engine         | Config        | Implementation | Standards     |
+
+  - id: monitoring-observability
+    title: Monitoring & Observability
+    instruction: Design comprehensive observability strategy covering metrics, logs, traces, and business KPIs. Ensure alignment with SLA/SLO requirements.
+    template: |
+      - Metrics Collection
+      - Logging Strategy
+      - Tracing Implementation
+      - Alerting & Incident Response
+      - Dashboards & Visualization
+
+  - id: cicd-pipeline
+    title: CI/CD Pipeline
+    instruction: |
+      Design deployment pipeline that balances speed with safety. Include progressive deployment strategies and automated quality gates.
+      
+      Create pipeline diagram showing:
+      - Build stages
+      - Test gates
+      - Deployment stages
+      - Approval points
+      - Rollback triggers
+    template: |
+      - Pipeline Architecture
+      - Build Process
+      - Deployment Strategy
+      - Rollback Procedures
+      - Approval Gates
+    sections:
+      - id: progressive-deployment
+        title: Progressive Deployment Strategy
+        condition: Uses progressive deployment
+        template: |
+          - **Canary Deployment:** {{canary_config}}
+          - **Blue-Green Deployment:** {{blue_green_config}}
+          - **Feature Flags:** {{feature_flag_integration}}
+          - **Traffic Splitting:** {{traffic_split_rules}}
+
+  - id: disaster-recovery
+    title: Disaster Recovery
+    instruction: Design DR strategy based on business continuity requirements. Define clear RTO/RPO targets and ensure they align with business needs.
+    template: |
+      - Backup Strategy
+      - Recovery Procedures
+      - RTO & RPO Targets
+      - DR Testing Approach
+      
+      <critical_rule>DR procedures must be tested at least quarterly. Document test results and improvement actions.</critical_rule>
+
+  - id: cost-optimization
+    title: Cost Optimization
+    instruction: Balance cost efficiency with performance and reliability requirements. Include both immediate optimizations and long-term strategies.
+    template: |
+      - Resource Sizing Strategy
+      - Reserved Instances/Commitments
+      - Cost Monitoring & Reporting
+      - Optimization Recommendations
+
+  - id: bmad-integration
+    title: BMad Integration Architecture
+    instruction: Design infrastructure to specifically support other BMad agents and their workflows. This ensures the infrastructure enables the entire BMad methodology.
+    sections:
+      - id: dev-agent-support
+        title: Development Agent Support
+        template: |
+          - Container platform for development environments
+          - GitOps workflows for application deployment
+          - Service mesh integration for development testing
+          - Developer self-service platform capabilities
+      - id: product-architecture-alignment
+        title: Product & Architecture Alignment
+        template: |
+          - Infrastructure implementing PRD scalability requirements
+          - Deployment automation supporting product iteration speed
+          - Service reliability meeting product SLAs
+          - Architecture patterns properly implemented in infrastructure
+      - id: cross-agent-integration
+        title: Cross-Agent Integration Points
+        template: |
+          - CI/CD pipelines supporting Frontend, Backend, and Full Stack development workflows
+          - Monitoring and observability data accessible to QA and DevOps agents
+          - Infrastructure enabling Design Architect's UI/UX performance requirements
+          - Platform supporting Analyst's data collection and analysis needs
+
+  - id: feasibility-review
+    title: DevOps/Platform Feasibility Review
+    instruction: |
+      CRITICAL STEP - Present architectural blueprint summary to DevOps/Platform Engineering Agent for feasibility review. Request specific feedback on:
+      
+      - **Operational Complexity:** Are the proposed patterns implementable with current tooling and expertise?
+      - **Resource Constraints:** Do infrastructure requirements align with available resources and budgets?
+      - **Security Implementation:** Are security patterns achievable with current security toolchain?
+      - **Operational Overhead:** Will the proposed architecture create excessive operational burden?
+      - **Technology Constraints:** Are selected technologies compatible with existing infrastructure?
+      
+      Document all feasibility feedback and concerns raised. Iterate on architectural decisions based on operational constraints and feedback.
+      
+      <critical_rule>Address all critical feasibility concerns before proceeding to final architecture documentation. If critical blockers identified, revise architecture before continuing.</critical_rule>
+    sections:
+      - id: feasibility-results
+        title: Feasibility Assessment Results
+        template: |
+          - **Green Light Items:** {{feasible_items}}
+          - **Yellow Light Items:** {{items_needing_adjustment}}
+          - **Red Light Items:** {{items_requiring_redesign}}
+          - **Mitigation Strategies:** {{mitigation_plans}}
+
+  - id: infrastructure-verification
+    title: Infrastructure Verification
+    sections:
+      - id: validation-framework
+        title: Validation Framework
+        content: |
+          This infrastructure architecture will be validated using the comprehensive `infrastructure-checklist.md`, with particular focus on Section 12: Architecture Documentation Validation. The checklist ensures:
+          
+          - Completeness of architecture documentation
+          - Consistency with broader system architecture
+          - Appropriate level of detail for different stakeholders
+          - Clear implementation guidance
+          - Future evolution considerations
+      - id: validation-process
+        title: Validation Process
+        content: |
+          The architecture documentation validation should be performed:
+          
+          - After initial architecture development
+          - After significant architecture changes
+          - Before major implementation phases
+          - During periodic architecture reviews
+          
+          The Platform Engineer should use the infrastructure checklist to systematically validate all aspects of this architecture document.
+
+  - id: implementation-handoff
+    title: Implementation Handoff
+    instruction: Create structured handoff documentation for implementation team. This ensures architecture decisions are properly communicated and implemented.
+    sections:
+      - id: adrs
+        title: Architecture Decision Records (ADRs)
+        content: |
+          Create ADRs for key infrastructure decisions:
+          
+          - Cloud provider selection rationale
+          - Container orchestration platform choice
+          - Networking architecture decisions
+          - Security implementation choices
+          - Cost optimization trade-offs
+      - id: implementation-validation
+        title: Implementation Validation Criteria
+        content: |
+          Define specific criteria for validating correct implementation:
+          
+          - Infrastructure as Code quality gates
+          - Security compliance checkpoints
+          - Performance benchmarks
+          - Cost targets
+          - Operational readiness criteria
+      - id: knowledge-transfer
+        title: Knowledge Transfer Requirements
+        template: |
+          - Technical documentation for operations team
+          - Runbook creation requirements
+          - Training needs for platform team
+          - Handoff meeting agenda items
+
+  - id: infrastructure-evolution
+    title: Infrastructure Evolution
+    instruction: Document the long-term vision and evolution path for the infrastructure. Consider technology trends, anticipated growth, and technical debt management.
+    template: |
+      - Technical Debt Inventory
+      - Planned Upgrades and Migrations
+      - Deprecation Schedule
+      - Technology Roadmap
+      - Capacity Planning
+      - Scalability Considerations
+
+  - id: app-integration
+    title: Integration with Application Architecture
+    instruction: Map infrastructure components to application services. Ensure infrastructure design supports application requirements and patterns defined in main architecture.
+    template: |
+      - Service-to-Infrastructure Mapping
+      - Application Dependency Matrix
+      - Performance Requirements Implementation
+      - Security Requirements Implementation
+      - Data Flow to Infrastructure Correlation
+      - API Gateway and Service Mesh Integration
+
+  - id: cross-team-collaboration
+    title: Cross-Team Collaboration
+    instruction: Define clear interfaces and communication patterns between teams. This section is critical for operational success and should include specific touchpoints and escalation paths.
+    template: |
+      - Platform Engineer and Developer Touchpoints
+      - Frontend/Backend Integration Requirements
+      - Product Requirements to Infrastructure Mapping
+      - Architecture Decision Impact Analysis
+      - Design Architect UI/UX Infrastructure Requirements
+      - Analyst Research Integration
+
+  - id: change-management
+    title: Infrastructure Change Management
+    instruction: Define structured process for infrastructure changes. Include risk assessment, testing requirements, and rollback procedures.
+    template: |
+      - Change Request Process
+      - Risk Assessment
+      - Testing Strategy
+      - Validation Procedures
+
+  - id: final-review
+    instruction: Final Review - Ensure all sections are complete and consistent. Verify feasibility review was conducted and all concerns addressed. Apply final validation against infrastructure checklist.
+    content: |
+      ---
+      
+      _Document Version: 1.0_
+      _Last Updated: {{current_date}}_
+      _Next Review: {{review_date}}_

expansion-packs/bmad-infrastructure-devops/templates/infrastructure-platform-from-arch-tmpl.yaml

@@ -0,0 +1,629 @@
+template:
+  id: infrastructure-platform-template-v2
+  name: Platform Infrastructure Implementation
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/platform-infrastructure/platform-implementation.md
+    title: "{{project_name}} Platform Infrastructure Implementation"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Platform Implementation Elicitation Actions"
+    sections:
+      - id: foundation-infrastructure
+        options:
+          - "Platform Layer Security Hardening - Additional security controls and compliance validation"
+          - "Performance Optimization - Network and resource optimization"
+          - "Operational Excellence Enhancement - Automation and monitoring improvements"
+          - "Platform Integration Validation - Verify foundation supports upper layers"
+          - "Developer Experience Analysis - Foundation impact on developer workflows"
+          - "Disaster Recovery Testing - Foundation resilience validation"
+          - "BMAD Workflow Integration - Cross-agent support verification"
+          - "Finalize and Proceed to Container Platform"
+
+sections:
+  - id: initial-setup
+    instruction: |
+      Initial Setup
+      
+      1. Replace {{project_name}} with the actual project name throughout the document
+      2. Gather and review required inputs:
+         - **Infrastructure Architecture Document** (Primary input - REQUIRED)
+         - Infrastructure Change Request (if applicable)
+         - Infrastructure Guidelines
+         - Technology Stack Document
+         - Infrastructure Checklist
+         - NOTE: If Infrastructure Architecture Document is missing, HALT and request: "I need the Infrastructure Architecture Document to proceed with platform implementation. This document defines the infrastructure design that we'll be implementing."
+      
+      3. Validate that the infrastructure architecture has been reviewed and approved
+      4. <critical_rule>All platform implementation must align with the approved infrastructure architecture. Any deviations require architect approval.</critical_rule>
+      
+      Output file location: `docs/platform-infrastructure/platform-implementation.md`
+
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide a high-level overview of the platform infrastructure being implemented, referencing the infrastructure architecture document's key decisions and requirements.
+    template: |
+      - Platform implementation scope and objectives
+      - Key architectural decisions being implemented
+      - Expected outcomes and benefits
+      - Timeline and milestones
+
+  - id: joint-planning
+    title: Joint Planning Session with Architect
+    instruction: Document the collaborative planning session between DevOps/Platform Engineer and Architect. This ensures alignment before implementation begins.
+    sections:
+      - id: architecture-alignment
+        title: Architecture Alignment Review
+        template: |
+          - Review of infrastructure architecture document
+          - Confirmation of design decisions
+          - Identification of any ambiguities or gaps
+          - Agreement on implementation approach
+      - id: implementation-strategy
+        title: Implementation Strategy Collaboration
+        template: |
+          - Platform layer sequencing
+          - Technology stack validation
+          - Integration approach between layers
+          - Testing and validation strategy
+      - id: risk-constraint
+        title: Risk & Constraint Discussion
+        template: |
+          - Technical risks and mitigation strategies
+          - Resource constraints and workarounds
+          - Timeline considerations
+          - Compliance and security requirements
+      - id: validation-planning
+        title: Implementation Validation Planning
+        template: |
+          - Success criteria for each platform layer
+          - Testing approach and acceptance criteria
+          - Rollback strategies
+          - Communication plan
+      - id: documentation-planning
+        title: Documentation & Knowledge Transfer Planning
+        template: |
+          - Documentation requirements
+          - Knowledge transfer approach
+          - Training needs identification
+          - Handoff procedures
+
+  - id: foundation-infrastructure
+    title: Foundation Infrastructure Layer
+    instruction: Implement the base infrastructure layer based on the infrastructure architecture. This forms the foundation for all platform services.
+    elicit: true
+    custom_elicitation: foundation-infrastructure
+    sections:
+      - id: cloud-provider-setup
+        title: Cloud Provider Setup
+        template: |
+          - Account/Subscription configuration
+          - Region selection and setup
+          - Resource group/organizational structure
+          - Cost management setup
+      - id: network-foundation
+        title: Network Foundation
+        type: code
+        language: hcl
+        template: |
+          # Example Terraform for VPC setup
+          module "vpc" {
+            source = "./modules/vpc"
+          
+            cidr_block = "{{vpc_cidr}}"
+            availability_zones = {{availability_zones}}
+            public_subnets = {{public_subnets}}
+            private_subnets = {{private_subnets}}
+          }
+      - id: security-foundation
+        title: Security Foundation
+        template: |
+          - IAM roles and policies
+          - Security groups and NACLs
+          - Encryption keys (KMS/Key Vault)
+          - Compliance controls
+      - id: core-services
+        title: Core Services
+        template: |
+          - DNS configuration
+          - Certificate management
+          - Logging infrastructure
+          - Monitoring foundation
+
+  - id: container-platform
+    title: Container Platform Implementation
+    instruction: Build the container orchestration platform on top of the foundation infrastructure, following the architecture's container strategy.
+    sections:
+      - id: kubernetes-setup
+        title: Kubernetes Cluster Setup
+        sections:
+          - id: eks-setup
+            condition: Uses EKS
+            type: code
+            language: bash
+            template: |
+              # EKS Cluster Configuration
+              eksctl create cluster \
+                --name {{cluster_name}} \
+                --region {{aws_region}} \
+                --nodegroup-name {{nodegroup_name}} \
+                --node-type {{instance_type}} \
+                --nodes {{node_count}}
+          - id: aks-setup
+            condition: Uses AKS
+            type: code
+            language: bash
+            template: |
+              # AKS Cluster Configuration
+              az aks create \
+                --resource-group {{resource_group}} \
+                --name {{cluster_name}} \
+                --node-count {{node_count}} \
+                --node-vm-size {{vm_size}} \
+                --network-plugin azure
+      - id: node-configuration
+        title: Node Configuration
+        template: |
+          - Node groups/pools setup
+          - Autoscaling configuration
+          - Node security hardening
+          - Resource quotas and limits
+      - id: cluster-services
+        title: Cluster Services
+        template: |
+          - CoreDNS configuration
+          - Ingress controller setup
+          - Certificate management
+          - Storage classes
+      - id: security-rbac
+        title: Security & RBAC
+        template: |
+          - RBAC policies
+          - Pod security policies/standards
+          - Network policies
+          - Secrets management
+
+  - id: gitops-workflow
+    title: GitOps Workflow Implementation
+    instruction: Implement GitOps patterns for declarative infrastructure and application management as defined in the architecture.
+    sections:
+      - id: gitops-tooling
+        title: GitOps Tooling Setup
+        sections:
+          - id: argocd-setup
+            condition: Uses ArgoCD
+            type: code
+            language: yaml
+            template: |
+              apiVersion: argoproj.io/v1alpha1
+              kind: Application
+              metadata:
+                name: argocd
+                namespace: argocd
+              spec:
+                source:
+                  repoURL: {{repo_url}}
+                  targetRevision: {{target_revision}}
+                  path: {{path}}
+          - id: flux-setup
+            condition: Uses Flux
+            type: code
+            language: yaml
+            template: |
+              apiVersion: source.toolkit.fluxcd.io/v1beta2
+              kind: GitRepository
+              metadata:
+                name: flux-system
+                namespace: flux-system
+              spec:
+                interval: 1m
+                ref:
+                  branch: {{branch}}
+                url: {{git_url}}
+      - id: repository-structure
+        title: Repository Structure
+        type: code
+        language: text
+        template: |
+          platform-gitops/
+             clusters/
+                production/
+                staging/
+                development/
+             infrastructure/
+                base/
+                overlays/
+             applications/
+                 base/
+                 overlays/
+      - id: deployment-workflows
+        title: Deployment Workflows
+        template: |
+          - Application deployment patterns
+          - Progressive delivery setup
+          - Rollback procedures
+          - Multi-environment promotion
+      - id: access-control
+        title: Access Control
+        template: |
+          - Git repository permissions
+          - GitOps tool RBAC
+          - Secret management integration
+          - Audit logging
+
+  - id: service-mesh
+    title: Service Mesh Implementation
+    instruction: Deploy service mesh for advanced traffic management, security, and observability as specified in the architecture.
+    sections:
+      - id: istio-mesh
+        title: Istio Service Mesh
+        condition: Uses Istio
+        sections:
+          - id: istio-install
+            type: code
+            language: bash
+            template: |
+              # Istio Installation
+              istioctl install --set profile={{istio_profile}} \
+                --set values.gateways.istio-ingressgateway.type={{ingress_type}}
+          - id: istio-config
+            template: |
+              - Control plane configuration
+              - Data plane injection
+              - Gateway configuration
+              - Observability integration
+      - id: linkerd-mesh
+        title: Linkerd Service Mesh
+        condition: Uses Linkerd
+        sections:
+          - id: linkerd-install
+            type: code
+            language: bash
+            template: |
+              # Linkerd Installation
+              linkerd install --cluster-name={{cluster_name}} | kubectl apply -f -
+              linkerd viz install | kubectl apply -f -
+          - id: linkerd-config
+            template: |
+              - Control plane setup
+              - Proxy injection
+              - Traffic policies
+              - Metrics collection
+      - id: traffic-management
+        title: Traffic Management
+        template: |
+          - Load balancing policies
+          - Circuit breakers
+          - Retry policies
+          - Canary deployments
+      - id: security-policies
+        title: Security Policies
+        template: |
+          - mTLS configuration
+          - Authorization policies
+          - Rate limiting
+          - Network segmentation
+
+  - id: developer-experience
+    title: Developer Experience Platform
+    instruction: Build the developer self-service platform to enable efficient development workflows as outlined in the architecture.
+    sections:
+      - id: developer-portal
+        title: Developer Portal
+        template: |
+          - Service catalog setup
+          - API documentation
+          - Self-service workflows
+          - Resource provisioning
+      - id: cicd-integration
+        title: CI/CD Integration
+        type: code
+        language: yaml
+        template: |
+          apiVersion: tekton.dev/v1beta1
+          kind: Pipeline
+          metadata:
+            name: platform-pipeline
+          spec:
+            tasks:
+              - name: build
+                taskRef:
+                  name: build-task
+              - name: test
+                taskRef:
+                  name: test-task
+              - name: deploy
+                taskRef:
+                  name: gitops-deploy
+      - id: development-tools
+        title: Development Tools
+        template: |
+          - Local development setup
+          - Remote development environments
+          - Testing frameworks
+          - Debugging tools
+      - id: self-service
+        title: Self-Service Capabilities
+        template: |
+          - Environment provisioning
+          - Database creation
+          - Feature flag management
+          - Configuration management
+
+  - id: platform-integration
+    title: Platform Integration & Security Hardening
+    instruction: Implement comprehensive platform-wide integration and security controls across all layers.
+    sections:
+      - id: end-to-end-security
+        title: End-to-End Security
+        template: |
+          - Platform-wide security policies
+          - Cross-layer authentication
+          - Encryption in transit and at rest
+          - Compliance validation
+      - id: integrated-monitoring
+        title: Integrated Monitoring
+        type: code
+        language: yaml
+        template: |
+          apiVersion: v1
+          kind: ConfigMap
+          metadata:
+            name: prometheus-config
+          data:
+            prometheus.yaml: |
+              global:
+                scrape_interval: {{scrape_interval}}
+              scrape_configs:
+                - job_name: 'kubernetes-pods'
+                  kubernetes_sd_configs:
+                    - role: pod
+      - id: platform-observability
+        title: Platform Observability
+        template: |
+          - Metrics aggregation
+          - Log collection and analysis
+          - Distributed tracing
+          - Dashboard creation
+      - id: backup-dr
+        title: Backup & Disaster Recovery
+        template: |
+          - Platform backup strategy
+          - Disaster recovery procedures
+          - RTO/RPO validation
+          - Recovery testing
+
+  - id: platform-operations
+    title: Platform Operations & Automation
+    instruction: Establish operational procedures and automation for platform management.
+    sections:
+      - id: monitoring-alerting
+        title: Monitoring & Alerting
+        template: |
+          - SLA/SLO monitoring
+          - Alert routing
+          - Incident response
+          - Performance baselines
+      - id: automation-framework
+        title: Automation Framework
+        type: code
+        language: yaml
+        template: |
+          apiVersion: operators.coreos.com/v1alpha1
+          kind: ClusterServiceVersion
+          metadata:
+            name: platform-operator
+          spec:
+            customresourcedefinitions:
+              owned:
+                - name: platformconfigs.platform.io
+                  version: v1alpha1
+      - id: maintenance-procedures
+        title: Maintenance Procedures
+        template: |
+          - Upgrade procedures
+          - Patch management
+          - Certificate rotation
+          - Capacity management
+      - id: operational-runbooks
+        title: Operational Runbooks
+        template: |
+          - Common operational tasks
+          - Troubleshooting guides
+          - Emergency procedures
+          - Recovery playbooks
+
+  - id: bmad-workflow-integration
+    title: BMAD Workflow Integration
+    instruction: Validate that the platform supports all BMAD agent workflows and cross-functional requirements.
+    sections:
+      - id: development-agent-support
+        title: Development Agent Support
+        template: |
+          - Frontend development workflows
+          - Backend development workflows
+          - Full-stack integration
+          - Local development experience
+      - id: iac-development
+        title: Infrastructure-as-Code Development
+        template: |
+          - IaC development workflows
+          - Testing frameworks
+          - Deployment automation
+          - Version control integration
+      - id: cross-agent-collaboration
+        title: Cross-Agent Collaboration
+        template: |
+          - Shared services access
+          - Communication patterns
+          - Data sharing mechanisms
+          - Security boundaries
+      - id: cicd-integration-workflow
+        title: CI/CD Integration
+        type: code
+        language: yaml
+        template: |
+          stages:
+            - analyze
+            - plan
+            - architect
+            - develop
+            - test
+            - deploy
+
+  - id: platform-validation
+    title: Platform Validation & Testing
+    instruction: Execute comprehensive validation to ensure the platform meets all requirements.
+    sections:
+      - id: functional-testing
+        title: Functional Testing
+        template: |
+          - Component testing
+          - Integration testing
+          - End-to-end testing
+          - Performance testing
+      - id: security-validation
+        title: Security Validation
+        template: |
+          - Penetration testing
+          - Compliance scanning
+          - Vulnerability assessment
+          - Access control validation
+      - id: dr-testing
+        title: Disaster Recovery Testing
+        template: |
+          - Backup restoration
+          - Failover procedures
+          - Recovery time validation
+          - Data integrity checks
+      - id: load-testing
+        title: Load Testing
+        type: code
+        language: typescript
+        template: |
+          // K6 Load Test Example
+          import http from 'k6/http';
+          import { check } from 'k6';
+          
+          export let options = {
+            stages: [
+              { duration: '5m', target: {{target_users}} },
+              { duration: '10m', target: {{target_users}} },
+              { duration: '5m', target: 0 },
+            ],
+          };
+
+  - id: knowledge-transfer
+    title: Knowledge Transfer & Documentation
+    instruction: Prepare comprehensive documentation and knowledge transfer materials.
+    sections:
+      - id: platform-documentation
+        title: Platform Documentation
+        template: |
+          - Architecture documentation
+          - Operational procedures
+          - Configuration reference
+          - API documentation
+      - id: training-materials
+        title: Training Materials
+        template: |
+          - Developer guides
+          - Operations training
+          - Security best practices
+          - Troubleshooting guides
+      - id: handoff-procedures
+        title: Handoff Procedures
+        template: |
+          - Team responsibilities
+          - Escalation procedures
+          - Support model
+          - Knowledge base
+
+  - id: implementation-review
+    title: Implementation Review with Architect
+    instruction: Document the post-implementation review session with the Architect to validate alignment and capture learnings.
+    sections:
+      - id: implementation-validation
+        title: Implementation Validation
+        template: |
+          - Architecture alignment verification
+          - Deviation documentation
+          - Performance validation
+          - Security review
+      - id: lessons-learned
+        title: Lessons Learned
+        template: |
+          - What went well
+          - Challenges encountered
+          - Process improvements
+          - Technical insights
+      - id: future-evolution
+        title: Future Evolution
+        template: |
+          - Enhancement opportunities
+          - Technical debt items
+          - Upgrade planning
+          - Capacity planning
+      - id: sign-off
+        title: Sign-off & Acceptance
+        template: |
+          - Architect approval
+          - Stakeholder acceptance
+          - Go-live authorization
+          - Support transition
+
+  - id: platform-metrics
+    title: Platform Metrics & KPIs
+    instruction: Define and implement key performance indicators for platform success measurement.
+    sections:
+      - id: technical-metrics
+        title: Technical Metrics
+        template: |
+          - Platform availability: {{availability_target}}
+          - Response time: {{response_time_target}}
+          - Resource utilization: {{utilization_target}}
+          - Error rates: {{error_rate_target}}
+      - id: business-metrics
+        title: Business Metrics
+        template: |
+          - Developer productivity
+          - Deployment frequency
+          - Lead time for changes
+          - Mean time to recovery
+      - id: operational-metrics
+        title: Operational Metrics
+        template: |
+          - Incident response time
+          - Patch compliance
+          - Cost per workload
+          - Resource efficiency
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: config-reference
+        title: A. Configuration Reference
+        instruction: Document all configuration parameters and their values used in the platform implementation.
+      - id: troubleshooting
+        title: B. Troubleshooting Guide
+        instruction: Provide common issues and their resolutions for platform operations.
+      - id: security-controls
+        title: C. Security Controls Matrix
+        instruction: Map implemented security controls to compliance requirements.
+      - id: integration-points
+        title: D. Integration Points
+        instruction: Document all integration points with external systems and services.
+
+  - id: final-review
+    instruction: Final Review - Ensure all platform layers are properly implemented, integrated, and documented. Verify that the implementation fully supports the BMAD methodology and all agent workflows. Confirm successful validation against the infrastructure checklist.
+    content: |
+      ---
+      
+      _Platform Version: 1.0_
+      _Implementation Date: {{implementation_date}}_
+      _Next Review: {{review_date}}_
+      _Approved by: {{architect_name}} (Architect), {{devops_name}} (DevOps/Platform Engineer)_

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "4.27.0",
+  "version": "4.27.2",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "4.27.0",
+      "version": "4.27.2",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.5.0",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.27.0",
+  "version": "4.27.2",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {

tools/builders/web-builder.js

@@ -211,6 +211,7 @@ These references map directly to bundle sections:
         parsed["activation-instructions"] = parsed["activation-instructions"].filter(
           (instruction) => {
             return (
+              typeof instruction === 'string' &&
               !instruction.startsWith("IDE-FILE-RESOLUTION:") &&
               !instruction.startsWith("REQUEST-RESOLUTION:")
             );
@@ -393,67 +394,57 @@ These references map directly to bundle sections:
             if (Array.isArray(resources)) {
               for (const resourceName of resources) {
                 let found = false;
-                const extensions = [".md", ".yaml"];
 
                 // Try expansion pack first
-                for (const ext of extensions) {
-                  const resourcePath = path.join(packDir, resourceType, `${resourceName}${ext}`);
-                  try {
-                    const resourceContent = await fs.readFile(resourcePath, "utf8");
-                    const resourceWebPath = this.convertToWebPath(resourcePath, packName);
-                    sections.push(
-                      this.formatSection(resourceWebPath, resourceContent, packName)
-                    );
-                    found = true;
-                    break;
-                  } catch (error) {
-                    // Not in expansion pack, continue
-                  }
+                const resourcePath = path.join(packDir, resourceType, resourceName);
+                try {
+                  const resourceContent = await fs.readFile(resourcePath, "utf8");
+                  const resourceWebPath = this.convertToWebPath(resourcePath, packName);
+                  sections.push(
+                    this.formatSection(resourceWebPath, resourceContent, packName)
+                  );
+                  found = true;
+                } catch (error) {
+                  // Not in expansion pack, continue
                 }
 
                 // If not found in expansion pack, try core
                 if (!found) {
-                  for (const ext of extensions) {
-                    const corePath = path.join(
-                      this.rootDir,
-                      "bmad-core",
-                      resourceType,
-                      `${resourceName}${ext}`
+                  const corePath = path.join(
+                    this.rootDir,
+                    "bmad-core",
+                    resourceType,
+                    resourceName
+                  );
+                  try {
+                    const coreContent = await fs.readFile(corePath, "utf8");
+                    const coreWebPath = this.convertToWebPath(corePath, packName);
+                    sections.push(
+                      this.formatSection(coreWebPath, coreContent, packName)
                     );
-                    try {
-                      const coreContent = await fs.readFile(corePath, "utf8");
-                      const coreWebPath = this.convertToWebPath(corePath, packName);
-                      sections.push(
-                        this.formatSection(coreWebPath, coreContent, packName)
-                      );
-                      found = true;
-                      break;
-                    } catch (error) {
-                      // Not in core either, continue
-                    }
+                    found = true;
+                  } catch (error) {
+                    // Not in core either, continue
                   }
                 }
 
                 // If not found in core, try common folder
                 if (!found) {
-                  for (const ext of extensions) {
-                    const commonPath = path.join(
-                      this.rootDir,
-                      "common",
-                      resourceType,
-                      `${resourceName}${ext}`
+                  const commonPath = path.join(
+                    this.rootDir,
+                    "common",
+                    resourceType,
+                    resourceName
+                  );
+                  try {
+                    const commonContent = await fs.readFile(commonPath, "utf8");
+                    const commonWebPath = this.convertToWebPath(commonPath, packName);
+                    sections.push(
+                      this.formatSection(commonWebPath, commonContent, packName)
                     );
-                    try {
-                      const commonContent = await fs.readFile(commonPath, "utf8");
-                      const commonWebPath = this.convertToWebPath(commonPath, packName);
-                      sections.push(
-                        this.formatSection(commonWebPath, commonContent, packName)
-                      );
-                      found = true;
-                      break;
-                    } catch (error) {
-                      // Not in common either, continue
-                    }
+                    found = true;
+                  } catch (error) {
+                    // Not in common either, continue
                   }
                 }
 
@@ -509,8 +500,7 @@ These references map directly to bundle sections:
         for (const resourceFile of resourceFiles.filter(
           (f) => f.endsWith(".md") || f.endsWith(".yaml")
         )) {
-          const fileName = resourceFile.replace(/\.(md|yaml)$/, "");
-          expansionResources.set(`${resourceDir}#${fileName}`, true);
+          expansionResources.set(`${resourceDir}#${resourceFile}`, true);
         }
       } catch (error) {
         // Directory might not exist, that's fine
@@ -597,55 +587,45 @@ These references map directly to bundle sections:
     // Always prefer expansion pack versions if they exist
     for (const [key, dep] of allDependencies) {
       let found = false;
-      const extensions = [".md", ".yaml"];
 
       // Always check expansion pack first, even if the dependency came from a core agent
       if (expansionResources.has(key)) {
         // We know it exists in expansion pack, find and load it
-        for (const ext of extensions) {
-          const expansionPath = path.join(packDir, dep.type, `${dep.name}${ext}`);
-          try {
-            const content = await fs.readFile(expansionPath, "utf8");
-            const expansionWebPath = this.convertToWebPath(expansionPath, packName);
-            sections.push(this.formatSection(expansionWebPath, content, packName));
-            console.log(`      ✓ Using expansion override for ${key}`);
-            found = true;
-            break;
-          } catch (error) {
-            // Try next extension
-          }
+        const expansionPath = path.join(packDir, dep.type, dep.name);
+        try {
+          const content = await fs.readFile(expansionPath, "utf8");
+          const expansionWebPath = this.convertToWebPath(expansionPath, packName);
+          sections.push(this.formatSection(expansionWebPath, content, packName));
+          console.log(`      ✓ Using expansion override for ${key}`);
+          found = true;
+        } catch (error) {
+          // Try next extension
         }
       }
 
       // If not found in expansion pack (or doesn't exist there), try core
       if (!found) {
-        for (const ext of extensions) {
-          const corePath = path.join(this.rootDir, "bmad-core", dep.type, `${dep.name}${ext}`);
-          try {
-            const content = await fs.readFile(corePath, "utf8");
-            const coreWebPath = this.convertToWebPath(corePath, packName);
-            sections.push(this.formatSection(coreWebPath, content, packName));
-            found = true;
-            break;
-          } catch (error) {
-            // Not in core either, continue
-          }
+        const corePath = path.join(this.rootDir, "bmad-core", dep.type, dep.name);
+        try {
+          const content = await fs.readFile(corePath, "utf8");
+          const coreWebPath = this.convertToWebPath(corePath, packName);
+          sections.push(this.formatSection(coreWebPath, content, packName));
+          found = true;
+        } catch (error) {
+          // Not in core either, continue
         }
       }
 
       // If not found in core, try common folder
       if (!found) {
-        for (const ext of extensions) {
-          const commonPath = path.join(this.rootDir, "common", dep.type, `${dep.name}${ext}`);
-          try {
-            const content = await fs.readFile(commonPath, "utf8");
-            const commonWebPath = this.convertToWebPath(commonPath, packName);
-            sections.push(this.formatSection(commonWebPath, content, packName));
-            found = true;
-            break;
-          } catch (error) {
-            // Not in common either, continue
-          }
+        const commonPath = path.join(this.rootDir, "common", dep.type, dep.name);
+        try {
+          const content = await fs.readFile(commonPath, "utf8");
+          const commonWebPath = this.convertToWebPath(commonPath, packName);
+          sections.push(this.formatSection(commonWebPath, content, packName));
+          found = true;
+        } catch (error) {
+          // Not in common either, continue
         }
       }
 

tools/installer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.27.0",
+  "version": "4.27.2",
   "description": "BMad Method installer - AI-powered Agile development framework",
   "main": "lib/installer.js",
   "bin": {

tools/lib/dependency-resolver.js

@@ -116,31 +116,20 @@ class DependencyResolver {
     }
 
     try {
-      const extensions = ['.md', '.yaml'];
       let content = null;
       let filePath = null;
 
       // First try bmad-core
-      for (const ext of extensions) {
+      try {
+        filePath = path.join(this.bmadCore, type, id);
+        content = await fs.readFile(filePath, 'utf8');
+      } catch (e) {
+        // If not found in bmad-core, try common folder
         try {
-          filePath = path.join(this.bmadCore, type, `${id}${ext}`);
+          filePath = path.join(this.common, type, id);
           content = await fs.readFile(filePath, 'utf8');
-          break;
-        } catch (e) {
-          // Try next extension
-        }
-      }
-      
-      // If not found in bmad-core, try common folder
-      if (!content) {
-        for (const ext of extensions) {
-          try {
-            filePath = path.join(this.common, type, `${id}${ext}`);
-            content = await fs.readFile(filePath, 'utf8');
-            break;
-          } catch (e) {
-            // Try next extension
-          }
+        } catch (e2) {
+          // File not found in either location
         }
       }
 

zoo/docs/architecture.md

@@ -0,0 +1,812 @@
+# TermTodo Architecture Document
+
+## Introduction
+
+This document outlines the overall project architecture for TermTodo, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
+
+**Relationship to Frontend Architecture:**
+If the project includes a significant user interface, a separate Frontend Architecture Document will detail the frontend-specific design and MUST be used in conjunction with this document. Core technology stack choices documented herein (see "Tech Stack") are definitive for the entire project, including any frontend components.
+
+### Starter Template or Existing Project
+
+N/A - This is a greenfield Rust CLI project with no starter template.
+
+### Change Log
+
+| Date       | Version | Description                                | Author              |
+| ---------- | ------- | ------------------------------------------ | ------------------- |
+| 2025-07-07 | 1.0     | Initial architecture based on TermTodo PRD | Winston (Architect) |
+
+## High Level Architecture
+
+### Technical Summary
+
+TermTodo is a monolithic, single-binary CLI application built with Rust, utilizing embedded SQLite for ACID-compliant local storage. The architecture employs clean architecture principles with clear separation between CLI parsing, business logic, and data persistence layers. Performance-critical design choices including synchronous execution, prepared statement caching, and minimal dependencies ensure sub-100ms command execution. The system implements repository and command patterns to maintain testability while delivering a zero-configuration tool that integrates seamlessly into developer workflows.
+
+### High Level Overview
+
+**Architectural Style:** Monolithic Single Binary
+
+- All functionality compiled into one executable for instant startup
+- No network dependencies or service discovery overhead
+- Embedded SQLite database with local file storage
+
+**Repository Structure:** Monorepo
+
+- Single repository containing all code, tests, and documentation
+- Simplified dependency management and atomic commits
+- Unified CI/CD pipeline for all components
+
+**Service Architecture:** Monolith
+
+- Single process handling all operations
+- Synchronous execution model (no async runtime needed)
+- Direct database access without network layers
+
+**Primary Data Flow:**
+
+1. User invokes `todo` command with arguments
+2. CLI parser validates and routes to appropriate command handler
+3. Command handler orchestrates business logic operations
+4. Repository layer manages SQLite transactions
+5. Formatted output returned to terminal
+
+**Key Architectural Decisions:**
+
+- **Synchronous Model**: Eliminates async runtime overhead for faster cold starts
+- **Embedded Database**: Zero configuration, portable data storage
+- **Static Linking**: Single binary distribution with no runtime dependencies
+- **Clean Architecture**: Testable layers despite monolithic structure
+
+### High Level Project Diagram
+
+```mermaid
+graph TB
+    User[Terminal User]
+
+    subgraph "TermTodo Binary"
+        CLI[CLI Parser<br/>clap v4]
+        CMD[Command Handlers]
+        BL[Business Logic]
+        REPO[Repository Layer]
+        DB[(SQLite DB)]
+        CONFIG[Config Manager<br/>TOML]
+    end
+
+    subgraph "File System"
+        DBFILE[todo.db]
+        CFGFILE[config.toml]
+    end
+
+    User -->|todo add/list/etc| CLI
+    CLI -->|Parsed Commands| CMD
+    CMD -->|Operations| BL
+    BL -->|Data Access| REPO
+    REPO -->|SQL| DB
+    DB -.->|File I/O| DBFILE
+    CONFIG -.->|Read/Write| CFGFILE
+
+    style User fill:#e1f5fe
+    style CLI fill:#fff3e0
+    style CMD fill:#fff3e0
+    style BL fill:#f3e5f5
+    style REPO fill:#e8f5e9
+    style DB fill:#e8f5e9
+```
+
+### Architectural and Design Patterns
+
+- **Clean Architecture:** Separation of concerns with CLI, Application, Domain, and Infrastructure layers - _Rationale:_ Enables 80%+ test coverage requirement by isolating business logic from I/O operations
+
+- **Repository Pattern:** Abstract SQLite operations behind trait-based interfaces - _Rationale:_ Allows in-memory repositories for unit tests and potential future database migrations
+
+- **Command Pattern:** Each CLI subcommand as a discrete handler with execute method - _Rationale:_ Simplifies testing and follows clap's natural structure for maintainable command routing
+
+- **Builder Pattern:** Fluent interfaces for constructing complex queries and task filters - _Rationale:_ Provides readable API for combining multiple filter criteria while maintaining performance
+
+- **Result/Option Monads:** Explicit error handling using Rust's type system - _Rationale:_ Prevents runtime panics and enables graceful error messages as required by NFR13
+
+## Tech Stack
+
+This is the DEFINITIVE technology selection for TermTodo. All implementation must use these exact versions and technologies.
+
+### Cloud Infrastructure
+
+- **Provider:** Local-only (No cloud requirements)
+- **Key Services:** N/A
+- **Deployment Regions:** N/A
+
+### Technology Stack Table
+
+| Category               | Technology     | Version | Purpose                       | Rationale                                                                 |
+| ---------------------- | -------------- | ------- | ----------------------------- | ------------------------------------------------------------------------- |
+| **Language**           | Rust           | 1.78.0  | Primary development language  | Zero-cost abstractions, memory safety, single binary output               |
+| **Database**           | SQLite         | 3.45.0  | Embedded database             | ACID compliance, zero configuration, excellent performance                |
+| **CLI Framework**      | clap           | 4.5.4   | Command-line argument parsing | Automatic help generation, shell completion, strong typing                |
+| **ORM/Query Builder**  | sqlx           | 0.7.4   | Database operations           | Compile-time checked queries, async support (if needed later), migrations |
+| **Date Parsing**       | chrono         | 0.4.38  | Date/time handling            | Comprehensive timezone support, widely adopted                            |
+| **Human Date Parsing** | chrono-english | 0.1.7   | Natural language dates        | Parses "tomorrow", "next friday" as required                              |
+| **Serialization**      | serde          | 1.0.197 | JSON/CSV export               | De facto standard, excellent performance                                  |
+| **Configuration**      | toml           | 0.8.12  | Config file parsing           | Human-readable, simple for users                                          |
+| **Terminal Colors**    | termcolor      | 1.4.1   | Colored output                | Respects NO_COLOR, cross-platform                                         |
+| **Error Handling**     | anyhow         | 1.0.82  | Application errors            | Simplified error handling with context                                    |
+| **Error Types**        | thiserror      | 1.0.58  | Custom error types            | Derive macro for error enums                                              |
+| **Testing**            | built-in       | std     | Unit/integration tests        | Rust's excellent built-in test framework                                  |
+| **Benchmarking**       | criterion      | 0.5.1   | Performance testing           | Statistical benchmarking for CI regression detection                      |
+| **Logging**            | env_logger     | 0.11.3  | Debug logging                 | Simple, runtime-configurable via RUST_LOG                                 |
+
+## Data Models
+
+### Task
+
+**Purpose:** Core entity representing a single todo item with all associated metadata
+
+**Key Attributes:**
+
+- `id`: i64 - Unique identifier (SQLite ROWID)
+- `description`: String - Task description (up to 1000 chars)
+- `status`: TaskStatus - Enum (Incomplete/Complete)
+- `project`: Option<String> - Optional project grouping
+- `priority`: Priority - Enum (High/Medium/Low), defaults to Medium
+- `due_date`: Option<DateTime> - Optional due date with timezone
+- `created_at`: DateTime - Creation timestamp
+- `updated_at`: DateTime - Last modification timestamp
+- `completed_at`: Option<DateTime> - Completion timestamp
+
+**Relationships:**
+
+- Has many Tags (many-to-many via task_tags table)
+- Belongs to one Project (denormalized for performance)
+
+### Tag
+
+**Purpose:** Flexible categorization system for tasks
+
+**Key Attributes:**
+
+- `id`: i64 - Unique identifier
+- `name`: String - Tag name (alphanumeric + dash/underscore)
+- `created_at`: DateTime - First use timestamp
+
+**Relationships:**
+
+- Has many Tasks (many-to-many via task_tags table)
+- Cascade delete orphaned tags
+
+### TaskTag
+
+**Purpose:** Junction table for many-to-many task-tag relationship
+
+**Key Attributes:**
+
+- `task_id`: i64 - Foreign key to tasks
+- `tag_id`: i64 - Foreign key to tags
+
+**Relationships:**
+
+- Composite primary key (task_id, tag_id)
+- ON DELETE CASCADE for both foreign keys
+
+## Components
+
+### CLI Parser
+
+**Responsibility:** Parse command-line arguments, validate inputs, and route to appropriate command handlers
+
+**Key Interfaces:**
+
+- `parse_args()` - Main entry point parsing std::env::args()
+- `generate_completions()` - Shell completion script generation
+- Subcommand routing to handlers
+
+**Dependencies:** clap v4 for parsing, command handlers for execution
+
+**Technology Stack:** Pure Rust with clap derive macros for type-safe parsing
+
+### Command Handlers
+
+**Responsibility:** Orchestrate business logic for each CLI subcommand (add, list, complete, etc.)
+
+**Key Interfaces:**
+
+- `execute(&self, app: &Application) -> Result<()>` - Common trait for all commands
+- Command-specific structs with validated parameters
+- Output formatting for terminal display
+
+**Dependencies:** Application service layer, terminal output formatters
+
+**Technology Stack:** Rust structs implementing Command trait, termcolor for output
+
+### Application Service
+
+**Responsibility:** Core business logic and workflow orchestration independent of I/O concerns
+
+**Key Interfaces:**
+
+- `add_task(desc: &str, opts: AddOptions) -> Result<Task>`
+- `list_tasks(filters: FilterOptions) -> Result<Vec<Task>>`
+- `complete_tasks(ids: &[i64]) -> Result<usize>`
+- `search_tasks(query: &str) -> Result<Vec<Task>>`
+
+**Dependencies:** Repository interfaces (traits), domain models
+
+**Technology Stack:** Pure Rust business logic with Result-based error handling
+
+### Repository Layer
+
+**Responsibility:** Abstract data persistence operations with SQLite implementation
+
+**Key Interfaces:**
+
+- `TaskRepository` trait with CRUD operations
+- `TagRepository` trait for tag management
+- `Transaction` support for atomic operations
+- Migration runner for schema updates
+
+**Dependencies:** sqlx for database access, domain models
+
+**Technology Stack:** sqlx with compile-time checked queries, connection pooling
+
+### Configuration Manager
+
+**Responsibility:** Load, validate, and provide access to user configuration
+
+**Key Interfaces:**
+
+- `load_config() -> Result<Config>` - Load from XDG directory
+- `save_config(&Config) -> Result<()>` - Persist changes
+- `get_default_project()` - Typed config access
+
+**Dependencies:** toml for parsing, serde for serialization
+
+**Technology Stack:** TOML files with serde deserialization
+
+### Database Manager
+
+**Responsibility:** SQLite connection lifecycle, migrations, and performance optimization
+
+**Key Interfaces:**
+
+- `connect() -> Result<SqlitePool>` - Initialize connection pool
+- `run_migrations() -> Result<()>` - Apply schema updates
+- Prepared statement caching
+- PRAGMA optimizations
+
+**Dependencies:** sqlx SQLite driver, migration files
+
+**Technology Stack:** SQLite with WAL mode, connection pool size of 1
+
+### Component Diagram
+
+```mermaid
+graph LR
+    subgraph "Presentation Layer"
+        CLI[CLI Parser]
+        FMT[Output Formatter]
+    end
+
+    subgraph "Application Layer"
+        CMD[Command Handlers]
+        APP[Application Service]
+    end
+
+    subgraph "Domain Layer"
+        MODELS[Domain Models]
+        TRAITS[Repository Traits]
+    end
+
+    subgraph "Infrastructure Layer"
+        REPO[SQLite Repository]
+        CONFIG[Config Manager]
+        DB[Database Manager]
+    end
+
+    CLI --> CMD
+    CMD --> APP
+    CMD --> FMT
+    APP --> TRAITS
+    TRAITS --> REPO
+    REPO --> DB
+    APP --> MODELS
+    CONFIG --> APP
+
+    style CLI fill:#fff3e0
+    style CMD fill:#fff3e0
+    style APP fill:#f3e5f5
+    style REPO fill:#e8f5e9
+    style DB fill:#e8f5e9
+```
+
+## External APIs
+
+This project does not require any external API integrations. All operations are performed locally with no network dependencies.
+
+## Core Workflows
+
+### Add Task Workflow
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant CLI
+    participant CMD as AddCommand
+    participant APP as Application
+    participant REPO as Repository
+    participant DB as SQLite
+
+    User->>CLI: todo add "Review PR" -p work -P high +review
+    CLI->>CMD: parse_add_command()
+    CMD->>CMD: validate_description_length()
+    CMD->>APP: add_task(desc, options)
+    APP->>APP: parse_tags_from_description()
+    APP->>REPO: begin_transaction()
+    REPO->>DB: BEGIN TRANSACTION
+    APP->>REPO: insert_task(task)
+    REPO->>DB: INSERT INTO tasks...
+    DB-->>REPO: task_id = 42
+    APP->>REPO: insert_tags(task_id, tags)
+    REPO->>DB: INSERT INTO tags...
+    REPO->>DB: INSERT INTO task_tags...
+    APP->>REPO: commit()
+    REPO->>DB: COMMIT
+    APP-->>CMD: Task { id: 42, ... }
+    CMD->>User: ✓ Added task #42
+```
+
+### List Tasks with Filters Workflow
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant CLI
+    participant CMD as ListCommand
+    participant APP as Application
+    participant REPO as Repository
+    participant DB as SQLite
+    participant FMT as Formatter
+
+    User->>CLI: todo list -p work -P high --due
+    CLI->>CMD: parse_list_command()
+    CMD->>APP: list_tasks(filters)
+    APP->>REPO: find_tasks_with_filters(filters)
+    REPO->>REPO: build_query_with_filters()
+    REPO->>DB: SELECT ... WHERE project=? AND priority=? AND due_date IS NOT NULL
+    DB-->>REPO: Vec<TaskRow>
+    REPO->>REPO: load_tags_for_tasks(task_ids)
+    REPO->>DB: SELECT ... FROM task_tags WHERE task_id IN (...)
+    DB-->>REPO: Vec<TagRow>
+    REPO-->>APP: Vec<Task>
+    APP-->>CMD: Vec<Task>
+    CMD->>FMT: format_task_list(tasks)
+    FMT->>User: ID  Description           Project  Priority  Due        Tags<br/>42  Review PR            work     !!!       tomorrow   #review
+```
+
+### Complete Task with Toggle Workflow
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant CLI
+    participant CMD as CompleteCommand
+    participant APP as Application
+    participant REPO as Repository
+    participant DB as SQLite
+
+    User->>CLI: todo complete 42 43
+    CLI->>CMD: parse_complete_command()
+    CMD->>APP: complete_tasks([42, 43])
+
+    loop For each task_id
+        APP->>REPO: find_task_by_id(task_id)
+        REPO->>DB: SELECT ... WHERE id = ?
+        DB-->>REPO: Task
+
+        alt Task exists
+            APP->>APP: toggle_status(task)
+            APP->>REPO: update_task_status(id, new_status)
+            REPO->>DB: UPDATE tasks SET status=?, completed_at=?
+            DB-->>REPO: 1 row affected
+        else Task not found
+            APP->>APP: record_error(task_id)
+        end
+    end
+
+    APP-->>CMD: CompletionResult { success: 2, failed: 0 }
+    CMD->>User: ✓ Completed tasks: #42, #43
+```
+
+## Database Schema
+
+```sql
+-- Enable foreign key constraints
+PRAGMA foreign_keys = ON;
+
+-- Enable Write-Ahead Logging for better concurrency
+PRAGMA journal_mode = WAL;
+
+-- Optimize for fast reads
+PRAGMA synchronous = NORMAL;
+PRAGMA temp_store = MEMORY;
+PRAGMA mmap_size = 30000000000;
+
+-- Tasks table: Core entity
+CREATE TABLE tasks (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    description TEXT NOT NULL CHECK(length(description) <= 1000),
+    status TEXT NOT NULL DEFAULT 'incomplete' CHECK(status IN ('incomplete', 'complete')),
+    project TEXT,
+    priority TEXT NOT NULL DEFAULT 'medium' CHECK(priority IN ('high', 'medium', 'low')),
+    due_date DATETIME,
+    created_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    updated_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    completed_at DATETIME
+);
+
+-- Indexes for common query patterns
+CREATE INDEX idx_tasks_status ON tasks(status);
+CREATE INDEX idx_tasks_project ON tasks(project) WHERE project IS NOT NULL;
+CREATE INDEX idx_tasks_priority ON tasks(priority);
+CREATE INDEX idx_tasks_due_date ON tasks(due_date) WHERE due_date IS NOT NULL;
+CREATE INDEX idx_tasks_created_at ON tasks(created_at);
+
+-- Composite index for common filter combinations
+CREATE INDEX idx_tasks_filters ON tasks(status, project, priority);
+
+-- Tags table
+CREATE TABLE tags (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    name TEXT NOT NULL UNIQUE CHECK(name REGEXP '^[a-zA-Z0-9][a-zA-Z0-9_-]*$'),
+    created_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
+);
+
+-- Junction table for many-to-many relationship
+CREATE TABLE task_tags (
+    task_id INTEGER NOT NULL,
+    tag_id INTEGER NOT NULL,
+    PRIMARY KEY (task_id, tag_id),
+    FOREIGN KEY (task_id) REFERENCES tasks(id) ON DELETE CASCADE,
+    FOREIGN KEY (tag_id) REFERENCES tags(id) ON DELETE CASCADE
+);
+
+-- Index for tag lookups
+CREATE INDEX idx_task_tags_tag_id ON task_tags(tag_id);
+
+-- Full-text search virtual table
+CREATE VIRTUAL TABLE tasks_fts USING fts5(
+    description,
+    project,
+    content=tasks,
+    content_rowid=id
+);
+
+-- Triggers to keep FTS index in sync
+CREATE TRIGGER tasks_fts_insert AFTER INSERT ON tasks
+BEGIN
+    INSERT INTO tasks_fts(rowid, description, project)
+    VALUES (new.id, new.description, new.project);
+END;
+
+CREATE TRIGGER tasks_fts_update AFTER UPDATE ON tasks
+BEGIN
+    UPDATE tasks_fts
+    SET description = new.description, project = new.project
+    WHERE rowid = old.id;
+END;
+
+CREATE TRIGGER tasks_fts_delete AFTER DELETE ON tasks
+BEGIN
+    DELETE FROM tasks_fts WHERE rowid = old.id;
+END;
+
+-- Update trigger for updated_at timestamp
+CREATE TRIGGER tasks_update_timestamp AFTER UPDATE ON tasks
+BEGIN
+    UPDATE tasks SET updated_at = CURRENT_TIMESTAMP WHERE id = NEW.id;
+END;
+
+-- Migration tracking table
+CREATE TABLE IF NOT EXISTS schema_migrations (
+    version INTEGER PRIMARY KEY,
+    applied_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
+);
+```
+
+## Source Tree
+
+```plaintext
+termtodo/
+├── Cargo.toml                 # Project manifest with dependencies
+├── Cargo.lock                # Locked dependency versions
+├── build.rs                   # Build script for embedding resources
+├── .github/
+│   └── workflows/
+│       ├── ci.yml            # Test, lint, build on all platforms
+│       └── release.yml       # Build and publish binaries on tag
+├── src/
+│   ├── main.rs              # Entry point, CLI setup
+│   ├── cli/
+│   │   ├── mod.rs           # CLI module exports
+│   │   ├── parser.rs        # Clap command definitions
+│   │   ├── commands/        # Command handlers
+│   │   │   ├── mod.rs
+│   │   │   ├── add.rs       # Add command implementation
+│   │   │   ├── list.rs      # List command with formatting
+│   │   │   ├── complete.rs  # Complete/uncomplete logic
+│   │   │   ├── delete.rs    # Delete command
+│   │   │   ├── search.rs    # Full-text search
+│   │   │   └── config.rs    # Config management commands
+│   │   └── output.rs        # Terminal output formatting
+│   ├── app/
+│   │   ├── mod.rs           # Application layer exports
+│   │   ├── service.rs       # Main application service
+│   │   ├── filters.rs       # Filter builder and logic
+│   │   └── errors.rs        # Application error types
+│   ├── domain/
+│   │   ├── mod.rs           # Domain model exports
+│   │   ├── task.rs          # Task entity and value objects
+│   │   ├── tag.rs           # Tag entity
+│   │   └── types.rs         # Enums (Status, Priority)
+│   ├── infra/
+│   │   ├── mod.rs           # Infrastructure exports
+│   │   ├── db/
+│   │   │   ├── mod.rs       # Database module
+│   │   │   ├── connection.rs # Connection pool setup
+│   │   │   ├── migrations.rs # Migration runner
+│   │   │   └── queries.rs   # SQL query constants
+│   │   ├── repos/
+│   │   │   ├── mod.rs       # Repository traits
+│   │   │   ├── task_repo.rs # Task repository impl
+│   │   │   └── tag_repo.rs  # Tag repository impl
+│   │   └── config/
+│   │       ├── mod.rs       # Config module
+│   │       └── manager.rs   # Config file handling
+│   └── utils/
+│       ├── mod.rs           # Utility exports
+│       ├── dates.rs         # Date parsing helpers
+│       └── result.rs        # Result extensions
+├── tests/
+│   ├── integration/         # Integration tests
+│   │   ├── cli_tests.rs     # End-to-end CLI tests
+│   │   ├── db_tests.rs      # Database integration
+│   │   └── helpers/         # Test utilities
+│   └── fixtures/            # Test data files
+├── benches/
+│   └── performance.rs       # Criterion benchmarks
+├── migrations/              # SQL migration files
+│   ├── 001_initial.sql
+│   └── 002_add_fts.sql
+└── docs/
+    ├── architecture.md      # This document
+    ├── prd.md              # Product requirements
+    └── README.md           # User documentation
+```
+
+## Infrastructure and Deployment
+
+### Infrastructure as Code
+
+- **Tool:** Not applicable (local application)
+- **Location:** N/A
+- **Approach:** Single binary deployment
+
+### Deployment Strategy
+
+- **Strategy:** Direct binary distribution
+- **CI/CD Platform:** GitHub Actions
+- **Pipeline Configuration:** `.github/workflows/release.yml`
+
+### Environments
+
+- **Development:** Local developer machine with debug builds
+- **Testing:** CI environment with all platforms (Linux, macOS, Windows)
+- **Production:** User's local machine with release binary
+
+### Environment Promotion Flow
+
+```text
+Development (local) -> CI Testing -> GitHub Release -> User Installation
+                         ↓
+                    Failed tests
+                         ↓
+                    Fix & retry
+```
+
+### Rollback Strategy
+
+- **Primary Method:** Previous version binary installation
+- **Trigger Conditions:** User-reported critical bugs, data corruption
+- **Recovery Time Objective:** < 5 minutes (download previous release)
+
+## Error Handling Strategy
+
+### General Approach
+
+- **Error Model:** Result<T, Error> for all fallible operations
+- **Exception Hierarchy:** anyhow::Error for applications, custom types for libraries
+- **Error Propagation:** ? operator with context via .context()
+
+### Logging Standards
+
+- **Library:** env_logger 0.11.3
+- **Format:** `[TIMESTAMP] [LEVEL] [MODULE] Message`
+- **Levels:** ERROR, WARN, INFO, DEBUG, TRACE
+- **Required Context:**
+  - Correlation ID: Not needed (single-user CLI)
+  - Service Context: Module path automatically included
+  - User Context: Never log user data or task content
+
+### Error Handling Patterns
+
+#### External API Errors
+
+- **Retry Policy:** No external APIs
+- **Circuit Breaker:** Not applicable
+- **Timeout Configuration:** Not applicable
+- **Error Translation:** Not applicable
+
+#### Business Logic Errors
+
+- **Custom Exceptions:**
+  - `TaskNotFound(id)`
+  - `InvalidTaskDescription(reason)`
+  - `DuplicateTag(name)`
+  - `ConfigError(path, reason)`
+- **User-Facing Errors:** Clear, actionable messages via Display trait
+- **Error Codes:** Not used - descriptive messages preferred
+
+#### Data Consistency
+
+- **Transaction Strategy:** Explicit transactions for multi-table operations
+- **Compensation Logic:** Not needed with ACID SQLite
+- **Idempotency:** Complete/uncomplete operations are naturally idempotent
+
+## Coding Standards
+
+These standards are MANDATORY for AI agents and define project-specific conventions.
+
+### Core Standards
+
+- **Languages & Runtimes:** Rust 1.78.0 (edition 2021)
+- **Style & Linting:** rustfmt with default config, clippy with pedantic lints
+- **Test Organization:** Unit tests in `#[cfg(test)]` modules, integration tests in tests/
+
+### Naming Conventions
+
+| Element   | Convention      | Example               |
+| --------- | --------------- | --------------------- |
+| Structs   | PascalCase      | `TaskFilter`          |
+| Functions | snake_case      | `parse_due_date`      |
+| Constants | SCREAMING_SNAKE | `MAX_DESCRIPTION_LEN` |
+| Modules   | snake_case      | `task_repo`           |
+
+### Critical Rules
+
+- **No unwrap() in production code:** Use expect() with clear message or proper error handling
+- **All public functions must have doc comments:** Include examples for complex APIs
+- **SQL queries must use parameterized statements:** Never concatenate user input
+- **Benchmark new features:** Add criterion benchmarks for any performance-critical code
+- **Check Task description length:** Enforce 1000 character limit at CLI parsing layer
+
+## Test Strategy and Standards
+
+### Testing Philosophy
+
+- **Approach:** Test-after development with comprehensive coverage
+- **Coverage Goals:** 80% overall, 90% for business logic
+- **Test Pyramid:** 70% unit, 25% integration, 5% e2e
+
+### Test Types and Organization
+
+#### Unit Tests
+
+- **Framework:** Rust built-in testing
+- **File Convention:** Tests in same file as code under `#[cfg(test)]` module
+- **Location:** Bottom of each source file
+- **Mocking Library:** Manual test doubles (traits make this easy)
+- **Coverage Requirement:** 90% for domain and app layers
+
+**AI Agent Requirements:**
+
+- Generate tests for all public methods
+- Cover edge cases and error conditions
+- Follow AAA pattern (Arrange, Act, Assert)
+- Mock all external dependencies
+
+#### Integration Tests
+
+- **Scope:** Database operations, CLI parsing, file I/O
+- **Location:** `tests/integration/`
+- **Test Infrastructure:**
+  - **Database:** In-memory SQLite for speed
+  - **File System:** tempfile crate for isolated testing
+  - **CLI:** assert_cmd for command execution tests
+
+#### End-to-End Tests
+
+- **Framework:** assert_cmd 2.0.14
+- **Scope:** Full command execution with real database
+- **Environment:** Isolated temp directory per test
+- **Test Data:** Fixtures in tests/fixtures/
+
+### Test Data Management
+
+- **Strategy:** Builder pattern for test objects
+- **Fixtures:** `tests/fixtures/` for import/export tests
+- **Factories:** TaskBuilder, TagBuilder in test modules
+- **Cleanup:** Automatic via tempfile cleanup
+
+### Continuous Testing
+
+- **CI Integration:** Run on every push (test, clippy, fmt)
+- **Performance Tests:** Criterion benchmarks with 5% regression threshold
+- **Security Tests:** cargo audit in CI pipeline
+
+## Security
+
+### Input Validation
+
+- **Validation Library:** Built-in Rust type system + manual checks
+- **Validation Location:** CLI parsing layer before any processing
+- **Required Rules:**
+  - All external inputs MUST be validated
+  - Validation at API boundary before processing
+  - Whitelist approach preferred over blacklist
+
+### Authentication & Authorization
+
+- **Auth Method:** Not applicable (local single-user application)
+- **Session Management:** Not applicable
+- **Required Patterns:**
+  - File permissions rely on OS user permissions
+  - XDG directory compliance for proper isolation
+
+### Secrets Management
+
+- **Development:** No secrets required
+- **Production:** No secrets required
+- **Code Requirements:**
+  - NEVER hardcode secrets
+  - Access via configuration service only
+  - No secrets in logs or error messages
+
+### API Security
+
+Not applicable - no network APIs exposed
+
+### Data Protection
+
+- **Encryption at Rest:** Relies on OS disk encryption
+- **Encryption in Transit:** Not applicable (local only)
+- **PII Handling:** Task descriptions may contain PII - never log
+- **Logging Restrictions:** Never log task content, only IDs and metadata
+
+### Dependency Security
+
+- **Scanning Tool:** cargo audit
+- **Update Policy:** Monthly dependency updates
+- **Approval Process:** Review changelog for breaking changes
+
+### Security Testing
+
+- **SAST Tool:** cargo clippy with security lints
+- **DAST Tool:** Not applicable
+- **Penetration Testing:** Not required for local CLI
+
+## Checklist Results Report
+
+To be completed after architecture review.
+
+## Next Steps
+
+### Developer Handoff
+
+Begin implementation with the following:
+
+- Reference this architecture document and coding standards throughout development
+- Start with Epic 1, Story 1.1: Project Setup and Infrastructure
+- Key technical decisions to follow:
+  - Use Rust 1.78.0 with 2021 edition
+  - Implement clean architecture layers as specified
+  - All commands must complete in < 100ms
+  - Use synchronous code (no async/await)
+  - Follow the defined error handling patterns

zoo/docs/brief.md

@@ -0,0 +1,253 @@
+# Project Brief: Terminal Todo App
+
+## Project Overview
+
+**Project Name:** TermTodo  
+**Version:** 1.0  
+**Date:** 2025-07-07  
+**Status:** Planning Phase
+
+### Executive Summary
+
+TermTodo is a lightweight, fast, and efficient terminal-based todo application designed for developers and power users who live in the command line. The application prioritizes speed, simplicity, and seamless integration with existing terminal workflows while providing robust task management capabilities.
+
+### Vision Statement
+
+To create the most efficient terminal todo app that enhances developer productivity by eliminating context switching between GUI applications and the command line environment.
+
+## Problem Statement
+
+### Current Pain Points
+
+- **Context Switching:** Developers lose focus switching between terminal and GUI todo apps
+- **Bloated Solutions:** Existing todo apps are feature-heavy and slow to load
+- **Poor CLI Integration:** Most todo apps don't integrate well with terminal workflows
+- **Sync Overhead:** Cloud-based solutions add unnecessary complexity for local task management
+
+### Target Opportunity
+
+Create a fast, local-first todo application that feels native to terminal users while providing essential productivity features without bloat.
+
+## Objectives & Success Metrics
+
+### Primary Objectives
+
+1. **Speed:** App launches and executes commands in <100ms
+2. **Simplicity:** Core functionality accessible through intuitive commands
+3. **Integration:** Seamless workflow integration with git, editors, and shell scripts
+4. **Reliability:** Zero data loss with robust local storage
+
+### Success Metrics
+
+- **Performance:** Sub-100ms command execution time
+- **Adoption:** 1000+ GitHub stars within 6 months
+- **Usage:** Daily active usage by 100+ developers
+- **Satisfaction:** 90%+ positive feedback on usability
+
+## Target Audience
+
+### Primary Users
+
+**Developer Power Users**
+
+- Daily terminal users
+- Prefer keyboard-driven workflows
+- Value speed and efficiency over visual polish
+- Work with multiple projects simultaneously
+
+**System Administrators**
+
+- Manage multiple servers and tasks
+- Need quick task tracking between systems
+- Prefer scriptable/automatable solutions
+
+### User Personas
+
+**"Terminal Tom" - Senior Developer**
+
+- 8+ years experience
+- Uses vim/emacs, tmux, custom shell setups
+- Manages 3-5 projects simultaneously
+- Values minimalism and efficiency
+
+**"DevOps Dana" - Infrastructure Engineer**
+
+- Manages CI/CD pipelines
+- Juggles multiple environments
+- Needs quick task capture during incidents
+- Prefers automation-friendly tools
+
+## Scope & Features
+
+### Core Features (MVP)
+
+1. **Basic Task Management**
+
+   - Add, edit, delete tasks
+   - Mark tasks as complete
+   - List tasks with filtering
+
+2. **Organization**
+
+   - Project-based task grouping
+   - Priority levels (high, medium, low)
+   - Due date support
+
+3. **Search & Filter**
+   - Text search across tasks
+   - Filter by status, priority, project
+   - Tag-based organization
+
+### Advanced Features (v2.0+)
+
+1. **Workflow Integration**
+
+   - Git branch integration
+   - Editor plugin support
+   - Shell completion
+
+2. **Automation**
+
+   - Recurring tasks
+   - Template tasks
+   - Bulk operations
+
+3. **Reporting**
+   - Productivity metrics
+   - Time tracking
+   - Export capabilities
+
+### Out of Scope
+
+- Web interface
+- Mobile applications
+- Cloud synchronization
+- Collaborative features
+- Complex project management
+
+## Technical Requirements
+
+### Technology Stack
+
+- **Language:** Rust (performance, single binary distribution)
+- **CLI Framework:** Clap (argument parsing)
+- **Storage:** SQLite (local, reliable, queryable)
+- **Configuration:** TOML files
+
+### Performance Requirements
+
+- **Startup Time:** <50ms cold start
+- **Command Execution:** <100ms for all operations
+- **Memory Usage:** <10MB resident memory
+- **Storage:** Efficient SQLite schema design
+
+### Platform Support
+
+- **Primary:** Linux, macOS
+- **Secondary:** Windows (WSL)
+- **Distribution:** Single binary, package managers
+
+## Implementation Strategy
+
+### Development Phases
+
+**Phase 1: Core MVP (4 weeks)**
+
+- Basic CRUD operations
+- SQLite storage layer
+- Command-line interface
+- Unit test coverage
+
+**Phase 2: Organization (3 weeks)**
+
+- Project grouping
+- Priority and due dates
+- Search and filtering
+- Integration testing
+
+**Phase 3: Polish (2 weeks)**
+
+- Shell completion
+- Configuration management
+- Documentation
+- Performance optimization
+
+### Risk Mitigation
+
+- **Technical Risk:** Rust learning curve → Start with simple CLI, iterate
+- **Market Risk:** Existing solutions → Focus on speed and terminal integration
+- **Adoption Risk:** Discoverability → Leverage dev community, GitHub
+
+## Timeline & Milestones
+
+### Key Milestones
+
+| Phase | Deliverable      | Timeline | Success Criteria               |
+| ----- | ---------------- | -------- | ------------------------------ |
+| 1     | MVP Release      | Week 4   | Core features functional       |
+| 2     | Beta Release     | Week 7   | Organization features complete |
+| 3     | v1.0 Release     | Week 9   | Production ready               |
+| 4     | Community Growth | Week 20  | 1000+ GitHub stars             |
+
+### Critical Path
+
+1. SQLite schema design
+2. Core command structure
+3. Performance optimization
+4. Documentation and examples
+
+## Team & Stakeholders
+
+### Core Team
+
+**Solo Developer** (Primary)
+
+- Full-stack development
+- Design and architecture
+- Testing and documentation
+
+### Advisory Stakeholders
+
+- **Developer Community:** Feedback and feature requests
+- **Beta Users:** Early testing and validation
+- **Open Source Community:** Contributions and maintenance
+
+## Budget & Resources
+
+### Development Resources
+
+- **Time Investment:** 20 hours/week for 9 weeks
+- **Infrastructure:** GitHub (free), domain name ($15/year)
+- **Tools:** Development environment, testing tools
+
+### Total Investment
+
+- **Development Time:** ~180 hours
+- **Direct Costs:** <$50
+- **Opportunity Cost:** Personal projects, learning time
+
+## Success Factors
+
+### Critical Success Factors
+
+1. **Performance First:** Every feature decision evaluated for speed impact
+2. **Developer Experience:** Intuitive commands that feel natural
+3. **Terminal Native:** Feels like a built-in shell command
+4. **Community Building:** Engage early adopters for feedback
+
+### Potential Risks
+
+- **Over-engineering:** Feature creep beyond core use cases
+- **Performance Degradation:** Complex features slowing core operations
+- **Adoption Challenges:** Difficulty reaching target developers
+
+## Next Steps
+
+1. **Technical Spike:** Rust CLI framework evaluation (Week 1)
+2. **Database Design:** SQLite schema and migration strategy
+3. **Core Architecture:** Command structure and data flow
+4. **MVP Development:** Begin core feature implementation
+
+---
+
+_This project brief will be reviewed and updated at each milestone to ensure alignment with objectives and market feedback._

zoo/docs/prd.md

@@ -0,0 +1,500 @@
+# TermTodo Product Requirements Document (PRD)
+
+## Goals and Background Context
+
+### Goals
+
+- Deliver a terminal todo app that executes all commands in under 100ms
+- Eliminate context switching for developers who live in the command line
+- Provide intuitive task management through simple, memorable commands
+- Enable seamless integration with existing terminal workflows (git, editors, scripts)
+- Achieve zero data loss with robust local SQLite storage
+- Build a tool that feels native to terminal power users
+- Create a maintainable single-binary distribution for easy installation
+
+### Background Context
+
+TermTodo addresses a critical gap in developer productivity tools. While numerous todo applications exist, they force developers to break their flow by switching between terminal and GUI applications. Current solutions are either bloated web applications with unnecessary features or simplistic command-line tools that lack essential task management capabilities. TermTodo strikes the balance by providing a fast, local-first solution that integrates naturally into terminal-based workflows.
+
+The application targets developers and system administrators who value speed and efficiency over visual polish. By focusing on sub-100ms execution times and keyboard-driven interactions, TermTodo eliminates the friction that prevents consistent task tracking in fast-paced development environments. The choice of Rust ensures performance goals are met while providing a single binary that's easy to distribute and install across Linux, macOS, and Windows (WSL) platforms.
+
+### Change Log
+
+| Date       | Version | Description                                 | Author   |
+| ---------- | ------- | ------------------------------------------- | -------- |
+| 2025-07-07 | 1.0     | Initial PRD creation based on Project Brief | PM Agent |
+
+## Requirements
+
+### Functional
+
+- FR1: The application must support adding tasks with a single command (e.g., `todo add "Complete code review"`)
+- FR2: Users must be able to mark tasks as complete/incomplete with toggle functionality
+- FR3: The application must support editing existing task descriptions
+- FR4: Users must be able to delete individual tasks or bulk delete completed tasks
+- FR5: The application must list tasks with configurable filtering by status, priority, project, and tags
+- FR6: Task organization must support project-based grouping with easy project switching
+- FR7: Each task must support priority levels (high, medium, low) with visual indicators in listings
+- FR8: Tasks must support optional due dates with human-readable input (e.g., "tomorrow", "next friday")
+- FR9: The application must provide full-text search across all task fields
+- FR10: Users must be able to add and remove tags from tasks for flexible categorization
+- FR11: The application must support task templates for recurring task patterns
+- FR12: Shell completion must be available for all commands and common parameters
+- FR13: The application must provide export functionality to common formats (JSON, CSV, Markdown)
+- FR14: Configuration must be manageable through TOML files with sensible defaults
+
+### Non Functional
+
+- NFR1: All commands must execute in under 100ms from invocation to completion
+- NFR2: Cold start time must be under 50ms on standard developer hardware
+- NFR3: Memory usage must not exceed 10MB during normal operation
+- NFR4: The application must be distributed as a single static binary with no runtime dependencies
+- NFR5: Data storage must use SQLite with ACID compliance for zero data loss
+- NFR6: The CLI must follow Unix conventions (stdin/stdout, exit codes, composability)
+- NFR7: All user-facing messages must be clear, concise, and actionable
+- NFR8: The application must support Linux and macOS as primary platforms, Windows via WSL
+- NFR9: Installation must be possible through major package managers (brew, apt, cargo)
+- NFR10: The codebase must maintain 80%+ test coverage for reliability
+- NFR11: All commands must be documented with man pages and --help output
+- NFR12: The application must handle 10,000+ tasks without performance degradation
+- NFR13: Error messages must provide clear guidance for resolution
+- NFR14: The application must support UTF-8 for international task descriptions
+
+## Technical Assumptions
+
+### Repository Structure: Monorepo
+
+Single repository containing all TermTodo code, tests, documentation, and build configurations. This simplifies development, testing, and distribution for a focused CLI tool.
+
+### Service Architecture
+
+**Monolith** - TermTodo will be built as a single, self-contained binary with all functionality compiled in. This architecture aligns with our performance goals (sub-50ms startup) and distribution requirements (single binary). The SQLite database will be embedded, and all operations will run in-process without network dependencies.
+
+### Testing Requirements
+
+**Full Testing Pyramid** - Given the critical nature of data integrity and performance requirements:
+
+- **Unit Tests**: Core business logic, data models, command parsing
+- **Integration Tests**: SQLite operations, file I/O, command execution flows
+- **E2E Tests**: Full command-line scenarios using the actual binary
+- **Performance Tests**: Automated benchmarks ensuring sub-100ms execution
+- **Manual Testing Helpers**: Debug commands and verbose modes for troubleshooting
+
+### Additional Technical Assumptions and Requests
+
+- **Language**: Rust (as specified in Project Brief) for performance and memory safety
+- **CLI Framework**: Clap v4+ for robust argument parsing and automatic help generation
+- **Database**: SQLite with schema migrations support (using sqlx or diesel)
+- **Error Handling**: Comprehensive error types with user-friendly messages using anyhow/thiserror
+- **Configuration**: TOML for human-readable config files, with XDG base directory compliance
+- **Build System**: Cargo with cross-compilation support for Linux/macOS/Windows targets
+- **Serialization**: Serde for JSON/CSV export functionality
+- **Date Parsing**: Chrono with chrono-english for human-readable date input
+- **Terminal Output**: Colored output using termcolor, respecting NO_COLOR environment variable
+- **Shell Completion**: Built-in completion generation for bash, zsh, fish, and PowerShell
+- **Packaging**: Release binaries via GitHub releases, plus cargo, brew tap, and AUR support
+- **Documentation**: Embedded man pages generated from clap, README with examples
+- **Logging**: Optional debug logging to file (not stdout) for troubleshooting
+- **Benchmarking**: Criterion.rs for performance regression testing in CI
+
+## Epic List
+
+- **Epic 1: Foundation & Core Task Management**: Establish project infrastructure, CI/CD, and implement basic CRUD operations for tasks with SQLite storage
+- **Epic 2: Organization & Filtering**: Implement project-based task grouping, priority levels, tags, and comprehensive filtering capabilities
+- **Epic 3: Advanced Features & Integration**: Add due dates, search functionality, shell completion, templates, and import/export capabilities
+
+## Epic 1: Foundation & Core Task Management
+
+Establish the foundational infrastructure for TermTodo including project setup, continuous integration, and core task CRUD operations. This epic delivers a functional but minimal todo application that can add, list, complete, and delete tasks with persistent SQLite storage, while meeting our aggressive performance requirements.
+
+### Story 1.1: Project Setup and Infrastructure
+
+As a developer,
+I want a properly structured Rust project with CI/CD pipelines,
+so that I can ensure code quality and automated releases from the start.
+
+#### Acceptance Criteria
+
+1: Repository initialized with Rust project structure and .gitignore
+2: Cargo.toml configured with project metadata and initial dependencies (clap, sqlx, tokio)
+3: GitHub Actions workflow for CI (test, lint, build) on all platforms
+4: GitHub Actions workflow for CD (release binaries) on tag push
+5: Basic README with project description and development setup instructions
+6: Pre-commit hooks configured for formatting (rustfmt) and linting (clippy)
+7: MIT License file added
+8: Makefile with common development commands (test, build, release)
+
+### Story 1.2: CLI Framework and Command Structure
+
+As a user,
+I want a well-structured command-line interface with help documentation,
+so that I can easily discover and use all available commands.
+
+#### Acceptance Criteria
+
+1: Main CLI entry point implemented with clap v4
+2: Subcommand structure established (add, list, complete, delete, etc.)
+3: Global flags implemented (--version, --help, --config)
+4: Auto-generated help text for all commands and subcommands
+5: Version information properly displayed from Cargo.toml
+6: Exit codes follow Unix conventions (0 for success, non-zero for errors)
+7: Basic error handling structure with user-friendly messages
+
+### Story 1.3: SQLite Database Layer
+
+As a developer,
+I want a robust database layer with schema management,
+so that I can reliably store and retrieve tasks with ACID compliance.
+
+#### Acceptance Criteria
+
+1: SQLite connection pool initialized with proper settings
+2: Initial schema migration creating tasks table (id, description, status, created_at, updated_at)
+3: Migration system implemented for future schema changes
+4: Database file created in XDG-compliant data directory
+5: Connection timeout and busy handling configured for concurrent access
+6: Basic database error handling with rollback support
+7: Database layer abstraction with trait for testability
+
+### Story 1.4: Add Task Functionality
+
+As a user,
+I want to quickly add new tasks from the command line,
+so that I can capture todo items without breaking my workflow.
+
+#### Acceptance Criteria
+
+1: "todo add <description>" command creates new task in database
+2: Task description supports UTF-8 and quotes/special characters
+3: Newly created task ID displayed on successful addition
+4: Task creation timestamp automatically recorded
+5: Performance requirement met: command completes in <100ms
+6: Error shown if description is empty or too long (>1000 chars)
+7: Success message confirms task was added
+
+### Story 1.5: List Tasks Functionality
+
+As a user,
+I want to see my current tasks in a clear format,
+so that I can review what needs to be done.
+
+#### Acceptance Criteria
+
+1: "todo list" command displays all incomplete tasks
+2: Output shows task ID, description, and age (e.g., "2 days ago")
+3: Tasks sorted by creation date (oldest first) by default
+4: Completed tasks hidden by default
+5: "--all" flag shows both complete and incomplete tasks
+6: Empty state message when no tasks exist
+7: Output formatted for terminal width with proper truncation
+
+### Story 1.6: Complete Task Functionality
+
+As a user,
+I want to mark tasks as complete,
+so that I can track my progress.
+
+#### Acceptance Criteria
+
+1: "todo complete <id>" marks specified task as complete
+2: Multiple IDs can be provided to complete multiple tasks
+3: Completion timestamp recorded in database
+4: Success message confirms which task(s) were completed
+5: Error shown for non-existent task IDs
+6: Already-completed tasks can be marked complete again (idempotent)
+7: Performance requirement met: command completes in <100ms
+
+### Story 1.7: Delete Task Functionality
+
+As a user,
+I want to delete tasks I no longer need,
+so that I can keep my task list clean and relevant.
+
+#### Acceptance Criteria
+
+1: "todo delete <id>" removes specified task from database
+2: Multiple IDs can be provided to delete multiple tasks
+3: Confirmation required by default (bypass with --force flag)
+4: Success message confirms which task(s) were deleted
+5: Error shown for non-existent task IDs
+6: "todo delete --completed" removes all completed tasks
+7: Deleted tasks cannot be recovered (documented in help)
+
+## Epic 2: Organization & Filtering
+
+Implement comprehensive task organization features including projects, priorities, tags, and filtering capabilities. This epic transforms the basic todo app into a powerful task management system that can handle complex workflows while maintaining simplicity and performance.
+
+### Story 2.1: Project-Based Task Grouping
+
+As a developer working on multiple projects,
+I want to organize tasks by project,
+so that I can focus on relevant tasks for my current context.
+
+#### Acceptance Criteria
+
+1: Tasks table schema updated to include optional project field
+2: "todo add -p <project> <description>" assigns task to project
+3: "todo list -p <project>" filters tasks by project
+4: "todo projects" lists all unique projects with task counts
+5: Default project configurable in TOML config file
+6: Project names validated (alphanumeric + dash/underscore)
+7: Tasks without project show under "default" in listings
+
+### Story 2.2: Priority Levels
+
+As a user,
+I want to assign priority levels to tasks,
+so that I can focus on what's most important.
+
+#### Acceptance Criteria
+
+1: Tasks table schema updated to include priority field (high/medium/low)
+2: "todo add -P high <description>" sets task priority
+3: Default priority is "medium" if not specified
+4: Priority shown in task listings with visual indicators (!, !!, !!!)
+5: "todo list --priority high" filters by priority level
+6: Tasks sorted by priority within date sorting
+7: Priority can be updated with "todo priority <id> <level>"
+
+### Story 2.3: Tag System
+
+As a user,
+I want to add tags to tasks for flexible categorization,
+so that I can create custom organizational schemes.
+
+#### Acceptance Criteria
+
+1: Tags table created with many-to-many relationship to tasks
+2: "todo add <description> +tag1 +tag2" adds tags during creation
+3: Tags parsed from description (+ prefix) and stored separately
+4: "todo tag <id> +tag" adds tags to existing tasks
+5: "todo tag <id> -tag" removes tags from tasks
+6: "todo list +tag" filters tasks by tag
+7: "todo tags" lists all tags with usage counts
+
+### Story 2.4: Advanced Filtering
+
+As a power user,
+I want to combine multiple filters when listing tasks,
+so that I can create precise views of my work.
+
+#### Acceptance Criteria
+
+1: Multiple filters can be combined (project AND priority AND tags)
+2: "todo list -p work -P high +urgent" shows filtered results
+3: Date range filtering with --since and --until flags
+4: Status filtering with --status (incomplete/complete/all)
+5: Inverse filters supported with --not-project, --not-tag
+6: Filter combinations can be saved as named views in config
+7: Performance maintained under 100ms even with complex filters
+
+### Story 2.5: Configuration Management
+
+As a user,
+I want to customize default behaviors and preferences,
+so that the tool works the way I prefer.
+
+#### Acceptance Criteria
+
+1: TOML config file created at XDG config location on first run
+2: Config supports: default project, default priority, date format
+3: Config supports: color preferences, list sort order
+4: "todo config" opens config file in $EDITOR
+5: "todo config --list" shows current configuration
+6: Invalid config shows clear error without crashing
+7: Config changes take effect immediately (no restart needed)
+
+## Epic 3: Advanced Features & Integration
+
+Add power-user features including due dates, full-text search, shell completion, templates, and data portability. This epic completes the feature set needed for TermTodo to become an indispensable part of a developer's workflow.
+
+### Story 3.1: Due Date Support
+
+As a user,
+I want to set due dates on tasks,
+so that I can manage time-sensitive work effectively.
+
+#### Acceptance Criteria
+
+1: Tasks table schema updated to include optional due_date field
+2: "todo add <description> due:tomorrow" sets due date with natural language
+3: Supported formats: "due:2024-12-31", "due:friday", "due:3d" (3 days)
+4: Due dates shown in task listings with urgency indicators
+5: "todo list --due" shows only tasks with due dates
+6: "todo list --overdue" shows past-due tasks highlighted
+7: Due date can be updated with "todo due <id> <date>"
+
+### Story 3.2: Full-Text Search
+
+As a user with many tasks,
+I want to search across all task fields,
+so that I can quickly find specific items.
+
+#### Acceptance Criteria
+
+1: "todo search <query>" searches description, project, and tags
+2: Search uses SQLite FTS5 for performance and features
+3: Results show matched tasks with search terms highlighted
+4: Search supports quoted phrases for exact matching
+5: Boolean operators AND/OR supported in queries
+6: Search results include context around matches
+7: Performance requirement met: search completes in <100ms
+
+### Story 3.3: Shell Completion
+
+As a command-line power user,
+I want shell completion for all commands and parameters,
+so that I can work more efficiently.
+
+#### Acceptance Criteria
+
+1: Completion scripts generated for bash, zsh, fish, PowerShell
+2: Command completion includes all subcommands and flags
+3: Project names completed for -p flag from existing projects
+4: Tag names completed after + prefix from existing tags
+5: Task IDs completed for complete/delete/update commands
+6: Installation instructions included in README
+7: Completion scripts included in distribution packages
+
+### Story 3.4: Task Templates
+
+As a user with recurring task patterns,
+I want to create templates for common tasks,
+so that I can quickly add similar tasks.
+
+#### Acceptance Criteria
+
+1: Templates stored in TOML config file with name and pattern
+2: "todo template create <name>" interactively creates template
+3: "todo template list" shows available templates
+4: "todo add --template <name>" creates task from template
+5: Templates support placeholders like {date}, {project}
+6: Templates can include default project, priority, tags
+7: "todo template delete <name>" removes unused templates
+
+### Story 3.5: Import/Export Functionality
+
+As a user,
+I want to export and import my tasks in common formats,
+so that I can backup data or integrate with other tools.
+
+#### Acceptance Criteria
+
+1: "todo export --format json" exports all tasks to JSON
+2: "todo export --format csv" exports tasks to CSV format
+3: "todo export --format markdown" creates Markdown task list
+4: Export supports filtering (only export filtered tasks)
+5: "todo import <file>" imports tasks from JSON format
+6: Import validates data and reports errors without corruption
+7: Export includes all fields: description, project, priority, tags, dates
+
+### Story 3.6: Performance Optimization
+
+As a developer using the tool hundreds of times per day,
+I want consistent sub-100ms performance,
+so that the tool never slows down my workflow.
+
+#### Acceptance Criteria
+
+1: Benchmark suite implemented using criterion.rs
+2: All commands benchmarked in CI to prevent regression
+3: Database indexes optimized for common query patterns
+4: Prepared statements cached for repeated queries
+5: Binary size optimized with release flags and LTO
+6: Cold start optimized to meet <50ms requirement
+7: Performance guide documented with optimization tips
+
+## Checklist Results Report
+
+### Executive Summary
+
+- **Overall PRD Completeness**: 95%
+- **MVP Scope Appropriateness**: Just Right
+- **Readiness for Architecture Phase**: Ready
+- **Most Critical Gaps**: None - PRD is comprehensive and well-structured
+
+### Category Analysis Table
+
+| Category                         | Status | Critical Issues          |
+| -------------------------------- | ------ | ------------------------ |
+| 1. Problem Definition & Context  | PASS   | None                     |
+| 2. MVP Scope Definition          | PASS   | None                     |
+| 3. User Experience Requirements  | PASS   | CLI-focused, appropriate |
+| 4. Functional Requirements       | PASS   | None                     |
+| 5. Non-Functional Requirements   | PASS   | None                     |
+| 6. Epic & Story Structure        | PASS   | None                     |
+| 7. Technical Guidance            | PASS   | None                     |
+| 8. Cross-Functional Requirements | PASS   | None                     |
+| 9. Clarity & Communication       | PASS   | None                     |
+
+### Top Issues by Priority
+
+**BLOCKERS**: None identified
+
+**HIGH**: None identified
+
+**MEDIUM**:
+
+- Consider adding explicit data migration strategy for future schema changes
+- May want to specify exact Rust version requirements
+
+**LOW**:
+
+- Could add more specific examples of shell script integration possibilities
+- Might benefit from explicit CI/CD tool preferences (GitHub Actions assumed)
+
+### MVP Scope Assessment
+
+**Scope Analysis**:
+
+- The MVP scope is appropriately minimal while delivering core value
+- Epic 1 provides a working todo app with essential CRUD operations
+- Epic 2 and 3 can be delivered incrementally based on user feedback
+- No features appear superfluous for the target audience
+
+**Timeline Realism**:
+
+- 9-week timeline is aggressive but achievable for a solo developer
+- Story sizing is appropriate for AI-assisted development
+- Performance requirements may require iteration but are well-defined
+
+### Technical Readiness
+
+**Clarity of Technical Constraints**:
+
+- Technology stack clearly defined (Rust, SQLite, Clap)
+- Performance requirements explicit and measurable
+- Distribution strategy well-planned
+
+**Identified Technical Risks**:
+
+- SQLite cold-start performance for <50ms requirement
+- Cross-platform shell completion complexity
+- Natural language date parsing edge cases
+
+**Areas Needing Architect Investigation**:
+
+- Optimal SQLite configuration for performance
+- Schema design for efficient filtering and search
+- Binary size optimization strategies
+
+### Recommendations
+
+1. **Proceed to Architecture Phase**: The PRD is comprehensive and ready
+2. **Early Performance Validation**: Create a spike to validate SQLite startup times
+3. **Schema Evolution Strategy**: Document migration approach early in development
+4. **User Testing Plan**: Consider early beta program for developer feedback
+
+### Final Decision
+
+**READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design. The document provides clear requirements, appropriate technical constraints, and a well-sequenced implementation plan suitable for the target developer audience.
+
+## Next Steps
+
+### Design Architect Prompt
+
+Review the TermTodo PRD and create a comprehensive UI/UX design specification for this CLI application, focusing on terminal-based interaction patterns, command syntax design, output formatting, and the overall developer experience.
+
+### Architect Prompt
+
+Analyze the TermTodo PRD and create a detailed technical architecture document including: database schema design, Rust module structure, performance optimization strategies, error handling patterns, and a concrete implementation plan for achieving sub-100ms execution times.