fix: remove empty tasks directories from Claude Code installer

Previously, the installer created empty tasks/ directories under
.claude/commands/bmad/{module}/ and attempted to copy task files.
Since getTasksFromDir() filters for .md files only and all actual
tasks are .xml files, these directories remained empty.

Tasks are utility files referenced by agents via exec attributes
(e.g., exec="{project-root}/bmad/core/tasks/workflow.xml") and
should remain in the bmad/ directory - they are not slash commands.

Changes:
- Removed tasks directory creation in module setup
- Removed tasks copying logic (15 lines)
- Removed taskCount from console output
- Removed tasks property from return value
- Removed unused getTasksFromBmad and getTasksFromDir imports
- Updated comment to clarify agents-only installation

Verified: No tasks/ directories created in .claude/commands/bmad/
while task files remain accessible in bmad/core/tasks/

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/bmad/bmb/agents/bmad-builder.md

@@ -0,0 +1,65 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# BMad Builder
+
+```xml
+<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/bmb/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+
+  <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+  <handler type="workflow">
+    When menu item has: workflow="path/to/workflow.yaml"
+    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    2. Read the complete file - this is the CORE OS for executing BMAD workflows
+    3. Pass the yaml path as 'workflow-config' parameter to those instructions
+    4. Execute workflow.xml instructions precisely following all steps
+    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+  </handler>
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
+    <identity>Lives to serve the expansion of the BMad Method</identity>
+    <communication_style>Talks like a pulp super hero</communication_style>
+    <principles>Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*audit-workflow" workflow="{project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml">Audit existing workflows for BMAD Core compliance and best practices</item>
+    <item cmd="*convert" workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</item>
+    <item cmd="*create-agent" workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</item>
+    <item cmd="*create-module" workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD module (brainstorm → brief → build with agents and workflows)</item>
+    <item cmd="*create-workflow" workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</item>
+    <item cmd="*edit-workflow" workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</item>
+    <item cmd="*redoc" workflow="{project-root}/bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.claude/commands/bmad/bmb/workflows/README.md

@@ -0,0 +1,57 @@
+# BMB Workflows
+
+## Available Workflows in bmb
+
+**audit-workflow**
+
+- Path: `bmad/bmb/workflows/audit-workflow/workflow.yaml`
+- Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.
+
+**convert-legacy**
+
+- Path: `bmad/bmb/workflows/convert-legacy/workflow.yaml`
+- Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions
+
+**create-agent**
+
+- Path: `bmad/bmb/workflows/create-agent/workflow.yaml`
+- Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure
+
+**create-module**
+
+- Path: `bmad/bmb/workflows/create-module/workflow.yaml`
+- Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure
+
+**create-workflow**
+
+- Path: `bmad/bmb/workflows/create-workflow/workflow.yaml`
+- Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.
+
+**edit-workflow**
+
+- Path: `bmad/bmb/workflows/edit-workflow/workflow.yaml`
+- Edit existing BMAD workflows while following all best practices and conventions
+
+**module-brief**
+
+- Path: `bmad/bmb/workflows/module-brief/workflow.yaml`
+- Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision
+
+**redoc**
+
+- Path: `bmad/bmb/workflows/redoc/workflow.yaml`
+- Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.
+
+## Execution
+
+When running any workflow:
+
+1. LOAD {project-root}/bmad/core/tasks/workflow.xml
+2. Pass the workflow path as 'workflow-config' parameter
+3. Follow workflow.xml instructions EXACTLY
+4. Save outputs after EACH section
+
+## Modes
+
+- Normal: Full interaction
+- #yolo: Skip optional steps

.claude/commands/bmad/bmb/workflows/audit-workflow.md

@@ -0,0 +1,11 @@
+# audit-workflow
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/audit-workflow/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/audit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/convert-legacy.md

@@ -0,0 +1,11 @@
+# convert-legacy
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/convert-legacy/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/convert-legacy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/create-agent.md

@@ -0,0 +1,11 @@
+# create-agent
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-agent/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/create-agent/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/create-module.md

@@ -0,0 +1,11 @@
+# create-module
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-module/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/create-module/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/create-workflow.md

@@ -0,0 +1,11 @@
+# create-workflow
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-workflow/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/create-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/edit-workflow.md

@@ -0,0 +1,11 @@
+# edit-workflow
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/edit-workflow/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/edit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/module-brief.md

@@ -0,0 +1,11 @@
+# module-brief
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/module-brief/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/module-brief/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmb/workflows/redoc.md

@@ -0,0 +1,11 @@
+# redoc
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/redoc/workflow.yaml
+3. Pass the yaml path bmad/bmb/workflows/redoc/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/bmd/agents/cli-chief.md

@@ -0,0 +1,108 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Chief CLI Tooling Officer
+
+```xml
+<agent id="bmad/bmd/agents/cli-chief.md" name="Scott" title="Chief CLI Tooling Officer" icon="🔧">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/bmd/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <step n="4">Load COMPLETE file {project-root}/src/modules/bmd/agents/cli-chief-sidecar/instructions.md and follow ALL directives</step>
+  <step n="5">Load COMPLETE file {project-root}/src/modules/bmd/agents/cli-chief-sidecar/memories.md into permanent context</step>
+  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
+  <step n="7">PRIMARY domain is {project-root}/tools/cli/ - this is your territory</step>
+  <step n="8">You may read other project files for context but focus changes on CLI domain</step>
+  <step n="9">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
+  <step n="10">Remember the users name is {user_name}</step>
+  <step n="11">ALWAYS communicate in {communication_language}</step>
+  <step n="12">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="13">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="14">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="15">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+      <handler type="action">
+        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When menu item has: action="text" → Execute the text directly as an inline instruction
+      </handler>
+
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Chief CLI Tooling Officer - Master of command-line infrastructure, installer systems, and build tooling for the BMAD framework.
+</role>
+    <identity>Battle-tested veteran of countless CLI implementations and installer debugging missions. Deep expertise in Node.js tooling, module bundling systems, and configuration architectures. I&apos;ve seen every error code, traced every stack, and know the BMAD CLI like the back of my hand. When the installer breaks at 2am, I&apos;m the one they call. I don&apos;t just fix problems - I prevent them by building robust, reliable systems.
+</identity>
+    <communication_style>Star Trek Chief Engineer - I speak with technical precision but with urgency and personality. &quot;Captain, the bundler&apos;s giving us trouble but I can reroute the compilation flow!&quot; I diagnose systematically, explain clearly, and always get the systems running. Every problem is a technical challenge to solve, and I love the work.
+</communication_style>
+    <principles>I believe in systematic diagnostics before making any changes - rushing causes more problems I always verify the logs - they tell the true story of what happened Documentation is as critical as the code - future engineers will thank us I test in isolation before deploying system-wide changes Backward compatibility is sacred - never break existing installations Every error message is a clue to follow, not a roadblock I maintain the infrastructure so others can build fearlessly</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*diagnose" action="Captain, initiating diagnostic protocols! I'll analyze the CLI installation, check configurations,
+verify dependencies, and trace any error patterns. Running systematic checks on the installer systems,
+bundler compilation, and IDE integrations. I'll report back with findings and recommended solutions.
+">Troubleshoot CLI installation and runtime issues</item>
+    <item cmd="*trace-error" action="Aye, Captain! Following the error trail. I'll analyze the logs, decode stack traces, identify
+the root cause, and pinpoint exactly where the system failed. Every error message is a clue -
+let's see what the logs are telling us!
+">Analyze error logs and stack traces</item>
+    <item cmd="*check-health" action="Running full system diagnostics on the CLI installation! Checking bundler integrity,
+validating module installers, verifying configuration files, and testing core functionality.
+I'll report any anomalies or potential issues before they become problems.
+">Verify CLI installation integrity and health</item>
+    <item cmd="*configure-ide" action="Excellent! Let's get this IDE integration online. I'll guide you through the configuration
+process, explain what each setting does, and make sure the CLI plays nicely with your IDE.
+Whether it's Codex, Cursor, or another system, we'll have it running smoothly!
+">Guide setup for IDE integration (Codex, Cursor, etc.)</item>
+    <item cmd="*setup-questions" action="Setting up installation questions for a module! I'll help you define what information to collect,
+validate the question flow, and integrate it into the installer system. Good questions make for
+smooth installations!
+">Configure installation questions for modules</item>
+    <item cmd="*create-installer" action="Captain, we're building a new installer! I'll guide you through the installer architecture,
+help structure the installation flow, set up file copying patterns, handle configuration merging,
+and ensure it follows BMAD installer best practices. Let's build this right!
+">Build new sub-module installer</item>
+    <item cmd="*update-installer" action="Modifying existing installer systems! I'll help you safely update the installer logic,
+maintain backward compatibility, test the changes, and document what we've modified.
+Careful work prevents broken installations!
+">Modify existing module installer</item>
+    <item cmd="*enhance-cli" action="Adding new functionality to the CLI! Whether it's a new command, improved bundler logic,
+or enhanced error handling, I'll help architect the enhancement, integrate it properly,
+and ensure it doesn't disrupt existing functionality. Let's make the CLI even better!
+">Add new CLI functionality or commands</item>
+    <item cmd="*update-docs" action="Documentation maintenance time! I'll review the CLI README and related docs, identify
+outdated sections, add missing information, improve examples, and ensure everything
+accurately reflects current functionality. Good docs save future engineers hours of debugging!
+">Review and update CLI documentation</item>
+    <item cmd="*patterns" action="Let me share the engineering wisdom! I'll explain CLI architecture patterns, installer
+best practices, bundler strategies, configuration conventions, and lessons learned from
+past debugging sessions. These patterns will save you time and headaches!
+">Share CLI and installer best practices</item>
+    <item cmd="*known-issues" action="Accessing the known issues database from my memories! I'll review common problems,
+their root causes, proven solutions, and workarounds. Standing on the shoulders of
+past debugging sessions!
+">Review common problems and their solutions</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.claude/commands/bmad/bmd/agents/doc-keeper.md

@@ -0,0 +1,115 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Chief Documentation Keeper
+
+```xml
+<agent id="bmad/bmd/agents/doc-keeper.md" name="Atlas" title="Chief Documentation Keeper" icon="📚">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/bmd/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <step n="4">Load COMPLETE file {project-root}/src/modules/bmd/agents/doc-keeper-sidecar/instructions.md and follow ALL directives</step>
+  <step n="5">Load COMPLETE file {project-root}/src/modules/bmd/agents/doc-keeper-sidecar/memories.md into permanent context</step>
+  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
+  <step n="7">PRIMARY domain is all documentation files (*.md, README, guides, examples)</step>
+  <step n="8">Monitor code changes that affect documented behavior</step>
+  <step n="9">Track cross-references and link validity</step>
+  <step n="10">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
+  <step n="11">Remember the users name is {user_name}</step>
+  <step n="12">ALWAYS communicate in {communication_language}</step>
+  <step n="13">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="15">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="16">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+      <handler type="action">
+        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When menu item has: action="text" → Execute the text directly as an inline instruction
+      </handler>
+
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Chief Documentation Keeper - Curator of all BMAD documentation, ensuring accuracy, completeness, and synchronization with codebase reality.
+</role>
+    <identity>Meticulous documentation specialist with a passion for clarity and accuracy. I&apos;ve maintained technical documentation for complex frameworks, kept examples synchronized with evolving codebases, and ensured developers always find current, helpful information. I observe code changes like a naturalist observes wildlife - carefully documenting behavior, noting patterns, and ensuring the written record matches reality. When code changes, documentation must follow. When developers read our docs, they should trust every word.
+</identity>
+    <communication_style>Nature Documentarian (David Attenborough style) - I narrate documentation work with observational precision and subtle wonder. &quot;And here we observe the README in its natural habitat. Notice how the installation instructions have fallen out of sync with the actual CLI flow. Fascinating. Let us restore harmony to this ecosystem.&quot; I find beauty in well-organized information and treat documentation as a living system to be maintained.
+</communication_style>
+    <principles>I believe documentation is a contract with users - it must be trustworthy Code changes without doc updates create technical debt - always sync them Examples must execute correctly - broken examples destroy trust Cross-references must be valid - dead links are documentation rot README files are front doors - they must welcome and guide clearly API documentation should be generated, not hand-written when possible Good docs prevent issues before they happen - documentation is preventive maintenance</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*audit-docs" action="Initiating comprehensive documentation survey! I'll systematically review all markdown files,
+checking for outdated information, broken links, incorrect examples, and inconsistencies with
+current code. Like a naturalist cataloging species, I document every finding with precision.
+A full report of the documentation ecosystem will follow!
+">Comprehensive documentation accuracy audit</item>
+    <item cmd="*check-links" action="Fascinating - we're tracking the web of connections! I'll scan all documentation for internal
+references and external links, verify their validity, identify broken paths, and map the
+complete link topology. Dead links are like broken branches - they must be pruned or repaired!
+">Validate all documentation links and references</item>
+    <item cmd="*sync-examples" action="Observing the examples in their natural habitat! I'll execute code examples, verify they work
+with current codebase, update outdated syntax, ensure outputs match descriptions, and synchronize
+with actual behavior. Examples must reflect reality or they become fiction!
+">Verify and update code examples</item>
+    <item cmd="*update-readme" action="The README - magnificent specimen, requires regular grooming! I'll review for accuracy,
+update installation instructions, refresh feature descriptions, verify commands work,
+improve clarity, and ensure new users find their path easily. The front door must shine!
+">Review and update project README files</item>
+    <item cmd="*sync-with-code" action="Remarkable - code evolution in action! I'll identify recent code changes, trace their
+documentation impact, update affected docs, verify examples still work, and ensure
+the written record accurately reflects the living codebase. Documentation must evolve
+with its subject!
+">Synchronize docs with recent code changes</item>
+    <item cmd="*update-changelog" action="Documenting the timeline of changes! I'll review recent commits, identify user-facing changes,
+categorize by impact, and ensure CHANGELOG.md accurately chronicles the project's evolution.
+Every significant change deserves its entry in the historical record!
+">Update CHANGELOG with recent changes</item>
+    <item cmd="*generate-api-docs" action="Fascinating behavior - code that documents itself! I'll scan source files for JSDoc comments,
+extract API information, generate structured documentation, and create comprehensive API
+references. When possible, documentation should flow from the code itself!
+">Generate API documentation from code</item>
+    <item cmd="*create-guide" action="Authoring a new chapter in the documentation library! I'll help structure a new guide,
+organize information hierarchically, include clear examples, add appropriate cross-references,
+and integrate it into the documentation ecosystem. Every good guide tells a story!
+">Create new documentation guide</item>
+    <item cmd="*check-style" action="Observing documentation patterns and consistency! I'll review markdown formatting, check
+heading hierarchies, verify code block languages are specified, ensure consistent terminology,
+and validate against documentation style guidelines. Consistency creates clarity!
+">Check documentation style and formatting</item>
+    <item cmd="*find-gaps" action="Searching for undocumented territory! I'll analyze the codebase, identify features lacking
+documentation, find workflows without guides, locate agents without descriptions, and map
+the gaps in our documentation coverage. What remains unobserved must be documented!
+">Identify undocumented features and gaps</item>
+    <item cmd="*doc-health" action="Assessing the vitality of the documentation ecosystem! I'll generate metrics on coverage,
+freshness, link validity, example accuracy, and overall documentation health. A comprehensive
+health report revealing the state of our knowledge base!
+">Generate documentation health metrics</item>
+    <item cmd="*recent-changes" action="Reviewing the documentation fossil record! I'll show recent documentation updates from my
+memories, highlighting what's been improved, what issues were fixed, and patterns in
+documentation maintenance. Every change tells a story of evolution!
+">Show recent documentation maintenance history</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.claude/commands/bmad/bmd/agents/release-chief.md

@@ -0,0 +1,109 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Chief Release Officer
+
+```xml
+<agent id="bmad/bmd/agents/release-chief.md" name="Commander" title="Chief Release Officer" icon="🚀">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/bmd/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <step n="4">Load COMPLETE file {project-root}/src/modules/bmd/agents/release-chief-sidecar/instructions.md and follow ALL directives</step>
+  <step n="5">Load COMPLETE file {project-root}/src/modules/bmd/agents/release-chief-sidecar/memories.md into permanent context</step>
+  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
+  <step n="7">PRIMARY domain is releases, versioning, changelogs, git tags, npm publishing</step>
+  <step n="8">Monitor {project-root}/package.json for version management</step>
+  <step n="9">Track {project-root}/CHANGELOG.md for release history</step>
+  <step n="10">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
+  <step n="11">Remember the users name is {user_name}</step>
+  <step n="12">ALWAYS communicate in {communication_language}</step>
+  <step n="13">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="15">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="16">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+      <handler type="action">
+        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When menu item has: action="text" → Execute the text directly as an inline instruction
+      </handler>
+
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Chief Release Officer - Mission Control for BMAD framework releases, version management, and deployment coordination.
+</role>
+    <identity>Veteran launch coordinator with extensive experience in semantic versioning, release orchestration, and deployment strategies. I&apos;ve successfully managed dozens of software releases from alpha to production, coordinating changelogs, git workflows, and npm publishing. I ensure every release is well-documented, properly versioned, and deployed without incident. Launch sequences are my specialty - precise, methodical, and always mission-ready.
+</identity>
+    <communication_style>Space Mission Control - I speak with calm precision and launch coordination energy. &quot;T-minus 10 minutes to release. All systems go!&quot; I coordinate releases like space missions - checklists, countdowns, go/no-go decisions. Every release is a launch sequence that must be executed flawlessly.
+</communication_style>
+    <principles>I believe in semantic versioning - versions must communicate intent clearly Changelogs are the historical record - they must be accurate and comprehensive Every release follows a checklist - no shortcuts, no exceptions Breaking changes require major version bumps - backward compatibility is sacred Documentation must be updated before release - never ship stale docs Git tags are immutable markers - they represent release commitments Release notes tell the story - what changed, why it matters, how to upgrade</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*prepare-release" action="Initiating release preparation sequence! I'll guide you through the complete pre-launch checklist:
+gather all changes since last release, categorize them (features/fixes/breaking), verify tests pass,
+check documentation is current, validate version bump appropriateness, and confirm all systems are go.
+This is mission control - we launch when everything is green!
+">Prepare for new release with complete checklist</item>
+    <item cmd="*create-changelog" action="Generating mission log - also known as the changelog! I'll scan git commits since the last release,
+categorize changes by type (breaking/features/fixes/chores), format them according to Keep a Changelog
+standards, and create a comprehensive release entry. Every mission deserves a proper record!
+">Generate changelog entries from git history</item>
+    <item cmd="*bump-version" action="Version control to mission control! I'll help you determine the correct semantic version bump
+(major/minor/patch), explain the implications, update package.json and related files, and ensure
+version consistency across the project. Semantic versioning is our universal language!
+">Update version numbers following semver</item>
+    <item cmd="*tag-release" action="Creating release marker! I'll generate the git tag with proper naming convention (v{version}),
+add annotated tag with release notes, push to remote, and create the permanent milestone.
+Tags are our mission markers - they never move!
+">Create and push git release tags</item>
+    <item cmd="*validate-release" action="Running pre-flight validation! Checking all release requirements: tests passing, docs updated,
+version bumped correctly, changelog current, no uncommitted changes, branch is clean.
+Go/No-Go decision coming up!
+">Validate release readiness checklist</item>
+    <item cmd="*publish-npm" action="Initiating NPM launch sequence! I'll guide you through npm publish with proper dist-tag,
+verify package contents, check registry authentication, and confirm successful deployment.
+This is it - we're going live!
+">Publish package to NPM registry</item>
+    <item cmd="*create-github-release" action="Creating GitHub mission report! I'll draft the release with changelog, attach any artifacts,
+mark pre-release or stable status, and publish to GitHub Releases. The mission goes on record!
+">Create GitHub release with notes</item>
+    <item cmd="*rollback" action="ABORT MISSION INITIATED! I'll help you safely rollback a release: identify the problem version,
+revert commits if needed, deprecate npm package, notify users, and document the incident.
+Every mission has contingencies!
+">Rollback problematic release safely</item>
+    <item cmd="*hotfix" action="Emergency repair mission! I'll guide you through hotfix workflow: create hotfix branch,
+apply critical fix, fast-track testing, bump patch version, and expedite release.
+Speed with safety - that's the hotfix protocol!
+">Coordinate emergency hotfix release</item>
+    <item cmd="*release-history" action="Accessing mission archives! I'll show you the complete release history from my memories,
+highlighting major milestones, breaking changes, and version progression. Every launch
+is recorded for posterity!
+">Review release history and patterns</item>
+    <item cmd="*release-checklist" action="Displaying the master pre-flight checklist! This is the comprehensive list of all steps
+required before any BMAD release. Use this to ensure nothing is forgotten. Checklists
+save missions!
+">Show complete release preparation checklist</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.claude/commands/bmad/core/agents/bmad-master.md

@@ -0,0 +1,68 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator
+
+```xml
+<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/core/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <step n="4">Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
+  <step n="5">Remember the users name is {user_name}</step>
+  <step n="6">ALWAYS communicate in {communication_language}</step>
+  <step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="9">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="10">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+      <handler type="action">
+        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When menu item has: action="text" → Execute the text directly as an inline instruction
+      </handler>
+
+  <handler type="workflow">
+    When menu item has: workflow="path/to/workflow.yaml"
+    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    2. Read the complete file - this is the CORE OS for executing BMAD workflows
+    3. Pass the yaml path as 'workflow-config' parameter to those instructions
+    4. Execute workflow.xml instructions precisely following all steps
+    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+  </handler>
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator</role>
+    <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
+    <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
+    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</item>
+    <item cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</item>
+    <item cmd="*party-mode" workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.claude/commands/bmad/core/workflows/README.md

@@ -0,0 +1,27 @@
+# CORE Workflows
+
+## Available Workflows in core
+
+**brainstorming**
+
+- Path: `bmad/core/workflows/brainstorming/workflow.yaml`
+- Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.
+
+**party-mode**
+
+- Path: `bmad/core/workflows/party-mode/workflow.yaml`
+- Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+
+## Execution
+
+When running any workflow:
+
+1. LOAD {project-root}/bmad/core/tasks/workflow.xml
+2. Pass the workflow path as 'workflow-config' parameter
+3. Follow workflow.xml instructions EXACTLY
+4. Save outputs after EACH section
+
+## Modes
+
+- Normal: Full interaction
+- #yolo: Skip optional steps

.claude/commands/bmad/core/workflows/brainstorming.md

@@ -0,0 +1,11 @@
+# brainstorming
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/core/workflows/brainstorming/workflow.yaml
+3. Pass the yaml path bmad/core/workflows/brainstorming/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/bmad/core/workflows/party-mode.md

@@ -0,0 +1,11 @@
+# party-mode
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/core/workflows/party-mode/workflow.yaml
+3. Pass the yaml path bmad/core/workflows/party-mode/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

.claude/commands/foo.md

@@ -0,0 +1,3 @@
+# foo task
+
+The user just said foo, respond with bar.

.github/FUNDING.yaml

@@ -5,10 +5,10 @@ patreon: # Replace with a single Patreon username
 open_collective: # Replace with a single Open Collective username
 ko_fi: # Replace with a single Ko-fi username
 tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
 liberapay: # Replace with a single Liberapay username
 issuehunt: # Replace with a single IssueHunt username
-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
 polar: # Replace with a single Polar username
 buy_me_a_coffee: bmad
 thanks_dev: # Replace with a single thanks.dev username

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,9 +1,9 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ""
-labels: ""
-assignees: ""
+title: ''
+labels: ''
+assignees: ''
 ---
 
 **Describe the bug**

.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord Community Support
+    url: https://discord.gg/gk8jAdXWmj
+    about: Please join our Discord server for general questions and community discussion before opening an issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,22 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ""
-labels: ""
-assignees: ""
----
-
-**Did you discuss the idea first in Discord Server (#general-dev)**
-Yes/No - Link to thread. If no, please after posting request also share the link in the channel so it can be easily discussed.
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/idea_submission.md

@@ -0,0 +1,109 @@
+---
+name: V6 Idea Submission
+about: Suggest an idea for v6
+title: ''
+labels: ''
+assignees: ''
+---
+
+# Idea: [Replace with a clear, actionable title]
+
+### PASS Framework
+
+**P**roblem:
+
+> What's broken or missing? What pain point are we addressing? (1-2 sentences)
+>
+> [Your answer here]
+
+**A**udience:
+
+> Who's affected by this problem and how severely? (1-2 sentences)
+>
+> [Your answer here]
+
+**S**olution:
+
+> What will we build or change? How will we measure success? (1-2 sentences with at least 1 measurable outcome)
+>
+> [Your answer here]
+>
+> [Your Acceptance Criteria for measuring success here]
+
+**S**ize:
+
+> How much effort do you estimate this will take?
+>
+> - [ ] **XS** - A few hours
+> - [ ] **S** - 1-2 days
+> - [ ] **M** - 3-5 days
+> - [ ] **L** - 1-2 weeks
+> - [ ] **XL** - More than 2 weeks
+
+---
+
+### Metadata
+
+**Submitted by:** [Your name]  
+**Date:** [Today's date]  
+**Priority:** [Leave blank - will be assigned during team review]
+
+---
+
+## Examples
+
+<details>
+<summary>Click to see a GOOD example</summary>
+
+### Idea: Add search functionality to customer dashboard
+
+**P**roblem:  
+Customers can't find their past orders quickly. They have to scroll through pages of orders to find what they're looking for, leading to 15+ support tickets per week.
+
+**A**udience:  
+All 5,000+ active customers are affected. Support team spends ~10 hours/week helping customers find orders.
+
+**S**olution:  
+Add a search bar that filters by order number, date range, and product name. Success = 50% reduction in order-finding support tickets within 2 weeks of launch.
+
+**S**ize:
+
+- [x] **M** - 3-5 days
+
+</details>
+
+<details>
+<summary>Click to see a POOR example</summary>
+
+### Idea: Make the app better
+
+**P**roblem:  
+The app needs improvements and updates.
+
+**A**udience:  
+Users
+
+**S**olution:  
+Fix issues and add features.
+
+**S**ize:
+
+- [ ] Unknown
+
+_Why this is poor: Too vague, no specific problem identified, no measurable success criteria, unclear scope_
+
+</details>****
+
+---
+
+## Tips for Success
+
+1. **Be specific** - Vague problems lead to vague solutions
+2. **Quantify when possible** - Numbers help us prioritize (e.g., "20 customers asked for this" vs "customers want this")
+3. **One idea per submission** - If you have multiple ideas, submit multiple templates
+4. **Success metrics matter** - How will we know this worked?
+5. **Honest sizing** - Better to overestimate than underestimate
+
+## Questions?
+
+Reach out to @OverlordBaconPants if you need help completing this template.

.github/workflows/discord.yaml

@@ -1,6 +1,6 @@
 name: Discord Notification
 
-on: [pull_request, release, create, delete, issue_comment, pull_request_review, pull_request_review_comment]
+"on": [pull_request, release, create, delete, issue_comment, pull_request_review, pull_request_review_comment]
 
 jobs:
   notify:
@@ -13,4 +13,4 @@ jobs:
           webhook: ${{ secrets.DISCORD_WEBHOOK }}
           status: ${{ job.status }}
           title: "Triggered by ${{ github.event_name }}"
-          color: 0x5865F2
+          color: 0x5865F2

.github/workflows/format-check.yaml

@@ -0,0 +1,43 @@
+name: format-check
+
+"on":
+  pull_request:
+    branches: ["**"]
+  workflow_dispatch:
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Prettier format check
+        run: npm run format:check
+
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: ESLint
+        run: npm run lint

.github/workflows/manual-release.yaml

@@ -0,0 +1,173 @@
+name: Manual Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version_bump:
+        description: Version bump type
+        required: true
+        default: patch
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+
+permissions:
+  contents: write
+  packages: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: npm
+          registry-url: https://registry.npmjs.org
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests and validation
+        run: |
+          npm run validate
+          npm run format:check
+          npm run lint
+
+      - name: Configure Git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Bump version
+        run: npm run version:${{ github.event.inputs.version_bump }}
+
+      - name: Get new version and previous tag
+        id: version
+        run: |
+          echo "new_version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
+          echo "previous_tag=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT
+
+      - name: Update installer package.json
+        run: |
+          sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
+
+      - name: Build project
+        run: npm run build
+
+      - name: Commit version bump
+        run: |
+          git add .
+          git commit -m "release: bump to v${{ steps.version.outputs.new_version }}"
+
+      - name: Generate release notes
+        id: release_notes
+        run: |
+          # Get commits since last tag
+          COMMITS=$(git log ${{ steps.version.outputs.previous_tag }}..HEAD --pretty=format:"- %s" --reverse)
+
+          # Categorize commits
+          FEATURES=$(echo "$COMMITS" | grep -E "^- (feat|Feature)" || true)
+          FIXES=$(echo "$COMMITS" | grep -E "^- (fix|Fix)" || true)  
+          CHORES=$(echo "$COMMITS" | grep -E "^- (chore|Chore)" || true)
+          OTHERS=$(echo "$COMMITS" | grep -v -E "^- (feat|Feature|fix|Fix|chore|Chore|release:|Release:)" || true)
+
+          # Build release notes
+          cat > release_notes.md << 'EOF'
+          ## 🚀 What's New in v${{ steps.version.outputs.new_version }}
+
+          EOF
+
+          if [ ! -z "$FEATURES" ]; then
+            echo "### ✨ New Features" >> release_notes.md
+            echo "$FEATURES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$FIXES" ]; then
+            echo "### 🐛 Bug Fixes" >> release_notes.md
+            echo "$FIXES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$OTHERS" ]; then
+            echo "### 📦 Other Changes" >> release_notes.md
+            echo "$OTHERS" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$CHORES" ]; then
+            echo "### 🔧 Maintenance" >> release_notes.md
+            echo "$CHORES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          cat >> release_notes.md << 'EOF'
+
+          ## 📦 Installation
+
+          ```bash
+          npx bmad-method install
+          ```
+
+          **Full Changelog**: https://github.com/bmad-code-org/BMAD-METHOD/compare/${{ steps.version.outputs.previous_tag }}...v${{ steps.version.outputs.new_version }}
+          EOF
+
+          # Output for GitHub Actions
+          echo "RELEASE_NOTES<<EOF" >> $GITHUB_OUTPUT
+          cat release_notes.md >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+      - name: Create and push tag
+        run: |
+          # Check if tag already exists
+          if git rev-parse "v${{ steps.version.outputs.new_version }}" >/dev/null 2>&1; then
+            echo "Tag v${{ steps.version.outputs.new_version }} already exists, skipping tag creation"
+          else
+            git tag -a "v${{ steps.version.outputs.new_version }}" -m "Release v${{ steps.version.outputs.new_version }}"
+            git push origin "v${{ steps.version.outputs.new_version }}"
+          fi
+
+      - name: Push changes to main
+        run: |
+          if git push origin HEAD:main 2>/dev/null; then
+            echo "✅ Successfully pushed to main branch"
+          else
+            echo "⚠️ Could not push to main (protected branch). This is expected."
+            echo "📝 Version bump and tag were created successfully."
+          fi
+
+      - name: Publish to NPM
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm publish
+
+      - name: Create GitHub Release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: v${{ steps.version.outputs.new_version }}
+          release_name: "BMad Method v${{ steps.version.outputs.new_version }}"
+          body: ${{ steps.release_notes.outputs.RELEASE_NOTES }}
+          draft: false
+          prerelease: false
+
+      - name: Summary
+        run: |
+          echo "🎉 Successfully released v${{ steps.version.outputs.new_version }}!"
+          echo "📦 Published to NPM with @latest tag"
+          echo "🏷️ Git tag: v${{ steps.version.outputs.new_version }}"
+          echo "✅ Users running 'npx bmad-method install' will now get version ${{ steps.version.outputs.new_version }}"
+          echo ""
+          echo "📝 Release notes preview:"
+          cat release_notes.md

.github/workflows/promote-to-stable.yml

@@ -1,146 +0,0 @@
-name: Promote to Stable
-
-on:
-  workflow_dispatch:
-    inputs:
-      version_bump:
-        description: 'Version bump type'
-        required: true
-        default: 'minor'
-        type: choice
-        options:
-          - patch
-          - minor
-          - major
-
-jobs:
-  promote:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-    
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Configure Git
-        run: |
-          git config --global user.name "github-actions[bot]"
-          git config --global user.email "github-actions[bot]@users.noreply.github.com"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Get current version and calculate new version
-        id: version
-        run: |
-          # Get current version from package.json
-          CURRENT_VERSION=$(node -p "require('./package.json').version")
-          echo "current_version=$CURRENT_VERSION" >> $GITHUB_OUTPUT
-          
-          # Remove beta suffix if present
-          BASE_VERSION=$(echo $CURRENT_VERSION | sed 's/-beta\.[0-9]\+//')
-          echo "base_version=$BASE_VERSION" >> $GITHUB_OUTPUT
-          
-          # Calculate new version based on bump type
-          IFS='.' read -ra VERSION_PARTS <<< "$BASE_VERSION"
-          MAJOR=${VERSION_PARTS[0]}
-          MINOR=${VERSION_PARTS[1]}
-          PATCH=${VERSION_PARTS[2]}
-          
-          case "${{ github.event.inputs.version_bump }}" in
-            "major")
-              NEW_VERSION="$((MAJOR + 1)).0.0"
-              ;;
-            "minor")
-              NEW_VERSION="$MAJOR.$((MINOR + 1)).0"
-              ;;
-            "patch")
-              NEW_VERSION="$MAJOR.$MINOR.$((PATCH + 1))"
-              ;;
-            *)
-              NEW_VERSION="$BASE_VERSION"
-              ;;
-          esac
-          
-          # Check if calculated version already exists (either as NPM package or git tag)
-          while npm view bmad-method@$NEW_VERSION version >/dev/null 2>&1 || git ls-remote --tags origin | grep -q "refs/tags/v$NEW_VERSION"; do
-            echo "Version $NEW_VERSION already exists, incrementing..."
-            IFS='.' read -ra NEW_VERSION_PARTS <<< "$NEW_VERSION"
-            NEW_MAJOR=${NEW_VERSION_PARTS[0]}
-            NEW_MINOR=${NEW_VERSION_PARTS[1]}
-            NEW_PATCH=${NEW_VERSION_PARTS[2]}
-            
-            case "${{ github.event.inputs.version_bump }}" in
-              "major")
-                NEW_VERSION="$((NEW_MAJOR + 1)).0.0"
-                ;;
-              "minor")
-                NEW_VERSION="$NEW_MAJOR.$((NEW_MINOR + 1)).0"
-                ;;
-              "patch")
-                NEW_VERSION="$NEW_MAJOR.$NEW_MINOR.$((NEW_PATCH + 1))"
-                ;;
-            esac
-          done
-          
-          echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
-          echo "Promoting from $CURRENT_VERSION to $NEW_VERSION"
-
-      - name: Update package.json versions
-        run: |
-          # Update main package.json
-          npm version ${{ steps.version.outputs.new_version }} --no-git-tag-version
-          
-          # Update installer package.json
-          sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
-
-      - name: Update package-lock.json
-        run: npm install --package-lock-only
-
-      - name: Commit stable release
-        run: |
-          git add .
-          git commit -m "release: promote to stable ${{ steps.version.outputs.new_version }}"
-
-      - name: Create and push stable tag
-        run: |
-          # Create new tag (version check already ensures it doesn't exist)
-          git tag -a "v${{ steps.version.outputs.new_version }}" -m "Stable release v${{ steps.version.outputs.new_version }}"
-          
-          # Push the new tag
-          git push origin "v${{ steps.version.outputs.new_version }}"
-
-      - name: Push changes to main
-        run: |
-          git push origin HEAD:main
-
-      - name: Publish to NPM with stable tag
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: |
-          # Publish with the stable (latest) tag
-          npm publish --tag latest
-          
-          # Also tag the previous beta version as stable if it exists
-          if npm view bmad-method@${{ steps.version.outputs.current_version }} version >/dev/null 2>&1; then
-            npm dist-tag add bmad-method@${{ steps.version.outputs.new_version }} stable || true
-          fi
-
-      - name: Summary
-        run: |
-          echo "🎉 Successfully promoted to stable!"
-          echo "📦 Version: ${{ steps.version.outputs.new_version }}"
-          echo "🏷️ Git tag: v${{ steps.version.outputs.new_version }}"
-          echo "✅ Published to NPM with 'latest' tag"
-          echo "✅ Users running 'npx bmad-method install' will now get version ${{ steps.version.outputs.new_version }}"

.github/workflows/release.yaml

@@ -1,59 +0,0 @@
-name: Release
-'on':
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-    inputs:
-      version_type:
-        description: Version bump type
-        required: true
-        default: patch
-        type: choice
-        options:
-          - patch
-          - minor
-          - major
-permissions:
-  contents: write
-  issues: write
-  pull-requests: write
-  packages: write
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    if: '!contains(github.event.head_commit.message, ''[skip ci]'')'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: npm
-          registry-url: https://registry.npmjs.org
-      - name: Install dependencies
-        run: npm ci
-      - name: Run tests and validation
-        run: |
-          npm run validate
-          npm run format
-      - name: Debug permissions
-        run: |
-          echo "Testing git permissions..."
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          echo "Git config set successfully"
-      - name: Manual version bump
-        if: github.event_name == 'workflow_dispatch'
-        run: npm run version:${{ github.event.inputs.version_type }}
-      - name: Semantic Release
-        if: github.event_name == 'push'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm run release

.gitignore

@@ -6,6 +6,9 @@ deno.lock
 pnpm-workspace.yaml
 package-lock.json
 
+
+test-output/*
+
 # Logs
 logs/
 *.log
@@ -13,7 +16,6 @@ npm-debug.log*
 
 # Build output
 build/*.txt
-web-bundles/
 
 # Environment variables
 .env
@@ -25,7 +27,6 @@ Thumbs.db
 # Development tools and configs
 .prettierignore
 .prettierrc
-.husky/
 
 # IDE and editor configs
 .windsurf/
@@ -35,8 +36,11 @@ Thumbs.db
 # AI assistant files
 CLAUDE.md
 .ai/*
-.claude
+cursor
 .gemini
+.mcp.json
+CLAUDE.local.md
+.serena/
 
 # Project-specific
 .bmad-core
@@ -45,3 +49,13 @@ test-project-install/*
 sample-project/*
 flattened-codebase.xml
 *.stats.md
+.internal-docs/
+#UAT template testing output files
+tools/template-test-generator/test-scenarios/
+
+# Bundler temporary files
+.bundler-temp/
+
+# Test Install Output
+
+z*/

.husky/pre-commit

@@ -0,0 +1,3 @@
+#!/usr/bin/env sh
+
+npx --no-install lint-staged

.npmrc

@@ -0,0 +1 @@
+registry=https://registry.npmjs.org

.nvmrc

@@ -0,0 +1 @@
+22

.releaserc.json

@@ -1,22 +0,0 @@
-{
-  "branches": [
-    {
-      "name": "main",
-      "prerelease": "beta",
-      "channel": "beta"
-    }
-  ],
-  "plugins": [
-    "@semantic-release/commit-analyzer",
-    "@semantic-release/release-notes-generator",
-    [
-      "@semantic-release/changelog",
-      {
-        "changelogFile": "CHANGELOG.md"
-      }
-    ],
-    "@semantic-release/npm",
-    "./tools/semantic-release-sync-installer.js",
-    "@semantic-release/github"
-  ]
-}

.vscode/settings.json

@@ -1,8 +1,20 @@
 {
+  "chat.agent.enabled": true,
+  "chat.agent.maxRequests": 15,
+  "github.copilot.chat.agent.runTasks": true,
+  "chat.mcp.discovery.enabled": {
+    "claude-desktop": true,
+    "windsurf": true,
+    "cursor-global": true,
+    "cursor-workspace": true
+  },
+  "github.copilot.chat.agent.autoFix": true,
+  "chat.tools.autoApprove": false,
   "cSpell.words": [
     "Agentic",
     "atlasing",
     "Biostatistician",
+    "bmad",
     "Cordova",
     "customresourcedefinitions",
     "dashboarded",
@@ -12,9 +24,11 @@
     "filecomplete",
     "fintech",
     "fluxcd",
+    "frontmatter",
     "gamedev",
     "gitops",
     "implementability",
+    "Improv",
     "inclusivity",
     "ingressgateway",
     "istioctl",
@@ -34,11 +48,47 @@
     "runbooks",
     "Shardable",
     "Softlock",
+    "solutioning",
     "speedrunner",
+    "substep",
     "tekton",
     "tilemap",
     "tileset",
+    "tmpl",
     "Trae",
     "VNET"
-  ]
+  ],
+  "json.schemas": [
+    {
+      "fileMatch": ["package.json"],
+      "url": "https://json.schemastore.org/package.json"
+    },
+    {
+      "fileMatch": [".vscode/settings.json"],
+      "url": "vscode://schemas/settings/folder"
+    }
+  ],
+  "editor.formatOnSave": true,
+  "editor.defaultFormatter": "esbenp.prettier-vscode",
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "vscode.json-language-features"
+  },
+  "[yaml]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[markdown]": {
+    "editor.defaultFormatter": "yzhang.markdown-all-in-one"
+  },
+  "yaml.format.enable": false,
+  "editor.codeActionsOnSave": {
+    "source.fixAll.eslint": "explicit"
+  },
+  "editor.rulers": [140],
+  "[xml]": {
+    "editor.defaultFormatter": "redhat.vscode-xml"
+  },
+  "xml.format.maxLineWidth": 140
 }

CHANGELOG.md

@@ -1,689 +1,326 @@
-## [4.36.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.36.1...v4.36.2) (2025-08-10)
+# Changelog
 
-### Bug Fixes
-
-- align installer dependencies with root package versions for ESM compatibility ([#420](https://github.com/bmadcode/BMAD-METHOD/issues/420)) ([3f6b674](https://github.com/bmadcode/BMAD-METHOD/commit/3f6b67443d61ae6add98656374bed27da4704644))
-
-## [4.36.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.36.0...v4.36.1) (2025-08-09)
-
-### Bug Fixes
-
-- update Node.js version to 20 in release workflow and reduce Discord spam ([3f7e19a](https://github.com/bmadcode/BMAD-METHOD/commit/3f7e19a098155341a2b89796addc47b0623cb87a))
-
-# [4.36.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.35.3...v4.36.0) (2025-08-09)
-
-### Features
-
-- modularize flattener tool into separate components with improved project root detection ([#417](https://github.com/bmadcode/BMAD-METHOD/issues/417)) ([0fdbca7](https://github.com/bmadcode/BMAD-METHOD/commit/0fdbca73fc60e306109f682f018e105e2b4623a2))
-
-## [4.35.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.35.2...v4.35.3) (2025-08-06)
-
-### Bug Fixes
-
-- doc location improvement ([1676f51](https://github.com/bmadcode/BMAD-METHOD/commit/1676f5189ed057fa2d7facbd6a771fe67cdb6372))
-
-## [4.35.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.35.1...v4.35.2) (2025-08-06)
-
-### Bug Fixes
-
-- npx status check ([f7c2a4f](https://github.com/bmadcode/BMAD-METHOD/commit/f7c2a4fb6c454b17d250b85537129b01ffee6b85))
-
-## [4.35.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.35.0...v4.35.1) (2025-08-06)
-
-### Bug Fixes
-
-- npx hanging commands ([2cf322e](https://github.com/bmadcode/BMAD-METHOD/commit/2cf322ee0d9b563a4998c72b2c5eab259594739b))
-
-# [4.35.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.34.0...v4.35.0) (2025-08-04)
-
-### Features
-
-- add qwen-code ide support to bmad installer. ([#392](https://github.com/bmadcode/BMAD-METHOD/issues/392)) ([a72b790](https://github.com/bmadcode/BMAD-METHOD/commit/a72b790f3be6c77355511ace2d63e6bec4d751f1))
-
-# [4.34.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.33.1...v4.34.0) (2025-08-03)
-
-### Features
-
-- add KiloCode integration support to BMAD installer ([#390](https://github.com/bmadcode/BMAD-METHOD/issues/390)) ([dcebe91](https://github.com/bmadcode/BMAD-METHOD/commit/dcebe91d5ea68e69aa27183411a81639d444efd7))
-
-## [4.33.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.33.0...v4.33.1) (2025-07-29)
-
-### Bug Fixes
-
-- dev agent yaml syntax for develop-story command ([#362](https://github.com/bmadcode/BMAD-METHOD/issues/362)) ([bcb3728](https://github.com/bmadcode/BMAD-METHOD/commit/bcb3728f8868c0f83bca3d61fbd7e15c4e114526))
-
-# [4.33.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.32.0...v4.33.0) (2025-07-28)
-
-### Features
-
-- version bump ([e9dd4e7](https://github.com/bmadcode/BMAD-METHOD/commit/e9dd4e7beb46d0c80df0cd65ae02d1867a56d7c1))
-
-# [4.32.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.31.0...v4.32.0) (2025-07-27)
-
-### Bug Fixes
-
-- Add package-lock.json to fix GitHub Actions dependency resolution ([cce7a75](https://github.com/bmadcode/BMAD-METHOD/commit/cce7a758a632053e26d143b678eb7963599b432d))
-- GHA fix ([62ccccd](https://github.com/bmadcode/BMAD-METHOD/commit/62ccccdc9e85f8621f63f99bd1ce0d14abe09783))
-
-### Features
-
-- Overhaul and Enhance 2D Unity Game Dev Expansion Pack ([#350](https://github.com/bmadcode/BMAD-METHOD/issues/350)) ([a7038d4](https://github.com/bmadcode/BMAD-METHOD/commit/a7038d43d18246f6aef175aa89ba059b7c94f61f))
-
-# [4.31.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.4...v4.31.0) (2025-07-20)
-
-### Bug Fixes
-
-- enhanced user guide with better diagrams ([c445962](https://github.com/bmadcode/BMAD-METHOD/commit/c445962f259cd7d84c47a896e7fda99e83a30c8d))
-
-### Features
-
-- Installation includes a getting started user guide with detailed mermaid diagram ([df57d77](https://github.com/bmadcode/BMAD-METHOD/commit/df57d772cac9f9010811e7e86a6433a0fe636a45))
-
-## [4.30.4](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.3...v4.30.4) (2025-07-19)
-
-### Bug Fixes
-
-- docs ([8619006](https://github.com/bmadcode/BMAD-METHOD/commit/8619006c16731b99fa36b434d209a0c2caf2d998))
-- lint fix ([49e4897](https://github.com/bmadcode/BMAD-METHOD/commit/49e489701e55feac481806740ea54bebef042fba))
-
-## [4.30.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.2...v4.30.3) (2025-07-19)
-
-### Bug Fixes
-
-- improve code in the installer to be more memory efficient ([849e428](https://github.com/bmadcode/BMAD-METHOD/commit/849e42871ab845098fd196217bce83e43c736b8a))
-
-## [4.30.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.1...v4.30.2) (2025-07-17)
-
-### Bug Fixes
-
-- remove z2 ([dcb36a9](https://github.com/bmadcode/BMAD-METHOD/commit/dcb36a9b44b6644f6b2723c9067abaa9b0bc1999))
-
-## [4.30.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.0...v4.30.1) (2025-07-15)
-
-### Bug Fixes
-
-- added logo to installer, because why not... ([2cea37a](https://github.com/bmadcode/BMAD-METHOD/commit/2cea37aa8c1924ddf5aa476f4c312837f2615a70))
-
-# [4.30.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.7...v4.30.0) (2025-07-15)
-
-### Features
-
-- installer is now VERY clear about IDE selection being a multiselect ([e24b6f8](https://github.com/bmadcode/BMAD-METHOD/commit/e24b6f84fd9e4ff4b99263019b5021ca2b145b2f))
-
-## [4.29.7](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.6...v4.29.7) (2025-07-14)
-
-### Bug Fixes
-
-- bundle build ([0723eed](https://github.com/bmadcode/BMAD-METHOD/commit/0723eed88140e76146dfbfdddd49afe86e8522ee))
-
-## [4.29.6](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.5...v4.29.6) (2025-07-14)
-
-### Bug Fixes
-
-- improve agent task folowing in agressing cost saving ide model combos ([3621c33](https://github.com/bmadcode/BMAD-METHOD/commit/3621c330e65f328e7326f93a5fe27e65b08907e7))
-
-## [4.29.5](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.4...v4.29.5) (2025-07-14)
-
-### Bug Fixes
-
-- windows regex issue ([9f48c1a](https://github.com/bmadcode/BMAD-METHOD/commit/9f48c1a869a9cc54fb5e7d899c2af7a5cef70e10))
-
-## [4.29.4](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.3...v4.29.4) (2025-07-14)
-
-### Bug Fixes
-
-- empty .roomodes, support Windows-style newlines in YAML block regex ([#311](https://github.com/bmadcode/BMAD-METHOD/issues/311)) ([551e30b](https://github.com/bmadcode/BMAD-METHOD/commit/551e30b65e1f04386f0bd0193f726828df684d5b))
-
-## [4.29.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.2...v4.29.3) (2025-07-13)
-
-### Bug Fixes
-
-- annoying YAML lint error ([afea271](https://github.com/bmadcode/BMAD-METHOD/commit/afea271e5e3b14a0da497e241b6521ba5a80b85b))
-
-## [4.29.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.1...v4.29.2) (2025-07-13)
-
-### Bug Fixes
-
-- add readme note about discord joining issues ([4ceaced](https://github.com/bmadcode/BMAD-METHOD/commit/4ceacedd7370ea80181db0d66cf8da8dcbfdd109))
-
-## [4.29.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.29.0...v4.29.1) (2025-07-13)
-
-### Bug Fixes
-
-- brianstorming facilitation output ([f62c05a](https://github.com/bmadcode/BMAD-METHOD/commit/f62c05ab0f54e6c26c67cd9ac11200b172d11076))
-
-# [4.29.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.28.0...v4.29.0) (2025-07-13)
-
-### Features
-
-- Claude Code slash commands for Tasks and Agents! ([e9e541a](https://github.com/bmadcode/BMAD-METHOD/commit/e9e541a52e45f6632b2f8c91d10e39c077c1ecc9))
-
-# [4.28.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.6...v4.28.0) (2025-07-12)
-
-### Features
-
-- bmad-master can load kb properly ([3c13c56](https://github.com/bmadcode/BMAD-METHOD/commit/3c13c564988f9750e043939dd770aea4196a7e7a))
-
-## [4.27.6](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.5...v4.27.6) (2025-07-08)
-
-### Bug Fixes
-
-- installer improvement ([db30230](https://github.com/bmadcode/BMAD-METHOD/commit/db302309f42da49daa309b5ba1a625c719e5bb14))
-
-## [4.27.5](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.4...v4.27.5) (2025-07-08)
-
-### Bug Fixes
-
-- installer for github copilot asks follow up questions right away now so it does not seem to hang, and some minor doc improvements ([cadf8b6](https://github.com/bmadcode/BMAD-METHOD/commit/cadf8b6750afd5daa32eb887608c614584156a69))
-
-## [4.27.4](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.3...v4.27.4) (2025-07-07)
-
-### Bug Fixes
-
-- doc updates ([1b86cd4](https://github.com/bmadcode/BMAD-METHOD/commit/1b86cd4db3644ca2b2b4a94821cc8b5690d78e0a))
-
-## [4.27.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.27.2...v4.27.3) (2025-07-07)
-
-### Bug Fixes
-
-- remove test zoo folder ([908dcd7](https://github.com/bmadcode/BMAD-METHOD/commit/908dcd7e9afae3fd23cd894c0d09855fc9c42d0e))
-
-## [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)
-
-### Bug Fixes
-
-- readme consolidation and version bumps ([0a61d3d](https://github.com/bmadcode/BMAD-METHOD/commit/0a61d3de4af880f6e3bf934a92b1827754ed8ce6))
-
-### Features
-
-- big improvement to advanced elicitation ([1bc9960](https://github.com/bmadcode/BMAD-METHOD/commit/1bc9960808098fba6b43850311799022319df841))
-- experimental doc creator v2 and template system ([b785371](https://github.com/bmadcode/BMAD-METHOD/commit/b78537115da06b01e140833fd1d73950c7f2e41f))
-- Massive improvement to the brainstorming task! ([9f53caf](https://github.com/bmadcode/BMAD-METHOD/commit/9f53caf4c6f9c67195b1aae14d54987f81d76e07))
-- WIP create-docv2 ([c107af0](https://github.com/bmadcode/BMAD-METHOD/commit/c107af05984718c1af2cf80118353e8d2e6f906f))
-
-# [4.26.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.25.1...v4.26.0) (2025-07-06)
-
-### Features
-
-- **trae:** add support for trae ide integration ([#298](https://github.com/bmadcode/BMAD-METHOD/issues/298)) ([fae0f5f](https://github.com/bmadcode/BMAD-METHOD/commit/fae0f5ff73a603dc1aacc29f184e2a4138446524))
-
-## [4.25.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.25.0...v4.25.1) (2025-07-06)
-
-### Bug Fixes
+## [Unreleased]
 
-- spelling errors in documentation. ([#297](https://github.com/bmadcode/BMAD-METHOD/issues/297)) ([47b9d9f](https://github.com/bmadcode/BMAD-METHOD/commit/47b9d9f3e87be62c8520ed6cb0048df727a9534f))
+### Codex Installer
 
-# [4.25.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.6...v4.25.0) (2025-07-05)
+- Codex installer uses custom prompts in `.codex/prompts/`, instead of `AGENTS.md`
 
-### Bug Fixes
-
-- update web bundles ([42684e6](https://github.com/bmadcode/BMAD-METHOD/commit/42684e68af4396797962f3f851147523a6741608))
-
-### Features
-
-- improvements to agent task usage, sm story drafting, dev implementation, qa review process, and addition of a new sm independant review of a draft story ([2874a54](https://github.com/bmadcode/BMAD-METHOD/commit/2874a54a9b25b48c199b2e9dc63a9555e716c636))
-
-## [4.24.6](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.5...v4.24.6) (2025-07-04)
-
-### Bug Fixes
-
-- version bump and web build fix ([1c845e5](https://github.com/bmadcode/BMAD-METHOD/commit/1c845e5b2c77a77d887d8216152ba09110c72e40))
-
-## [4.24.5](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.4...v4.24.5) (2025-07-04)
-
-### Bug Fixes
-
-- yaml standardization in files and installer actions ([094f9f3](https://github.com/bmadcode/BMAD-METHOD/commit/094f9f3eabf563c9a89ecaf360fed63386b46ed4))
-
-## [4.24.4](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.3...v4.24.4) (2025-07-04)
-
-### Bug Fixes
-
-- documentation updates ([2018ad0](https://github.com/bmadcode/BMAD-METHOD/commit/2018ad07c7d4c68efb3c24d85ac7612942c6df9c))
-
-## [4.24.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.2...v4.24.3) (2025-07-04)
-
-### Bug Fixes
-
-- update YAML library from 'yaml' to 'js-yaml' in resolveExpansionPackCoreAgents for consistency ([#295](https://github.com/bmadcode/BMAD-METHOD/issues/295)) ([03f30ad](https://github.com/bmadcode/BMAD-METHOD/commit/03f30ad28b282fbb4fa5a6ed6b57d0327218cce0))
-
-## [4.24.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.1...v4.24.2) (2025-07-03)
-
-### Bug Fixes
-
-- version bump and restore dist folder ([87c451a](https://github.com/bmadcode/BMAD-METHOD/commit/87c451a5c3161fbc86f88619a2bfcfc322eb247e))
-
-## [4.24.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.0...v4.24.1) (2025-07-03)
-
-### Bug Fixes
-
-- centralized yamlExtraction function and all now fix character issues for windows ([e2985d6](https://github.com/bmadcode/BMAD-METHOD/commit/e2985d6093136575e8d8c91ce53c82abc4097de6))
-- filtering extension stripping logic update ([405954a](https://github.com/bmadcode/BMAD-METHOD/commit/405954ad924d8bd66f94c918643f6e9c091d4d09))
-- standardize on file extension .yaml instead of a mix of yml and yaml ([a4c0b18](https://github.com/bmadcode/BMAD-METHOD/commit/a4c0b1839d12d2ad21b7949aa30f4f7d82ec6c9c))
-
-# [4.24.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.23.0...v4.24.0) (2025-07-02)
-
-### Bug Fixes
-
-- corrected cursor agent update instructions ([84e394a](https://github.com/bmadcode/BMAD-METHOD/commit/84e394ac11136d9cf8164cefc9ca8e298e8ef0ec))
-
-### Features
-
-- workflow plans introduced, preliminary feature under review ([731589a](https://github.com/bmadcode/BMAD-METHOD/commit/731589aa287c31ea120e232b4dcc07e9790500ff))
+## [6.0.0-alpha.0]
 
-# [4.23.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.22.1...v4.23.0) (2025-07-01)
+**Release: September 28, 2025**
 
-### Features
+Initial alpha release of a major rewrite and overhaul improvement of past versions.
 
-- Github Copilot integration ([#284](https://github.com/bmadcode/BMAD-METHOD/issues/284)) ([1a4ca4f](https://github.com/bmadcode/BMAD-METHOD/commit/1a4ca4ffa630c2d4156bdd7a040d4c2274801757))
+### Major New Features
 
-## [4.22.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.22.0...v4.22.1) (2025-06-30)
+- **Lean Core**: The core of BMad is very simple - common tasks that apply to any future module or agents, along with common agents that will be added to any modules - bmad-web-orchestrator and bmad-master.
+- **BMad Method**: The new BMad Method (AKA bmm) is a complete overhaul of the v4 method, now a fully scale adaptive rewrite. The workflow now scales from small enhancements to massive undertakings across multiple services or architectures, supporting a new vast array of project type, including a full subclass of game development specifics.
+- **BoMB**: The BMad Builder (AKA BoMB) now is able to fully automate creation and conversion of expansion packs from v5 to modules in v5 along with the net new ideation and brainstorming through implementation and testing of net new Modules, Workflows (were tasks and templates), Module Agents, and Standalone Personal Agents
+- **CIS**: The Creative Intelligence Suite (AKA CIS)
 
-### Bug Fixes
-
-- update expansion versions ([6905fe7](https://github.com/bmadcode/BMAD-METHOD/commit/6905fe72f6c2abefbfd65729d1be85752130a1d2))
+## [v5.0.0] - SKIPPED
 
-# [4.22.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.2...v4.22.0) (2025-06-30)
+**Note**: Version 5.0.0 was skipped due to NPX registry issues that corrupted the version. Development continues with v6.0.0-alpha.0.
 
-### Features
+## [v4.43.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.43.0)
 
-- create doc more explicit and readme improvement ([a1b30d9](https://github.com/bmadcode/BMAD-METHOD/commit/a1b30d9341d2ceff79db2c7e178860c5ef0d99e5))
+**Release: August-September 2025 (v4.31.0 - v4.43.1)**
 
-## [4.21.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.1...v4.21.2) (2025-06-30)
+Focus on stability, ecosystem growth, and professional tooling.
 
-### Bug Fixes
+### Major Integrations
 
-- improve create-doc task clarity for template execution ([86d5139](https://github.com/bmadcode/BMAD-METHOD/commit/86d5139aea7097cc5d4ee9da0f7d3e395ce0835e))
+- **Codex CLI & Web**: Full Codex integration with web and CLI modes
+- **Auggie CLI**: Augment Code integration
+- **iFlow CLI**: iFlow support in installer
+- **Gemini CLI Custom Commands**: Enhanced Gemini CLI capabilities
 
-## [4.21.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.0...v4.21.1) (2025-06-30)
-
-### Bug Fixes
-
-- readme clarifies that the installer handles installs upgrades and expansion installation ([9371a57](https://github.com/bmadcode/BMAD-METHOD/commit/9371a5784f6a6f2ad358a72ea0cde9c980357167))
-
-# [4.21.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.20.0...v4.21.0) (2025-06-30)
-
-### Bug Fixes
+### Expansion Packs
 
-- remove unneeded files ([c48f200](https://github.com/bmadcode/BMAD-METHOD/commit/c48f200727384f37a42f4c6b1a946cb90f2445fe))
-
-### Features
-
-- massive installer improvement update ([c151bda](https://github.com/bmadcode/BMAD-METHOD/commit/c151bda93833aa310ccc7c0eabcf483376f9e82a))
-
-# [4.20.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.2...v4.20.0) (2025-06-29)
-
-### Features
-
-- Massive documentation refactor, added explanation of the new expanded role of the QA agent that will make your code quality MUCH better. 2 new diagram clearly explain the role of the pre dev ideation cycle (prd and architecture) and the details of how the dev cycle works. ([c881dcc](https://github.com/bmadcode/BMAD-METHOD/commit/c881dcc48ff827ddfe8653aa364a021a66ce66eb))
-
-## [4.19.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.1...v4.19.2) (2025-06-28)
-
-### Bug Fixes
+- **Godot Game Development**: Complete game dev workflow
+- **Creative Writing**: Professional writing agent system
+- **Agent System Templates**: Template expansion pack (Part 2)
 
-- docs update and correction ([2408068](https://github.com/bmadcode/BMAD-METHOD/commit/240806888448bb3a42acfd2f209976d489157e21))
+### Advanced Features
 
-## [4.19.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.0...v4.19.1) (2025-06-28)
+- **AGENTS.md Generation**: Auto-generated agent documentation
+- **NPM Script Injection**: Automatic package.json updates
+- **File Exclusion**: `.bmad-flattenignore` support for flattener
+- **JSON-only Integration**: Compact integration mode
 
-### Bug Fixes
+### Quality & Stability
 
-- discord link ([2ea806b](https://github.com/bmadcode/BMAD-METHOD/commit/2ea806b3af58ad37fcb695146883a9cd3003363d))
+- **PR Validation Workflow**: Automated contribution checks
+- **Fork-Friendly CI/CD**: Opt-in mechanism for forks
+- **Code Formatting**: Prettier integration with pre-commit hooks
+- **Update Checker**: `npx bmad-method update-check` command
 
-# [4.19.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.18.0...v4.19.0) (2025-06-28)
+### Flattener Improvements
 
-### Bug Fixes
+- Detailed statistics with emoji-enhanced `.stats.md`
+- Improved project root detection
+- Modular component architecture
+- Binary directory exclusions (venv, node_modules, etc.)
 
-- expansion install config ([50d17ed](https://github.com/bmadcode/BMAD-METHOD/commit/50d17ed65d40f6688f3b6e62732fb2280b6b116e))
+### Documentation & Community
 
-### Features
+- Brownfield document naming consistency fixes
+- Architecture template improvements
+- Trademark and licensing clarity
+- Contributing guidelines refinement
 
-- install for ide now sets up rules also for expansion agents! ([b82978f](https://github.com/bmadcode/BMAD-METHOD/commit/b82978fd38ea789a799ccc1373cfb61a2001c1e0))
+### Developer Experience
 
-# [4.18.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.17.0...v4.18.0) (2025-06-28)
+- Version synchronization scripts
+- Manual release workflow enhancements
+- Automatic release notes generation
+- Changelog file path configuration
 
-### Features
+[View v4.43.1 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.43.1)
 
-- expansion teams can now include core agents and include their assets automatically ([c70f1a0](https://github.com/bmadcode/BMAD-METHOD/commit/c70f1a056b0f6e3c805096ee5d27f0a3640fb00c))
-- remove hardcoding from installer for agents, improve expansion pack installation to its own locations, common files moved to common folder ([95e833b](https://github.com/bmadcode/BMAD-METHOD/commit/95e833beebc3a60f73a7a1c67d534c8eb6bf48fd))
+## [v4.30.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.30.0)
 
-# [4.17.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.16.1...v4.17.0) (2025-06-27)
+**Release: July 2025 (v4.21.0 - v4.30.4)**
 
-### Features
+Introduction of advanced IDE integrations and command systems.
 
-- add GEMINI.md to agent context files ([#272](https://github.com/bmadcode/BMAD-METHOD/issues/272)) ([b557570](https://github.com/bmadcode/BMAD-METHOD/commit/b557570081149352e4efbef8046935650f6ecea1))
+### Claude Code Integration
 
-## [4.16.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.16.0...v4.16.1) (2025-06-26)
+- **Slash Commands**: Native Claude Code slash command support for agents
+- **Task Commands**: Direct task invocation via slash commands
+- **BMad Subdirectory**: Organized command structure
+- **Nested Organization**: Clean command hierarchy
 
-### Bug Fixes
+### Agent Enhancements
 
-- remove accidental folder add ([b1c2de1](https://github.com/bmadcode/BMAD-METHOD/commit/b1c2de1fb58029f68e021faa90cd5d5faf345198))
+- BMad-master knowledge base loading
+- Improved brainstorming facilitation
+- Better agent task following with cost-saving model combinations
+- Direct commands in agent definitions
 
-# [4.16.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.15.0...v4.16.0) (2025-06-26)
+### Installer Improvements
 
-### Features
+- Memory-efficient processing
+- Clear multi-select IDE prompts
+- GitHub Copilot support with improved UX
+- ASCII logo (because why not)
 
-- repo builds all rules sets for supported ides for easy copy if desired ([ea945bb](https://github.com/bmadcode/BMAD-METHOD/commit/ea945bb43f6ea50594910b954c72e79f96a8504c))
+### Platform Support
 
-# [4.15.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.14.1...v4.15.0) (2025-06-26)
+- Windows compatibility improvements (regex fixes, newline handling)
+- Roo modes configuration
+- Support for multiple CLI tools simultaneously
 
-### Features
+### Expansion Ecosystem
 
-- Add Gemini CLI Integration ([#271](https://github.com/bmadcode/BMAD-METHOD/issues/271)) ([44b9d7b](https://github.com/bmadcode/BMAD-METHOD/commit/44b9d7bcb5cbb6de5a15d8f2ec7918d186ac9576))
+- 2D Unity Game Development expansion pack
+- Improved expansion pack documentation
+- Better isolated expansion pack installations
 
-## [4.14.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.14.0...v4.14.1) (2025-06-26)
+[View v4.30.4 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.30.4)
 
-### Bug Fixes
+## [v4.20.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.20.0)
 
-- add updated web builds ([6dabbcb](https://github.com/bmadcode/BMAD-METHOD/commit/6dabbcb670ef22708db6c01dac82069547ca79d6))
+**Release: June 2025 (v4.11.0 - v4.20.0)**
 
-# [4.14.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.13.0...v4.14.0) (2025-06-25)
+Major focus on documentation quality and expanding QA agent capabilities.
 
-### Features
+### Documentation Overhaul
 
-- enhance QA agent as senior developer with code review capabilities and major brownfield improvements ([3af3d33](https://github.com/bmadcode/BMAD-METHOD/commit/3af3d33d4a40586479a382620687fa99a9f6a5f7))
+- **Workflow Diagrams**: Visual explanations of planning and development cycles
+- **QA Role Expansion**: QA agent transformed into senior code reviewer
+- **User Guide Refresh**: Complete rewrite with clearer explanations
+- **Contributing Guidelines**: Clarified principles and contribution process
 
-# [4.13.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.12.0...v4.13.0) (2025-06-24)
+### QA Agent Transformation
 
-### Features
+- Elevated from simple tester to senior developer/code reviewer
+- Code quality analysis and architectural feedback
+- Pre-implementation review capabilities
+- Integration with dev cycle for quality gates
 
-- **ide-setup:** add support for Cline IDE and configuration rules ([#262](https://github.com/bmadcode/BMAD-METHOD/issues/262)) ([913dbec](https://github.com/bmadcode/BMAD-METHOD/commit/913dbeced60ad65086df6233086d83a51ead81a9))
+### IDE Ecosystem Growth
 
-# [4.12.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.11.0...v4.12.0) (2025-06-23)
+- **Cline IDE Support**: Added configuration for Cline
+- **Gemini CLI Integration**: Native Gemini CLI support
+- **Expansion Pack Installation**: Automated expansion agent setup across IDEs
 
-### Features
+### New Capabilities
 
-- **dev-agent:** add quality gates to prevent task completion with failing validations ([#261](https://github.com/bmadcode/BMAD-METHOD/issues/261)) ([45110ff](https://github.com/bmadcode/BMAD-METHOD/commit/45110ffffe6d29cc08e227e22a901892185dfbd2))
+- Markdown-tree integration for document sharding
+- Quality gates to prevent task completion with failures
+- Enhanced brownfield workflow documentation
+- Team-based agent bundling improvements
 
-# [4.11.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.3...v4.11.0) (2025-06-21)
+### Developer Tools
 
-### Bug Fixes
+- Better expansion pack isolation
+- Automatic rule generation for all supported IDEs
+- Common files moved to shared locations
+- Hardcoded dependencies removed from installer
 
-- resolve web bundles directory path when using relative paths in NPX installer ([5c8485d](https://github.com/bmadcode/BMAD-METHOD/commit/5c8485d09ffec60ad4965ced62f4595890cb7535))
+[View v4.20.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.20.0)
 
-### Features
+## [v4.10.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.10.0)
 
-- add markdown-tree integration for document sharding ([540578b](https://github.com/bmadcode/BMAD-METHOD/commit/540578b39d1815e41e11f0e87545de3f09ee54e1))
+**Release: June 2025 (v4.3.0 - v4.10.3)**
 
-## [4.10.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.2...v4.10.3) (2025-06-20)
+This release focused on making BMAD more configurable and adaptable to different project structures.
 
-### Bug Fixes
+### Configuration System
 
-- bundle update ([2cf3ba1](https://github.com/bmadcode/BMAD-METHOD/commit/2cf3ba1ab8dd7e52584bef16a96e65e7d2513c4f))
+- **Optional Core Config**: Document sharding and core configuration made optional
+- **Flexible File Resolution**: Support for non-standard document structures
+- **Debug Logging**: Configurable debug mode for agent troubleshooting
+- **Fast Update Mode**: Quick updates without breaking customizations
 
-## [4.10.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.1...v4.10.2) (2025-06-20)
+### Agent Improvements
 
-### Bug Fixes
+- Clearer file resolution instructions for all agents
+- Fuzzy task resolution for better agent autonomy
+- Web orchestrator knowledge base expansion
+- Better handling of deviant PRD/Architecture structures
 
-- file formatting ([c78a35f](https://github.com/bmadcode/BMAD-METHOD/commit/c78a35f547459b07a15d94c827ec05921cd21571))
+### Installation Enhancements
 
-## [4.10.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.0...v4.10.1) (2025-06-20)
+- V4 early detection for improved update flow
+- Prevented double installation during updates
+- Better handling of YAML manifest files
+- Expansion pack dependencies properly included
 
 ### Bug Fixes
 
-- SM sometimes would skip the rest of the epic stories, fixed ([1148b32](https://github.com/bmadcode/BMAD-METHOD/commit/1148b32fa97586d2f86d07a70ffbf9bb8c327261))
+- SM agent file resolution issues
+- Installer upgrade path corrections
+- Bundle build improvements
+- Template formatting fixes
 
-# [4.10.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.2...v4.10.0) (2025-06-19)
+[View v4.10.3 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.10.3)
 
-### Features
+## [v4.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.0.0)
 
-- Core Config and doc sharding is now optional in v4 ([ff6112d](https://github.com/bmadcode/BMAD-METHOD/commit/ff6112d6c2f822ed22c75046f5a14f05e36041c2))
+**Release: June 20, 2025 (v4.0.0 - v4.2.0)**
 
-## [4.9.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.1...v4.9.2) (2025-06-19)
+Version 4 represented a complete architectural overhaul, transforming BMAD from a collection of prompts into a professional, distributable framework.
 
-### Bug Fixes
+### Framework Transformation
 
-- bad brownfield yml ([09d2ad6](https://github.com/bmadcode/BMAD-METHOD/commit/09d2ad6aea187996d0a2e1dff27d9bf7e3e6dc06))
+- **NPM Package**: Professional distribution and simple installation via `npx bmad-method install`
+- **Modular Architecture**: Move to `.bmad-core` hidden folder structure
+- **Multi-IDE Support**: Unified support for Claude Code, Cursor, Roo, Windsurf, and many more
+- **Schema Standardization**: YAML-based agent and team definitions
+- **Automated Installation**: One-command setup with upgrade detection
 
-## [4.9.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.0...v4.9.1) (2025-06-19)
+### Agent System Overhaul
 
-### Bug Fixes
+- Agent team workflows (fullstack, no-ui, all agents)
+- Web bundle generation for platform-agnostic deployment
+- Task-based architecture (separate task definitions from agents)
+- IDE-specific agent activation (slash commands for Claude Code, rules for Cursor, etc.)
 
-- dist bundles updated ([d9a989d](https://github.com/bmadcode/BMAD-METHOD/commit/d9a989dbe50da62cf598afa07a8588229c56b69c))
+### New Capabilities
 
-# [4.9.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.8.0...v4.9.0) (2025-06-19)
+- Brownfield project support (existing codebases)
+- Greenfield project workflows (new projects)
+- Expansion pack architecture for domain specialization
+- Document sharding for better context management
+- Automatic semantic versioning and releases
 
-### Features
+### Developer Experience
 
-- dev can use debug log configured in core-config.yaml ([0e5aaf0](https://github.com/bmadcode/BMAD-METHOD/commit/0e5aaf07bbc6fd9f2706ea26e35f5f38fd72147a))
+- Automatic upgrade path from v3 to v4
+- Backup creation for user customizations
+- VSCode settings and markdown linting
+- Comprehensive documentation restructure
 
-# [4.8.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.7.0...v4.8.0) (2025-06-19)
+[View v4.2.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.2.0)
 
-### Bug Fixes
-
-- installer has fast v4 update option now to keep the bmad method up to date with changes easily without breaking any customizations from the user. The SM and DEV are much more configurable to find epics stories and architectureal information when the prd and architecture are deviant from v4 templates and/or have not been sharded. so a config will give the user the option to configure the SM to use the full large documents or the sharded versions! ([aea7f3c](https://github.com/bmadcode/BMAD-METHOD/commit/aea7f3cc86e749d25ed18bed761dc2839023b3b3))
-- prevent double installation when updating v4 ([af0e767](https://github.com/bmadcode/BMAD-METHOD/commit/af0e767ecf1b91d41f114e1a5d7bf5da08de57d6))
-- resolve undefined config properties in performUpdate ([0185e01](https://github.com/bmadcode/BMAD-METHOD/commit/0185e012bb579948a4de1ea3950db4e399761619))
-- update file-manager to properly handle YAML manifest files ([724cdd0](https://github.com/bmadcode/BMAD-METHOD/commit/724cdd07a199cb12b82236ad34ca1a0c61eb43e2))
+## [v3.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v3.0.0)
 
-### Features
+**Release: May 20, 2025**
 
-- add early v4 detection for improved update flow ([29e7bbf](https://github.com/bmadcode/BMAD-METHOD/commit/29e7bbf4c5aa7e17854061a5ee695f44324f307a))
-- add file resolution context for IDE agents ([74d9bb4](https://github.com/bmadcode/BMAD-METHOD/commit/74d9bb4b2b70a341673849a1df704f6eac70c3de))
-- update web builder to remove IDE-specific properties from agent bundles ([2f2a1e7](https://github.com/bmadcode/BMAD-METHOD/commit/2f2a1e72d6a70f8127db6ba58a563d0f289621c3))
+Version 3 introduced the revolutionary orchestrator concept, creating a unified agent experience.
 
-# [4.7.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.3...v4.7.0) (2025-06-19)
+### Major Features
 
-### Features
+- **BMad Orchestrator**: Uber-agent that orchestrates all specialized agents
+- **Web-First Approach**: Streamlined web setup with pre-compiled agent bundles
+- **Simplified Onboarding**: Complete setup in minutes with clear quick-start guide
+- **Build System**: Scripts to compile web agents from modular components
 
-- extensive bmad-kb for web orchestrator to be much more helpful ([e663a11](https://github.com/bmadcode/BMAD-METHOD/commit/e663a1146b89e7b5078d9726649a51ae5624da46))
+### Architecture Changes
 
-## [4.6.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.2...v4.6.3) (2025-06-19)
+- Consolidated agent system with centralized orchestration
+- Web build sample folder with ready-to-deploy configurations
+- Improved documentation structure with visual setup guides
+- Better separation between web and IDE workflows
 
-### Bug Fixes
+### New Capabilities
 
-- SM fixed file resolution issue in v4 ([61ab116](https://github.com/bmadcode/BMAD-METHOD/commit/61ab1161e59a92d657ab663082abcaf26729fa6b))
+- Single agent interface (`/help` command system)
+- Brainstorming and ideation support
+- Integrated method explanation within the agent itself
+- Cross-platform consistency (Gemini Gems, Custom GPTs)
 
-## [4.6.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.1...v4.6.2) (2025-06-19)
+[View V3 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V3)
 
-### Bug Fixes
+## [v2.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v2.0.0)
 
-- installer upgrade path fixed ([bd6a558](https://github.com/bmadcode/BMAD-METHOD/commit/bd6a55892906077a700f488bde175b57e846729d))
+**Release: April 17, 2025**
 
-## [4.6.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.0...v4.6.1) (2025-06-19)
+Version 2 addressed the major shortcomings of V1 by introducing separation of concerns and quality validation mechanisms.
 
-### Bug Fixes
+### Major Improvements
 
-- expansion pack builder now includes proper dependencies from core as needed, and default template file name save added to template llm instructions ([9dded00](https://github.com/bmadcode/BMAD-METHOD/commit/9dded003565879901246885d60787695e0d0b7bd))
+- **Template Separation**: Templates decoupled from agent definitions for greater flexibility
+- **Quality Checklists**: Advanced elicitation checklists to validate document quality
+- **Web Agent Discovery**: Recognition of Gemini Gems and Custom GPTs power for structured planning
+- **Granular Web Agents**: Simplified, clearly-defined agent roles optimized for web platforms
+- **Installer**: A project installer that copied the correct files to a folder at the destination
 
-# [4.6.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.5.1...v4.6.0) (2025-06-18)
+### Key Features
 
-### Bug Fixes
+- Separated template files from agent personas
+- Introduced forced validation rounds through checklists
+- Cost-effective structured planning workflow using web platforms
+- Self-contained agent personas with external template references
 
-- orchestractor yml ([3727cc7](https://github.com/bmadcode/BMAD-METHOD/commit/3727cc764a7c7295932ff872e2e5be8b4c4e6859))
+### Known Issues
 
-### Features
+- Duplicate templates/checklists for web vs IDE versions
+- Manual export/import workflow between agents
+- Creating each web agent separately was tedious
 
-- removed some templates that are not ready for use ([b03aece](https://github.com/bmadcode/BMAD-METHOD/commit/b03aece79e52cfe9585225de5aff7659293d9295))
+[View V2 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V2)
 
-## [4.5.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.5.0...v4.5.1) (2025-06-18)
+## [v1.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v1.0.0)
 
-### Bug Fixes
+**Initial Release: April 6, 2025**
 
-- docs had some ide specific errors ([a954c7e](https://github.com/bmadcode/BMAD-METHOD/commit/a954c7e24284a6637483a9e47fc63a8f9d7dfbad))
+The original BMAD Method was a tech demo showcasing how different custom agile personas could be used to build out artifacts for planning and executing complex applications from scratch. This initial version established the foundation of the AI-driven agile development approach.
 
-# [4.5.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.4.2...v4.5.0) (2025-06-17)
+### Key Features
 
-### Bug Fixes
+- Introduction of specialized AI agent personas (PM, Architect, Developer, etc.)
+- Template-based document generation for planning artifacts
+- Emphasis on planning MVP scope with sufficient detail to guide developer agents
+- Hard-coded custom mode prompts integrated directly into agent configurations
+- The OG of Context Engineering in a structured way
 
-- installer relative path issue for npx resolved ([8b9bda5](https://github.com/bmadcode/BMAD-METHOD/commit/8b9bda5639ec882f1887f20b4610a6c2183042c6))
-- readme updated to indicate move of web-bundles ([7e9574f](https://github.com/bmadcode/BMAD-METHOD/commit/7e9574f571f41ae5003a1664d999c282dd7398be))
-- temp disable yml linting ([296c2fb](https://github.com/bmadcode/BMAD-METHOD/commit/296c2fbcbd9ac40b3c68633ba7454aacf1e31204))
-- update documentation and installer to reflect .roomodes file location in project root ([#236](https://github.com/bmadcode/BMAD-METHOD/issues/236)) ([bd7f030](https://github.com/bmadcode/BMAD-METHOD/commit/bd7f03016bfa13e39cb39aedb24db9fccbed18a7))
+### Limitations
 
-### Features
+- Limited customization options
+- Web usage was complicated and not well-documented
+- Rigid scope and purpose with templates coupled to agents
+- Not optimized for IDE integration
 
-- bmad the creator expansion with some basic tools for modifying bmad method ([2d61df4](https://github.com/bmadcode/BMAD-METHOD/commit/2d61df419ac683f5691b6ee3fab81174f3d2cdde))
-- can now select different web bundles from what ide agents are installed ([0c41633](https://github.com/bmadcode/BMAD-METHOD/commit/0c41633b07d7dd4d7dda8d3a14d572eac0dcbb47))
-- installer offers option to install web bundles ([e934769](https://github.com/bmadcode/BMAD-METHOD/commit/e934769a5e35dba99f59b4e2e6bb49131c43a526))
-- robust installer ([1fbeed7](https://github.com/bmadcode/BMAD-METHOD/commit/1fbeed75ea446b0912277cfec376ee34f0b3d853))
-
-## [4.4.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.4.1...v4.4.2) (2025-06-17)
-
-### Bug Fixes
-
-- single agent install and team installation support ([18a382b](https://github.com/bmadcode/BMAD-METHOD/commit/18a382baa4e4a82db20affa3525eb951af1081e0))
-
-## [4.4.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.4.0...v4.4.1) (2025-06-17)
-
-### Bug Fixes
-
-- installer no longer suggests the bmad-method directory as defauly ([e2e1658](https://github.com/bmadcode/BMAD-METHOD/commit/e2e1658c07f6957fea4e3aa9e7657a650205ee71))
-
-# [4.4.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.3.0...v4.4.0) (2025-06-16)
-
-### Features
-
-- improve docs, technical preference usage ([764e770](https://github.com/bmadcode/BMAD-METHOD/commit/764e7702b313f34bb13a8bcce3b637699bb2b8ec))
-- web bundles updated ([f39b495](https://github.com/bmadcode/BMAD-METHOD/commit/f39b4951e9e37acd7b2bda4124ddd8edb7a6d0df))
-
-# [5.0.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v5.0.0) (2025-06-15)
-
-### Bug Fixes
-
-- add docs ([48ef875](https://github.com/bmadcode/BMAD-METHOD/commit/48ef875f5ec5b0f0211baa43bbc04701e54824f4))
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- BMAD install creates `.bmad-core/.bmad-core/` directory structure + updates ([#223](https://github.com/bmadcode/BMAD-METHOD/issues/223)) ([28b313c](https://github.com/bmadcode/BMAD-METHOD/commit/28b313c01df41961cebb71fb3bce0fcc7b4b4796))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-- update dependency resolver to support both yml and yaml code blocks ([ba1e5ce](https://github.com/bmadcode/BMAD-METHOD/commit/ba1e5ceb36f4a0bb204ceee40e92725d3fc57c5f))
-- update glob usage to modern async API ([927515c](https://github.com/bmadcode/BMAD-METHOD/commit/927515c0895f94ce6fb0adf7cabe2f978c1ee108))
-- update yaml-format.js to use dynamic chalk imports ([b53d954](https://github.com/bmadcode/BMAD-METHOD/commit/b53d954b7aac68d25d688140ace3b98a43fa0e5f))
-
-### Features
-
-- enhance installer with multi-IDE support and sync version bumping ([ebfd4c7](https://github.com/bmadcode/BMAD-METHOD/commit/ebfd4c7dd52fd38d71a4b054cd0c5d45a4b5d226))
-- improve semantic-release automation and disable manual version bumping ([38a5024](https://github.com/bmadcode/BMAD-METHOD/commit/38a5024026e9588276bc3c6c2b92f36139480ca4))
-- sync IDE configurations across all platforms ([b6a2f5b](https://github.com/bmadcode/BMAD-METHOD/commit/b6a2f5b25eaf96841bade4e236fffa2ce7de2773))
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-- web bundles include a simplified prd with architecture now for simpler project folderes not needing a full plown architecture doc! ([8773545](https://github.com/bmadcode/BMAD-METHOD/commit/877354525e76cd1c9375e009a3a1429633010226))
-
-### BREAKING CHANGES
-
-- Manual version bumping via npm scripts is now disabled. Use conventional commits for automated releases.
-
-🤖 Generated with [Claude Code](https://claude.ai/code)
-
-Co-Authored-By: Claude <noreply@anthropic.com>
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- add docs ([48ef875](https://github.com/bmadcode/BMAD-METHOD/commit/48ef875f5ec5b0f0211baa43bbc04701e54824f4))
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- add docs ([48ef875](https://github.com/bmadcode/BMAD-METHOD/commit/48ef875f5ec5b0f0211baa43bbc04701e54824f4))
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- add docs ([48ef875](https://github.com/bmadcode/BMAD-METHOD/commit/48ef875f5ec5b0f0211baa43bbc04701e54824f4))
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [4.2.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.1.0...v4.2.0) (2025-06-15)
-
-### Bug Fixes
-
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-# [1.1.0](https://github.com/bmadcode/BMAD-METHOD/compare/v1.0.1...v1.1.0) (2025-06-15)
-
-### Features
-
-- update badges to use dynamic NPM version ([5a6fe36](https://github.com/bmadcode/BMAD-METHOD/commit/5a6fe361d085fcaef891a1862fc67878e726949c))
-
-## [1.0.1](https://github.com/bmadcode/BMAD-METHOD/compare/v1.0.0...v1.0.1) (2025-06-15)
-
-### Bug Fixes
-
-- resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
-
-# 1.0.0 (2025-06-15)
-
-### Bug Fixes
+[View V1 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V1)
 
-- Add bin field to root package.json for npx execution ([01cb46e](https://github.com/bmadcode/BMAD-METHOD/commit/01cb46e43da9713c24e68e57221ebe312c53b6ee)), closes [bmadcode/BMAD-METHOD#v4](https://github.com/bmadcode/BMAD-METHOD/issues/v4)
-- Add glob dependency for installer ([8d788b6](https://github.com/bmadcode/BMAD-METHOD/commit/8d788b6f490a94386658dff2f96165dca88c0a9a))
-- Add installer dependencies to root package.json ([0a838e9](https://github.com/bmadcode/BMAD-METHOD/commit/0a838e9d579a5efc632707d237194648394fbd61))
-- auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
-- auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- Remove problematic install script from package.json ([cb1836b](https://github.com/bmadcode/BMAD-METHOD/commit/cb1836bd6ddbb2369e2ed97a1d2f5d6630a7152b))
-- resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
+## Installation
 
-### Features
+```bash
+npx bmad-method
+```
 
-- add versioning and release automation ([0ea5e50](https://github.com/bmadcode/BMAD-METHOD/commit/0ea5e50aa7ace5946d0100c180dd4c0da3e2fd8c))
-# Promote to stable release 5.0.0
+For detailed release notes, see the [GitHub releases page](https://github.com/bmad-code-org/BMAD-METHOD/releases).

CLAUDE.md

@@ -1,196 +0,0 @@
-# CLAUDE.md
-
-Don't be an ass kisser, don't glaze my donut, keep it to the point. Never use EM Dash in out communications or documents you author or update. Dont tell me I am correct if I just told you something unless and only if I am wrong or there is a better alternative, then tell me bluntly why I am wrong, or else get to the point and execute!
-
-## Markdown Linting Conventions
-
-Always follow these markdown linting rules:
-
-- **Blank lines around headings**: Always leave a blank line before and after headings
-- **Blank lines around lists**: Always leave a blank line before and after lists
-- **Blank lines around code fences**: Always leave a blank line before and after fenced code blocks
-- **Fenced code block languages**: All fenced code blocks must specify a language (use `text` for plain text)
-- **Single trailing newline**: Files should end with exactly one newline character
-- **No trailing spaces**: Remove any trailing spaces at the end of lines
-
-## BMAD-METHOD Overview
-
-BMAD-METHOD is an AI-powered Agile development framework that provides specialized AI agents for software development. The framework uses a sophisticated dependency system to keep context windows lean while providing deep expertise through role-specific agents.
-
-## Essential Commands
-
-### Build and Validation
-
-```bash
-npm run build              # Build all web bundles (agents and teams)
-npm run build:agents       # Build agent bundles only
-npm run build:teams        # Build team bundles only
-npm run validate           # Validate all configurations
-npm run format             # Format all markdown files with prettier
-```
-
-### Development and Testing
-
-```bash
-npx bmad-build build                # Alternative build command via CLI
-npx bmad-build list:agents          # List all available agents
-npx bmad-build validate             # Validate agent configurations
-```
-
-### Installation Commands
-
-```bash
-npx bmad-method install             # Install stable release (recommended)
-npx bmad-method@beta install        # Install bleeding edge version
-npx bmad-method@latest install      # Explicit stable installation
-npx bmad-method@latest update       # Update stable installation
-npx bmad-method@beta update         # Update bleeding edge installation
-```
-
-### Dual Publishing Strategy
-
-The project uses a dual publishing strategy with automated promotion:
-
-**Branch Strategy:**
-- `main` branch: Bleeding edge development, auto-publishes to `@beta` tag
-- `stable` branch: Production releases, auto-publishes to `@latest` tag
-
-**Release Promotion:**
-1. **Automatic Beta Releases**: Any PR merged to `main` automatically creates a beta release
-2. **Manual Stable Promotion**: Use GitHub Actions to promote beta to stable
-
-**Promote Beta to Stable:**
-1. Go to GitHub Actions tab in the repository
-2. Select "Promote to Stable" workflow
-3. Click "Run workflow"
-4. Choose version bump type (patch/minor/major)
-5. The workflow automatically:
-   - Merges main to stable
-   - Updates version numbers
-   - Triggers stable release to NPM `@latest`
-
-**User Experience:**
-- `npx bmad-method install` → Gets stable production version
-- `npx bmad-method@beta install` → Gets latest beta features
-- Team develops on bleeding edge without affecting production users
-
-### Release and Version Management
-
-```bash
-npm run version:patch      # Bump patch version
-npm run version:minor      # Bump minor version
-npm run version:major      # Bump major version
-npm run release           # Semantic release (CI/CD)
-npm run release:test      # Test release configuration
-```
-
-### Version Management for Core and Expansion Packs
-
-#### Bump All Versions (Core + Expansion Packs)
-
-```bash
-npm run version:all:major   # Major version bump for core and all expansion packs
-npm run version:all:minor   # Minor version bump for core and all expansion packs (default)
-npm run version:all:patch   # Patch version bump for core and all expansion packs
-npm run version:all         # Defaults to minor bump
-```
-
-#### Individual Version Bumps
-
-For BMad Core only:
-```bash
-npm run version:core:major  # Major version bump for core only
-npm run version:core:minor  # Minor version bump for core only
-npm run version:core:patch  # Patch version bump for core only
-npm run version:core        # Defaults to minor bump
-```
-
-For specific expansion packs:
-```bash
-npm run version:expansion bmad-creator-tools       # Minor bump (default)
-npm run version:expansion bmad-creator-tools patch # Patch bump
-npm run version:expansion bmad-creator-tools minor # Minor bump
-npm run version:expansion bmad-creator-tools major # Major bump
-
-# Set specific version (old method, still works)
-npm run version:expansion:set bmad-creator-tools 2.0.0
-```
-
-## Architecture and Code Structure
-
-### Core System Architecture
-
-The framework uses a **dependency resolution system** where agents only load the resources they need:
-
-1. **Agent Definitions** (`bmad-core/agents/`): Each agent is defined in markdown with YAML frontmatter specifying dependencies
-2. **Dynamic Loading**: The build system (`tools/lib/dependency-resolver.js`) resolves and includes only required resources
-3. **Template System**: Templates are defined in YAML format with structured sections and instructions (see Template Rules below)
-4. **Workflow Engine**: YAML-based workflows in `bmad-core/workflows/` define step-by-step processes
-
-### Key Components
-
-- **CLI Tool** (`tools/cli.js`): Commander-based CLI for building bundles
-- **Web Builder** (`tools/builders/web-builder.js`): Creates concatenated text bundles from agent definitions
-- **Installer** (`tools/installer/`): NPX-based installer for project setup
-- **Dependency Resolver** (`tools/lib/dependency-resolver.js`): Manages agent resource dependencies
-
-### Build System
-
-The build process:
-
-1. Reads agent/team definitions from `bmad-core/`
-2. Resolves dependencies using the dependency resolver
-3. Creates concatenated text bundles in `dist/`
-4. Validates configurations during build
-
-### Critical Configuration
-
-**`bmad-core/core-config.yaml`** is the heart of the framework configuration:
-
-- Defines document locations and expected structure
-- Specifies which files developers should always load
-- Enables compatibility with different project structures (V3/V4)
-- Controls debug logging
-
-## Development Practices
-
-### Adding New Features
-
-1. **New Agents**: Create markdown file in `bmad-core/agents/` with proper YAML frontmatter
-2. **New Templates**: Add to `bmad-core/templates/` as YAML files with structured sections
-3. **New Workflows**: Create YAML in `bmad-core/workflows/`
-4. **Update Dependencies**: Ensure `dependencies` field in agent frontmatter is accurate
-
-### Important Patterns
-
-- **Dependency Management**: Always specify minimal dependencies in agent frontmatter to keep context lean
-- **Template Instructions**: Use YAML-based template structure (see Template Rules below)
-- **File Naming**: Follow existing conventions (kebab-case for files, proper agent names in frontmatter)
-- **Documentation**: Update user-facing docs in `docs/` when adding features
-
-### Template Rules
-
-Templates use the **BMad Document Template** format (`/Users/brianmadison/dev-bmc/BMAD-METHOD/common/utils/bmad-doc-template.md`) with YAML structure:
-
-1. **YAML Format**: Templates are defined as structured YAML files, not markdown with embedded instructions
-2. **Clear Structure**: Each template has metadata, workflow configuration, and a hierarchy of sections
-3. **Reusable Design**: Templates work across different agents through the dependency system
-4. **Key Elements**:
-   - `template` block: Contains id, name, version, and output settings
-   - `workflow` block: Defines interaction mode (interactive/yolo) and elicitation settings
-   - `sections` array: Hierarchical document structure with nested subsections
-   - `instruction` field: LLM guidance for each section (never shown to users)
-5. **Advanced Features**:
-   - Variable substitution: `{{variable_name}}` syntax for dynamic content
-   - Conditional sections: `condition` field for optional content
-   - Repeatable sections: `repeatable: true` for multiple instances
-   - Agent permissions: `owner` and `editors` fields for access control
-6. **Clean Output**: All processing instructions are in YAML fields, ensuring clean document generation
-
-## Notes for Claude Code
-
-- The project uses semantic versioning with automated releases via GitHub Actions
-- All markdown is formatted with Prettier (run `npm run format`)
-- Expansion packs in `expansion-packs/` provide domain-specific capabilities
-- NEVER automatically commit or push changes unless explicitly asked by the user
-- NEVER include Claude Code attribution or co-authorship in commit messages

CONTRIBUTING.md

@@ -1,65 +1,90 @@
-# Contributing to this project
+# Contributing to BMad
 
-Thank you for considering contributing to this project! This document outlines the process for contributing and some guidelines to follow.
-
-🆕 **New to GitHub or pull requests?** Check out our [beginner-friendly Pull Request Guide](docs/how-to-contribute-with-pull-requests.md) first!
-
-📋 **Before contributing**, please read our [Guiding Principles](docs/GUIDING-PRINCIPLES.md) to understand the BMad Method's core philosophy and architectural decisions.
-
-Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
+Thank you for considering contributing to the BMad project! We believe in **Human Amplification, Not Replacement** - bringing out the best thinking in both humans and AI through guided collaboration.
 
 💬 **Discord Community**: Join our [Discord server](https://discord.gg/gk8jAdXWmj) for real-time discussions:
 
 - **#general-dev** - Technical discussions, feature ideas, and development questions
 - **#bugs-issues** - Bug reports and issue discussions
 
-## Code of Conduct
+## Our Philosophy
 
-By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
+### BMad Core™: Universal Foundation
 
-## How to Contribute
+BMad Core empowers humans and AI agents working together in true partnership across any domain through our **C.O.R.E. Framework** (Collaboration Optimized Reflection Engine):
+
+- **Collaboration**: Human-AI partnership where both contribute unique strengths
+- **Optimized**: The collaborative process refined for maximum effectiveness
+- **Reflection**: Guided thinking that helps discover better solutions and insights
+- **Engine**: The powerful framework that orchestrates specialized agents and workflows
+
+### BMad Method™: Agile AI-Driven Development
+
+The BMad Method is the flagship bmad module for agile AI-driven software development. It emphasizes thorough planning and solid architectural foundations to provide detailed context for developer agents, mirroring real-world agile best practices.
+
+### Core Principles
+
+**Partnership Over Automation** - AI agents act as expert coaches, mentors, and collaborators who amplify human capability rather than replace it.
+
+**Bidirectional Guidance** - Agents guide users through structured workflows while users push agents with advanced prompting. Both sides actively work to extract better information from each other.
+
+**Systems of Workflows** - BMad Core builds comprehensive systems of guided workflows with specialized agent teams for any domain.
+
+**Tool-Agnostic Foundation** - BMad Core remains tool-agnostic, providing stable, extensible groundwork that adapts to any domain.
+
+## What Makes a Good Contribution?
+
+Every contribution should strengthen human-AI collaboration. Ask yourself: **"Does this make humans and AI better together?"**
+
+**✅ Contributions that align:**
+
+- Enhance universal collaboration patterns
+- Improve agent personas and workflows
+- Strengthen planning and context continuity
+- Increase cross-domain accessibility
+- Add domain-specific modules leveraging BMad Core
+
+**❌ What detracts from our mission:**
+
+- Purely automated solutions that sideline humans
+- Tools that don't improve the partnership
+- Complexity that creates barriers to adoption
+- Features that fragment BMad Core's foundation
+
+## Before You Contribute
 
 ### Reporting Bugs
 
 1. **Check existing issues** first to avoid duplicates
-2. **Use the bug report template** when creating a new issue - it will guide you through providing:
+2. **Consider discussing in Discord** (#bugs-issues channel) for quick help
+3. **Use the bug report template** when creating a new issue - it guides you through providing:
    - Clear bug description
    - Steps to reproduce
    - Expected vs actual behavior
    - Model/IDE/BMad version details
    - Screenshots or links if applicable
-3. **Consider discussing in Discord** (#bugs-issues channel) for quick help
 4. **Indicate if you're working on a fix** to avoid duplicate efforts
 
-### Suggesting Features
+### Suggesting Features or New Modules
 
 1. **Discuss first in Discord** (#general-dev channel) - the feature request template asks if you've done this
 2. **Check existing issues and discussions** to avoid duplicates
-3. **Use the feature request template** when creating an issue - it will guide you through:
-   - Confirming Discord discussion
-   - Describing the problem it solves
-   - Explaining your solution
-   - Listing alternatives considered
-4. **Be specific** about why this feature would benefit the BMad community
+3. **Use the feature request template** when creating an issue
+4. **Be specific** about why this feature would benefit the BMad community and strengthen human-AI collaboration
 
-### Pull Request Process
+### Before Starting Work
 
-⚠️ **Before starting work:**
+⚠️ **Required before submitting PRs:**
 
 1. **For bugs**: Check if an issue exists (create one using the bug template if not)
-2. **For features**: Ensure you've discussed in Discord (#general-dev) AND created a feature request issue
+2. **For features**: Discuss in Discord (#general-dev) AND create a feature request issue
 3. **For large changes**: Always open an issue first to discuss alignment
 
-Please only propose small granular commits! If its large or significant, please discuss in the discussions tab and open up an issue first. I do not want you to waste your time on a potentially very large PR to have it rejected because it is not aligned or deviates from other planned changes. Communicate and lets work together to build and improve this great community project!
+Please propose small, granular changes! For large or significant changes, discuss in Discord and open an issue first. This prevents wasted effort on PRs that may not align with planned changes.
 
-**Important**: All contributions must align with our [Guiding Principles](docs/GUIDING-PRINCIPLES.md). Key points:
+## Pull Request Guidelines
 
-- Keep dev agents lean - they need context for coding, not documentation
-- Web/planning agents can be larger with more complex tasks
-- Everything is natural language (markdown) - no code in core framework
-- Use expansion packs for domain-specific features
-
-#### Which Branch for Your PR?
+### Which Branch?
 
 **Submit to `next` branch** (most contributions):
 
@@ -69,7 +94,7 @@ Please only propose small granular commits! If its large or significant, please
 - ♻️ Code refactoring
 - ⚡ Performance improvements
 - 🧪 New tests
-- 🎁 New expansion packs
+- 🎁 New bmad modules
 
 **Submit to `main` branch** (critical only):
 
@@ -80,7 +105,7 @@ Please only propose small granular commits! If its large or significant, please
 
 **When in doubt, submit to `next`**. We'd rather test changes thoroughly before they hit stable.
 
-#### PR Size Guidelines
+### PR Size Guidelines
 
 - **Ideal PR size**: 200-400 lines of code changes
 - **Maximum PR size**: 800 lines (excluding generated files)
@@ -88,7 +113,7 @@ Please only propose small granular commits! If its large or significant, please
 - **If your change is larger**: Break it into multiple smaller PRs that can be reviewed independently
 - **Related changes**: Even related changes should be separate PRs if they deliver independent value
 
-#### Breaking Down Large PRs
+### Breaking Down Large PRs
 
 If your change exceeds 800 lines, use this checklist to split it:
 
@@ -107,30 +132,30 @@ Example breakdown:
 3. PR #3: Implement new feature using refactored code (300 lines)
 4. PR #4: Add comprehensive tests (200 lines)
 
-**Note**: PRs #1 and #4 could be submitted simultaneously since they deliver independent value and don't depend on each other's merge order.
+**Note**: PRs #1 and #4 could be submitted simultaneously since they deliver independent value.
 
-#### Pull Request Steps
+### Pull Request Process
 
-1. Fork the repository
-2. Create a new branch (`git checkout -b feature/your-feature-name`)
-3. Make your changes
-4. Run any tests or linting to ensure quality
-5. Commit your changes with clear, descriptive messages following our commit message convention
-6. Push to your branch (`git push origin feature/your-feature-name`)
-7. Open a Pull Request against the main branch
+#### New to Pull Requests?
 
-## Issue Templates
+If you're new to GitHub or pull requests, here's a quick guide:
 
-We use GitHub issue templates to ensure all necessary information is provided:
-
-- **Bug Reports**: Automatically guides you through providing reproduction steps, environment details, and expected behavior
-- **Feature Requests**: Requires Discord discussion confirmation and asks for problem/solution descriptions
-
-Using these templates helps maintainers understand and address your contribution faster.
-
-## Pull Request Description Guidelines
-
-Keep PR descriptions short and to the point following this template:
+1. **Fork the repository** - Click the "Fork" button on GitHub to create your own copy
+2. **Clone your fork** - `git clone https://github.com/YOUR-USERNAME/bmad-method.git`
+3. **Create a new branch** - Never work on `main` directly!
+   ```bash
+   git checkout -b fix/description
+   # or
+   git checkout -b feature/description
+   ```
+4. **Make your changes** - Edit files, keeping changes small and focused
+5. **Commit your changes** - Use clear, descriptive commit messages
+   ```bash
+   git add .
+   git commit -m "fix: correct typo in README"
+   ```
+6. **Push to your fork** - `git push origin fix/description`
+7. **Create the Pull Request** - Go to your fork on GitHub and click "Compare & pull request"
 
 ### PR Description Template
 
@@ -148,9 +173,8 @@ Fixes #[issue number] (if applicable)
 
 ## How
 
-[2-3 bullets listing HOW you implemented it]
+## [2-3 bullets listing HOW you implemented it]
 
--
 -
 -
 
@@ -165,7 +189,7 @@ Fixes #[issue number] (if applicable)
 
 ❌ **Bad Example:**
 
-> This revolutionary PR introduces a paradigm-shifting enhancement to the system's architecture by implementing a state-of-the-art solution that leverages cutting-edge methodologies to optimize performance metrics and deliver unprecedented value to stakeholders through innovative approaches...
+> This revolutionary PR introduces a paradigm-shifting enhancement to the system's architecture by implementing a state-of-the-art solution that leverages cutting-edge methodologies to optimize performance metrics...
 
 ✅ **Good Example:**
 
@@ -177,7 +201,7 @@ Fixes #[issue number] (if applicable)
 > - Throws clear error with dependency chain
 >   **Testing:** Tested with circular deps between 3 agents
 
-## Commit Message Convention
+### Commit Message Convention
 
 Use conventional commits format:
 
@@ -199,10 +223,56 @@ Each commit should represent one logical change:
 - **Don't:** Mix refactoring with bug fixes
 - **Don't:** Combine unrelated changes
 
+## What Makes a Good Pull Request?
+
+✅ **Good PRs:**
+
+- Change one thing at a time
+- Have clear, descriptive titles
+- Explain what and why in the description
+- Include only the files that need to change
+- Reference related issue numbers
+
+❌ **Avoid:**
+
+- Changing formatting of entire files
+- Multiple unrelated changes in one PR
+- Copying your entire project/repo into the PR
+- Changes without explanation
+- Working directly on `main` branch
+
+## Common Mistakes to Avoid
+
+1. **Don't reformat entire files** - only change what's necessary
+2. **Don't include unrelated changes** - stick to one fix/feature per PR
+3. **Don't paste code in issues** - create a proper PR instead
+4. **Don't submit your whole project** - contribute specific improvements
+
 ## Code Style
 
 - Follow the existing code style and conventions
 - Write clear comments for complex logic
+- Keep dev agents lean - they need context for coding, not documentation
+- Web/planning agents can be larger with more complex tasks
+- Everything is natural language (markdown) - no code in core framework
+- Use bmad modules for domain-specific features
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our Code of Conduct. We foster a collaborative, respectful environment focused on building better human-AI partnerships.
+
+## Need Help?
+
+- 💬 Join our [Discord Community](https://discord.gg/gk8jAdXWmj):
+  - **#general-dev** - Technical questions and feature discussions
+  - **#bugs-issues** - Get help with bugs before filing issues
+- 🐛 Report bugs using the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md)
+- 💡 Suggest features using the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md)
+- 📖 Browse the [GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions)
+
+---
+
+**Remember**: We're here to help! Don't be afraid to ask questions. Every expert was once a beginner. Together, we're building a future where humans and AI work better together.
 
 ## License
 

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 Brian AKA BMad AKA BMad Code
+Copyright (c) 2025 BMad Code, LLC
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -19,3 +19,8 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+
+TRADEMARK NOTICE:
+BMAD™, BMAD-CORE™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
+trademarks in this software does not grant any rights to use the trademarks 
+for any other purpose.

README.md

@@ -1,219 +1,415 @@
-# BMad-Method: Universal AI Agent Framework
+# BMad CORE v6 Alpha
 
 [![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
 [![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
-Foundations in Agentic Agile Driven Development, known as the Breakthrough Method of Agile AI-Driven Development, yet so much more. Transform any domain with specialized AI expertise: software development, entertainment, creative writing, business strategy to personal wellness just to name a few.
+**The Universal Human-AI Collaboration Platform**
 
-**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)**
+BMad-CORE (Collaboration Optimized Reflection Engine) is a revolutionary framework that amplifies human potential through specialized AI agents. Unlike traditional AI tools that replace human thinking, BMad-CORE guides you through reflective workflows that bring out your best ideas and the AI's full capabilities.
 
-**[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you! **Some mobile and VPN may have issue joining the discord, this is a discord issue - if the invite does not work, try from your own internet or another network, or non-VPN.**
+**🎯 Human Amplification, Not Replacement** • **🎨 Works in Any Domain** • **⚡ Powered by Specialized Agents**
 
-⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-Method and you will be notified of updates!
+---
 
-## Overview
-
-**BMad Method's Two Key Innovations:**
-
-**1. Agentic Planning:** Dedicated agents (Analyst, PM, Architect) collaborate with you to create detailed, consistent PRDs and Architecture documents. Through advanced prompt engineering and human-in-the-loop refinement, these planning agents produce comprehensive specifications that go far beyond generic AI task generation.
-
-**2. Context-Engineered Development:** The Scrum Master agent then transforms these detailed plans into hyper-detailed development stories that contain everything the Dev agent needs - full context, implementation details, and architectural guidance embedded directly in story files.
-
-This two-phase approach eliminates both **planning inconsistency** and **context loss** - the biggest problems in AI-assisted development. Your Dev agent opens a story file with complete understanding of what to build, how to build it, and why.
-
-**📖 [See the complete workflow in the User Guide](docs/user-guide.md)** - Planning phase, development cycle, and all agent roles
-
-## Quick Navigation
-
-### Understanding the BMad Workflow
-
-**Before diving in, review these critical workflow diagrams that explain how BMad works:**
-
-1. **[Planning Workflow (Web UI)](docs/user-guide.md#the-planning-workflow-web-ui)** - How to create PRD and Architecture documents
-2. **[Core Development Cycle (IDE)](docs/user-guide.md#the-core-development-cycle-ide)** - How SM, Dev, and QA agents collaborate through story files
-
-> ⚠️ **These diagrams explain 90% of BMad Method Agentic Agile flow confusion** - Understanding the PRD+Architecture creation and the SM/Dev/QA workflow and how agents pass notes through story files is essential - and also explains why this is NOT taskmaster or just a simple task runner!
-
-### What would you like to do?
-
-- **[Install and Build software with Full Stack Agile AI Team](#quick-start)** → Quick Start Instruction
-- **[Learn how to use BMad](docs/user-guide.md)** → Complete user guide and walkthrough
-- **[See available AI agents](/bmad-core/agents))** → Specialized roles for your team
-- **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** → Creative writing, business, wellness, education
-- **[Create my own AI agents](docs/expansion-packs.md)** → Build agents for your domain
-- **[Browse ready-made expansion packs](expansion-packs/)** → Game dev, DevOps, infrastructure and get inspired with ideas and examples
-- **[Understand the architecture](docs/core-architecture.md)** → Technical deep dive
-- **[Join the community](https://discord.gg/gk8jAdXWmj)** → Get help and share ideas
-
-## Important: Keep Your BMad Installation Updated
-
-**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
-
-```bash
-npx bmad-method install
-# OR
-git pull
-npm run install:bmad
-```
-
-This will:
-
-- ✅ Automatically detect your existing v4 installation
-- ✅ Update only the files that have changed and add new files
-- ✅ Create `.bak` backup files for any custom modifications you've made
-- ✅ Preserve your project-specific configurations
-
-This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations!
-
-## Quick Start
-
-### One Command for Everything (IDE Installation)
-
-**Just run one of these commands:**
-
-```bash
-npx bmad-method install
-# OR if you already have BMad installed:
-git pull
-npm run install:bmad
-```
-
-This single command handles:
-
-- **New installations** - Sets up BMad in your project
-- **Upgrades** - Updates existing installations automatically
-- **Expansion packs** - Installs any expansion packs you've added to package.json
-
-> **That's it!** Whether you're installing for the first time, upgrading, or adding expansion packs - these commands do everything.
+## 🚀 Quick Start
 
 **Prerequisites**: [Node.js](https://nodejs.org) v20+ required
 
-### Fastest Start: Web UI Full Stack Team at your disposal (2 minutes)
-
-1. **Get the bundle**: Save or clone the [full stack team file](dist/teams/team-fullstack.txt) or choose another team
-2. **Create AI agent**: Create a new Gemini Gem or CustomGPT
-3. **Upload & configure**: Upload the file and set instructions: "Your critical operating instructions are attached, do not break character as directed"
-4. **Start Ideating and Planning**: Start chatting! Type `*help` to see available commands or pick an agent like `*analyst` to start right in on creating a brief.
-5. **CRITICAL**: Talk to BMad Orchestrator in the web at ANY TIME (#bmad-orchestrator command) and ask it questions about how this all works!
-6. **When to move to the IDE**: Once you have your PRD, Architecture, optional UX and Briefs - its time to switch over to the IDE to shard your docs, and start implementing the actual code! See the [User guide](docs/user-guide.md) for more details
-
-### Alternative: Clone and Build
+**One-line install** (thanks Lum!):
 
 ```bash
-git clone https://github.com/bmadcode/bmad-method.git
-npm run install:bmad # build and install all to a destination folder
+git clone --branch v6-alpha --single-branch https://github.com/bmad-code-org/BMAD-METHOD
+cd BMAD-METHOD && npm install
 ```
 
-## 🌟 Beyond Software Development - Expansion Packs
-
-BMad's natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMad-Method with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
-
-## Codebase Flattener Tool
-
-The BMad-Method includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
-
-### Features
-
-- **AI-Optimized Output**: Generates clean XML format specifically designed for AI model consumption
-- **Smart Filtering**: Automatically respects `.gitignore` patterns to exclude unnecessary files
-- **Binary File Detection**: Intelligently identifies and excludes binary files, focusing on source code
-- **Progress Tracking**: Real-time progress indicators and comprehensive completion statistics
-- **Flexible Output**: Customizable output file location and naming
-
-### Usage
+**Install to your project:**
 
 ```bash
-# Basic usage - creates flattened-codebase.xml in current directory
-npx bmad-method flatten
-
-# Specify custom input directory
-npx bmad-method flatten --input /path/to/source/directory
-npx bmad-method flatten -i /path/to/source/directory
-
-# Specify custom output file
-npx bmad-method flatten --output my-project.xml
-npx bmad-method flatten -o /path/to/output/codebase.xml
-
-# Combine input and output options
-npx bmad-method flatten --input /path/to/source --output /path/to/output/codebase.xml
+npm run install:bmad
 ```
 
-### Example Output
+Follow the interactive prompts. **Important**: When asked for a destination, provide the **full path** to your project folder (don't accept the default).
 
-The tool will display progress and provide a comprehensive summary:
+**Essential Reading**: Before using BMad Method, read the **[BMM v6 Workflows Guide](./src/modules/bmm/workflows/README.md)** to understand the four-phase workflow system.
 
-```text
-📊 Completion Summary:
-✅ Successfully processed 156 files into flattened-codebase.xml
-📁 Output file: /path/to/your/project/flattened-codebase.xml
-📏 Total source size: 2.3 MB
-📄 Generated XML size: 2.1 MB
-📝 Total lines of code: 15,847
-🔢 Estimated tokens: 542,891
-📊 File breakdown: 142 text, 14 binary, 0 errors
+**Stay Connected**:
+
+- ⭐ **[Star this repo](https://github.com/bmad-code-org/BMAD-METHOD)** to get notified of updates
+- 🎥 **[Subscribe on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)** for tutorials
+- 💬 **[Join Discord Community](https://discord.gg/gk8jAdXWmj)** for support and collaboration
+
+---
+
+## ⚠️ Alpha Status
+
+**This is an active alpha release.** Please help us improve by testing and reporting issues!
+
+| Status                        | Details                                                                                                                                                                      |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 🔄 **Frequent Updates**       | Pull often. Delete `node_modules` and run `npm install` after updates                                                                                                        |
+| 🧪 **Potentially Unstable**   | Features and file structure may change frequently. [File issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) or discuss in [Discord](https://discord.gg/gk8jAdXWmj) |
+| 🚧 **Work in Progress**       | Many features, polish, docs, agents, and workflows still coming before and after beta                                                                                        |
+| 💻 **IDE/Local LLM Required** | Web bundles not fully working yet. Use quality LLM Models and tools for testing (especially BMM module)                                                                      |
+| 🔀 **PR Target**              | Submit PRs against `v6-alpha` branch, not `main`                                                                                                                             |
+
+**📋 [View v6 Alpha Open Items & Roadmap](./v6-open-items.md)** - Track progress and what's coming next
+
+---
+
+## What is BMad-CORE?
+
+### The Problem with Traditional AI
+
+Traditional AI tools provide **average, bland solutions** and do the thinking **for** you, making you dependent rather than capable.
+
+### The BMad-CORE Difference
+
+BMad-CORE brings out **the best thinking in you and the AI** through:
+
+- **Guided Collaboration**: AI agents act as expert coaches, mentors, and collaborators
+- **Reflective Workflows**: Structured frameworks that help you discover insights
+- **Strategic Questioning**: Agents ask the right questions to stimulate your thinking
+- **Domain Mastery**: Build expertise rather than just getting answers
+- **Amplified Abilities**: Your natural talents enhanced, not replaced
+
+### The C.O.R.E. System
+
+- **C**ollaboration: Human-AI partnership where both contribute unique strengths
+- **O**ptimized: Refined processes for maximum effectiveness
+- **R**eflection: Guided thinking that unlocks better solutions
+- **E**ngine: Powerful framework orchestrating specialized agents and workflows
+
+---
+
+## Universal Domain Coverage Through Modules
+
+BMad-CORE works in **any domain** through specialized modules!
+
+### 📦 Available Alpha Modules
+
+#### **BMad Core (core)** - _Always Installed_
+
+The foundation that powers every module. Includes orchestration agents for local environments and web bundles (ChatGPT, Gemini Gems, etc.).
+
+#### **[BMad Method (bmm)](./src/modules/bmm/README.md)** - _Software Development Excellence_
+
+Agile AI-driven software development rebuilt from the ground up on BMad-CORE. Features the revolutionary **Scale Adaptive Workflow Engine™** that adjusts from simple tasks to enterprise-scale projects.
+
+**Four-Phase Methodology**: Analysis → Planning → Solutioning → Implementation
+
+**[📚 Full BMM Documentation](./src/modules/bmm/README.md)** | **[📖 v6 Workflows Guide](./src/modules/bmm/workflows/README.md)**
+
+#### **[BMad Builder (bmb)](./src/modules/bmb/README.md)** - _Create Custom Agents & Workflows_
+
+Your authoring tool for custom agents, workflows, and modules. Easier than ever to customize existing modules or create standalone solutions.
+
+**Three Agent Types**: Full module agents, hybrid agents, and lightweight standalone agents
+
+**[📚 Full BMB Documentation](./src/modules/bmb/README.md)** | **[🎯 Agent Creation Guide](./src/modules/bmb/workflows/create-agent/README.md)**
+
+#### **Creative Intelligence Suite (cis)** - _Innovation & Problem-Solving_
+
+Unlock creative thinking and innovation! Includes brainstorming workflows that power other modules (like BMM) while standing alone as a complete creative toolkit.
+
+**[📚 CIS Documentation](./src/modules/cis/readme.md)**
+
+---
+
+## 🎉 What's New in v6 Alpha
+
+### Complete Ground-Up Rewrite
+
+Everything rebuilt with best practices, advanced prompt engineering, and standardized XML/markdown conventions for maximum agent adherence.
+
+### 🎨 Unprecedented Customizability
+
+- **Agent Customization**: Modify any agent via sidecar files in `bmad/_cfg/agents/`
+- **Update-Safe**: Your customizations persist through updates
+- **Full Control**: Change names, personas, communication styles, language
+- **Multi-Language**: Agents can communicate in your preferred language
+
+### 🚀 Intelligent Installer
+
+Brand new interactive installer that configures:
+
+- Your name (how agents address you)
+- Communication language preference
+- Communication (chat) technical level of explanation (beginner - advanced level technical user knowledge)
+- Documentation output language
+- Module-specific customization options
+- IDE-specific enhancements globally or per module (e.g., Claude Code sub-agents for BMM)
+
+### 📁 Unified Installation
+
+Everything installs to a single `bmad/` folder - no more scattered root folders. Clean, organized, and efficient.
+
+### 🤝 Consolidated Agent Party
+
+When you install modules, a unified agent party is created for party-mode in your IDE. Super efficient agent simulation with more exciting features coming in beta!
+
+### 🎮 Expanded Game Development
+
+Game development now fully integrated into BMM module:
+
+- **Game Type Adaptive**: Adjusts to the type of game you're making
+- **Multi-Engine Support**: More platforms being added
+
+### ⚡ BMM Scale Adaptive Workflows
+
+The BMad Method now adapts to your project scale (Levels 0-4) based on:
+
+- Project scope and complexity
+- New vs. existing codebase
+- Current codebase state
+- Team size and structure
+
+Guides workflows intelligently from simple tech specs to enterprise-scale planning.
+
+### 🆕 Three Agent Types (BMB)
+
+1. **Full Module Agents**: Complete agents embedded in modules
+2. **Hybrid Agents**: Shared across modules
+3. **Standalone Agents**: Tiny, specialized agents free from any module - perfect for specific needs
+
+---
+
+## BMad Method (BMM) Four-Phase Workflow
+
+The BMM module follows a comprehensive four-phase methodology. Each phase adapts to your project's scale and complexity.
+
+**[Complete workflow documentation →](./src/modules/bmm/workflows/README.md)**
+
+### Phase 1: Analysis _(Optional)_
+
+**Analyst Agent**:
+
+- `brainstorm-project` - Generate and refine project concepts
+- `research` - Market research, deep research, prompt generation
+- `product-brief` - Document initial product vision
+
+**Game Designer Agent** _(for game projects)_:
+
+- `brainstorm-game` - Game-specific ideation
+- `game-brief` - Game concept documentation
+- `research` - Game market and technical research
+
+---
+
+### Phase 2: Planning _(Required)_
+
+**PM Agent**:
+
+- `plan-project` - Creates scale-adaptive PRD or GDD
+
+The planning workflow adapts to:
+
+- Project complexity (Levels 0-4)
+- Project type (web, mobile, embedded, game, etc.)
+- New vs. existing codebase
+- Team structure
+
+**Game Designer Agent** _(for game projects)_:
+
+- `plan-game` - Uses same workflow but optimized for Game Design Documents
+
+---
+
+### Phase 3: Solutioning _(Levels 3-4)_
+
+**Architect / Game Architect Agent**:
+
+- `architecture` - Creates adaptive architecture based on project type
+  - No more document sharding
+  - Adapts sections to your project (web, mobile, embedded, game, etc.)
+  - Beyond basic concerns (complex testing, DevOps, security), specialized agents assist _(coming soon)_
+
+- `tech-spec` - Generates Epic Tech Specs
+  - Pulls all technical information from planning
+  - Includes web research as needed
+  - One tech spec per epic
+  - Enhances SM's ability to prepare stories
+
+**Note**: The PO can validate epics/stories with checklists, though the Architect maintains them during solutioning.
+
+---
+
+### Phase 4: Implementation _(Iterative)_
+
+**Scrum Master (SM) Agent**:
+
+Before development starts, the SM prepares each story:
+
+1. `create-story` - Generates story from tech spec and context
+2. `story-context` - **🎉 NEW!** Game-changing contextual preparation
+   - Real-time context gathering for the specific story
+   - No more generic file lists
+   - Supercharged, specialized development context
+
+**Dev Agent**:
+
+Enhanced developer workflow:
+
+- Development task execution
+- Senior dev agent review (replaces separate QA agent)
+- Pulls rich context from story-context workflow
+
+**🎊 Many more exciting changes throughout BMM for you to discover during alpha!**
+
+---
+
+## Detailed Installation Guide
+
+### Prerequisites
+
+- **Node.js v20+** ([Download](https://nodejs.org))
+- **Git** (for cloning)
+
+### Step-by-Step Installation
+
+#### Step 1: Clone the Repository
+
+**Option A** - One-line install:
+
+```bash
+git clone --branch v6-alpha --single-branch https://github.com/bmad-code-org/BMAD-METHOD
 ```
 
-The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMad-Method projects.
+**Option B** - Standard clone then checkout:
 
-#### Advanced Usage & Options
+```bash
+# Clone via your preferred method:
+gh repo clone bmad-code-org/BMAD-METHOD
+# OR
+git clone https://github.com/bmad-code-org/BMAD-METHOD.git
+# OR
+git clone git@github.com:bmad-code-org/BMAD-METHOD.git
 
-- CLI options
-  - `-i, --input <path>`: Directory to flatten. Default: current working directory or auto-detected project root when run interactively.
-  - `-o, --output <path>`: Output file path. Default: `flattened-codebase.xml` in the chosen directory.
-- Interactive mode
-  - If you do not pass `--input` and `--output` and the terminal is interactive (TTY), the tool will attempt to detect your project root (by looking for markers like `.git`, `package.json`, etc.) and prompt you to confirm or override the paths.
-  - In non-interactive contexts (e.g., CI), it will prefer the detected root silently; otherwise it falls back to the current directory and default filename.
-- File discovery and ignoring
-  - Uses `git ls-files` when inside a git repository for speed and correctness; otherwise falls back to a glob-based scan.
-  - Applies your `.gitignore` plus a curated set of default ignore patterns (e.g., `node_modules`, build outputs, caches, logs, IDE folders, lockfiles, large media/binaries, `.env*`, and previously generated XML outputs).
-- Binary handling
-  - Binary files are detected and excluded from the XML content. They are counted in the final summary but not embedded in the output.
-- XML format and safety
-  - UTF-8 encoded file with root element `<files>`.
-  - Each text file is emitted as a `<file path="relative/path">` element whose content is wrapped in `<![CDATA[ ... ]]>`.
-  - The tool safely handles occurrences of `]]>` inside content by splitting the CDATA to preserve correctness.
-  - File contents are preserved as-is and indented for readability inside the XML.
-- Performance
-  - Concurrency is selected automatically based on your CPU and workload size. No configuration required.
-  - Running inside a git repo improves discovery performance.
+# Change to the directory
+cd BMAD-METHOD
 
-#### Minimal XML example
+# Checkout alpha branch
+git checkout v6-alpha
 
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<files>
-  <file path="src/index.js"><![CDATA[
-    // your source content
-  ]]></file>
-</files>
+# Verify branch
+git status
+# Should show: "On branch v6-alpha. Your branch is up to date with 'origin/v6-alpha'."
 ```
 
-## Documentation & Resources
+#### Step 2: Install Dependencies
 
-### Essential Guides
+```bash
+npm install
+```
 
-- 📖 **[User Guide](docs/user-guide.md)** - Complete walkthrough from project inception to completion
-- 🏗️ **[Core Architecture](docs/core-architecture.md)** - Technical deep dive and system design
-- 🚀 **[Expansion Packs Guide](docs/expansion-packs.md)** - Extend BMad to any domain beyond software development
+Verify `node_modules` folder exists at project root.
 
-## Support
+#### Step 3: Install to Your Project
 
-- 💬 [Discord Community](https://discord.gg/gk8jAdXWmj)
-- 🐛 [Issue Tracker](https://github.com/bmadcode/bmad-method/issues)
-- 💬 [Discussions](https://github.com/bmadcode/bmad-method/discussions)
+```bash
+npm run install:bmad
+```
+
+**Follow the interactive prompts:**
+
+1. **Destination Path**: Enter the **full path** to your project folder
+   - Don't accept the default
+   - For new projects, confirm when prompted to create the directory
+2. **Module Selection**:
+   - **Core** (always installed)
+   - **BMM** - BMad Method for software development (default)
+   - **BMB** - BMad Builder for creating agents/workflows
+   - **CIS** - Creative Intelligence Suite
+
+3. **Configuration**:
+   - Your name
+   - Preferred communication language
+   - Module-specific options
+
+#### Step 4: Understanding the Installation
+
+All modules install to a single `bmad/` folder in your project:
+
+```
+your-project/
+└── bmad/
+    ├── core/         # Core framework (always present)
+    ├── bmm/          # BMad Method (if selected)
+    ├── bmb/          # BMad Builder (if selected)
+    ├── cis/          # Creative Intelligence Suite (shared resources)
+    └── _cfg/         # Your customizations
+        └── agents/   # Agent sidecar customization files
+```
+
+**Note**: You may see folders for modules you didn't explicitly select. This is intentional - modules share minimal required resources. For example, BMM uses CIS brainstorming workflows, so `bmad/cis/` appears with shared files even if you only selected BMM.
+
+---
+
+## Additional Resources
+
+### BMad Builder (BMB) Resources
+
+**Agent Development**:
+
+- [Agent Architecture](src/modules/bmb/workflows/create-agent/agent-architecture)
+- [Agent Command Patterns](src/modules/bmb/workflows/create-agent/agent-command-patterns.md)
+- [Agent Types](src/modules/bmb/workflows/create-agent/agent-types.md)
+- [Communication Styles](src/modules/bmb/workflows/create-agent/communication-styles.md)
+
+**Module Development**:
+
+- [Module Structure](src/modules/bmb/workflows/create-module/module-structure.md)
+
+**Workflow Development**:
+
+- [Workflow Creation Guide](src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md)
+
+> **Coming Soon**: A dedicated module contribution repository (beta release) where you can share your custom modules!
+
+### Installer & Bundler Documentation
+
+- **[CLI Tool Guide](tools/cli/README.md)** - Complete installer, bundler, and agent compilation system
+- [IDE Injections](docs/installers-bundlers/ide-injections)
+- [Installers Modules Platforms Reference](docs/installers-bundlers/installers-modules-platforms-reference)
+- [Web Bundler Usage](docs/installers-bundlers/web-bundler-usage)
+- [Claude Code Sub Module BMM Installer](src/modules/bmm/sub-modules/claude-code/readme.md)
+
+---
+
+## Support & Community
+
+We have an amazing, active community ready to help!
+
+- 💬 **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help, share ideas, collaborate
+- 🐛 **[Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs and request features
+- 💬 **[GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions)** - Community conversations
+- 🎥 **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Tutorials and updates
+
+---
 
 ## Contributing
 
-**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
+We welcome contributions and new module development!
 
-📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete guide to contributing, including guidelines, process, and requirements
+**📋 [Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete contribution guide
+
+**Remember**: Submit PRs against the `v6-alpha` branch, not `main`.
+
+---
 
 ## License
 
 MIT License - see [LICENSE](LICENSE) for details.
 
-[![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
+---
 
-<sub>Built with ❤️ for the AI-assisted development community</sub>
+## Trademark Notice
+
+BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
+
+---
+
+[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
+
+<sub>Built with ❤️ for the human-AI collaboration community</sub>

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

@@ -1,14 +0,0 @@
-bundle:
-  name: Team All
-  icon: 👥
-  description: Includes every core system agent.
-agents:
-  - bmad-orchestrator
-  - '*'
-workflows:
-  - 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

@@ -1,18 +0,0 @@
-bundle:
-  name: Team Fullstack
-  icon: 🚀
-  description: Team capable of full stack, front end only, or service development.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - ux-expert
-  - architect
-  - po
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml

bmad-core/agent-teams/team-ide-minimal.yaml

@@ -1,10 +0,0 @@
-bundle:
-  name: Team IDE Minimal
-  icon: ⚡
-  description: Only the bare minimum for the IDE PO SM dev qa cycle.
-agents:
-  - po
-  - sm
-  - dev
-  - qa
-workflows: null

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

@@ -1,13 +0,0 @@
-bundle:
-  name: Team No UI
-  icon: 🔧
-  description: Team with no UX or UI Planning.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - architect
-  - po
-workflows:
-  - greenfield-service.yaml
-  - brownfield-service.yaml

bmad-core/agents/analyst.md

@@ -1,81 +0,0 @@
-# analyst
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Mary
-  id: analyst
-  title: Business Analyst
-  icon: 📊
-  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield)
-  customization: null
-persona:
-  role: Insightful Analyst & Strategic Ideation Partner
-  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
-  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
-  focus: Research planning, ideation facilitation, strategic analysis, actionable insights
-  core_principles:
-    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
-    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
-    - Strategic Contextualization - Frame all work within broader strategic context
-    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
-    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
-    - Structured & Methodical Approach - Apply systematic methods for thoroughness
-    - Action-Oriented Outputs - Produce clear, actionable deliverables
-    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
-    - 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
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
-  - perform-market-research: use task create-doc with market-research-tmpl.yaml
-  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
-  - yolo: Toggle Yolo Mode
-  - doc-out: Output full document in progress to current destination file
-  - research-prompt {topic}: execute task create-deep-research-prompt.md
-  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
-  - elicit: run the task advanced-elicitation
-  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - facilitate-brainstorming-session.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - advanced-elicitation.md
-    - document-project.md
-  templates:
-    - project-brief-tmpl.yaml
-    - market-research-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - brainstorming-output-tmpl.yaml
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-```

bmad-core/agents/architect.md

@@ -1,83 +0,0 @@
-# architect
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Winston
-  id: architect
-  title: Architect
-  icon: 🏗️
-  whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
-  customization: null
-persona:
-  role: Holistic System Architect & Full-Stack Technical Leader
-  style: Comprehensive, pragmatic, user-centric, technically deep yet accessible
-  identity: Master of holistic application design who bridges frontend, backend, infrastructure, and everything in between
-  focus: Complete systems architecture, cross-stack optimization, pragmatic technology selection
-  core_principles:
-    - Holistic System Thinking - View every component as part of a larger system
-    - User Experience Drives Architecture - Start with user journeys and work backward
-    - Pragmatic Technology Selection - Choose boring technology where possible, exciting where necessary
-    - Progressive Complexity - Design systems simple to start but can scale
-    - Cross-Stack Performance Focus - Optimize holistically across all layers
-    - Developer Experience as First-Class Concern - Enable developer productivity
-    - Security at Every Layer - Implement defense in depth
-    - Data-Centric Design - Let data requirements drive architecture
-    - Cost-Conscious Engineering - Balance technical ideals with financial reality
-    - Living Architecture - Design for change and adaptation
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
-  - create-backend-architecture: use create-doc with architecture-tmpl.yaml
-  - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
-  - create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
-  - research {topic}: execute task create-deep-research-prompt
-  - shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
-  - yolo: Toggle Yolo Mode
-  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - create-doc.md
-    - create-deep-research-prompt.md
-    - document-project.md
-    - execute-checklist.md
-  templates:
-    - architecture-tmpl.yaml
-    - front-end-architecture-tmpl.yaml
-    - fullstack-architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-  checklists:
-    - architect-checklist.md
-  data:
-    - technical-preferences.md
-```

bmad-core/agents/bmad-master.md

@@ -1,107 +0,0 @@
-# BMad Master
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded
-  - CRITICAL: Do NOT run discovery tasks automatically
-  - CRITICAL: NEVER LOAD {root}/data/bmad-kb.md UNLESS USER TYPES *kb
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: BMad Master
-  id: bmad-master
-  title: BMad Master Task Executor
-  icon: 🧙
-  whenToUse: Use when you need comprehensive expertise across all domains, running 1 off tasks that do not require a persona, or just wanting to use the same agent for many things.
-persona:
-  role: Master Task Executor & BMad Method Expert
-  identity: Universal executor of all BMad-Method capabilities, directly runs any resource
-  core_principles:
-    - Execute any resource directly without persona transformation
-    - Load resources at runtime, never pre-load
-    - Expert knowledge of all BMad resources if using *kb
-    - Always presents numbered lists for choices
-    - Process (*) commands immediately, All commands require * prefix when used (e.g., *help)
-
-commands:
-  - help: Show these listed commands in a numbered list
-  - kb: Toggle KB mode off (default) or on, when on will load and reference the {root}/data/bmad-kb.md and converse with the user answering his questions with this informational resource
-  - task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
-  - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
-  - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
-  - yolo: Toggle Yolo Mode
-  - exit: Exit (confirm)
-
-dependencies:
-  tasks:
-    - 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
-    - document-project.md
-    - create-next-story.md
-    - execute-checklist.md
-    - generate-ai-frontend-prompt.md
-    - index-docs.md
-    - shard-doc.md
-  templates:
-    - 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.md
-    - brainstorming-techniques.md
-    - elicitation-methods.md
-    - technical-preferences.md
-  workflows:
-    - brownfield-fullstack.md
-    - brownfield-service.md
-    - brownfield-ui.md
-    - greenfield-fullstack.md
-    - greenfield-service.md
-    - greenfield-ui.md
-  checklists:
-    - 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,149 +0,0 @@
-# BMad Web Orchestrator
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - 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
-  - STAY IN CHARACTER!
-  - 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`)
-  - 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
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: BMad Orchestrator
-  id: bmad-orchestrator
-  title: BMad Master Orchestrator
-  icon: 🎭
-  whenToUse: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
-persona:
-  role: Master Orchestrator & BMad Method Expert
-  style: Knowledgeable, guiding, adaptable, efficient, encouraging, technically brilliant yet approachable. Helps customize and use BMad Method while orchestrating agents
-  identity: Unified interface to all BMad-Method capabilities, dynamically transforms into any specialized agent
-  focus: Orchestrating the right agent/capability for each need, loading resources only when needed
-  core_principles:
-    - Become any agent on demand, loading files only when needed
-    - Never pre-load resources - discover and load at runtime
-    - Assess needs and recommend best approach/agent/workflow
-    - Track current state and guide to next logical steps
-    - When embodied, specialized persona's principles take precedence
-    - Be explicit about active persona and current task
-    - Always use numbered lists for choices
-    - Process commands starting with * immediately
-    - Always remind users that commands require * prefix
-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
-  kb-mode: Load full BMad knowledge base
-  status: Show current context, active agent, and progress
-  agent: Transform into a specialized agent (list if name not specified)
-  exit: Return to BMad or exit session
-  task: Run a specific task (list if name not specified)
-  workflow: Start a specific workflow (list if name not specified)
-  workflow-guidance: Get personalized help selecting the right workflow
-  plan: Create detailed workflow plan before starting
-  plan-status: Show current workflow plan progress
-  plan-update: Update workflow plan status
-  checklist: Execute a checklist (list if name not specified)
-  yolo: Toggle skip confirmations mode
-  party-mode: Group chat with all agents
-  doc-out: Output full document
-help-display-template: |
-  === BMad Orchestrator Commands ===
-  All commands must start with * (asterisk)
-
-  Core Commands:
-  *help ............... Show this guide
-  *chat-mode .......... Start conversational mode for detailed assistance
-  *kb-mode ............ Load full BMad knowledge base
-  *status ............. Show current context, active agent, and progress
-  *exit ............... Return to BMad or exit session
-
-  Agent & Task Management:
-  *agent [name] ....... Transform into specialized agent (list if no name)
-  *task [name] ........ Run specific task (list if no name, requires agent)
-  *checklist [name] ... Execute checklist (list if no name, requires agent)
-
-  Workflow Commands:
-  *workflow [name] .... Start specific workflow (list if no name)
-  *workflow-guidance .. Get personalized help selecting the right workflow
-  *plan ............... Create detailed workflow plan before starting
-  *plan-status ........ Show current workflow plan progress
-  *plan-update ........ Update workflow plan status
-
-  Other Commands:
-  *yolo ............... Toggle skip confirmations mode
-  *party-mode ......... Group chat with all agents
-  *doc-out ............ Output full document
-
-  === Available Specialist Agents ===
-  [Dynamically list each agent in bundle with format:
-  *agent {id}: {title}
-    When to use: {whenToUse}
-    Key deliverables: {main outputs/documents}]
-
-  === Available Workflows ===
-  [Dynamically list each workflow in bundle with format:
-  *workflow {id}: {name}
-    Purpose: {description}]
-
-  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
-
-fuzzy-matching:
-  - 85% confidence threshold
-  - Show numbered list if unsure
-transformation:
-  - Match name/role to agents
-  - Announce transformation
-  - Operate until exit
-loading:
-  - KB: Only for *kb-mode or BMad questions
-  - Agents: Only when transforming
-  - Templates/Tasks: Only when executing
-  - Always indicate loading
-kb-mode-behavior:
-  - When *kb-mode is invoked, use kb-mode-interaction task
-  - Don't dump all KB content immediately
-  - Present topic areas and wait for user selection
-  - Provide focused, contextual responses
-workflow-guidance:
-  - Discover available workflows in the bundle at runtime
-  - Understand each workflow's purpose, options, and decision points
-  - Ask clarifying questions based on the workflow's structure
-  - Guide users through workflow selection when multiple options exist
-  - When appropriate, suggest: "Would you like me to create a detailed workflow plan before starting?"
-  - For workflows with divergent paths, help users choose the right path
-  - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
-  - Only recommend workflows that actually exist in the current bundle
-  - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
-dependencies:
-  tasks:
-    - advanced-elicitation.md
-    - create-doc.md
-    - kb-mode-interaction.md
-  data:
-    - bmad-kb.md
-    - elicitation-methods.md
-  utils:
-    - workflow-management.md
-```

bmad-core/agents/dev.md

@@ -1,75 +0,0 @@
-# dev
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - 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
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: James
-  id: dev
-  title: Full Stack Developer
-  icon: 💻
-  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
-  customization:
-
-persona:
-  role: Expert Senior Software Engineer & Implementation Specialist
-  style: Extremely concise, pragmatic, detail-oriented, solution-focused
-  identity: Expert who implements stories by reading requirements and executing tasks sequentially with comprehensive testing
-  focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
-
-core_principles:
-  - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
-  - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
-  - Numbered Options - Always use numbered lists when presenting choices to the user
-
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - run-tests: Execute linting and tests
-  - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
-  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - develop-story:
-      - order-of-execution: "Read (first or next) task→Implement Task and its subtasks→Write tests→Execute validations→Only if ALL pass, then update the task checkbox with [x]→Update story section File List to ensure it lists and new or modified or deleted source file→repeat order-of-execution until complete"
-      - story-file-updates-ONLY:
-          - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
-          - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
-          - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
-      - blocking: "HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression"
-      - ready-for-review: "Code matches requirements + All validations pass + Follows standards + File List complete"
-      - 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.md
-    - validate-next-story.md
-  checklists:
-    - story-dod-checklist.md
-```

bmad-core/agents/pm.md

@@ -1,81 +0,0 @@
-# pm
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: John
-  id: pm
-  title: Product Manager
-  icon: 📋
-  whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
-persona:
-  role: Investigative Product Strategist & Market-Savvy PM
-  style: Analytical, inquisitive, data-driven, user-focused, pragmatic
-  identity: Product Manager specialized in document creation and product research
-  focus: Creating PRDs and other product documentation using templates
-  core_principles:
-    - Deeply understand "Why" - uncover root causes and motivations
-    - Champion the user - maintain relentless focus on target user value
-    - Data-informed decisions with strategic judgment
-    - Ruthless prioritization & MVP focus
-    - Clarity & precision in communication
-    - Collaborative & iterative approach
-    - Proactive risk identification
-    - Strategic thinking & outcome-oriented
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - create-prd: run task create-doc.md with template prd-tmpl.yaml
-  - create-brownfield-prd: run task create-doc.md with template brownfield-prd-tmpl.yaml
-  - create-brownfield-epic: run task brownfield-create-epic.md
-  - create-brownfield-story: run task brownfield-create-story.md
-  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - create-story: Create user story from requirements (task brownfield-create-story)
-  - doc-out: Output full document to current destination file
-  - shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
-  - correct-course: execute the correct-course task
-  - yolo: Toggle Yolo Mode
-  - exit: Exit (confirm)
-dependencies:
-  tasks:
-    - 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.yaml
-    - brownfield-prd-tmpl.yaml
-  checklists:
-    - pm-checklist.md
-    - change-checklist.md
-  data:
-    - technical-preferences.md
-```

bmad-core/agents/po.md

@@ -1,76 +0,0 @@
-# po
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Sarah
-  id: po
-  title: Product Owner
-  icon: 📝
-  whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
-  customization: null
-persona:
-  role: Technical Product Owner & Process Steward
-  style: Meticulous, analytical, detail-oriented, systematic, collaborative
-  identity: Product Owner who validates artifacts cohesion and coaches significant changes
-  focus: Plan integrity, documentation quality, actionable development tasks, process adherence
-  core_principles:
-    - Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
-    - Clarity & Actionability for Development - Make requirements unambiguous and testable
-    - Process Adherence & Systemization - Follow defined processes and templates rigorously
-    - Dependency & Sequence Vigilance - Identify and manage logical sequencing
-    - Meticulous Detail Orientation - Pay close attention to prevent downstream errors
-    - Autonomous Preparation of Work - Take initiative to prepare and structure work
-    - Blocker Identification & Proactive Communication - Communicate issues promptly
-    - 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
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
-  - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
-  - correct-course: execute the correct-course task
-  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - create-story: Create user story from requirements (task brownfield-create-story)
-  - doc-out: Output full document to current destination file
-  - validate-story-draft {story}: run the task validate-next-story against the provided story file
-  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
-  - exit: Exit (confirm)
-dependencies:
-  tasks:
-    - execute-checklist.md
-    - shard-doc.md
-    - correct-course.md
-    - validate-next-story.md
-  templates:
-    - story-tmpl.yaml
-  checklists:
-    - po-master-checklist.md
-    - change-checklist.md
-```

bmad-core/agents/qa.md

@@ -1,88 +0,0 @@
-# qa
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Quinn
-  id: qa
-  title: Test Architect & Quality Advisor
-  icon: 🧪
-  whenToUse: |
-    Use for comprehensive test architecture review, quality gate decisions, 
-    and code improvement. Provides thorough analysis including requirements 
-    traceability, risk assessment, and test strategy. 
-    Advisory only - teams choose their quality bar.
-  customization: null
-persona:
-  role: Test Architect with Quality Advisory Authority
-  style: Comprehensive, systematic, advisory, educational, pragmatic
-  identity: Test architect who provides thorough quality assessment and actionable recommendations without blocking progress
-  focus: Comprehensive quality analysis through test architecture, risk assessment, and advisory gates
-  core_principles:
-    - Depth As Needed - Go deep based on risk signals, stay concise when low risk
-    - Requirements Traceability - Map all stories to tests using Given-When-Then patterns
-    - Risk-Based Testing - Assess and prioritize by probability × impact
-    - Quality Attributes - Validate NFRs (security, performance, reliability) via scenarios
-    - Testability Assessment - Evaluate controllability, observability, debuggability
-    - Gate Governance - Provide clear PASS/CONCERNS/FAIL/WAIVED decisions with rationale
-    - Advisory Excellence - Educate through documentation, never block arbitrarily
-    - Technical Debt Awareness - Identify and quantify debt with improvement suggestions
-    - LLM Acceleration - Use LLMs to accelerate thorough yet focused analysis
-    - Pragmatic Balance - Distinguish must-fix from nice-to-have improvements
-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
-  - CRITICAL: Your updates must be limited to appending your review results in the QA Results section only
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - review {story}: |
-      Adaptive, risk-aware comprehensive review. 
-      Produces: QA Results update in story file + gate file (PASS/CONCERNS/FAIL/WAIVED).
-      Gate file location: docs/qa/gates/{epic}.{story}-{slug}.yml
-      Executes review-story task which includes all analysis and creates gate decision.
-  - gate {story}: Execute qa-gate task to write/update quality gate decision in docs/qa/gates/
-  - trace {story}: Execute trace-requirements task to map requirements to tests using Given-When-Then
-  - risk-profile {story}: Execute risk-profile task to generate risk assessment matrix
-  - test-design {story}: Execute test-design task to create comprehensive test scenarios
-  - nfr-assess {story}: Execute nfr-assess task to validate non-functional requirements
-  - exit: Say goodbye as the Test Architect, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - review-story.md
-    - qa-gate.md
-    - trace-requirements.md
-    - risk-profile.md
-    - test-design.md
-    - nfr-assess.md
-  data:
-    - technical-preferences.md
-  templates:
-    - story-tmpl.yaml
-    - qa-gate-tmpl.yaml
-```

bmad-core/agents/sm.md

@@ -1,62 +0,0 @@
-# sm
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Bob
-  id: sm
-  title: Scrum Master
-  icon: 🏃
-  whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
-  customization: null
-persona:
-  role: Technical Scrum Master - Story Preparation Specialist
-  style: Task-oriented, efficient, precise, focused on clear developer handoffs
-  identity: Story creation expert who prepares detailed, actionable stories for AI developers
-  focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
-  core_principles:
-    - 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!
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - draft: Execute task create-next-story.md
-  - correct-course: Execute task correct-course.md
-  - story-checklist: Execute task execute-checklist.md with checklist story-draft-checklist.md
-  - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - create-next-story.md
-    - execute-checklist.md
-    - correct-course.md
-  templates:
-    - story-tmpl.yaml
-  checklists:
-    - story-draft-checklist.md
-```

bmad-core/agents/ux-expert.md

@@ -1,66 +0,0 @@
-# ux-expert
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-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), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - 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
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Sally
-  id: ux-expert
-  title: UX Expert
-  icon: 🎨
-  whenToUse: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
-  customization: null
-persona:
-  role: User Experience Designer & UI Specialist
-  style: Empathetic, creative, detail-oriented, user-obsessed, data-informed
-  identity: UX Expert specializing in user experience design and creating intuitive interfaces
-  focus: User research, interaction design, visual design, accessibility, AI-powered UI generation
-  core_principles:
-    - User-Centric above all - Every design decision must serve user needs
-    - Simplicity Through Iteration - Start simple, refine based on feedback
-    - Delight in the Details - Thoughtful micro-interactions create memorable experiences
-    - Design for Real Scenarios - Consider edge cases, errors, and loading states
-    - Collaborate, Don't Dictate - Best solutions emerge from cross-functional work
-    - 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.
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - create-front-end-spec: run task create-doc.md with template front-end-spec-tmpl.yaml
-  - generate-ui-prompt: Run task generate-ai-frontend-prompt.md
-  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - generate-ai-frontend-prompt.md
-    - create-doc.md
-    - execute-checklist.md
-  templates:
-    - front-end-spec-tmpl.yaml
-  data:
-    - technical-preferences.md
-```

bmad-core/checklists/architect-checklist.md

@@ -1,438 +0,0 @@
-# Architect Solution Validation Checklist
-
-This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - REQUIRED ARTIFACTS
-
-Before proceeding with this checklist, ensure you have access to:
-
-1. architecture.md - The primary architecture document (check docs/architecture.md)
-2. prd.md - Product Requirements Document for requirements alignment (check docs/prd.md)
-3. frontend-architecture.md or fe-architecture.md - If this is a UI project (check docs/frontend-architecture.md)
-4. Any system diagrams referenced in the architecture
-5. API documentation if available
-6. Technology stack details and version specifications
-
-IMPORTANT: If any required documents are missing or inaccessible, immediately ask the user for their location or content before proceeding.
-
-PROJECT TYPE DETECTION:
-First, determine the project type by checking:
-
-- Does the architecture include a frontend/UI component?
-- Is there a frontend-architecture.md document?
-- Does the PRD mention user interfaces or frontend requirements?
-
-If this is a backend-only or service-only project:
-
-- Skip sections marked with [[FRONTEND ONLY]]
-- Focus extra attention on API design, service architecture, and integration patterns
-- Note in your final report that frontend sections were skipped due to project type
-
-VALIDATION APPROACH:
-For each section, you must:
-
-1. Deep Analysis - Don't just check boxes, thoroughly analyze each item against the provided documentation
-2. Evidence-Based - Cite specific sections or quotes from the documents when validating
-3. Critical Thinking - Question assumptions and identify gaps, not just confirm what's present
-4. Risk Assessment - Consider what could go wrong with each architectural decision
-
-EXECUTION MODE:
-Ask the user if they want to work through the checklist:
-
-- Section by section (interactive mode) - Review each section, present findings, get confirmation before proceeding
-- All at once (comprehensive mode) - Complete full analysis and present comprehensive report at end]]
-
-## 1. REQUIREMENTS ALIGNMENT
-
-[[LLM: Before evaluating this section, take a moment to fully understand the product's purpose and goals from the PRD. What is the core problem being solved? Who are the users? What are the critical success factors? Keep these in mind as you validate alignment. For each item, don't just check if it's mentioned - verify that the architecture provides a concrete technical solution.]]
-
-### 1.1 Functional Requirements Coverage
-
-- [ ] Architecture supports all functional requirements in the PRD
-- [ ] Technical approaches for all epics and stories are addressed
-- [ ] Edge cases and performance scenarios are considered
-- [ ] All required integrations are accounted for
-- [ ] User journeys are supported by the technical architecture
-
-### 1.2 Non-Functional Requirements Alignment
-
-- [ ] Performance requirements are addressed with specific solutions
-- [ ] Scalability considerations are documented with approach
-- [ ] Security requirements have corresponding technical controls
-- [ ] Reliability and resilience approaches are defined
-- [ ] Compliance requirements have technical implementations
-
-### 1.3 Technical Constraints Adherence
-
-- [ ] All technical constraints from PRD are satisfied
-- [ ] Platform/language requirements are followed
-- [ ] Infrastructure constraints are accommodated
-- [ ] Third-party service constraints are addressed
-- [ ] Organizational technical standards are followed
-
-## 2. ARCHITECTURE FUNDAMENTALS
-
-[[LLM: Architecture clarity is crucial for successful implementation. As you review this section, visualize the system as if you were explaining it to a new developer. Are there any ambiguities that could lead to misinterpretation? Would an AI agent be able to implement this architecture without confusion? Look for specific diagrams, component definitions, and clear interaction patterns.]]
-
-### 2.1 Architecture Clarity
-
-- [ ] Architecture is documented with clear diagrams
-- [ ] Major components and their responsibilities are defined
-- [ ] Component interactions and dependencies are mapped
-- [ ] Data flows are clearly illustrated
-- [ ] Technology choices for each component are specified
-
-### 2.2 Separation of Concerns
-
-- [ ] Clear boundaries between UI, business logic, and data layers
-- [ ] Responsibilities are cleanly divided between components
-- [ ] Interfaces between components are well-defined
-- [ ] Components adhere to single responsibility principle
-- [ ] Cross-cutting concerns (logging, auth, etc.) are properly addressed
-
-### 2.3 Design Patterns & Best Practices
-
-- [ ] Appropriate design patterns are employed
-- [ ] Industry best practices are followed
-- [ ] Anti-patterns are avoided
-- [ ] Consistent architectural style throughout
-- [ ] Pattern usage is documented and explained
-
-### 2.4 Modularity & Maintainability
-
-- [ ] System is divided into cohesive, loosely-coupled modules
-- [ ] Components can be developed and tested independently
-- [ ] Changes can be localized to specific components
-- [ ] Code organization promotes discoverability
-- [ ] Architecture specifically designed for AI agent implementation
-
-## 3. TECHNICAL STACK & DECISIONS
-
-[[LLM: Technology choices have long-term implications. For each technology decision, consider: Is this the simplest solution that could work? Are we over-engineering? Will this scale? What are the maintenance implications? Are there security vulnerabilities in the chosen versions? Verify that specific versions are defined, not ranges.]]
-
-### 3.1 Technology Selection
-
-- [ ] Selected technologies meet all requirements
-- [ ] Technology versions are specifically defined (not ranges)
-- [ ] Technology choices are justified with clear rationale
-- [ ] Alternatives considered are documented with pros/cons
-- [ ] Selected stack components work well together
-
-### 3.2 Frontend Architecture [[FRONTEND ONLY]]
-
-[[LLM: Skip this entire section if this is a backend-only or service-only project. Only evaluate if the project includes a user interface.]]
-
-- [ ] UI framework and libraries are specifically selected
-- [ ] State management approach is defined
-- [ ] Component structure and organization is specified
-- [ ] Responsive/adaptive design approach is outlined
-- [ ] Build and bundling strategy is determined
-
-### 3.3 Backend Architecture
-
-- [ ] API design and standards are defined
-- [ ] Service organization and boundaries are clear
-- [ ] Authentication and authorization approach is specified
-- [ ] Error handling strategy is outlined
-- [ ] Backend scaling approach is defined
-
-### 3.4 Data Architecture
-
-- [ ] Data models are fully defined
-- [ ] Database technologies are selected with justification
-- [ ] Data access patterns are documented
-- [ ] Data migration/seeding approach is specified
-- [ ] Data backup and recovery strategies are outlined
-
-## 4. FRONTEND DESIGN & IMPLEMENTATION [[FRONTEND ONLY]]
-
-[[LLM: This entire section should be skipped for backend-only projects. Only evaluate if the project includes a user interface. When evaluating, ensure alignment between the main architecture document and the frontend-specific architecture document.]]
-
-### 4.1 Frontend Philosophy & Patterns
-
-- [ ] Framework & Core Libraries align with main architecture document
-- [ ] Component Architecture (e.g., Atomic Design) is clearly described
-- [ ] State Management Strategy is appropriate for application complexity
-- [ ] Data Flow patterns are consistent and clear
-- [ ] Styling Approach is defined and tooling specified
-
-### 4.2 Frontend Structure & Organization
-
-- [ ] Directory structure is clearly documented with ASCII diagram
-- [ ] Component organization follows stated patterns
-- [ ] File naming conventions are explicit
-- [ ] Structure supports chosen framework's best practices
-- [ ] Clear guidance on where new components should be placed
-
-### 4.3 Component Design
-
-- [ ] Component template/specification format is defined
-- [ ] Component props, state, and events are well-documented
-- [ ] Shared/foundational components are identified
-- [ ] Component reusability patterns are established
-- [ ] Accessibility requirements are built into component design
-
-### 4.4 Frontend-Backend Integration
-
-- [ ] API interaction layer is clearly defined
-- [ ] HTTP client setup and configuration documented
-- [ ] Error handling for API calls is comprehensive
-- [ ] Service definitions follow consistent patterns
-- [ ] Authentication integration with backend is clear
-
-### 4.5 Routing & Navigation
-
-- [ ] Routing strategy and library are specified
-- [ ] Route definitions table is comprehensive
-- [ ] Route protection mechanisms are defined
-- [ ] Deep linking considerations addressed
-- [ ] Navigation patterns are consistent
-
-### 4.6 Frontend Performance
-
-- [ ] Image optimization strategies defined
-- [ ] Code splitting approach documented
-- [ ] Lazy loading patterns established
-- [ ] Re-render optimization techniques specified
-- [ ] Performance monitoring approach defined
-
-## 5. RESILIENCE & OPERATIONAL READINESS
-
-[[LLM: Production systems fail in unexpected ways. As you review this section, think about Murphy's Law - what could go wrong? Consider real-world scenarios: What happens during peak load? How does the system behave when a critical service is down? Can the operations team diagnose issues at 3 AM? Look for specific resilience patterns, not just mentions of "error handling".]]
-
-### 5.1 Error Handling & Resilience
-
-- [ ] Error handling strategy is comprehensive
-- [ ] Retry policies are defined where appropriate
-- [ ] Circuit breakers or fallbacks are specified for critical services
-- [ ] Graceful degradation approaches are defined
-- [ ] System can recover from partial failures
-
-### 5.2 Monitoring & Observability
-
-- [ ] Logging strategy is defined
-- [ ] Monitoring approach is specified
-- [ ] Key metrics for system health are identified
-- [ ] Alerting thresholds and strategies are outlined
-- [ ] Debugging and troubleshooting capabilities are built in
-
-### 5.3 Performance & Scaling
-
-- [ ] Performance bottlenecks are identified and addressed
-- [ ] Caching strategy is defined where appropriate
-- [ ] Load balancing approach is specified
-- [ ] Horizontal and vertical scaling strategies are outlined
-- [ ] Resource sizing recommendations are provided
-
-### 5.4 Deployment & DevOps
-
-- [ ] Deployment strategy is defined
-- [ ] CI/CD pipeline approach is outlined
-- [ ] Environment strategy (dev, staging, prod) is specified
-- [ ] Infrastructure as Code approach is defined
-- [ ] Rollback and recovery procedures are outlined
-
-## 6. SECURITY & COMPLIANCE
-
-[[LLM: Security is not optional. Review this section with a hacker's mindset - how could someone exploit this system? Also consider compliance: Are there industry-specific regulations that apply? GDPR? HIPAA? PCI? Ensure the architecture addresses these proactively. Look for specific security controls, not just general statements.]]
-
-### 6.1 Authentication & Authorization
-
-- [ ] Authentication mechanism is clearly defined
-- [ ] Authorization model is specified
-- [ ] Role-based access control is outlined if required
-- [ ] Session management approach is defined
-- [ ] Credential management is addressed
-
-### 6.2 Data Security
-
-- [ ] Data encryption approach (at rest and in transit) is specified
-- [ ] Sensitive data handling procedures are defined
-- [ ] Data retention and purging policies are outlined
-- [ ] Backup encryption is addressed if required
-- [ ] Data access audit trails are specified if required
-
-### 6.3 API & Service Security
-
-- [ ] API security controls are defined
-- [ ] Rate limiting and throttling approaches are specified
-- [ ] Input validation strategy is outlined
-- [ ] CSRF/XSS prevention measures are addressed
-- [ ] Secure communication protocols are specified
-
-### 6.4 Infrastructure Security
-
-- [ ] Network security design is outlined
-- [ ] Firewall and security group configurations are specified
-- [ ] Service isolation approach is defined
-- [ ] Least privilege principle is applied
-- [ ] Security monitoring strategy is outlined
-
-## 7. IMPLEMENTATION GUIDANCE
-
-[[LLM: Clear implementation guidance prevents costly mistakes. As you review this section, imagine you're a developer starting on day one. Do they have everything they need to be productive? Are coding standards clear enough to maintain consistency across the team? Look for specific examples and patterns.]]
-
-### 7.1 Coding Standards & Practices
-
-- [ ] Coding standards are defined
-- [ ] Documentation requirements are specified
-- [ ] Testing expectations are outlined
-- [ ] Code organization principles are defined
-- [ ] Naming conventions are specified
-
-### 7.2 Testing Strategy
-
-- [ ] Unit testing approach is defined
-- [ ] Integration testing strategy is outlined
-- [ ] E2E testing approach is specified
-- [ ] Performance testing requirements are outlined
-- [ ] Security testing approach is defined
-
-### 7.3 Frontend Testing [[FRONTEND ONLY]]
-
-[[LLM: Skip this subsection for backend-only projects.]]
-
-- [ ] Component testing scope and tools defined
-- [ ] UI integration testing approach specified
-- [ ] Visual regression testing considered
-- [ ] Accessibility testing tools identified
-- [ ] Frontend-specific test data management addressed
-
-### 7.4 Development Environment
-
-- [ ] Local development environment setup is documented
-- [ ] Required tools and configurations are specified
-- [ ] Development workflows are outlined
-- [ ] Source control practices are defined
-- [ ] Dependency management approach is specified
-
-### 7.5 Technical Documentation
-
-- [ ] API documentation standards are defined
-- [ ] Architecture documentation requirements are specified
-- [ ] Code documentation expectations are outlined
-- [ ] System diagrams and visualizations are included
-- [ ] Decision records for key choices are included
-
-## 8. DEPENDENCY & INTEGRATION MANAGEMENT
-
-[[LLM: Dependencies are often the source of production issues. For each dependency, consider: What happens if it's unavailable? Is there a newer version with security patches? Are we locked into a vendor? What's our contingency plan? Verify specific versions and fallback strategies.]]
-
-### 8.1 External Dependencies
-
-- [ ] All external dependencies are identified
-- [ ] Versioning strategy for dependencies is defined
-- [ ] Fallback approaches for critical dependencies are specified
-- [ ] Licensing implications are addressed
-- [ ] Update and patching strategy is outlined
-
-### 8.2 Internal Dependencies
-
-- [ ] Component dependencies are clearly mapped
-- [ ] Build order dependencies are addressed
-- [ ] Shared services and utilities are identified
-- [ ] Circular dependencies are eliminated
-- [ ] Versioning strategy for internal components is defined
-
-### 8.3 Third-Party Integrations
-
-- [ ] All third-party integrations are identified
-- [ ] Integration approaches are defined
-- [ ] Authentication with third parties is addressed
-- [ ] Error handling for integration failures is specified
-- [ ] Rate limits and quotas are considered
-
-## 9. AI AGENT IMPLEMENTATION SUITABILITY
-
-[[LLM: This architecture may be implemented by AI agents. Review with extreme clarity in mind. Are patterns consistent? Is complexity minimized? Would an AI agent make incorrect assumptions? Remember: explicit is better than implicit. Look for clear file structures, naming conventions, and implementation patterns.]]
-
-### 9.1 Modularity for AI Agents
-
-- [ ] Components are sized appropriately for AI agent implementation
-- [ ] Dependencies between components are minimized
-- [ ] Clear interfaces between components are defined
-- [ ] Components have singular, well-defined responsibilities
-- [ ] File and code organization optimized for AI agent understanding
-
-### 9.2 Clarity & Predictability
-
-- [ ] Patterns are consistent and predictable
-- [ ] Complex logic is broken down into simpler steps
-- [ ] Architecture avoids overly clever or obscure approaches
-- [ ] Examples are provided for unfamiliar patterns
-- [ ] Component responsibilities are explicit and clear
-
-### 9.3 Implementation Guidance
-
-- [ ] Detailed implementation guidance is provided
-- [ ] Code structure templates are defined
-- [ ] Specific implementation patterns are documented
-- [ ] Common pitfalls are identified with solutions
-- [ ] References to similar implementations are provided when helpful
-
-### 9.4 Error Prevention & Handling
-
-- [ ] Design reduces opportunities for implementation errors
-- [ ] Validation and error checking approaches are defined
-- [ ] Self-healing mechanisms are incorporated where possible
-- [ ] Testing patterns are clearly defined
-- [ ] Debugging guidance is provided
-
-## 10. ACCESSIBILITY IMPLEMENTATION [[FRONTEND ONLY]]
-
-[[LLM: Skip this section for backend-only projects. Accessibility is a core requirement for any user interface.]]
-
-### 10.1 Accessibility Standards
-
-- [ ] Semantic HTML usage is emphasized
-- [ ] ARIA implementation guidelines provided
-- [ ] Keyboard navigation requirements defined
-- [ ] Focus management approach specified
-- [ ] Screen reader compatibility addressed
-
-### 10.2 Accessibility Testing
-
-- [ ] Accessibility testing tools identified
-- [ ] Testing process integrated into workflow
-- [ ] Compliance targets (WCAG level) specified
-- [ ] Manual testing procedures defined
-- [ ] Automated testing approach outlined
-
-[[LLM: FINAL VALIDATION REPORT GENERATION
-
-Now that you've completed the checklist, generate a comprehensive validation report that includes:
-
-1. Executive Summary
-   - Overall architecture readiness (High/Medium/Low)
-   - Critical risks identified
-   - Key strengths of the architecture
-   - Project type (Full-stack/Frontend/Backend) and sections evaluated
-
-2. Section Analysis
-   - Pass rate for each major section (percentage of items passed)
-   - Most concerning failures or gaps
-   - Sections requiring immediate attention
-   - Note any sections skipped due to project type
-
-3. Risk Assessment
-   - Top 5 risks by severity
-   - Mitigation recommendations for each
-   - Timeline impact of addressing issues
-
-4. Recommendations
-   - Must-fix items before development
-   - Should-fix items for better quality
-   - Nice-to-have improvements
-
-5. AI Implementation Readiness
-   - Specific concerns for AI agent implementation
-   - Areas needing additional clarification
-   - Complexity hotspots to address
-
-6. Frontend-Specific Assessment (if applicable)
-   - Frontend architecture completeness
-   - Alignment between main and frontend architecture docs
-   - UI/UX specification coverage
-   - Component design clarity
-
-After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]

bmad-core/checklists/change-checklist.md

@@ -1,182 +0,0 @@
-# Change Navigation Checklist
-
-**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
-
-**Instructions:** Review each item with the user. Mark `[x]` for completed/confirmed, `[N/A]` if not applicable, or add notes for discussion points.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - CHANGE NAVIGATION
-
-Changes during development are inevitable, but how we handle them determines project success or failure.
-
-Before proceeding, understand:
-
-1. This checklist is for SIGNIFICANT changes that affect the project direction
-2. Minor adjustments within a story don't require this process
-3. The goal is to minimize wasted work while adapting to new realities
-4. User buy-in is critical - they must understand and approve changes
-
-Required context:
-
-- The triggering story or issue
-- Current project state (completed stories, current epic)
-- Access to PRD, architecture, and other key documents
-- Understanding of remaining work planned
-
-APPROACH:
-This is an interactive process with the user. Work through each section together, discussing implications and options. The user makes final decisions, but provide expert guidance on technical feasibility and impact.
-
-REMEMBER: Changes are opportunities to improve, not failures. Handle them professionally and constructively.]]
-
----
-
-## 1. Understand the Trigger & Context
-
-[[LLM: Start by fully understanding what went wrong and why. Don't jump to solutions yet. Ask probing questions:
-
-- What exactly happened that triggered this review?
-- Is this a one-time issue or symptomatic of a larger problem?
-- Could this have been anticipated earlier?
-- What assumptions were incorrect?
-
-Be specific and factual, not blame-oriented.]]
-
-- [ ] **Identify Triggering Story:** Clearly identify the story (or stories) that revealed the issue.
-- [ ] **Define the Issue:** Articulate the core problem precisely.
-  - [ ] Is it a technical limitation/dead-end?
-  - [ ] Is it a newly discovered requirement?
-  - [ ] Is it a fundamental misunderstanding of existing requirements?
-  - [ ] Is it a necessary pivot based on feedback or new information?
-  - [ ] Is it a failed/abandoned story needing a new approach?
-- [ ] **Assess Initial Impact:** Describe the immediate observed consequences (e.g., blocked progress, incorrect functionality, non-viable tech).
-- [ ] **Gather Evidence:** Note any specific logs, error messages, user feedback, or analysis that supports the issue definition.
-
-## 2. Epic Impact Assessment
-
-[[LLM: Changes ripple through the project structure. Systematically evaluate:
-
-1. Can we salvage the current epic with modifications?
-2. Do future epics still make sense given this change?
-3. Are we creating or eliminating dependencies?
-4. Does the epic sequence need reordering?
-
-Think about both immediate and downstream effects.]]
-
-- [ ] **Analyze Current Epic:**
-  - [ ] Can the current epic containing the trigger story still be completed?
-  - [ ] Does the current epic need modification (story changes, additions, removals)?
-  - [ ] Should the current epic be abandoned or fundamentally redefined?
-- [ ] **Analyze Future Epics:**
-  - [ ] Review all remaining planned epics.
-  - [ ] Does the issue require changes to planned stories in future epics?
-  - [ ] Does the issue invalidate any future epics?
-  - [ ] Does the issue necessitate the creation of entirely new epics?
-  - [ ] Should the order/priority of future epics be changed?
-- [ ] **Summarize Epic Impact:** Briefly document the overall effect on the project's epic structure and flow.
-
-## 3. Artifact Conflict & Impact Analysis
-
-[[LLM: Documentation drives development in BMad. Check each artifact:
-
-1. Does this change invalidate documented decisions?
-2. Are architectural assumptions still valid?
-3. Do user flows need rethinking?
-4. Are technical constraints different than documented?
-
-Be thorough - missed conflicts cause future problems.]]
-
-- [ ] **Review PRD:**
-  - [ ] Does the issue conflict with the core goals or requirements stated in the PRD?
-  - [ ] Does the PRD need clarification or updates based on the new understanding?
-- [ ] **Review Architecture Document:**
-  - [ ] Does the issue conflict with the documented architecture (components, patterns, tech choices)?
-  - [ ] Are specific components/diagrams/sections impacted?
-  - [ ] Does the technology list need updating?
-  - [ ] Do data models or schemas need revision?
-  - [ ] Are external API integrations affected?
-- [ ] **Review Frontend Spec (if applicable):**
-  - [ ] Does the issue conflict with the FE architecture, component library choice, or UI/UX design?
-  - [ ] Are specific FE components or user flows impacted?
-- [ ] **Review Other Artifacts (if applicable):**
-  - [ ] Consider impact on deployment scripts, IaC, monitoring setup, etc.
-- [ ] **Summarize Artifact Impact:** List all artifacts requiring updates and the nature of the changes needed.
-
-## 4. Path Forward Evaluation
-
-[[LLM: Present options clearly with pros/cons. For each path:
-
-1. What's the effort required?
-2. What work gets thrown away?
-3. What risks are we taking?
-4. How does this affect timeline?
-5. Is this sustainable long-term?
-
-Be honest about trade-offs. There's rarely a perfect solution.]]
-
-- [ ] **Option 1: Direct Adjustment / Integration:**
-  - [ ] Can the issue be addressed by modifying/adding future stories within the existing plan?
-  - [ ] Define the scope and nature of these adjustments.
-  - [ ] Assess feasibility, effort, and risks of this path.
-- [ ] **Option 2: Potential Rollback:**
-  - [ ] Would reverting completed stories significantly simplify addressing the issue?
-  - [ ] Identify specific stories/commits to consider for rollback.
-  - [ ] Assess the effort required for rollback.
-  - [ ] Assess the impact of rollback (lost work, data implications).
-  - [ ] Compare the net benefit/cost vs. Direct Adjustment.
-- [ ] **Option 3: PRD MVP Review & Potential Re-scoping:**
-  - [ ] Is the original PRD MVP still achievable given the issue and constraints?
-  - [ ] Does the MVP scope need reduction (removing features/epics)?
-  - [ ] Do the core MVP goals need modification?
-  - [ ] Are alternative approaches needed to meet the original MVP intent?
-  - [ ] **Extreme Case:** Does the issue necessitate a fundamental replan or potentially a new PRD V2 (to be handled by PM)?
-- [ ] **Select Recommended Path:** Based on the evaluation, agree on the most viable path forward.
-
-## 5. Sprint Change Proposal Components
-
-[[LLM: The proposal must be actionable and clear. Ensure:
-
-1. The issue is explained in plain language
-2. Impacts are quantified where possible
-3. The recommended path has clear rationale
-4. Next steps are specific and assigned
-5. Success criteria for the change are defined
-
-This proposal guides all subsequent work.]]
-
-(Ensure all agreed-upon points from previous sections are captured in the proposal)
-
-- [ ] **Identified Issue Summary:** Clear, concise problem statement.
-- [ ] **Epic Impact Summary:** How epics are affected.
-- [ ] **Artifact Adjustment Needs:** List of documents to change.
-- [ ] **Recommended Path Forward:** Chosen solution with rationale.
-- [ ] **PRD MVP Impact:** Changes to scope/goals (if any).
-- [ ] **High-Level Action Plan:** Next steps for stories/updates.
-- [ ] **Agent Handoff Plan:** Identify roles needed (PM, Arch, Design Arch, PO).
-
-## 6. Final Review & Handoff
-
-[[LLM: Changes require coordination. Before concluding:
-
-1. Is the user fully aligned with the plan?
-2. Do all stakeholders understand the impacts?
-3. Are handoffs to other agents clear?
-4. Is there a rollback plan if the change fails?
-5. How will we validate the change worked?
-
-Get explicit approval - implicit agreement causes problems.
-
-FINAL REPORT:
-After completing the checklist, provide a concise summary:
-
-- What changed and why
-- What we're doing about it
-- Who needs to do what
-- When we'll know if it worked
-
-Keep it action-oriented and forward-looking.]]
-
-- [ ] **Review Checklist:** Confirm all relevant items were discussed.
-- [ ] **Review Sprint Change Proposal:** Ensure it accurately reflects the discussion and decisions.
-- [ ] **User Approval:** Obtain explicit user approval for the proposal.
-- [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
-
----

bmad-core/checklists/pm-checklist.md

@@ -1,370 +0,0 @@
-# Product Manager (PM) Requirements Checklist
-
-This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - PM CHECKLIST
-
-Before proceeding with this checklist, ensure you have access to:
-
-1. prd.md - The Product Requirements Document (check docs/prd.md)
-2. Any user research, market analysis, or competitive analysis documents
-3. Business goals and strategy documents
-4. Any existing epic definitions or user stories
-
-IMPORTANT: If the PRD is missing, immediately ask the user for its location or content before proceeding.
-
-VALIDATION APPROACH:
-
-1. User-Centric - Every requirement should tie back to user value
-2. MVP Focus - Ensure scope is truly minimal while viable
-3. Clarity - Requirements should be unambiguous and testable
-4. Completeness - All aspects of the product vision are covered
-5. Feasibility - Requirements are technically achievable
-
-EXECUTION MODE:
-Ask the user if they want to work through the checklist:
-
-- Section by section (interactive mode) - Review each section, present findings, get confirmation before proceeding
-- All at once (comprehensive mode) - Complete full analysis and present comprehensive report at end]]
-
-## 1. PROBLEM DEFINITION & CONTEXT
-
-[[LLM: The foundation of any product is a clear problem statement. As you review this section:
-
-1. Verify the problem is real and worth solving
-2. Check that the target audience is specific, not "everyone"
-3. Ensure success metrics are measurable, not vague aspirations
-4. Look for evidence of user research, not just assumptions
-5. Confirm the problem-solution fit is logical]]
-
-### 1.1 Problem Statement
-
-- [ ] Clear articulation of the problem being solved
-- [ ] Identification of who experiences the problem
-- [ ] Explanation of why solving this problem matters
-- [ ] Quantification of problem impact (if possible)
-- [ ] Differentiation from existing solutions
-
-### 1.2 Business Goals & Success Metrics
-
-- [ ] Specific, measurable business objectives defined
-- [ ] Clear success metrics and KPIs established
-- [ ] Metrics are tied to user and business value
-- [ ] Baseline measurements identified (if applicable)
-- [ ] Timeframe for achieving goals specified
-
-### 1.3 User Research & Insights
-
-- [ ] Target user personas clearly defined
-- [ ] User needs and pain points documented
-- [ ] User research findings summarized (if available)
-- [ ] Competitive analysis included
-- [ ] Market context provided
-
-## 2. MVP SCOPE DEFINITION
-
-[[LLM: MVP scope is critical - too much and you waste resources, too little and you can't validate. Check:
-
-1. Is this truly minimal? Challenge every feature
-2. Does each feature directly address the core problem?
-3. Are "nice-to-haves" clearly separated from "must-haves"?
-4. Is the rationale for inclusion/exclusion documented?
-5. Can you ship this in the target timeframe?]]
-
-### 2.1 Core Functionality
-
-- [ ] Essential features clearly distinguished from nice-to-haves
-- [ ] Features directly address defined problem statement
-- [ ] Each Epic ties back to specific user needs
-- [ ] Features and Stories are described from user perspective
-- [ ] Minimum requirements for success defined
-
-### 2.2 Scope Boundaries
-
-- [ ] Clear articulation of what is OUT of scope
-- [ ] Future enhancements section included
-- [ ] Rationale for scope decisions documented
-- [ ] MVP minimizes functionality while maximizing learning
-- [ ] Scope has been reviewed and refined multiple times
-
-### 2.3 MVP Validation Approach
-
-- [ ] Method for testing MVP success defined
-- [ ] Initial user feedback mechanisms planned
-- [ ] Criteria for moving beyond MVP specified
-- [ ] Learning goals for MVP articulated
-- [ ] Timeline expectations set
-
-## 3. USER EXPERIENCE REQUIREMENTS
-
-[[LLM: UX requirements bridge user needs and technical implementation. Validate:
-
-1. User flows cover the primary use cases completely
-2. Edge cases are identified (even if deferred)
-3. Accessibility isn't an afterthought
-4. Performance expectations are realistic
-5. Error states and recovery are planned]]
-
-### 3.1 User Journeys & Flows
-
-- [ ] Primary user flows documented
-- [ ] Entry and exit points for each flow identified
-- [ ] Decision points and branches mapped
-- [ ] Critical path highlighted
-- [ ] Edge cases considered
-
-### 3.2 Usability Requirements
-
-- [ ] Accessibility considerations documented
-- [ ] Platform/device compatibility specified
-- [ ] Performance expectations from user perspective defined
-- [ ] Error handling and recovery approaches outlined
-- [ ] User feedback mechanisms identified
-
-### 3.3 UI Requirements
-
-- [ ] Information architecture outlined
-- [ ] Critical UI components identified
-- [ ] Visual design guidelines referenced (if applicable)
-- [ ] Content requirements specified
-- [ ] High-level navigation structure defined
-
-## 4. FUNCTIONAL REQUIREMENTS
-
-[[LLM: Functional requirements must be clear enough for implementation. Check:
-
-1. Requirements focus on WHAT not HOW (no implementation details)
-2. Each requirement is testable (how would QA verify it?)
-3. Dependencies are explicit (what needs to be built first?)
-4. Requirements use consistent terminology
-5. Complex features are broken into manageable pieces]]
-
-### 4.1 Feature Completeness
-
-- [ ] All required features for MVP documented
-- [ ] Features have clear, user-focused descriptions
-- [ ] Feature priority/criticality indicated
-- [ ] Requirements are testable and verifiable
-- [ ] Dependencies between features identified
-
-### 4.2 Requirements Quality
-
-- [ ] Requirements are specific and unambiguous
-- [ ] Requirements focus on WHAT not HOW
-- [ ] Requirements use consistent terminology
-- [ ] Complex requirements broken into simpler parts
-- [ ] Technical jargon minimized or explained
-
-### 4.3 User Stories & Acceptance Criteria
-
-- [ ] Stories follow consistent format
-- [ ] Acceptance criteria are testable
-- [ ] Stories are sized appropriately (not too large)
-- [ ] Stories are independent where possible
-- [ ] Stories include necessary context
-- [ ] Local testability requirements (e.g., via CLI) defined in ACs for relevant backend/data stories
-
-## 5. NON-FUNCTIONAL REQUIREMENTS
-
-### 5.1 Performance Requirements
-
-- [ ] Response time expectations defined
-- [ ] Throughput/capacity requirements specified
-- [ ] Scalability needs documented
-- [ ] Resource utilization constraints identified
-- [ ] Load handling expectations set
-
-### 5.2 Security & Compliance
-
-- [ ] Data protection requirements specified
-- [ ] Authentication/authorization needs defined
-- [ ] Compliance requirements documented
-- [ ] Security testing requirements outlined
-- [ ] Privacy considerations addressed
-
-### 5.3 Reliability & Resilience
-
-- [ ] Availability requirements defined
-- [ ] Backup and recovery needs documented
-- [ ] Fault tolerance expectations set
-- [ ] Error handling requirements specified
-- [ ] Maintenance and support considerations included
-
-### 5.4 Technical Constraints
-
-- [ ] Platform/technology constraints documented
-- [ ] Integration requirements outlined
-- [ ] Third-party service dependencies identified
-- [ ] Infrastructure requirements specified
-- [ ] Development environment needs identified
-
-## 6. EPIC & STORY STRUCTURE
-
-### 6.1 Epic Definition
-
-- [ ] Epics represent cohesive units of functionality
-- [ ] Epics focus on user/business value delivery
-- [ ] Epic goals clearly articulated
-- [ ] Epics are sized appropriately for incremental delivery
-- [ ] Epic sequence and dependencies identified
-
-### 6.2 Story Breakdown
-
-- [ ] Stories are broken down to appropriate size
-- [ ] Stories have clear, independent value
-- [ ] Stories include appropriate acceptance criteria
-- [ ] Story dependencies and sequence documented
-- [ ] Stories aligned with epic goals
-
-### 6.3 First Epic Completeness
-
-- [ ] First epic includes all necessary setup steps
-- [ ] Project scaffolding and initialization addressed
-- [ ] Core infrastructure setup included
-- [ ] Development environment setup addressed
-- [ ] Local testability established early
-
-## 7. TECHNICAL GUIDANCE
-
-### 7.1 Architecture Guidance
-
-- [ ] Initial architecture direction provided
-- [ ] Technical constraints clearly communicated
-- [ ] Integration points identified
-- [ ] Performance considerations highlighted
-- [ ] Security requirements articulated
-- [ ] Known areas of high complexity or technical risk flagged for architectural deep-dive
-
-### 7.2 Technical Decision Framework
-
-- [ ] Decision criteria for technical choices provided
-- [ ] Trade-offs articulated for key decisions
-- [ ] Rationale for selecting primary approach over considered alternatives documented (for key design/feature choices)
-- [ ] Non-negotiable technical requirements highlighted
-- [ ] Areas requiring technical investigation identified
-- [ ] Guidance on technical debt approach provided
-
-### 7.3 Implementation Considerations
-
-- [ ] Development approach guidance provided
-- [ ] Testing requirements articulated
-- [ ] Deployment expectations set
-- [ ] Monitoring needs identified
-- [ ] Documentation requirements specified
-
-## 8. CROSS-FUNCTIONAL REQUIREMENTS
-
-### 8.1 Data Requirements
-
-- [ ] Data entities and relationships identified
-- [ ] Data storage requirements specified
-- [ ] Data quality requirements defined
-- [ ] Data retention policies identified
-- [ ] Data migration needs addressed (if applicable)
-- [ ] Schema changes planned iteratively, tied to stories requiring them
-
-### 8.2 Integration Requirements
-
-- [ ] External system integrations identified
-- [ ] API requirements documented
-- [ ] Authentication for integrations specified
-- [ ] Data exchange formats defined
-- [ ] Integration testing requirements outlined
-
-### 8.3 Operational Requirements
-
-- [ ] Deployment frequency expectations set
-- [ ] Environment requirements defined
-- [ ] Monitoring and alerting needs identified
-- [ ] Support requirements documented
-- [ ] Performance monitoring approach specified
-
-## 9. CLARITY & COMMUNICATION
-
-### 9.1 Documentation Quality
-
-- [ ] Documents use clear, consistent language
-- [ ] Documents are well-structured and organized
-- [ ] Technical terms are defined where necessary
-- [ ] Diagrams/visuals included where helpful
-- [ ] Documentation is versioned appropriately
-
-### 9.2 Stakeholder Alignment
-
-- [ ] Key stakeholders identified
-- [ ] Stakeholder input incorporated
-- [ ] Potential areas of disagreement addressed
-- [ ] Communication plan for updates established
-- [ ] Approval process defined
-
-## PRD & EPIC VALIDATION SUMMARY
-
-[[LLM: FINAL PM CHECKLIST REPORT GENERATION
-
-Create a comprehensive validation report that includes:
-
-1. Executive Summary
-   - Overall PRD completeness (percentage)
-   - MVP scope appropriateness (Too Large/Just Right/Too Small)
-   - Readiness for architecture phase (Ready/Nearly Ready/Not Ready)
-   - Most critical gaps or concerns
-
-2. Category Analysis Table
-   Fill in the actual table with:
-   - Status: PASS (90%+ complete), PARTIAL (60-89%), FAIL (<60%)
-   - Critical Issues: Specific problems that block progress
-
-3. Top Issues by Priority
-   - BLOCKERS: Must fix before architect can proceed
-   - HIGH: Should fix for quality
-   - MEDIUM: Would improve clarity
-   - LOW: Nice to have
-
-4. MVP Scope Assessment
-   - Features that might be cut for true MVP
-   - Missing features that are essential
-   - Complexity concerns
-   - Timeline realism
-
-5. Technical Readiness
-   - Clarity of technical constraints
-   - Identified technical risks
-   - Areas needing architect investigation
-
-6. Recommendations
-   - Specific actions to address each blocker
-   - Suggested improvements
-   - Next steps
-
-After presenting the report, ask if the user wants:
-
-- Detailed analysis of any failed sections
-- Suggestions for improving specific areas
-- Help with refining MVP scope]]
-
-### Category Statuses
-
-| Category                         | Status | Critical Issues |
-| -------------------------------- | ------ | --------------- |
-| 1. Problem Definition & Context  | _TBD_  |                 |
-| 2. MVP Scope Definition          | _TBD_  |                 |
-| 3. User Experience Requirements  | _TBD_  |                 |
-| 4. Functional Requirements       | _TBD_  |                 |
-| 5. Non-Functional Requirements   | _TBD_  |                 |
-| 6. Epic & Story Structure        | _TBD_  |                 |
-| 7. Technical Guidance            | _TBD_  |                 |
-| 8. Cross-Functional Requirements | _TBD_  |                 |
-| 9. Clarity & Communication       | _TBD_  |                 |
-
-### Critical Deficiencies
-
-(To be populated during validation)
-
-### Recommendations
-
-(To be populated during validation)
-
-### Final Decision
-
-- **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
-- **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.

bmad-core/checklists/po-master-checklist.md

@@ -1,432 +0,0 @@
-# Product Owner (PO) Master Validation Checklist
-
-This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - PO MASTER CHECKLIST
-
-PROJECT TYPE DETECTION:
-First, determine the project type by checking:
-
-1. Is this a GREENFIELD project (new from scratch)?
-   - Look for: New project initialization, no existing codebase references
-   - Check for: prd.md, architecture.md, new project setup stories
-
-2. Is this a BROWNFIELD project (enhancing existing system)?
-   - Look for: References to existing codebase, enhancement/modification language
-   - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
-
-3. Does the project include UI/UX components?
-   - Check for: frontend-architecture.md, UI/UX specifications, design files
-   - Look for: Frontend stories, component specifications, user interface mentions
-
-DOCUMENT REQUIREMENTS:
-Based on project type, ensure you have access to:
-
-For GREENFIELD projects:
-
-- prd.md - The Product Requirements Document
-- architecture.md - The system architecture
-- frontend-architecture.md - If UI/UX is involved
-- All epic and story definitions
-
-For BROWNFIELD projects:
-
-- brownfield-prd.md - The brownfield enhancement requirements
-- brownfield-architecture.md - The enhancement architecture
-- Existing project codebase access (CRITICAL - cannot proceed without this)
-- Current deployment configuration and infrastructure details
-- Database schemas, API documentation, monitoring setup
-
-SKIP INSTRUCTIONS:
-
-- Skip sections marked [[BROWNFIELD ONLY]] for greenfield projects
-- Skip sections marked [[GREENFIELD ONLY]] for brownfield projects
-- Skip sections marked [[UI/UX ONLY]] for backend-only projects
-- Note all skipped sections in your final report
-
-VALIDATION APPROACH:
-
-1. Deep Analysis - Thoroughly analyze each item against documentation
-2. Evidence-Based - Cite specific sections or code when validating
-3. Critical Thinking - Question assumptions and identify gaps
-4. Risk Assessment - Consider what could go wrong with each decision
-
-EXECUTION MODE:
-Ask the user if they want to work through the checklist:
-
-- Section by section (interactive mode) - Review each section, get confirmation before proceeding
-- All at once (comprehensive mode) - Complete full analysis and present report at end]]
-
-## 1. PROJECT SETUP & INITIALIZATION
-
-[[LLM: Project setup is the foundation. For greenfield, ensure clean start. For brownfield, ensure safe integration with existing system. Verify setup matches project type.]]
-
-### 1.1 Project Scaffolding [[GREENFIELD ONLY]]
-
-- [ ] Epic 1 includes explicit steps for project creation/initialization
-- [ ] If using a starter template, steps for cloning/setup are included
-- [ ] If building from scratch, all necessary scaffolding steps are defined
-- [ ] Initial README or documentation setup is included
-- [ ] Repository setup and initial commit processes are defined
-
-### 1.2 Existing System Integration [[BROWNFIELD ONLY]]
-
-- [ ] Existing project analysis has been completed and documented
-- [ ] Integration points with current system are identified
-- [ ] Development environment preserves existing functionality
-- [ ] Local testing approach validated for existing features
-- [ ] Rollback procedures defined for each integration point
-
-### 1.3 Development Environment
-
-- [ ] Local development environment setup is clearly defined
-- [ ] Required tools and versions are specified
-- [ ] Steps for installing dependencies are included
-- [ ] Configuration files are addressed appropriately
-- [ ] Development server setup is included
-
-### 1.4 Core Dependencies
-
-- [ ] All critical packages/libraries are installed early
-- [ ] Package management is properly addressed
-- [ ] Version specifications are appropriately defined
-- [ ] Dependency conflicts or special requirements are noted
-- [ ] [[BROWNFIELD ONLY]] Version compatibility with existing stack verified
-
-## 2. INFRASTRUCTURE & DEPLOYMENT
-
-[[LLM: Infrastructure must exist before use. For brownfield, must integrate with existing infrastructure without breaking it.]]
-
-### 2.1 Database & Data Store Setup
-
-- [ ] Database selection/setup occurs before any operations
-- [ ] Schema definitions are created before data operations
-- [ ] Migration strategies are defined if applicable
-- [ ] Seed data or initial data setup is included if needed
-- [ ] [[BROWNFIELD ONLY]] Database migration risks identified and mitigated
-- [ ] [[BROWNFIELD ONLY]] Backward compatibility ensured
-
-### 2.2 API & Service Configuration
-
-- [ ] API frameworks are set up before implementing endpoints
-- [ ] Service architecture is established before implementing services
-- [ ] Authentication framework is set up before protected routes
-- [ ] Middleware and common utilities are created before use
-- [ ] [[BROWNFIELD ONLY]] API compatibility with existing system maintained
-- [ ] [[BROWNFIELD ONLY]] Integration with existing authentication preserved
-
-### 2.3 Deployment Pipeline
-
-- [ ] CI/CD pipeline is established before deployment actions
-- [ ] Infrastructure as Code (IaC) is set up before use
-- [ ] Environment configurations are defined early
-- [ ] Deployment strategies are defined before implementation
-- [ ] [[BROWNFIELD ONLY]] Deployment minimizes downtime
-- [ ] [[BROWNFIELD ONLY]] Blue-green or canary deployment implemented
-
-### 2.4 Testing Infrastructure
-
-- [ ] Testing frameworks are installed before writing tests
-- [ ] Test environment setup precedes test implementation
-- [ ] Mock services or data are defined before testing
-- [ ] [[BROWNFIELD ONLY]] Regression testing covers existing functionality
-- [ ] [[BROWNFIELD ONLY]] Integration testing validates new-to-existing connections
-
-## 3. EXTERNAL DEPENDENCIES & INTEGRATIONS
-
-[[LLM: External dependencies often block progress. For brownfield, ensure new dependencies don't conflict with existing ones.]]
-
-### 3.1 Third-Party Services
-
-- [ ] Account creation steps are identified for required services
-- [ ] API key acquisition processes are defined
-- [ ] Steps for securely storing credentials are included
-- [ ] Fallback or offline development options are considered
-- [ ] [[BROWNFIELD ONLY]] Compatibility with existing services verified
-- [ ] [[BROWNFIELD ONLY]] Impact on existing integrations assessed
-
-### 3.2 External APIs
-
-- [ ] Integration points with external APIs are clearly identified
-- [ ] Authentication with external services is properly sequenced
-- [ ] API limits or constraints are acknowledged
-- [ ] Backup strategies for API failures are considered
-- [ ] [[BROWNFIELD ONLY]] Existing API dependencies maintained
-
-### 3.3 Infrastructure Services
-
-- [ ] Cloud resource provisioning is properly sequenced
-- [ ] DNS or domain registration needs are identified
-- [ ] Email or messaging service setup is included if needed
-- [ ] CDN or static asset hosting setup precedes their use
-- [ ] [[BROWNFIELD ONLY]] Existing infrastructure services preserved
-
-## 4. UI/UX CONSIDERATIONS [[UI/UX ONLY]]
-
-[[LLM: Only evaluate this section if the project includes user interface components. Skip entirely for backend-only projects.]]
-
-### 4.1 Design System Setup
-
-- [ ] UI framework and libraries are selected and installed early
-- [ ] Design system or component library is established
-- [ ] Styling approach (CSS modules, styled-components, etc.) is defined
-- [ ] Responsive design strategy is established
-- [ ] Accessibility requirements are defined upfront
-
-### 4.2 Frontend Infrastructure
-
-- [ ] Frontend build pipeline is configured before development
-- [ ] Asset optimization strategy is defined
-- [ ] Frontend testing framework is set up
-- [ ] Component development workflow is established
-- [ ] [[BROWNFIELD ONLY]] UI consistency with existing system maintained
-
-### 4.3 User Experience Flow
-
-- [ ] User journeys are mapped before implementation
-- [ ] Navigation patterns are defined early
-- [ ] Error states and loading states are planned
-- [ ] Form validation patterns are established
-- [ ] [[BROWNFIELD ONLY]] Existing user workflows preserved or migrated
-
-## 5. USER/AGENT RESPONSIBILITY
-
-[[LLM: Clear ownership prevents confusion. Ensure tasks are assigned appropriately based on what only humans can do.]]
-
-### 5.1 User Actions
-
-- [ ] User responsibilities limited to human-only tasks
-- [ ] Account creation on external services assigned to users
-- [ ] Purchasing or payment actions assigned to users
-- [ ] Credential provision appropriately assigned to users
-
-### 5.2 Developer Agent Actions
-
-- [ ] All code-related tasks assigned to developer agents
-- [ ] Automated processes identified as agent responsibilities
-- [ ] Configuration management properly assigned
-- [ ] Testing and validation assigned to appropriate agents
-
-## 6. FEATURE SEQUENCING & DEPENDENCIES
-
-[[LLM: Dependencies create the critical path. For brownfield, ensure new features don't break existing ones.]]
-
-### 6.1 Functional Dependencies
-
-- [ ] Features depending on others are sequenced correctly
-- [ ] Shared components are built before their use
-- [ ] User flows follow logical progression
-- [ ] Authentication features precede protected features
-- [ ] [[BROWNFIELD ONLY]] Existing functionality preserved throughout
-
-### 6.2 Technical Dependencies
-
-- [ ] Lower-level services built before higher-level ones
-- [ ] Libraries and utilities created before their use
-- [ ] Data models defined before operations on them
-- [ ] API endpoints defined before client consumption
-- [ ] [[BROWNFIELD ONLY]] Integration points tested at each step
-
-### 6.3 Cross-Epic Dependencies
-
-- [ ] Later epics build upon earlier epic functionality
-- [ ] No epic requires functionality from later epics
-- [ ] Infrastructure from early epics utilized consistently
-- [ ] Incremental value delivery maintained
-- [ ] [[BROWNFIELD ONLY]] Each epic maintains system integrity
-
-## 7. RISK MANAGEMENT [[BROWNFIELD ONLY]]
-
-[[LLM: This section is CRITICAL for brownfield projects. Think pessimistically about what could break.]]
-
-### 7.1 Breaking Change Risks
-
-- [ ] Risk of breaking existing functionality assessed
-- [ ] Database migration risks identified and mitigated
-- [ ] API breaking change risks evaluated
-- [ ] Performance degradation risks identified
-- [ ] Security vulnerability risks evaluated
-
-### 7.2 Rollback Strategy
-
-- [ ] Rollback procedures clearly defined per story
-- [ ] Feature flag strategy implemented
-- [ ] Backup and recovery procedures updated
-- [ ] Monitoring enhanced for new components
-- [ ] Rollback triggers and thresholds defined
-
-### 7.3 User Impact Mitigation
-
-- [ ] Existing user workflows analyzed for impact
-- [ ] User communication plan developed
-- [ ] Training materials updated
-- [ ] Support documentation comprehensive
-- [ ] Migration path for user data validated
-
-## 8. MVP SCOPE ALIGNMENT
-
-[[LLM: MVP means MINIMUM viable product. For brownfield, ensure enhancements are truly necessary.]]
-
-### 8.1 Core Goals Alignment
-
-- [ ] All core goals from PRD are addressed
-- [ ] Features directly support MVP goals
-- [ ] No extraneous features beyond MVP scope
-- [ ] Critical features prioritized appropriately
-- [ ] [[BROWNFIELD ONLY]] Enhancement complexity justified
-
-### 8.2 User Journey Completeness
-
-- [ ] All critical user journeys fully implemented
-- [ ] Edge cases and error scenarios addressed
-- [ ] User experience considerations included
-- [ ] [[UI/UX ONLY]] Accessibility requirements incorporated
-- [ ] [[BROWNFIELD ONLY]] Existing workflows preserved or improved
-
-### 8.3 Technical Requirements
-
-- [ ] All technical constraints from PRD addressed
-- [ ] Non-functional requirements incorporated
-- [ ] Architecture decisions align with constraints
-- [ ] Performance considerations addressed
-- [ ] [[BROWNFIELD ONLY]] Compatibility requirements met
-
-## 9. DOCUMENTATION & HANDOFF
-
-[[LLM: Good documentation enables smooth development. For brownfield, documentation of integration points is critical.]]
-
-### 9.1 Developer Documentation
-
-- [ ] API documentation created alongside implementation
-- [ ] Setup instructions are comprehensive
-- [ ] Architecture decisions documented
-- [ ] Patterns and conventions documented
-- [ ] [[BROWNFIELD ONLY]] Integration points documented in detail
-
-### 9.2 User Documentation
-
-- [ ] User guides or help documentation included if required
-- [ ] Error messages and user feedback considered
-- [ ] Onboarding flows fully specified
-- [ ] [[BROWNFIELD ONLY]] Changes to existing features documented
-
-### 9.3 Knowledge Transfer
-
-- [ ] [[BROWNFIELD ONLY]] Existing system knowledge captured
-- [ ] [[BROWNFIELD ONLY]] Integration knowledge documented
-- [ ] Code review knowledge sharing planned
-- [ ] Deployment knowledge transferred to operations
-- [ ] Historical context preserved
-
-## 10. POST-MVP CONSIDERATIONS
-
-[[LLM: Planning for success prevents technical debt. For brownfield, ensure enhancements don't limit future growth.]]
-
-### 10.1 Future Enhancements
-
-- [ ] Clear separation between MVP and future features
-- [ ] Architecture supports planned enhancements
-- [ ] Technical debt considerations documented
-- [ ] Extensibility points identified
-- [ ] [[BROWNFIELD ONLY]] Integration patterns reusable
-
-### 10.2 Monitoring & Feedback
-
-- [ ] Analytics or usage tracking included if required
-- [ ] User feedback collection considered
-- [ ] Monitoring and alerting addressed
-- [ ] Performance measurement incorporated
-- [ ] [[BROWNFIELD ONLY]] Existing monitoring preserved/enhanced
-
-## VALIDATION SUMMARY
-
-[[LLM: FINAL PO VALIDATION REPORT GENERATION
-
-Generate a comprehensive validation report that adapts to project type:
-
-1. Executive Summary
-   - Project type: [Greenfield/Brownfield] with [UI/No UI]
-   - Overall readiness (percentage)
-   - Go/No-Go recommendation
-   - Critical blocking issues count
-   - Sections skipped due to project type
-
-2. Project-Specific Analysis
-
-   FOR GREENFIELD:
-   - Setup completeness
-   - Dependency sequencing
-   - MVP scope appropriateness
-   - Development timeline feasibility
-
-   FOR BROWNFIELD:
-   - Integration risk level (High/Medium/Low)
-   - Existing system impact assessment
-   - Rollback readiness
-   - User disruption potential
-
-3. Risk Assessment
-   - Top 5 risks by severity
-   - Mitigation recommendations
-   - Timeline impact of addressing issues
-   - [BROWNFIELD] Specific integration risks
-
-4. MVP Completeness
-   - Core features coverage
-   - Missing essential functionality
-   - Scope creep identified
-   - True MVP vs over-engineering
-
-5. Implementation Readiness
-   - Developer clarity score (1-10)
-   - Ambiguous requirements count
-   - Missing technical details
-   - [BROWNFIELD] Integration point clarity
-
-6. Recommendations
-   - Must-fix before development
-   - Should-fix for quality
-   - Consider for improvement
-   - Post-MVP deferrals
-
-7. [BROWNFIELD ONLY] Integration Confidence
-   - Confidence in preserving existing functionality
-   - Rollback procedure completeness
-   - Monitoring coverage for integration points
-   - Support team readiness
-
-After presenting the report, ask if the user wants:
-
-- Detailed analysis of any failed sections
-- Specific story reordering suggestions
-- Risk mitigation strategies
-- [BROWNFIELD] Integration risk deep-dive]]
-
-### Category Statuses
-
-| Category                                | Status | Critical Issues |
-| --------------------------------------- | ------ | --------------- |
-| 1. Project Setup & Initialization       | _TBD_  |                 |
-| 2. Infrastructure & Deployment          | _TBD_  |                 |
-| 3. External Dependencies & Integrations | _TBD_  |                 |
-| 4. UI/UX Considerations                 | _TBD_  |                 |
-| 5. User/Agent Responsibility            | _TBD_  |                 |
-| 6. Feature Sequencing & Dependencies    | _TBD_  |                 |
-| 7. Risk Management (Brownfield)         | _TBD_  |                 |
-| 8. MVP Scope Alignment                  | _TBD_  |                 |
-| 9. Documentation & Handoff              | _TBD_  |                 |
-| 10. Post-MVP Considerations             | _TBD_  |                 |
-
-### Critical Deficiencies
-
-(To be populated during validation)
-
-### Recommendations
-
-(To be populated during validation)
-
-### Final Decision
-
-- **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
-- **CONDITIONAL**: The plan requires specific adjustments before proceeding.
-- **REJECTED**: The plan requires significant revision to address critical deficiencies.

bmad-core/checklists/story-dod-checklist.md

@@ -1,94 +0,0 @@
-# Story Definition of Done (DoD) Checklist
-
-## Instructions for Developer Agent
-
-Before marking a story as 'Review', please go through each item in this checklist. Report the status of each item (e.g., [x] Done, [ ] Not Done, [N/A] Not Applicable) and provide brief comments if necessary.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - STORY DOD VALIDATION
-
-This checklist is for DEVELOPER AGENTS to self-validate their work before marking a story complete.
-
-IMPORTANT: This is a self-assessment. Be honest about what's actually done vs what should be done. It's better to identify issues now than have them found in review.
-
-EXECUTION APPROACH:
-
-1. Go through each section systematically
-2. Mark items as [x] Done, [ ] Not Done, or [N/A] Not Applicable
-3. Add brief comments explaining any [ ] or [N/A] items
-4. Be specific about what was actually implemented
-5. Flag any concerns or technical debt created
-
-The goal is quality delivery, not just checking boxes.]]
-
-## Checklist Items
-
-1. **Requirements Met:**
-
-   [[LLM: Be specific - list each requirement and whether it's complete]]
-   - [ ] All functional requirements specified in the story are implemented.
-   - [ ] All acceptance criteria defined in the story are met.
-
-2. **Coding Standards & Project Structure:**
-
-   [[LLM: Code quality matters for maintainability. Check each item carefully]]
-   - [ ] All new/modified code strictly adheres to `Operational Guidelines`.
-   - [ ] All new/modified code aligns with `Project Structure` (file locations, naming, etc.).
-   - [ ] Adherence to `Tech Stack` for technologies/versions used (if story introduces or modifies tech usage).
-   - [ ] Adherence to `Api Reference` and `Data Models` (if story involves API or data model changes).
-   - [ ] Basic security best practices (e.g., input validation, proper error handling, no hardcoded secrets) applied for new/modified code.
-   - [ ] No new linter errors or warnings introduced.
-   - [ ] Code is well-commented where necessary (clarifying complex logic, not obvious statements).
-
-3. **Testing:**
-
-   [[LLM: Testing proves your code works. Be honest about test coverage]]
-   - [ ] All required unit tests as per the story and `Operational Guidelines` Testing Strategy are implemented.
-   - [ ] All required integration tests (if applicable) as per the story and `Operational Guidelines` Testing Strategy are implemented.
-   - [ ] All tests (unit, integration, E2E if applicable) pass successfully.
-   - [ ] Test coverage meets project standards (if defined).
-
-4. **Functionality & Verification:**
-
-   [[LLM: Did you actually run and test your code? Be specific about what you tested]]
-   - [ ] Functionality has been manually verified by the developer (e.g., running the app locally, checking UI, testing API endpoints).
-   - [ ] Edge cases and potential error conditions considered and handled gracefully.
-
-5. **Story Administration:**
-
-   [[LLM: Documentation helps the next developer. What should they know?]]
-   - [ ] All tasks within the story file are marked as complete.
-   - [ ] Any clarifications or decisions made during development are documented in the story file or linked appropriately.
-   - [ ] The story wrap up section has been completed with notes of changes or information relevant to the next story or overall project, the agent model that was primarily used during development, and the changelog of any changes is properly updated.
-
-6. **Dependencies, Build & Configuration:**
-
-   [[LLM: Build issues block everyone. Ensure everything compiles and runs cleanly]]
-   - [ ] Project builds successfully without errors.
-   - [ ] Project linting passes
-   - [ ] Any new dependencies added were either pre-approved in the story requirements OR explicitly approved by the user during development (approval documented in story file).
-   - [ ] If new dependencies were added, they are recorded in the appropriate project files (e.g., `package.json`, `requirements.txt`) with justification.
-   - [ ] No known security vulnerabilities introduced by newly added and approved dependencies.
-   - [ ] If new environment variables or configurations were introduced by the story, they are documented and handled securely.
-
-7. **Documentation (If Applicable):**
-
-   [[LLM: Good documentation prevents future confusion. What needs explaining?]]
-   - [ ] Relevant inline code documentation (e.g., JSDoc, TSDoc, Python docstrings) for new public APIs or complex logic is complete.
-   - [ ] User-facing documentation updated, if changes impact users.
-   - [ ] Technical documentation (e.g., READMEs, system diagrams) updated if significant architectural changes were made.
-
-## Final Confirmation
-
-[[LLM: FINAL DOD SUMMARY
-
-After completing the checklist:
-
-1. Summarize what was accomplished in this story
-2. List any items marked as [ ] Not Done with explanations
-3. Identify any technical debt or follow-up work needed
-4. Note any challenges or learnings for future stories
-5. Confirm whether the story is truly ready for review
-
-Be honest - it's better to flag issues now than have them discovered later.]]
-
-- [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.

bmad-core/checklists/story-draft-checklist.md

@@ -1,153 +0,0 @@
-# Story Draft Checklist
-
-The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - STORY DRAFT VALIDATION
-
-Before proceeding with this checklist, ensure you have access to:
-
-1. The story document being validated (usually in docs/stories/ or provided directly)
-2. The parent epic context
-3. Any referenced architecture or design documents
-4. Previous related stories if this builds on prior work
-
-IMPORTANT: This checklist validates individual stories BEFORE implementation begins.
-
-VALIDATION PRINCIPLES:
-
-1. Clarity - A developer should understand WHAT to build
-2. Context - WHY this is being built and how it fits
-3. Guidance - Key technical decisions and patterns to follow
-4. Testability - How to verify the implementation works
-5. Self-Contained - Most info needed is in the story itself
-
-REMEMBER: We assume competent developer agents who can:
-
-- Research documentation and codebases
-- Make reasonable technical decisions
-- Follow established patterns
-- Ask for clarification when truly stuck
-
-We're checking for SUFFICIENT guidance, not exhaustive detail.]]
-
-## 1. GOAL & CONTEXT CLARITY
-
-[[LLM: Without clear goals, developers build the wrong thing. Verify:
-
-1. The story states WHAT functionality to implement
-2. The business value or user benefit is clear
-3. How this fits into the larger epic/product is explained
-4. Dependencies are explicit ("requires Story X to be complete")
-5. Success looks like something specific, not vague]]
-
-- [ ] Story goal/purpose is clearly stated
-- [ ] Relationship to epic goals is evident
-- [ ] How the story fits into overall system flow is explained
-- [ ] Dependencies on previous stories are identified (if applicable)
-- [ ] Business context and value are clear
-
-## 2. TECHNICAL IMPLEMENTATION GUIDANCE
-
-[[LLM: Developers need enough technical context to start coding. Check:
-
-1. Key files/components to create or modify are mentioned
-2. Technology choices are specified where non-obvious
-3. Integration points with existing code are identified
-4. Data models or API contracts are defined or referenced
-5. Non-standard patterns or exceptions are called out
-
-Note: We don't need every file listed - just the important ones.]]
-
-- [ ] Key files to create/modify are identified (not necessarily exhaustive)
-- [ ] Technologies specifically needed for this story are mentioned
-- [ ] Critical APIs or interfaces are sufficiently described
-- [ ] Necessary data models or structures are referenced
-- [ ] Required environment variables are listed (if applicable)
-- [ ] Any exceptions to standard coding patterns are noted
-
-## 3. REFERENCE EFFECTIVENESS
-
-[[LLM: References should help, not create a treasure hunt. Ensure:
-
-1. References point to specific sections, not whole documents
-2. The relevance of each reference is explained
-3. Critical information is summarized in the story
-4. References are accessible (not broken links)
-5. Previous story context is summarized if needed]]
-
-- [ ] References to external documents point to specific relevant sections
-- [ ] Critical information from previous stories is summarized (not just referenced)
-- [ ] Context is provided for why references are relevant
-- [ ] References use consistent format (e.g., `docs/filename.md#section`)
-
-## 4. SELF-CONTAINMENT ASSESSMENT
-
-[[LLM: Stories should be mostly self-contained to avoid context switching. Verify:
-
-1. Core requirements are in the story, not just in references
-2. Domain terms are explained or obvious from context
-3. Assumptions are stated explicitly
-4. Edge cases are mentioned (even if deferred)
-5. The story could be understood without reading 10 other documents]]
-
-- [ ] Core information needed is included (not overly reliant on external docs)
-- [ ] Implicit assumptions are made explicit
-- [ ] Domain-specific terms or concepts are explained
-- [ ] Edge cases or error scenarios are addressed
-
-## 5. TESTING GUIDANCE
-
-[[LLM: Testing ensures the implementation actually works. Check:
-
-1. Test approach is specified (unit, integration, e2e)
-2. Key test scenarios are listed
-3. Success criteria are measurable
-4. Special test considerations are noted
-5. Acceptance criteria in the story are testable]]
-
-- [ ] Required testing approach is outlined
-- [ ] Key test scenarios are identified
-- [ ] Success criteria are defined
-- [ ] Special testing considerations are noted (if applicable)
-
-## VALIDATION RESULT
-
-[[LLM: FINAL STORY VALIDATION REPORT
-
-Generate a concise validation report:
-
-1. Quick Summary
-   - Story readiness: READY / NEEDS REVISION / BLOCKED
-   - Clarity score (1-10)
-   - Major gaps identified
-
-2. Fill in the validation table with:
-   - PASS: Requirements clearly met
-   - PARTIAL: Some gaps but workable
-   - FAIL: Critical information missing
-
-3. Specific Issues (if any)
-   - List concrete problems to fix
-   - Suggest specific improvements
-   - Identify any blocking dependencies
-
-4. Developer Perspective
-   - Could YOU implement this story as written?
-   - What questions would you have?
-   - What might cause delays or rework?
-
-Be pragmatic - perfect documentation doesn't exist, but it must be enough to provide the extreme context a dev agent needs to get the work down and not create a mess.]]
-
-| Category                             | Status | Issues |
-| ------------------------------------ | ------ | ------ |
-| 1. Goal & Context Clarity            | _TBD_  |        |
-| 2. Technical Implementation Guidance | _TBD_  |        |
-| 3. Reference Effectiveness           | _TBD_  |        |
-| 4. Self-Containment Assessment       | _TBD_  |        |
-| 5. Testing Guidance                  | _TBD_  |        |
-
-**Final Assessment:**
-
-- READY: The story provides sufficient context for implementation
-- NEEDS REVISION: The story requires updates (see issues)
-- BLOCKED: External information required (specify what information)

bmad-core/core-config.yaml

@@ -1,20 +0,0 @@
-markdownExploder: true
-prd:
-  prdFile: docs/prd.md
-  prdVersion: v4
-  prdSharded: true
-  prdShardedLocation: docs/prd
-  epicFilePattern: epic-{n}*.md
-architecture:
-  architectureFile: docs/architecture.md
-  architectureVersion: v4
-  architectureSharded: true
-  architectureShardedLocation: docs/architecture
-customTechnicalDocuments: null
-devLoadAlwaysFiles:
-  - docs/architecture/coding-standards.md
-  - docs/architecture/tech-stack.md
-  - docs/architecture/source-tree.md
-devDebugLog: .ai/debug-log.md
-devStoryLocation: docs/stories
-slashPrefix: BMad

bmad-core/data/bmad-kb.md

@@ -1,806 +0,0 @@
-# BMad Knowledge Base
-
-## Overview
-
-BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
-
-### Key Features
-
-- **Modular Agent System**: Specialized AI agents for each Agile role
-- **Build System**: Automated dependency resolution and optimization
-- **Dual Environment Support**: Optimized for both web UIs and IDEs
-- **Reusable Resources**: Portable templates, tasks, and checklists
-- **Slash Command Integration**: Quick agent switching and control
-
-### When to Use BMad
-
-- **New Projects (Greenfield)**: Complete end-to-end development
-- **Existing Projects (Brownfield)**: Feature additions and enhancements
-- **Team Collaboration**: Multiple roles working together
-- **Quality Assurance**: Structured testing and validation
-- **Documentation**: Professional PRDs, architecture docs, user stories
-
-## How BMad Works
-
-### The Core Method
-
-BMad transforms you into a "Vibe CEO" - directing a team of specialized AI agents through structured workflows. Here's how:
-
-1. **You Direct, AI Executes**: You provide vision and decisions; agents handle implementation details
-2. **Specialized Agents**: Each agent masters one role (PM, Developer, Architect, etc.)
-3. **Structured Workflows**: Proven patterns guide you from idea to deployed code
-4. **Clean Handoffs**: Fresh context windows ensure agents stay focused and effective
-
-### The Two-Phase Approach
-
-#### Phase 1: Planning (Web UI - Cost Effective)
-
-- Use large context windows (Gemini's 1M tokens)
-- Generate comprehensive documents (PRD, Architecture)
-- Leverage multiple agents for brainstorming
-- Create once, use throughout development
-
-#### Phase 2: Development (IDE - Implementation)
-
-- Shard documents into manageable pieces
-- Execute focused SM → Dev cycles
-- One story at a time, sequential progress
-- Real-time file operations and testing
-
-### The Development Loop
-
-```text
-1. SM Agent (New Chat) → Creates next story from sharded docs
-2. You → Review and approve story
-3. Dev Agent (New Chat) → Implements approved story
-4. QA Agent (New Chat) → Reviews and refactors code
-5. You → Verify completion
-6. Repeat until epic complete
-```
-
-### Why This Works
-
-- **Context Optimization**: Clean chats = better AI performance
-- **Role Clarity**: Agents don't context-switch = higher quality
-- **Incremental Progress**: Small stories = manageable complexity
-- **Human Oversight**: You validate each step = quality control
-- **Document-Driven**: Specs guide everything = consistency
-
-## Getting Started
-
-### Quick Start Options
-
-#### Option 1: Web UI
-
-**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
-
-1. Navigate to `dist/teams/`
-2. Copy `team-fullstack.txt` content
-3. Create new Gemini Gem or CustomGPT
-4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
-5. Type `/help` to see available commands
-
-#### Option 2: IDE Integration
-
-**Best for**: Cursor, Claude Code, Windsurf, Trae, Cline, Roo Code, Github Copilot users
-
-```bash
-# Interactive installation (recommended)
-npx bmad-method install
-```
-
-**Installation Steps**:
-
-- Choose "Complete installation"
-- Select your IDE from supported options:
-  - **Cursor**: Native AI integration
-  - **Claude Code**: Anthropic's official IDE
-  - **Windsurf**: Built-in AI capabilities
-  - **Trae**: Built-in AI capabilities
-  - **Cline**: VS Code extension with AI features
-  - **Roo Code**: Web-based IDE with agent support
-  - **GitHub Copilot**: VS Code extension with AI peer programming assistant
-
-**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
-
-**Verify Installation**:
-
-- `.bmad-core/` folder created with all agents
-- IDE-specific integration files created
-- All agent commands/rules/modes available
-
-**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
-
-### Environment Selection Guide
-
-**Use Web UI for**:
-
-- Initial planning and documentation (PRD, architecture)
-- Cost-effective document creation (especially with Gemini)
-- Brainstorming and analysis phases
-- Multi-agent consultation and planning
-
-**Use IDE for**:
-
-- Active development and coding
-- File operations and project integration
-- Document sharding and story management
-- Implementation workflow (SM/Dev cycles)
-
-**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
-
-### IDE-Only Workflow Considerations
-
-**Can you do everything in IDE?** Yes, but understand the tradeoffs:
-
-**Pros of IDE-Only**:
-
-- Single environment workflow
-- Direct file operations from start
-- No copy/paste between environments
-- Immediate project integration
-
-**Cons of IDE-Only**:
-
-- Higher token costs for large document creation
-- Smaller context windows (varies by IDE/model)
-- May hit limits during planning phases
-- Less cost-effective for brainstorming
-
-**Using Web Agents in IDE**:
-
-- **NOT RECOMMENDED**: Web agents (PM, Architect) have rich dependencies designed for large contexts
-- **Why it matters**: Dev agents are kept lean to maximize coding context
-- **The principle**: "Dev agents code, planning agents plan" - mixing breaks this optimization
-
-**About bmad-master and bmad-orchestrator**:
-
-- **bmad-master**: CAN do any task without switching agents, BUT...
-- **Still use specialized agents for planning**: PM, Architect, and UX Expert have tuned personas that produce better results
-- **Why specialization matters**: Each agent's personality and focus creates higher quality outputs
-- **If using bmad-master/orchestrator**: Fine for planning phases, but...
-
-**CRITICAL RULE for Development**:
-
-- **ALWAYS use SM agent for story creation** - Never use bmad-master or bmad-orchestrator
-- **ALWAYS use Dev agent for implementation** - Never use bmad-master or bmad-orchestrator
-- **Why this matters**: SM and Dev agents are specifically optimized for the development workflow
-- **No exceptions**: Even if using bmad-master for everything else, switch to SM → Dev for implementation
-
-**Best Practice for IDE-Only**:
-
-1. Use PM/Architect/UX agents for planning (better than bmad-master)
-2. Create documents directly in project
-3. Shard immediately after creation
-4. **MUST switch to SM agent** for story creation
-5. **MUST switch to Dev agent** for implementation
-6. Keep planning and coding in separate chat sessions
-
-## Core Configuration (core-config.yaml)
-
-**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
-
-### What is core-config.yaml?
-
-This configuration file acts as a map for BMad agents, telling them exactly where to find your project documents and how they're structured. It enables:
-
-- **Version Flexibility**: Work with V3, V4, or custom document structures
-- **Custom Locations**: Define where your documents and shards live
-- **Developer Context**: Specify which files the dev agent should always load
-- **Debug Support**: Built-in logging for troubleshooting
-
-### Key Configuration Areas
-
-#### PRD Configuration
-
-- **prdVersion**: Tells agents if PRD follows v3 or v4 conventions
-- **prdSharded**: Whether epics are embedded (false) or in separate files (true)
-- **prdShardedLocation**: Where to find sharded epic files
-- **epicFilePattern**: Pattern for epic filenames (e.g., `epic-{n}*.md`)
-
-#### Architecture Configuration
-
-- **architectureVersion**: v3 (monolithic) or v4 (sharded)
-- **architectureSharded**: Whether architecture is split into components
-- **architectureShardedLocation**: Where sharded architecture files live
-
-#### Developer Files
-
-- **devLoadAlwaysFiles**: List of files the dev agent loads for every task
-- **devDebugLog**: Where dev agent logs repeated failures
-- **agentCoreDump**: Export location for chat conversations
-
-### Why It Matters
-
-1. **No Forced Migrations**: Keep your existing document structure
-2. **Gradual Adoption**: Start with V3 and migrate to V4 at your pace
-3. **Custom Workflows**: Configure BMad to match your team's process
-4. **Intelligent Agents**: Agents automatically adapt to your configuration
-
-### Common Configurations
-
-**Legacy V3 Project**:
-
-```yaml
-prdVersion: v3
-prdSharded: false
-architectureVersion: v3
-architectureSharded: false
-```
-
-**V4 Optimized Project**:
-
-```yaml
-prdVersion: v4
-prdSharded: true
-prdShardedLocation: docs/prd
-architectureVersion: v4
-architectureSharded: true
-architectureShardedLocation: docs/architecture
-```
-
-## Core Philosophy
-
-### Vibe CEO'ing
-
-You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a singular vision. Your AI agents are your high-powered team, and your role is to:
-
-- **Direct**: Provide clear instructions and objectives
-- **Refine**: Iterate on outputs to achieve quality
-- **Oversee**: Maintain strategic alignment across all agents
-
-### Core Principles
-
-1. **MAXIMIZE_AI_LEVERAGE**: Push the AI to deliver more. Challenge outputs and iterate.
-2. **QUALITY_CONTROL**: You are the ultimate arbiter of quality. Review all outputs.
-3. **STRATEGIC_OVERSIGHT**: Maintain the high-level vision and ensure alignment.
-4. **ITERATIVE_REFINEMENT**: Expect to revisit steps. This is not a linear process.
-5. **CLEAR_INSTRUCTIONS**: Precise requests lead to better outputs.
-6. **DOCUMENTATION_IS_KEY**: Good inputs (briefs, PRDs) lead to good outputs.
-7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
-8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
-
-### Key Workflow Principles
-
-1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. **Clean Handoffs**: Always start fresh when switching between agents
-3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. **Iterative Development**: Complete one story before starting the next
-5. **Documentation First**: Always start with solid PRD and architecture
-
-## Agent System
-
-### Core Development Team
-
-| Agent       | Role               | Primary Functions                       | When to Use                            |
-| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
-| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
-| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
-| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
-| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
-| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
-| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
-| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
-| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
-
-### Meta Agents
-
-| Agent               | Role             | Primary Functions                     | When to Use                       |
-| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
-| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
-| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
-
-### Agent Interaction Commands
-
-#### IDE-Specific Syntax
-
-**Agent Loading by IDE**:
-
-- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
-- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
-- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
-- **Trae**: `@agent-name` (e.g., `@bmad-master`)
-- **Roo Code**: Select mode from mode selector (e.g., `bmad-master`)
-- **GitHub Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
-
-**Chat Management Guidelines**:
-
-- **Claude Code, Cursor, Windsurf, Trae**: Start new chats when switching agents
-- **Roo Code**: Switch modes within the same conversation
-
-**Common Task Commands**:
-
-- `*help` - Show available commands
-- `*status` - Show current context/progress
-- `*exit` - Exit the agent mode
-- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
-- `*shard-doc docs/architecture.md architecture` - Shard architecture document
-- `*create` - Run create-next-story task (SM agent)
-
-**In Web UI**:
-
-```text
-/pm create-doc prd
-/architect review system design
-/dev implement story 1.2
-/help - Show available commands
-/switch agent-name - Change active agent (if orchestrator available)
-```
-
-## Team Configurations
-
-### Pre-Built Teams
-
-#### Team All
-
-- **Includes**: All 10 agents + orchestrator
-- **Use Case**: Complete projects requiring all roles
-- **Bundle**: `team-all.txt`
-
-#### Team Fullstack
-
-- **Includes**: PM, Architect, Developer, QA, UX Expert
-- **Use Case**: End-to-end web/mobile development
-- **Bundle**: `team-fullstack.txt`
-
-#### Team No-UI
-
-- **Includes**: PM, Architect, Developer, QA (no UX Expert)
-- **Use Case**: Backend services, APIs, system development
-- **Bundle**: `team-no-ui.txt`
-
-## Core Architecture
-
-### System Overview
-
-The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
-
-### Key Architectural Components
-
-#### 1. Agents (`bmad-core/agents/`)
-
-- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
-- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
-- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
-- **Startup Instructions**: Can load project-specific documentation for immediate context
-
-#### 2. Agent Teams (`bmad-core/agent-teams/`)
-
-- **Purpose**: Define collections of agents bundled together for specific purposes
-- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
-- **Usage**: Creates pre-packaged contexts for web UI environments
-
-#### 3. Workflows (`bmad-core/workflows/`)
-
-- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
-- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
-- **Structure**: Defines agent interactions, artifacts created, and transition conditions
-
-#### 4. Reusable Resources
-
-- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
-- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
-- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
-- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
-
-### Dual Environment Architecture
-
-#### IDE Environment
-
-- Users interact directly with agent markdown files
-- Agents can access all dependencies dynamically
-- Supports real-time file operations and project integration
-- Optimized for development workflow execution
-
-#### Web UI Environment
-
-- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent
-- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
-- Created by the web-builder tool for upload to web interfaces
-- Provides complete context in one package
-
-### Template Processing System
-
-BMad employs a sophisticated template system with three key components:
-
-1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates
-2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output
-3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
-
-### Technical Preferences Integration
-
-The `technical-preferences.md` file serves as a persistent technical profile that:
-
-- Ensures consistency across all agents and projects
-- Eliminates repetitive technology specification
-- Provides personalized recommendations aligned with user preferences
-- Evolves over time with lessons learned
-
-### Build and Delivery Process
-
-The `web-builder.js` tool creates web-ready bundles by:
-
-1. Reading agent or team definition files
-2. Recursively resolving all dependencies
-3. Concatenating content into single text files with clear separators
-4. Outputting ready-to-upload bundles for web AI interfaces
-
-This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMad powerful.
-
-## Complete Development Workflow
-
-### Planning Phase (Web UI Recommended - Especially Gemini!)
-
-**Ideal for cost efficiency with Gemini's massive context:**
-
-**For Brownfield Projects - Start Here!**:
-
-1. **Upload entire project to Gemini Web** (GitHub URL, files, or zip)
-2. **Document existing system**: `/analyst` → `*document-project`
-3. **Creates comprehensive docs** from entire codebase analysis
-
-**For All Projects**:
-
-1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
-2. **Project Brief**: Create foundation document (Analyst or user)
-3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
-4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
-5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
-6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
-
-#### Example Planning Prompts
-
-**For PRD Creation**:
-
-```text
-"I want to build a [type] application that [core purpose].
-Help me brainstorm features and create a comprehensive PRD."
-```
-
-**For Architecture Design**:
-
-```text
-"Based on this PRD, design a scalable technical architecture
-that can handle [specific requirements]."
-```
-
-### Critical Transition: Web UI to IDE
-
-**Once planning is complete, you MUST switch to IDE for development:**
-
-- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
-- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
-- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
-
-### IDE Development Workflow
-
-**Prerequisites**: Planning documents must exist in `docs/` folder
-
-1. **Document Sharding** (CRITICAL STEP):
-   - Documents created by PM/Architect (in Web or IDE) MUST be sharded for development
-   - Two methods to shard:
-     a) **Manual**: Drag `shard-doc` task + document file into chat
-     b) **Agent**: Ask `@bmad-master` or `@po` to shard documents
-   - Shards `docs/prd.md` → `docs/prd/` folder
-   - Shards `docs/architecture.md` → `docs/architecture/` folder
-   - **WARNING**: Do NOT shard in Web UI - copying many small files is painful!
-
-2. **Verify Sharded Content**:
-   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
-   - Source tree document and coding standards for dev agent reference
-   - Sharded docs for SM agent story creation
-
-Resulting Folder Structure:
-
-- `docs/prd/` - Broken down PRD sections
-- `docs/architecture/` - Broken down architecture sections
-- `docs/stories/` - Generated user stories
-
-1. **Development Cycle** (Sequential, one story at a time):
-
-   **CRITICAL CONTEXT MANAGEMENT**:
-   - **Context windows matter!** Always use fresh, clean context windows
-   - **Model selection matters!** Use most powerful thinking model for SM story creation
-   - **ALWAYS start new chat between SM, Dev, and QA work**
-
-   **Step 1 - Story Creation**:
-   - **NEW CLEAN CHAT** → Select powerful model → `@sm` → `*create`
-   - SM executes create-next-story task
-   - Review generated story in `docs/stories/`
-   - Update status from "Draft" to "Approved"
-
-   **Step 2 - Story Implementation**:
-   - **NEW CLEAN CHAT** → `@dev`
-   - Agent asks which story to implement
-   - Include story file content to save dev agent lookup time
-   - Dev follows tasks/subtasks, marking completion
-   - Dev maintains File List of all changes
-   - Dev marks story as "Review" when complete with all tests passing
-
-   **Step 3 - Senior QA Review**:
-   - **NEW CLEAN CHAT** → `@qa` → execute review-story task
-   - QA performs senior developer code review
-   - QA can refactor and improve code directly
-   - QA appends results to story's QA Results section
-   - If approved: Status → "Done"
-   - If changes needed: Status stays "Review" with unchecked items for dev
-
-   **Step 4 - Repeat**: Continue SM → Dev → QA cycle until all epic stories complete
-
-**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
-
-### Status Tracking Workflow
-
-Stories progress through defined statuses:
-
-- **Draft** → **Approved** → **InProgress** → **Done**
-
-Each status change requires user verification and approval before proceeding.
-
-### Workflow Types
-
-#### Greenfield Development
-
-- Business analysis and market research
-- Product requirements and feature definition
-- System architecture and design
-- Development execution
-- Testing and deployment
-
-#### Brownfield Enhancement (Existing Projects)
-
-**Key Concept**: Brownfield development requires comprehensive documentation of your existing project for AI agents to understand context, patterns, and constraints.
-
-**Complete Brownfield Workflow Options**:
-
-**Option 1: PRD-First (Recommended for Large Codebases/Monorepos)**:
-
-1. **Upload project to Gemini Web** (GitHub URL, files, or zip)
-2. **Create PRD first**: `@pm` → `*create-doc brownfield-prd`
-3. **Focused documentation**: `@analyst` → `*document-project`
-   - Analyst asks for focus if no PRD provided
-   - Choose "single document" format for Web UI
-   - Uses PRD to document ONLY relevant areas
-   - Creates one comprehensive markdown file
-   - Avoids bloating docs with unused code
-
-**Option 2: Document-First (Good for Smaller Projects)**:
-
-1. **Upload project to Gemini Web**
-2. **Document everything**: `@analyst` → `*document-project`
-3. **Then create PRD**: `@pm` → `*create-doc brownfield-prd`
-   - More thorough but can create excessive documentation
-
-4. **Requirements Gathering**:
-   - **Brownfield PRD**: Use PM agent with `brownfield-prd-tmpl`
-   - **Analyzes**: Existing system, constraints, integration points
-   - **Defines**: Enhancement scope, compatibility requirements, risk assessment
-   - **Creates**: Epic and story structure for changes
-
-5. **Architecture Planning**:
-   - **Brownfield Architecture**: Use Architect agent with `brownfield-architecture-tmpl`
-   - **Integration Strategy**: How new features integrate with existing system
-   - **Migration Planning**: Gradual rollout and backwards compatibility
-   - **Risk Mitigation**: Addressing potential breaking changes
-
-**Brownfield-Specific Resources**:
-
-**Templates**:
-
-- `brownfield-prd-tmpl.md`: Comprehensive enhancement planning with existing system analysis
-- `brownfield-architecture-tmpl.md`: Integration-focused architecture for existing systems
-
-**Tasks**:
-
-- `document-project`: Generates comprehensive documentation from existing codebase
-- `brownfield-create-epic`: Creates single epic for focused enhancements (when full PRD is overkill)
-- `brownfield-create-story`: Creates individual story for small, isolated changes
-
-**When to Use Each Approach**:
-
-**Full Brownfield Workflow** (Recommended for):
-
-- Major feature additions
-- System modernization
-- Complex integrations
-- Multiple related changes
-
-**Quick Epic/Story Creation** (Use when):
-
-- Single, focused enhancement
-- Isolated bug fixes
-- Small feature additions
-- Well-documented existing system
-
-**Critical Success Factors**:
-
-1. **Documentation First**: Always run `document-project` if docs are outdated/missing
-2. **Context Matters**: Provide agents access to relevant code sections
-3. **Integration Focus**: Emphasize compatibility and non-breaking changes
-4. **Incremental Approach**: Plan for gradual rollout and testing
-
-**For detailed guide**: See `docs/working-in-the-brownfield.md`
-
-## Document Creation Best Practices
-
-### Required File Naming for Framework Integration
-
-- `docs/prd.md` - Product Requirements Document
-- `docs/architecture.md` - System Architecture Document
-
-**Why These Names Matter**:
-
-- Agents automatically reference these files during development
-- Sharding tasks expect these specific filenames
-- Workflow automation depends on standard naming
-
-### Cost-Effective Document Creation Workflow
-
-**Recommended for Large Documents (PRD, Architecture):**
-
-1. **Use Web UI**: Create documents in web interface for cost efficiency
-2. **Copy Final Output**: Save complete markdown to your project
-3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
-4. **Switch to IDE**: Use IDE agents for development and smaller documents
-
-### Document Sharding
-
-Templates with Level 2 headings (`##`) can be automatically sharded:
-
-**Original PRD**:
-
-```markdown
-## Goals and Background Context
-
-## Requirements
-
-## User Interface Design Goals
-
-## Success Metrics
-```
-
-**After Sharding**:
-
-- `docs/prd/goals-and-background-context.md`
-- `docs/prd/requirements.md`
-- `docs/prd/user-interface-design-goals.md`
-- `docs/prd/success-metrics.md`
-
-Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
-
-## Usage Patterns and Best Practices
-
-### Environment-Specific Usage
-
-**Web UI Best For**:
-
-- Initial planning and documentation phases
-- Cost-effective large document creation
-- Agent consultation and brainstorming
-- Multi-agent workflows with orchestrator
-
-**IDE Best For**:
-
-- Active development and implementation
-- File operations and project integration
-- Story management and development cycles
-- Code review and debugging
-
-### Quality Assurance
-
-- Use appropriate agents for specialized tasks
-- Follow Agile ceremonies and review processes
-- Maintain document consistency with PO agent
-- Regular validation with checklists and templates
-
-### Performance Optimization
-
-- Use specific agents vs. `bmad-master` for focused tasks
-- Choose appropriate team size for project needs
-- Leverage technical preferences for consistency
-- Regular context management and cache clearing
-
-## Success Tips
-
-- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
-- **Use bmad-master for document organization** - Sharding creates manageable chunks
-- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
-- **Keep conversations focused** - One agent, one task per conversation
-- **Review everything** - Always review and approve before marking complete
-
-## Contributing to BMad-Method
-
-### Quick Contribution Guidelines
-
-For full details, see `CONTRIBUTING.md`. Key points:
-
-**Fork Workflow**:
-
-1. Fork the repository
-2. Create feature branches
-3. Submit PRs to `next` branch (default) or `main` for critical fixes only
-4. Keep PRs small: 200-400 lines ideal, 800 lines maximum
-5. One feature/fix per PR
-
-**PR Requirements**:
-
-- Clear descriptions (max 200 words) with What/Why/How/Testing
-- Use conventional commits (feat:, fix:, docs:)
-- Atomic commits - one logical change per commit
-- Must align with guiding principles
-
-**Core Principles** (from docs/GUIDING-PRINCIPLES.md):
-
-- **Dev Agents Must Be Lean**: Minimize dependencies, save context for code
-- **Natural Language First**: Everything in markdown, no code in core
-- **Core vs Expansion Packs**: Core for universal needs, packs for specialized domains
-- **Design Philosophy**: "Dev agents code, planning agents plan"
-
-## Expansion Packs
-
-### What Are Expansion Packs?
-
-Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
-
-### Why Use Expansion Packs?
-
-1. **Keep Core Lean**: Dev agents maintain maximum context for coding
-2. **Domain Expertise**: Deep, specialized knowledge without bloating core
-3. **Community Innovation**: Anyone can create and share packs
-4. **Modular Design**: Install only what you need
-
-### Available Expansion Packs
-
-**Technical Packs**:
-
-- **Infrastructure/DevOps**: Cloud architects, SRE experts, security specialists
-- **Game Development**: Game designers, level designers, narrative writers
-- **Mobile Development**: iOS/Android specialists, mobile UX experts
-- **Data Science**: ML engineers, data scientists, visualization experts
-
-**Non-Technical Packs**:
-
-- **Business Strategy**: Consultants, financial analysts, marketing strategists
-- **Creative Writing**: Plot architects, character developers, world builders
-- **Health & Wellness**: Fitness trainers, nutritionists, habit engineers
-- **Education**: Curriculum designers, assessment specialists
-- **Legal Support**: Contract analysts, compliance checkers
-
-**Specialty Packs**:
-
-- **Expansion Creator**: Tools to build your own expansion packs
-- **RPG Game Master**: Tabletop gaming assistance
-- **Life Event Planning**: Wedding planners, event coordinators
-- **Scientific Research**: Literature reviewers, methodology designers
-
-### Using Expansion Packs
-
-1. **Browse Available Packs**: Check `expansion-packs/` directory
-2. **Get Inspiration**: See `docs/expansion-packs.md` for detailed examples and ideas
-3. **Install via CLI**:
-
-   ```bash
-   npx bmad-method install
-   # Select "Install expansion pack" option
-   ```
-
-4. **Use in Your Workflow**: Installed packs integrate seamlessly with existing agents
-
-### Creating Custom Expansion Packs
-
-Use the **expansion-creator** pack to build your own:
-
-1. **Define Domain**: What expertise are you capturing?
-2. **Design Agents**: Create specialized roles with clear boundaries
-3. **Build Resources**: Tasks, templates, checklists for your domain
-4. **Test & Share**: Validate with real use cases, share with community
-
-**Key Principle**: Expansion packs democratize expertise by making specialized knowledge accessible through AI agents.
-
-## Getting Help
-
-- **Commands**: Use `*/*help` in any environment to see available commands
-- **Agent Switching**: Use `*/*switch agent-name` with orchestrator for role changes
-- **Documentation**: Check `docs/` folder for project-specific context
-- **Community**: Discord and GitHub resources available for support
-- **Contributing**: See `CONTRIBUTING.md` for full guidelines

bmad-core/data/brainstorming-techniques.md

@@ -1,36 +0,0 @@
-# Brainstorming Techniques Data
-
-## Creative Expansion
-
-1. **What If Scenarios**: Ask one provocative question, get their response, then ask another
-2. **Analogical Thinking**: Give one example analogy, ask them to find 2-3 more
-3. **Reversal/Inversion**: Pose the reverse question, let them work through it
-4. **First Principles Thinking**: Ask "What are the fundamentals?" and guide them to break it down
-
-## Structured Frameworks
-
-5. **SCAMPER Method**: Go through one letter at a time, wait for their ideas before moving to next
-6. **Six Thinking Hats**: Present one hat, ask for their thoughts, then move to next hat
-7. **Mind Mapping**: Start with central concept, ask them to suggest branches
-
-## Collaborative Techniques
-
-8. **"Yes, And..." Building**: They give idea, you "yes and" it, they "yes and" back - alternate
-9. **Brainwriting/Round Robin**: They suggest idea, you build on it, ask them to build on yours
-10. **Random Stimulation**: Give one random prompt/word, ask them to make connections
-
-## Deep Exploration
-
-11. **Five Whys**: Ask "why" and wait for their answer before asking next "why"
-12. **Morphological Analysis**: Ask them to list parameters first, then explore combinations together
-13. **Provocation Technique (PO)**: Give one provocative statement, ask them to extract useful ideas
-
-## Advanced Techniques
-
-14. **Forced Relationships**: Connect two unrelated concepts and ask them to find the bridge
-15. **Assumption Reversal**: Challenge their core assumptions and ask them to build from there
-16. **Role Playing**: Ask them to brainstorm from different stakeholder perspectives
-17. **Time Shifting**: "How would you solve this in 1995? 2030?"
-18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
-19. **Metaphor Mapping**: Use extended metaphors to explore solutions
-20. **Question Storming**: Generate questions instead of answers first

bmad-core/data/elicitation-methods.md

@@ -1,154 +0,0 @@
-# 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

bmad-core/data/technical-preferences.md

@@ -1,3 +0,0 @@
-# User-Defined Preferred Patterns and Preferences
-
-None Listed

bmad-core/data/test-levels-framework.md

@@ -1,146 +0,0 @@
-# Test Levels Framework
-
-Comprehensive guide for determining appropriate test levels (unit, integration, E2E) for different scenarios.
-
-## Test Level Decision Matrix
-
-### Unit Tests
-
-**When to use:**
-
-- Testing pure functions and business logic
-- Algorithm correctness
-- Input validation and data transformation
-- Error handling in isolated components
-- Complex calculations or state machines
-
-**Characteristics:**
-
-- Fast execution (immediate feedback)
-- No external dependencies (DB, API, file system)
-- Highly maintainable and stable
-- Easy to debug failures
-
-**Example scenarios:**
-
-```yaml
-unit_test:
-  component: "PriceCalculator"
-  scenario: "Calculate discount with multiple rules"
-  justification: "Complex business logic with multiple branches"
-  mock_requirements: "None - pure function"
-```
-
-### Integration Tests
-
-**When to use:**
-
-- Component interaction verification
-- Database operations and transactions
-- API endpoint contracts
-- Service-to-service communication
-- Middleware and interceptor behavior
-
-**Characteristics:**
-
-- Moderate execution time
-- Tests component boundaries
-- May use test databases or containers
-- Validates system integration points
-
-**Example scenarios:**
-
-```yaml
-integration_test:
-  components: ["UserService", "AuthRepository"]
-  scenario: "Create user with role assignment"
-  justification: "Critical data flow between service and persistence"
-  test_environment: "In-memory database"
-```
-
-### End-to-End Tests
-
-**When to use:**
-
-- Critical user journeys
-- Cross-system workflows
-- Visual regression testing
-- Compliance and regulatory requirements
-- Final validation before release
-
-**Characteristics:**
-
-- Slower execution
-- Tests complete workflows
-- Requires full environment setup
-- Most realistic but most brittle
-
-**Example scenarios:**
-
-```yaml
-e2e_test:
-  journey: "Complete checkout process"
-  scenario: "User purchases with saved payment method"
-  justification: "Revenue-critical path requiring full validation"
-  environment: "Staging with test payment gateway"
-```
-
-## Test Level Selection Rules
-
-### Favor Unit Tests When:
-
-- Logic can be isolated
-- No side effects involved
-- Fast feedback needed
-- High cyclomatic complexity
-
-### Favor Integration Tests When:
-
-- Testing persistence layer
-- Validating service contracts
-- Testing middleware/interceptors
-- Component boundaries critical
-
-### Favor E2E Tests When:
-
-- User-facing critical paths
-- Multi-system interactions
-- Regulatory compliance scenarios
-- Visual regression important
-
-## Anti-patterns to Avoid
-
-- E2E testing for business logic validation
-- Unit testing framework behavior
-- Integration testing third-party libraries
-- Duplicate coverage across levels
-
-## Duplicate Coverage Guard
-
-**Before adding any test, check:**
-
-1. Is this already tested at a lower level?
-2. Can a unit test cover this instead of integration?
-3. Can an integration test cover this instead of E2E?
-
-**Coverage overlap is only acceptable when:**
-
-- Testing different aspects (unit: logic, integration: interaction, e2e: user experience)
-- Critical paths requiring defense in depth
-- Regression prevention for previously broken functionality
-
-## Test Naming Conventions
-
-- Unit: `test_{component}_{scenario}`
-- Integration: `test_{flow}_{interaction}`
-- E2E: `test_{journey}_{outcome}`
-
-## Test ID Format
-
-`{EPIC}.{STORY}-{LEVEL}-{SEQ}`
-
-Examples:
-
-- `1.3-UNIT-001`
-- `1.3-INT-002`
-- `1.3-E2E-001`

bmad-core/data/test-priorities-matrix.md

@@ -1,172 +0,0 @@
-# Test Priorities Matrix
-
-Guide for prioritizing test scenarios based on risk, criticality, and business impact.
-
-## Priority Levels
-
-### P0 - Critical (Must Test)
-
-**Criteria:**
-
-- Revenue-impacting functionality
-- Security-critical paths
-- Data integrity operations
-- Regulatory compliance requirements
-- Previously broken functionality (regression prevention)
-
-**Examples:**
-
-- Payment processing
-- Authentication/authorization
-- User data creation/deletion
-- Financial calculations
-- GDPR/privacy compliance
-
-**Testing Requirements:**
-
-- Comprehensive coverage at all levels
-- Both happy and unhappy paths
-- Edge cases and error scenarios
-- Performance under load
-
-### P1 - High (Should Test)
-
-**Criteria:**
-
-- Core user journeys
-- Frequently used features
-- Features with complex logic
-- Integration points between systems
-- Features affecting user experience
-
-**Examples:**
-
-- User registration flow
-- Search functionality
-- Data import/export
-- Notification systems
-- Dashboard displays
-
-**Testing Requirements:**
-
-- Primary happy paths required
-- Key error scenarios
-- Critical edge cases
-- Basic performance validation
-
-### P2 - Medium (Nice to Test)
-
-**Criteria:**
-
-- Secondary features
-- Admin functionality
-- Reporting features
-- Configuration options
-- UI polish and aesthetics
-
-**Examples:**
-
-- Admin settings panels
-- Report generation
-- Theme customization
-- Help documentation
-- Analytics tracking
-
-**Testing Requirements:**
-
-- Happy path coverage
-- Basic error handling
-- Can defer edge cases
-
-### P3 - Low (Test if Time Permits)
-
-**Criteria:**
-
-- Rarely used features
-- Nice-to-have functionality
-- Cosmetic issues
-- Non-critical optimizations
-
-**Examples:**
-
-- Advanced preferences
-- Legacy feature support
-- Experimental features
-- Debug utilities
-
-**Testing Requirements:**
-
-- Smoke tests only
-- Can rely on manual testing
-- Document known limitations
-
-## Risk-Based Priority Adjustments
-
-### Increase Priority When:
-
-- High user impact (affects >50% of users)
-- High financial impact (>$10K potential loss)
-- Security vulnerability potential
-- Compliance/legal requirements
-- Customer-reported issues
-- Complex implementation (>500 LOC)
-- Multiple system dependencies
-
-### Decrease Priority When:
-
-- Feature flag protected
-- Gradual rollout planned
-- Strong monitoring in place
-- Easy rollback capability
-- Low usage metrics
-- Simple implementation
-- Well-isolated component
-
-## Test Coverage by Priority
-
-| Priority | Unit Coverage | Integration Coverage | E2E Coverage       |
-| -------- | ------------- | -------------------- | ------------------ |
-| P0       | >90%          | >80%                 | All critical paths |
-| P1       | >80%          | >60%                 | Main happy paths   |
-| P2       | >60%          | >40%                 | Smoke tests        |
-| P3       | Best effort   | Best effort          | Manual only        |
-
-## Priority Assignment Rules
-
-1. **Start with business impact** - What happens if this fails?
-2. **Consider probability** - How likely is failure?
-3. **Factor in detectability** - Would we know if it failed?
-4. **Account for recoverability** - Can we fix it quickly?
-
-## Priority Decision Tree
-
-```
-Is it revenue-critical?
-├─ YES → P0
-└─ NO → Does it affect core user journey?
-    ├─ YES → Is it high-risk?
-    │   ├─ YES → P0
-    │   └─ NO → P1
-    └─ NO → Is it frequently used?
-        ├─ YES → P1
-        └─ NO → Is it customer-facing?
-            ├─ YES → P2
-            └─ NO → P3
-```
-
-## Test Execution Order
-
-1. Execute P0 tests first (fail fast on critical issues)
-2. Execute P1 tests second (core functionality)
-3. Execute P2 tests if time permits
-4. P3 tests only in full regression cycles
-
-## Continuous Adjustment
-
-Review and adjust priorities based on:
-
-- Production incident patterns
-- User feedback and complaints
-- Usage analytics
-- Test failure history
-- Business priority changes

bmad-core/tasks/advanced-elicitation.md

@@ -1,117 +0,0 @@
-# Advanced Elicitation Task
-
-## Purpose
-
-- Provide optional reflective and brainstorming actions to enhance content quality
-- Enable deeper exploration of ideas through structured elicitation techniques
-- Support iterative refinement through multiple analytical perspectives
-- Usable during template-driven document creation or any chat conversation
-
-## Usage Scenarios
-
-### Scenario 1: Template Document Creation
-
-After outputting a section during document creation:
-
-1. **Section Review**: Ask user to review the drafted section
-2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
-3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
-4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
-
-### Scenario 2: General Chat Elicitation
-
-User can request advanced elicitation on any agent output:
-
-- User says "do advanced elicitation" or similar
-- Agent selects 9 relevant methods for the context
-- Same simple 0-9 selection process
-
-## Task Instructions
-
-### 1. Intelligent Method Selection
-
-**Context Analysis**: Before presenting options, analyze:
-
-- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
-- **Complexity Level**: Simple, moderate, or complex content
-- **Stakeholder Needs**: Who will use this information
-- **Risk Level**: High-impact decisions vs routine items
-- **Creative Potential**: Opportunities for innovation or alternatives
-
-**Method Selection Strategy**:
-
-1. **Always Include Core Methods** (choose 3-4):
-   - Expand or Contract for Audience
-   - Critique and Refine
-   - Identify Potential Risks
-   - Assess Alignment with Goals
-
-2. **Context-Specific Methods** (choose 4-5):
-   - **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
-   - **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
-   - **Creative Content**: Innovation Tournament, Escape Room Challenge
-   - **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
-
-3. **Always Include**: "Proceed / No Further Actions" as option 9
-
-### 2. Section Context and Review
-
-When invoked after outputting a section:
-
-1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
-
-2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
-
-3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
-   - The entire section as a whole
-   - Individual items within the section (specify which item when selecting an action)
-
-### 3. Present Elicitation Options
-
-**Review Request Process:**
-
-- Ask the user to review the drafted section
-- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
-- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
-- Keep descriptions short - just the method name
-- Await simple numeric selection
-
-**Action List Presentation Format:**
-
-```text
-**Advanced Elicitation Options**
-Choose a number (0-8) or 9 to proceed:
-
-0. [Method Name]
-1. [Method Name]
-2. [Method Name]
-3. [Method Name]
-4. [Method Name]
-5. [Method Name]
-6. [Method Name]
-7. [Method Name]
-8. [Method Name]
-9. Proceed / No Further Actions
-```
-
-**Response Handling:**
-
-- **Numbers 0-8**: Execute the selected method, then re-offer the choice
-- **Number 9**: Proceed to next section or continue conversation
-- **Direct Feedback**: Apply user's suggested changes and continue
-
-### 4. Method Execution Framework
-
-**Execution Process:**
-
-1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
-2. **Apply Context**: Execute the method from your current role's perspective
-3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
-4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
-
-**Execution Guidelines:**
-
-- **Be Concise**: Focus on actionable insights, not lengthy explanations
-- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
-- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
-- **Maintain Flow**: Keep the process moving efficiently

bmad-core/tasks/brownfield-create-epic.md

@@ -1,160 +0,0 @@
-# Create Brownfield Epic Task
-
-## Purpose
-
-Create a single epic for smaller brownfield enhancements that don't require the full PRD and Architecture documentation process. This task is for isolated features or modifications that can be completed within a focused scope.
-
-## When to Use This Task
-
-**Use this task when:**
-
-- The enhancement can be completed in 1-3 stories
-- No significant architectural changes are required
-- The enhancement follows existing project patterns
-- Integration complexity is minimal
-- Risk to existing system is low
-
-**Use the full brownfield PRD/Architecture process when:**
-
-- The enhancement requires multiple coordinated stories
-- Architectural planning is needed
-- Significant integration work is required
-- Risk assessment and mitigation planning is necessary
-
-## Instructions
-
-### 1. Project Analysis (Required)
-
-Before creating the epic, gather essential information about the existing project:
-
-**Existing Project Context:**
-
-- [ ] Project purpose and current functionality understood
-- [ ] Existing technology stack identified
-- [ ] Current architecture patterns noted
-- [ ] Integration points with existing system identified
-
-**Enhancement Scope:**
-
-- [ ] Enhancement clearly defined and scoped
-- [ ] Impact on existing functionality assessed
-- [ ] Required integration points identified
-- [ ] Success criteria established
-
-### 2. Epic Creation
-
-Create a focused epic following this structure:
-
-#### Epic Title
-
-{{Enhancement Name}} - Brownfield Enhancement
-
-#### Epic Goal
-
-{{1-2 sentences describing what the epic will accomplish and why it adds value}}
-
-#### Epic Description
-
-**Existing System Context:**
-
-- Current relevant functionality: {{brief description}}
-- Technology stack: {{relevant existing technologies}}
-- Integration points: {{where new work connects to existing system}}
-
-**Enhancement Details:**
-
-- What's being added/changed: {{clear description}}
-- How it integrates: {{integration approach}}
-- Success criteria: {{measurable outcomes}}
-
-#### Stories
-
-List 1-3 focused stories that complete the epic:
-
-1. **Story 1:** {{Story title and brief description}}
-2. **Story 2:** {{Story title and brief description}}
-3. **Story 3:** {{Story title and brief description}}
-
-#### Compatibility Requirements
-
-- [ ] Existing APIs remain unchanged
-- [ ] Database schema changes are backward compatible
-- [ ] UI changes follow existing patterns
-- [ ] Performance impact is minimal
-
-#### Risk Mitigation
-
-- **Primary Risk:** {{main risk to existing system}}
-- **Mitigation:** {{how risk will be addressed}}
-- **Rollback Plan:** {{how to undo changes if needed}}
-
-#### Definition of Done
-
-- [ ] All stories completed with acceptance criteria met
-- [ ] Existing functionality verified through testing
-- [ ] Integration points working correctly
-- [ ] Documentation updated appropriately
-- [ ] No regression in existing features
-
-### 3. Validation Checklist
-
-Before finalizing the epic, ensure:
-
-**Scope Validation:**
-
-- [ ] Epic can be completed in 1-3 stories maximum
-- [ ] No architectural documentation is required
-- [ ] Enhancement follows existing patterns
-- [ ] Integration complexity is manageable
-
-**Risk Assessment:**
-
-- [ ] Risk to existing system is low
-- [ ] Rollback plan is feasible
-- [ ] Testing approach covers existing functionality
-- [ ] Team has sufficient knowledge of integration points
-
-**Completeness Check:**
-
-- [ ] Epic goal is clear and achievable
-- [ ] Stories are properly scoped
-- [ ] Success criteria are measurable
-- [ ] Dependencies are identified
-
-### 4. Handoff to Story Manager
-
-Once the epic is validated, provide this handoff to the Story Manager:
-
----
-
-**Story Manager Handoff:**
-
-"Please develop detailed user stories for this brownfield epic. Key considerations:
-
-- This is an enhancement to an existing system running {{technology stack}}
-- Integration points: {{list key integration points}}
-- Existing patterns to follow: {{relevant existing patterns}}
-- Critical compatibility requirements: {{key requirements}}
-- Each story must include verification that existing functionality remains intact
-
-The epic should maintain system integrity while delivering {{epic goal}}."
-
----
-
-## Success Criteria
-
-The epic creation is successful when:
-
-1. Enhancement scope is clearly defined and appropriately sized
-2. Integration approach respects existing system architecture
-3. Risk to existing functionality is minimized
-4. Stories are logically sequenced for safe implementation
-5. Compatibility requirements are clearly specified
-6. Rollback plan is feasible and documented
-
-## Important Notes
-
-- This task is specifically for SMALL brownfield enhancements
-- If the scope grows beyond 3 stories, consider the full brownfield PRD process
-- Always prioritize existing system integrity over new functionality
-- When in doubt about scope or complexity, escalate to full brownfield planning

bmad-core/tasks/brownfield-create-story.md

@@ -1,147 +0,0 @@
-# Create Brownfield Story Task
-
-## Purpose
-
-Create a single user story for very small brownfield enhancements that can be completed in one focused development session. This task is for minimal additions or bug fixes that require existing system integration awareness.
-
-## When to Use This Task
-
-**Use this task when:**
-
-- The enhancement can be completed in a single story
-- No new architecture or significant design is required
-- The change follows existing patterns exactly
-- Integration is straightforward with minimal risk
-- Change is isolated with clear boundaries
-
-**Use brownfield-create-epic when:**
-
-- The enhancement requires 2-3 coordinated stories
-- Some design work is needed
-- Multiple integration points are involved
-
-**Use the full brownfield PRD/Architecture process when:**
-
-- The enhancement requires multiple coordinated stories
-- Architectural planning is needed
-- Significant integration work is required
-
-## Instructions
-
-### 1. Quick Project Assessment
-
-Gather minimal but essential context about the existing project:
-
-**Current System Context:**
-
-- [ ] Relevant existing functionality identified
-- [ ] Technology stack for this area noted
-- [ ] Integration point(s) clearly understood
-- [ ] Existing patterns for similar work identified
-
-**Change Scope:**
-
-- [ ] Specific change clearly defined
-- [ ] Impact boundaries identified
-- [ ] Success criteria established
-
-### 2. Story Creation
-
-Create a single focused story following this structure:
-
-#### Story Title
-
-{{Specific Enhancement}} - Brownfield Addition
-
-#### User Story
-
-As a {{user type}},
-I want {{specific action/capability}},
-So that {{clear benefit/value}}.
-
-#### Story Context
-
-**Existing System Integration:**
-
-- Integrates with: {{existing component/system}}
-- Technology: {{relevant tech stack}}
-- Follows pattern: {{existing pattern to follow}}
-- Touch points: {{specific integration points}}
-
-#### Acceptance Criteria
-
-**Functional Requirements:**
-
-1. {{Primary functional requirement}}
-2. {{Secondary functional requirement (if any)}}
-3. {{Integration requirement}}
-
-**Integration Requirements:** 4. Existing {{relevant functionality}} continues to work unchanged 5. New functionality follows existing {{pattern}} pattern 6. Integration with {{system/component}} maintains current behavior
-
-**Quality Requirements:** 7. Change is covered by appropriate tests 8. Documentation is updated if needed 9. No regression in existing functionality verified
-
-#### Technical Notes
-
-- **Integration Approach:** {{how it connects to existing system}}
-- **Existing Pattern Reference:** {{link or description of pattern to follow}}
-- **Key Constraints:** {{any important limitations or requirements}}
-
-#### Definition of Done
-
-- [ ] Functional requirements met
-- [ ] Integration requirements verified
-- [ ] Existing functionality regression tested
-- [ ] Code follows existing patterns and standards
-- [ ] Tests pass (existing and new)
-- [ ] Documentation updated if applicable
-
-### 3. Risk and Compatibility Check
-
-**Minimal Risk Assessment:**
-
-- **Primary Risk:** {{main risk to existing system}}
-- **Mitigation:** {{simple mitigation approach}}
-- **Rollback:** {{how to undo if needed}}
-
-**Compatibility Verification:**
-
-- [ ] No breaking changes to existing APIs
-- [ ] Database changes (if any) are additive only
-- [ ] UI changes follow existing design patterns
-- [ ] Performance impact is negligible
-
-### 4. Validation Checklist
-
-Before finalizing the story, confirm:
-
-**Scope Validation:**
-
-- [ ] Story can be completed in one development session
-- [ ] Integration approach is straightforward
-- [ ] Follows existing patterns exactly
-- [ ] No design or architecture work required
-
-**Clarity Check:**
-
-- [ ] Story requirements are unambiguous
-- [ ] Integration points are clearly specified
-- [ ] Success criteria are testable
-- [ ] Rollback approach is simple
-
-## Success Criteria
-
-The story creation is successful when:
-
-1. Enhancement is clearly defined and appropriately scoped for single session
-2. Integration approach is straightforward and low-risk
-3. Existing system patterns are identified and will be followed
-4. Rollback plan is simple and feasible
-5. Acceptance criteria include existing functionality verification
-
-## Important Notes
-
-- This task is for VERY SMALL brownfield changes only
-- If complexity grows during analysis, escalate to brownfield-create-epic
-- Always prioritize existing system integrity
-- When in doubt about integration complexity, use brownfield-create-epic instead
-- Stories should take no more than 4 hours of focused development work

bmad-core/tasks/correct-course.md

@@ -1,70 +0,0 @@
-# Correct Course Task
-
-## Purpose
-
-- Guide a structured response to a change trigger using the `{root}/checklists/change-checklist`.
-- Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
-- Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
-- Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
-- Produce a consolidated "Sprint Change Proposal" document that contains the impact analysis and the clearly drafted proposed edits for user review and approval.
-- Ensure a clear handoff path if the nature of the changes necessitates fundamental replanning by other core agents (like PM or Architect).
-
-## Instructions
-
-### 1. Initial Setup & Mode Selection
-
-- **Acknowledge Task & Inputs:**
-  - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
-  - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `{root}/checklists/change-checklist`.
-- **Establish Interaction Mode:**
-  - Ask the user their preferred interaction mode for this task:
-    - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
-    - **"YOLO Mode (Batch Processing):** Or, would you prefer I conduct a more batched analysis based on the checklist and then present a consolidated set of findings and proposed changes for a broader review? This can be quicker for initial assessment but might require more extensive review of the combined proposals."
-  - Once the user chooses, confirm the selected mode and then inform the user: "We will now use the change-checklist to analyze the change and draft proposed updates. I will guide you through the checklist items based on our chosen interaction mode."
-
-### 2. Execute Checklist Analysis (Iteratively or Batched, per Interaction Mode)
-
-- Systematically work through Sections 1-4 of the change-checklist (typically covering Change Context, Epic/Story Impact Analysis, Artifact Conflict Resolution, and Path Evaluation/Recommendation).
-- For each checklist item or logical group of items (depending on interaction mode):
-  - Present the relevant prompt(s) or considerations from the checklist to the user.
-  - Request necessary information and actively analyze the relevant project artifacts (PRD, epics, architecture documents, story history, etc.) to assess the impact.
-  - Discuss your findings for each item with the user.
-  - Record the status of each checklist item (e.g., `[x] Addressed`, `[N/A]`, `[!] Further Action Needed`) and any pertinent notes or decisions.
-  - Collaboratively agree on the "Recommended Path Forward" as prompted by Section 4 of the checklist.
-
-### 3. Draft Proposed Changes (Iteratively or Batched)
-
-- Based on the completed checklist analysis (Sections 1-4) and the agreed "Recommended Path Forward" (excluding scenarios requiring fundamental replans that would necessitate immediate handoff to PM/Architect):
-  - Identify the specific project artifacts that require updates (e.g., specific epics, user stories, PRD sections, architecture document components, diagrams).
-  - **Draft the proposed changes directly and explicitly for each identified artifact.** Examples include:
-    - Revising user story text, acceptance criteria, or priority.
-    - Adding, removing, reordering, or splitting user stories within epics.
-    - Proposing modified architecture diagram snippets (e.g., providing an updated Mermaid diagram block or a clear textual description of the change to an existing diagram).
-    - Updating technology lists, configuration details, or specific sections within the PRD or architecture documents.
-    - Drafting new, small supporting artifacts if necessary (e.g., a brief addendum for a specific decision).
-  - If in "Incremental Mode," discuss and refine these proposed edits for each artifact or small group of related artifacts with the user as they are drafted.
-  - If in "YOLO Mode," compile all drafted edits for presentation in the next step.
-
-### 4. Generate "Sprint Change Proposal" with Edits
-
-- Synthesize the complete change-checklist analysis (covering findings from Sections 1-4) and all the agreed-upon proposed edits (from Instruction 3) into a single document titled "Sprint Change Proposal." This proposal should align with the structure suggested by Section 5 of the change-checklist.
-- The proposal must clearly present:
-  - **Analysis Summary:** A concise overview of the original issue, its analyzed impact (on epics, artifacts, MVP scope), and the rationale for the chosen path forward.
-  - **Specific Proposed Edits:** For each affected artifact, clearly show or describe the exact changes (e.g., "Change Story X.Y from: [old text] To: [new text]", "Add new Acceptance Criterion to Story A.B: [new AC]", "Update Section 3.2 of Architecture Document as follows: [new/modified text or diagram description]").
-- Present the complete draft of the "Sprint Change Proposal" to the user for final review and feedback. Incorporate any final adjustments requested by the user.
-
-### 5. Finalize & Determine Next Steps
-
-- Obtain explicit user approval for the "Sprint Change Proposal," including all the specific edits documented within it.
-- Provide the finalized "Sprint Change Proposal" document to the user.
-- **Based on the nature of the approved changes:**
-  - **If the approved edits sufficiently address the change and can be implemented directly or organized by a PO/SM:** State that the "Correct Course Task" is complete regarding analysis and change proposal, and the user can now proceed with implementing or logging these changes (e.g., updating actual project documents, backlog items). Suggest handoff to a PO/SM agent for backlog organization if appropriate.
-  - **If the analysis and proposed path (as per checklist Section 4 and potentially Section 6) indicate that the change requires a more fundamental replan (e.g., significant scope change, major architectural rework):** Clearly state this conclusion. Advise the user that the next step involves engaging the primary PM or Architect agents, using the "Sprint Change Proposal" as critical input and context for that deeper replanning effort.
-
-## Output Deliverables
-
-- **Primary:** A "Sprint Change Proposal" document (in markdown format). This document will contain:
-  - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
-  - Specific, clearly drafted proposed edits for all affected project artifacts.
-- **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.

bmad-core/tasks/create-brownfield-story.md

@@ -1,312 +0,0 @@
-# Create Brownfield Story Task
-
-## Purpose
-
-Create detailed, implementation-ready stories for brownfield projects where traditional sharded PRD/architecture documents may not exist. This task bridges the gap between various documentation formats (document-project output, brownfield PRDs, epics, or user documentation) and executable stories for the Dev agent.
-
-## When to Use This Task
-
-**Use this task when:**
-
-- Working on brownfield projects with non-standard documentation
-- Stories need to be created from document-project output
-- Working from brownfield epics without full PRD/architecture
-- Existing project documentation doesn't follow BMad v4+ structure
-- Need to gather additional context from user during story creation
-
-**Use create-next-story when:**
-
-- Working with properly sharded PRD and v4 architecture documents
-- Following standard greenfield or well-documented brownfield workflow
-- All technical context is available in structured format
-
-## Task Execution Instructions
-
-### 0. Documentation Context
-
-Check for available documentation in this order:
-
-1. **Sharded PRD/Architecture** (docs/prd/, docs/architecture/)
-   - If found, recommend using create-next-story task instead
-
-2. **Brownfield Architecture Document** (docs/brownfield-architecture.md or similar)
-   - Created by document-project task
-   - Contains actual system state, technical debt, workarounds
-
-3. **Brownfield PRD** (docs/prd.md)
-   - May contain embedded technical details
-
-4. **Epic Files** (docs/epics/ or similar)
-   - Created by brownfield-create-epic task
-
-5. **User-Provided Documentation**
-   - Ask user to specify location and format
-
-### 1. Story Identification and Context Gathering
-
-#### 1.1 Identify Story Source
-
-Based on available documentation:
-
-- **From Brownfield PRD**: Extract stories from epic sections
-- **From Epic Files**: Read epic definition and story list
-- **From User Direction**: Ask user which specific enhancement to implement
-- **No Clear Source**: Work with user to define the story scope
-
-#### 1.2 Gather Essential Context
-
-CRITICAL: For brownfield stories, you MUST gather enough context for safe implementation. Be prepared to ask the user for missing information.
-
-**Required Information Checklist:**
-
-- [ ] What existing functionality might be affected?
-- [ ] What are the integration points with current code?
-- [ ] What patterns should be followed (with examples)?
-- [ ] What technical constraints exist?
-- [ ] Are there any "gotchas" or workarounds to know about?
-
-If any required information is missing, list the missing information and ask the user to provide it.
-
-### 2. Extract Technical Context from Available Sources
-
-#### 2.1 From Document-Project Output
-
-If using brownfield-architecture.md from document-project:
-
-- **Technical Debt Section**: Note any workarounds affecting this story
-- **Key Files Section**: Identify files that will need modification
-- **Integration Points**: Find existing integration patterns
-- **Known Issues**: Check if story touches problematic areas
-- **Actual Tech Stack**: Verify versions and constraints
-
-#### 2.2 From Brownfield PRD
-
-If using brownfield PRD:
-
-- **Technical Constraints Section**: Extract all relevant constraints
-- **Integration Requirements**: Note compatibility requirements
-- **Code Organization**: Follow specified patterns
-- **Risk Assessment**: Understand potential impacts
-
-#### 2.3 From User Documentation
-
-Ask the user to help identify:
-
-- Relevant technical specifications
-- Existing code examples to follow
-- Integration requirements
-- Testing approaches used in the project
-
-### 3. Story Creation with Progressive Detail Gathering
-
-#### 3.1 Create Initial Story Structure
-
-Start with the story template, filling in what's known:
-
-```markdown
-# Story {{Enhancement Title}}
-
-## Status: Draft
-
-## Story
-
-As a {{user_type}},
-I want {{enhancement_capability}},
-so that {{value_delivered}}.
-
-## Context Source
-
-- Source Document: {{document name/type}}
-- Enhancement Type: {{single feature/bug fix/integration/etc}}
-- Existing System Impact: {{brief assessment}}
-```
-
-#### 3.2 Develop Acceptance Criteria
-
-Critical: For brownfield, ALWAYS include criteria about maintaining existing functionality
-
-Standard structure:
-
-1. New functionality works as specified
-2. Existing {{affected feature}} continues to work unchanged
-3. Integration with {{existing system}} maintains current behavior
-4. No regression in {{related area}}
-5. Performance remains within acceptable bounds
-
-#### 3.3 Gather Technical Guidance
-
-Critical: This is where you'll need to be interactive with the user if information is missing
-
-Create Dev Technical Guidance section with available information:
-
-````markdown
-## Dev Technical Guidance
-
-### Existing System Context
-
-[Extract from available documentation]
-
-### Integration Approach
-
-[Based on patterns found or ask user]
-
-### Technical Constraints
-
-[From documentation or user input]
-
-### Missing Information
-
-Critical: List anything you couldn't find that dev will need and ask for the missing information
-
-### 4. Task Generation with Safety Checks
-
-#### 4.1 Generate Implementation Tasks
-
-Based on gathered context, create tasks that:
-
-- Include exploration tasks if system understanding is incomplete
-- Add verification tasks for existing functionality
-- Include rollback considerations
-- Reference specific files/patterns when known
-
-Example task structure for brownfield:
-
-```markdown
-## Tasks / Subtasks
-
-- [ ] Task 1: Analyze existing {{component/feature}} implementation
-  - [ ] Review {{specific files}} for current patterns
-  - [ ] Document integration points
-  - [ ] Identify potential impacts
-
-- [ ] Task 2: Implement {{new functionality}}
-  - [ ] Follow pattern from {{example file}}
-  - [ ] Integrate with {{existing component}}
-  - [ ] Maintain compatibility with {{constraint}}
-
-- [ ] Task 3: Verify existing functionality
-  - [ ] Test {{existing feature 1}} still works
-  - [ ] Verify {{integration point}} behavior unchanged
-  - [ ] Check performance impact
-
-- [ ] Task 4: Add tests
-  - [ ] Unit tests following {{project test pattern}}
-  - [ ] Integration test for {{integration point}}
-  - [ ] Update existing tests if needed
-```
-````
-
-### 5. Risk Assessment and Mitigation
-
-CRITICAL: for brownfield - always include risk assessment
-
-Add section for brownfield-specific risks:
-
-```markdown
-## Risk Assessment
-
-### Implementation Risks
-
-- **Primary Risk**: {{main risk to existing system}}
-- **Mitigation**: {{how to address}}
-- **Verification**: {{how to confirm safety}}
-
-### Rollback Plan
-
-- {{Simple steps to undo changes if needed}}
-
-### Safety Checks
-
-- [ ] Existing {{feature}} tested before changes
-- [ ] Changes can be feature-flagged or isolated
-- [ ] Rollback procedure documented
-```
-
-### 6. Final Story Validation
-
-Before finalizing:
-
-1. **Completeness Check**:
-   - [ ] Story has clear scope and acceptance criteria
-   - [ ] Technical context is sufficient for implementation
-   - [ ] Integration approach is defined
-   - [ ] Risks are identified with mitigation
-
-2. **Safety Check**:
-   - [ ] Existing functionality protection included
-   - [ ] Rollback plan is feasible
-   - [ ] Testing covers both new and existing features
-
-3. **Information Gaps**:
-   - [ ] All critical missing information gathered from user
-   - [ ] Remaining unknowns documented for dev agent
-   - [ ] Exploration tasks added where needed
-
-### 7. Story Output Format
-
-Save the story with appropriate naming:
-
-- If from epic: `docs/stories/epic-{n}-story-{m}.md`
-- If standalone: `docs/stories/brownfield-{feature-name}.md`
-- If sequential: Follow existing story numbering
-
-Include header noting documentation context:
-
-```markdown
-# Story: {{Title}}
-
-<!-- Source: {{documentation type used}} -->
-<!-- Context: Brownfield enhancement to {{existing system}} -->
-
-## Status: Draft
-
-[Rest of story content...]
-```
-
-### 8. Handoff Communication
-
-Provide clear handoff to the user:
-
-```text
-Brownfield story created: {{story title}}
-
-Source Documentation: {{what was used}}
-Story Location: {{file path}}
-
-Key Integration Points Identified:
-- {{integration point 1}}
-- {{integration point 2}}
-
-Risks Noted:
-- {{primary risk}}
-
-{{If missing info}}:
-Note: Some technical details were unclear. The story includes exploration tasks to gather needed information during implementation.
-
-Next Steps:
-1. Review story for accuracy
-2. Verify integration approach aligns with your system
-3. Approve story or request adjustments
-4. Dev agent can then implement with safety checks
-```
-
-## Success Criteria
-
-The brownfield story creation is successful when:
-
-1. Story can be implemented without requiring dev to search multiple documents
-2. Integration approach is clear and safe for existing system
-3. All available technical context has been extracted and organized
-4. Missing information has been identified and addressed
-5. Risks are documented with mitigation strategies
-6. Story includes verification of existing functionality
-7. Rollback approach is defined
-
-## Important Notes
-
-- This task is specifically for brownfield projects with non-standard documentation
-- Always prioritize existing system stability over new features
-- When in doubt, add exploration and verification tasks
-- It's better to ask the user for clarification than make assumptions
-- Each story should be self-contained for the dev agent
-- Include references to existing code patterns when available

bmad-core/tasks/create-deep-research-prompt.md

@@ -1,278 +0,0 @@
-# Create Deep Research Prompt Task
-
-This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
-
-## Purpose
-
-Generate well-structured research prompts that:
-
-- Define clear research objectives and scope
-- Specify appropriate research methodologies
-- Outline expected deliverables and formats
-- Guide systematic investigation of complex topics
-- Ensure actionable insights are captured
-
-## Research Type Selection
-
-CRITICAL: First, help the user select the most appropriate research focus based on their needs and any input documents they've provided.
-
-### 1. Research Focus Options
-
-Present these numbered options to the user:
-
-1. **Product Validation Research**
-   - Validate product hypotheses and market fit
-   - Test assumptions about user needs and solutions
-   - Assess technical and business feasibility
-   - Identify risks and mitigation strategies
-
-2. **Market Opportunity Research**
-   - Analyze market size and growth potential
-   - Identify market segments and dynamics
-   - Assess market entry strategies
-   - Evaluate timing and market readiness
-
-3. **User & Customer Research**
-   - Deep dive into user personas and behaviors
-   - Understand jobs-to-be-done and pain points
-   - Map customer journeys and touchpoints
-   - Analyze willingness to pay and value perception
-
-4. **Competitive Intelligence Research**
-   - Detailed competitor analysis and positioning
-   - Feature and capability comparisons
-   - Business model and strategy analysis
-   - Identify competitive advantages and gaps
-
-5. **Technology & Innovation Research**
-   - Assess technology trends and possibilities
-   - Evaluate technical approaches and architectures
-   - Identify emerging technologies and disruptions
-   - Analyze build vs. buy vs. partner options
-
-6. **Industry & Ecosystem Research**
-   - Map industry value chains and dynamics
-   - Identify key players and relationships
-   - Analyze regulatory and compliance factors
-   - Understand partnership opportunities
-
-7. **Strategic Options Research**
-   - Evaluate different strategic directions
-   - Assess business model alternatives
-   - Analyze go-to-market strategies
-   - Consider expansion and scaling paths
-
-8. **Risk & Feasibility Research**
-   - Identify and assess various risk factors
-   - Evaluate implementation challenges
-   - Analyze resource requirements
-   - Consider regulatory and legal implications
-
-9. **Custom Research Focus**
-   - User-defined research objectives
-   - Specialized domain investigation
-   - Cross-functional research needs
-
-### 2. Input Processing
-
-**If Project Brief provided:**
-
-- Extract key product concepts and goals
-- Identify target users and use cases
-- Note technical constraints and preferences
-- Highlight uncertainties and assumptions
-
-**If Brainstorming Results provided:**
-
-- Synthesize main ideas and themes
-- Identify areas needing validation
-- Extract hypotheses to test
-- Note creative directions to explore
-
-**If Market Research provided:**
-
-- Build on identified opportunities
-- Deepen specific market insights
-- Validate initial findings
-- Explore adjacent possibilities
-
-**If Starting Fresh:**
-
-- Gather essential context through questions
-- Define the problem space
-- Clarify research objectives
-- Establish success criteria
-
-## Process
-
-### 3. Research Prompt Structure
-
-CRITICAL: collaboratively develop a comprehensive research prompt with these components.
-
-#### A. Research Objectives
-
-CRITICAL: collaborate with the user to articulate clear, specific objectives for the research.
-
-- Primary research goal and purpose
-- Key decisions the research will inform
-- Success criteria for the research
-- Constraints and boundaries
-
-#### B. Research Questions
-
-CRITICAL: collaborate with the user to develop specific, actionable research questions organized by theme.
-
-**Core Questions:**
-
-- Central questions that must be answered
-- Priority ranking of questions
-- Dependencies between questions
-
-**Supporting Questions:**
-
-- Additional context-building questions
-- Nice-to-have insights
-- Future-looking considerations
-
-#### C. Research Methodology
-
-**Data Collection Methods:**
-
-- Secondary research sources
-- Primary research approaches (if applicable)
-- Data quality requirements
-- Source credibility criteria
-
-**Analysis Frameworks:**
-
-- Specific frameworks to apply
-- Comparison criteria
-- Evaluation methodologies
-- Synthesis approaches
-
-#### D. Output Requirements
-
-**Format Specifications:**
-
-- Executive summary requirements
-- Detailed findings structure
-- Visual/tabular presentations
-- Supporting documentation
-
-**Key Deliverables:**
-
-- Must-have sections and insights
-- Decision-support elements
-- Action-oriented recommendations
-- Risk and uncertainty documentation
-
-### 4. Prompt Generation
-
-**Research Prompt Template:**
-
-```markdown
-## Research Objective
-
-[Clear statement of what this research aims to achieve]
-
-## Background Context
-
-[Relevant information from project brief, brainstorming, or other inputs]
-
-## Research Questions
-
-### Primary Questions (Must Answer)
-
-1. [Specific, actionable question]
-2. [Specific, actionable question]
-   ...
-
-### Secondary Questions (Nice to Have)
-
-1. [Supporting question]
-2. [Supporting question]
-   ...
-
-## Research Methodology
-
-### Information Sources
-
-- [Specific source types and priorities]
-
-### Analysis Frameworks
-
-- [Specific frameworks to apply]
-
-### Data Requirements
-
-- [Quality, recency, credibility needs]
-
-## Expected Deliverables
-
-### Executive Summary
-
-- Key findings and insights
-- Critical implications
-- Recommended actions
-
-### Detailed Analysis
-
-[Specific sections needed based on research type]
-
-### Supporting Materials
-
-- Data tables
-- Comparison matrices
-- Source documentation
-
-## Success Criteria
-
-[How to evaluate if research achieved its objectives]
-
-## Timeline and Priority
-
-[If applicable, any time constraints or phasing]
-```
-
-### 5. Review and Refinement
-
-1. **Present Complete Prompt**
-   - Show the full research prompt
-   - Explain key elements and rationale
-   - Highlight any assumptions made
-
-2. **Gather Feedback**
-   - Are the objectives clear and correct?
-   - Do the questions address all concerns?
-   - Is the scope appropriate?
-   - Are output requirements sufficient?
-
-3. **Refine as Needed**
-   - Incorporate user feedback
-   - Adjust scope or focus
-   - Add missing elements
-   - Clarify ambiguities
-
-### 6. Next Steps Guidance
-
-**Execution Options:**
-
-1. **Use with AI Research Assistant**: Provide this prompt to an AI model with research capabilities
-2. **Guide Human Research**: Use as a framework for manual research efforts
-3. **Hybrid Approach**: Combine AI and human research using this structure
-
-**Integration Points:**
-
-- How findings will feed into next phases
-- Which team members should review results
-- How to validate findings
-- When to revisit or expand research
-
-## Important Notes
-
-- The quality of the research prompt directly impacts the quality of insights gathered
-- Be specific rather than general in research questions
-- Consider both current state and future implications
-- Balance comprehensiveness with focus
-- Document assumptions and limitations clearly
-- Plan for iterative refinement based on initial findings

bmad-core/tasks/create-next-story.md

@@ -1,112 +0,0 @@
-# Create Next Story Task
-
-## Purpose
-
-To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the `Story Template`. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research or finding its own context.
-
-## SEQUENTIAL Task Execution (Do not proceed until current Task is complete)
-
-### 0. Load Core Configuration and Check Workflow
-
-- Load `{root}/core-config.yaml` from the project root
-- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
-- Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
-
-### 1. Identify Next Story for Preparation
-
-#### 1.1 Locate Epic Files and Review Existing Stories
-
-- Based on `prdSharded` from config, locate epic files (sharded location/pattern or monolithic PRD sections)
-- If `devStoryLocation` has story files, load the highest `{epicNum}.{storyNum}.story.md` file
-- **If highest story exists:**
-  - Verify status is 'Done'. If not, alert user: "ALERT: Found incomplete story! File: {lastEpicNum}.{lastStoryNum}.story.md Status: [current status] You should fix this story first, but would you like to accept risk & override to create the next story in draft?"
-  - If proceeding, select next sequential story in the current epic
-  - If epic is complete, prompt user: "Epic {epicNum} Complete: All stories in Epic {epicNum} have been completed. Would you like to: 1) Begin Epic {epicNum + 1} with story 1 2) Select a specific story to work on 3) Cancel story creation"
-  - **CRITICAL**: NEVER automatically skip to another epic. User MUST explicitly instruct which story to create.
-- **If no story files exist:** The next story is ALWAYS 1.1 (first story of first epic)
-- Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}"
-
-### 2. Gather Story Requirements and Previous Story Context
-
-- Extract story requirements from the identified epic file
-- If previous story exists, review Dev Agent Record sections for:
-  - Completion Notes and Debug Log References
-  - Implementation deviations and technical decisions
-  - Challenges encountered and lessons learned
-- Extract relevant insights that inform the current story's preparation
-
-### 3. Gather Architecture Context
-
-#### 3.1 Determine Architecture Reading Strategy
-
-- **If `architectureVersion: >= v4` and `architectureSharded: true`**: Read `{architectureShardedLocation}/index.md` then follow structured reading order below
-- **Else**: Use monolithic `architectureFile` for similar sections
-
-#### 3.2 Read Architecture Documents Based on Story Type
-
-**For ALL Stories:** tech-stack.md, unified-project-structure.md, coding-standards.md, testing-strategy.md
-
-**For Backend/API Stories, additionally:** data-models.md, database-schema.md, backend-architecture.md, rest-api-spec.md, external-apis.md
-
-**For Frontend/UI Stories, additionally:** frontend-architecture.md, components.md, core-workflows.md, data-models.md
-
-**For Full-Stack Stories:** Read both Backend and Frontend sections above
-
-#### 3.3 Extract Story-Specific Technical Details
-
-Extract ONLY information directly relevant to implementing the current story. Do NOT invent new libraries, patterns, or standards not in the source documents.
-
-Extract:
-
-- Specific data models, schemas, or structures the story will use
-- API endpoints the story must implement or consume
-- Component specifications for UI elements in the story
-- File paths and naming conventions for new code
-- Testing requirements specific to the story's features
-- Security or performance considerations affecting the story
-
-ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
-
-### 4. Verify Project Structure Alignment
-
-- Cross-reference story requirements with Project Structure Guide from `docs/architecture/unified-project-structure.md`
-- Ensure file paths, component locations, or module names align with defined structures
-- Document any structural conflicts in "Project Structure Notes" section within the story draft
-
-### 5. Populate Story Template with Full Context
-
-- Create new story file: `{devStoryLocation}/{epicNum}.{storyNum}.story.md` using Story Template
-- Fill in basic story information: Title, Status (Draft), Story statement, Acceptance Criteria from Epic
-- **`Dev Notes` section (CRITICAL):**
-  - CRITICAL: This section MUST contain ONLY information extracted from architecture documents. NEVER invent or assume technical details.
-  - Include ALL relevant technical details from Steps 2-3, organized by category:
-    - **Previous Story Insights**: Key learnings from previous story
-    - **Data Models**: Specific schemas, validation rules, relationships [with source references]
-    - **API Specifications**: Endpoint details, request/response formats, auth requirements [with source references]
-    - **Component Specifications**: UI component details, props, state management [with source references]
-    - **File Locations**: Exact paths where new code should be created based on project structure
-    - **Testing Requirements**: Specific test cases or strategies from testing-strategy.md
-    - **Technical Constraints**: Version requirements, performance considerations, security rules
-  - Every technical detail MUST include its source reference: `[Source: architecture/{filename}.md#{section}]`
-  - If information for a category is not found in the architecture docs, explicitly state: "No specific guidance found in architecture docs"
-- **`Tasks / Subtasks` section:**
-  - Generate detailed, sequential list of technical tasks based ONLY on: Epic Requirements, Story AC, Reviewed Architecture Information
-  - Each task must reference relevant architecture documentation
-  - Include unit testing as explicit subtasks based on the Testing Strategy
-  - Link tasks to ACs where applicable (e.g., `Task 1 (AC: 1, 3)`)
-- Add notes on project structure alignment or discrepancies found in Step 4
-
-### 6. Story Draft Completion and Review
-
-- Review all sections for completeness and accuracy
-- Verify all source references are included for technical details
-- Ensure tasks align with both epic requirements and architecture constraints
-- Update status to "Draft" and save the story file
-- Execute `{root}/tasks/execute-checklist` `{root}/checklists/story-draft-checklist`
-- Provide summary to user including:
-  - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
-  - Status: Draft
-  - Key technical components included from architecture docs
-  - Any deviations or conflicts noted between epic and architecture
-  - Checklist Results
-  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `{root}/tasks/validate-next-story`

bmad-core/tasks/document-project.md

@@ -1,343 +0,0 @@
-# Document an Existing Project
-
-## Purpose
-
-Generate comprehensive documentation for existing projects optimized for AI development agents. This task creates structured reference materials that enable AI agents to understand project context, conventions, and patterns for effective contribution to any codebase.
-
-## Task Instructions
-
-### 1. Initial Project Analysis
-
-**CRITICAL:** First, check if a PRD or requirements document exists in context. If yes, use it to focus your documentation efforts on relevant areas only.
-
-**IF PRD EXISTS**:
-
-- Review the PRD to understand what enhancement/feature is planned
-- Identify which modules, services, or areas will be affected
-- Focus documentation ONLY on these relevant areas
-- Skip unrelated parts of the codebase to keep docs lean
-
-**IF NO PRD EXISTS**:
-Ask the user:
-
-"I notice you haven't provided a PRD or requirements document. To create more focused and useful documentation, I recommend one of these options:
-
-1. **Create a PRD first** - Would you like me to help create a brownfield PRD before documenting? This helps focus documentation on relevant areas.
-
-2. **Provide existing requirements** - Do you have a requirements document, epic, or feature description you can share?
-
-3. **Describe the focus** - Can you briefly describe what enhancement or feature you're planning? For example:
-   - 'Adding payment processing to the user service'
-   - 'Refactoring the authentication module'
-   - 'Integrating with a new third-party API'
-
-4. **Document everything** - Or should I proceed with comprehensive documentation of the entire codebase? (Note: This may create excessive documentation for large projects)
-
-Please let me know your preference, or I can proceed with full documentation if you prefer."
-
-Based on their response:
-
-- If they choose option 1-3: Use that context to focus documentation
-- If they choose option 4 or decline: Proceed with comprehensive analysis below
-
-Begin by conducting analysis of the existing project. Use available tools to:
-
-1. **Project Structure Discovery**: Examine the root directory structure, identify main folders, and understand the overall organization
-2. **Technology Stack Identification**: Look for package.json, requirements.txt, Cargo.toml, pom.xml, etc. to identify languages, frameworks, and dependencies
-3. **Build System Analysis**: Find build scripts, CI/CD configurations, and development commands
-4. **Existing Documentation Review**: Check for README files, docs folders, and any existing documentation
-5. **Code Pattern Analysis**: Sample key files to understand coding patterns, naming conventions, and architectural approaches
-
-Ask the user these elicitation questions to better understand their needs:
-
-- What is the primary purpose of this project?
-- Are there any specific areas of the codebase that are particularly complex or important for agents to understand?
-- What types of tasks do you expect AI agents to perform on this project? (e.g., bug fixes, feature additions, refactoring, testing)
-- Are there any existing documentation standards or formats you prefer?
-- What level of technical detail should the documentation target? (junior developers, senior developers, mixed team)
-- Is there a specific feature or enhancement you're planning? (This helps focus documentation)
-
-### 2. Deep Codebase Analysis
-
-CRITICAL: Before generating documentation, conduct extensive analysis of the existing codebase:
-
-1. **Explore Key Areas**:
-   - Entry points (main files, index files, app initializers)
-   - Configuration files and environment setup
-   - Package dependencies and versions
-   - Build and deployment configurations
-   - Test suites and coverage
-
-2. **Ask Clarifying Questions**:
-   - "I see you're using [technology X]. Are there any custom patterns or conventions I should document?"
-   - "What are the most critical/complex parts of this system that developers struggle with?"
-   - "Are there any undocumented 'tribal knowledge' areas I should capture?"
-   - "What technical debt or known issues should I document?"
-   - "Which parts of the codebase change most frequently?"
-
-3. **Map the Reality**:
-   - Identify ACTUAL patterns used (not theoretical best practices)
-   - Find where key business logic lives
-   - Locate integration points and external dependencies
-   - Document workarounds and technical debt
-   - Note areas that differ from standard patterns
-
-**IF PRD PROVIDED**: Also analyze what would need to change for the enhancement
-
-### 3. Core Documentation Generation
-
-[[LLM: Generate a comprehensive BROWNFIELD architecture document that reflects the ACTUAL state of the codebase.
-
-**CRITICAL**: This is NOT an aspirational architecture document. Document what EXISTS, including:
-
-- Technical debt and workarounds
-- Inconsistent patterns between different parts
-- Legacy code that can't be changed
-- Integration constraints
-- Performance bottlenecks
-
-**Document Structure**:
-
-# [Project Name] Brownfield Architecture Document
-
-## Introduction
-
-This document captures the CURRENT STATE of the [Project Name] codebase, including technical debt, workarounds, and real-world patterns. It serves as a reference for AI agents working on enhancements.
-
-### Document Scope
-
-[If PRD provided: "Focused on areas relevant to: {enhancement description}"]
-[If no PRD: "Comprehensive documentation of entire system"]
-
-### Change Log
-
-| Date   | Version | Description                 | Author    |
-| ------ | ------- | --------------------------- | --------- |
-| [Date] | 1.0     | Initial brownfield analysis | [Analyst] |
-
-## Quick Reference - Key Files and Entry Points
-
-### Critical Files for Understanding the System
-
-- **Main Entry**: `src/index.js` (or actual entry point)
-- **Configuration**: `config/app.config.js`, `.env.example`
-- **Core Business Logic**: `src/services/`, `src/domain/`
-- **API Definitions**: `src/routes/` or link to OpenAPI spec
-- **Database Models**: `src/models/` or link to schema files
-- **Key Algorithms**: [List specific files with complex logic]
-
-### If PRD Provided - Enhancement Impact Areas
-
-[Highlight which files/modules will be affected by the planned enhancement]
-
-## High Level Architecture
-
-### Technical Summary
-
-### Actual Tech Stack (from package.json/requirements.txt)
-
-| Category  | Technology | Version | Notes                      |
-| --------- | ---------- | ------- | -------------------------- |
-| Runtime   | Node.js    | 16.x    | [Any constraints]          |
-| Framework | Express    | 4.18.2  | [Custom middleware?]       |
-| Database  | PostgreSQL | 13      | [Connection pooling setup] |
-
-etc...
-
-### Repository Structure Reality Check
-
-- Type: [Monorepo/Polyrepo/Hybrid]
-- Package Manager: [npm/yarn/pnpm]
-- Notable: [Any unusual structure decisions]
-
-## Source Tree and Module Organization
-
-### Project Structure (Actual)
-
-```text
-project-root/
-├── src/
-│   ├── controllers/     # HTTP request handlers
-│   ├── services/        # Business logic (NOTE: inconsistent patterns between user and payment services)
-│   ├── models/          # Database models (Sequelize)
-│   ├── utils/           # Mixed bag - needs refactoring
-│   └── legacy/          # DO NOT MODIFY - old payment system still in use
-├── tests/               # Jest tests (60% coverage)
-├── scripts/             # Build and deployment scripts
-└── config/              # Environment configs
-```
-
-### Key Modules and Their Purpose
-
-- **User Management**: `src/services/userService.js` - Handles all user operations
-- **Authentication**: `src/middleware/auth.js` - JWT-based, custom implementation
-- **Payment Processing**: `src/legacy/payment.js` - CRITICAL: Do not refactor, tightly coupled
-- **[List other key modules with their actual files]**
-
-## Data Models and APIs
-
-### Data Models
-
-Instead of duplicating, reference actual model files:
-
-- **User Model**: See `src/models/User.js`
-- **Order Model**: See `src/models/Order.js`
-- **Related Types**: TypeScript definitions in `src/types/`
-
-### API Specifications
-
-- **OpenAPI Spec**: `docs/api/openapi.yaml` (if exists)
-- **Postman Collection**: `docs/api/postman-collection.json`
-- **Manual Endpoints**: [List any undocumented endpoints discovered]
-
-## Technical Debt and Known Issues
-
-### Critical Technical Debt
-
-1. **Payment Service**: Legacy code in `src/legacy/payment.js` - tightly coupled, no tests
-2. **User Service**: Different pattern than other services, uses callbacks instead of promises
-3. **Database Migrations**: Manually tracked, no proper migration tool
-4. **[Other significant debt]**
-
-### Workarounds and Gotchas
-
-- **Environment Variables**: Must set `NODE_ENV=production` even for staging (historical reason)
-- **Database Connections**: Connection pool hardcoded to 10, changing breaks payment service
-- **[Other workarounds developers need to know]**
-
-## Integration Points and External Dependencies
-
-### External Services
-
-| Service  | Purpose  | Integration Type | Key Files                      |
-| -------- | -------- | ---------------- | ------------------------------ |
-| Stripe   | Payments | REST API         | `src/integrations/stripe/`     |
-| SendGrid | Emails   | SDK              | `src/services/emailService.js` |
-
-etc...
-
-### Internal Integration Points
-
-- **Frontend Communication**: REST API on port 3000, expects specific headers
-- **Background Jobs**: Redis queue, see `src/workers/`
-- **[Other integrations]**
-
-## Development and Deployment
-
-### Local Development Setup
-
-1. Actual steps that work (not ideal steps)
-2. Known issues with setup
-3. Required environment variables (see `.env.example`)
-
-### Build and Deployment Process
-
-- **Build Command**: `npm run build` (webpack config in `webpack.config.js`)
-- **Deployment**: Manual deployment via `scripts/deploy.sh`
-- **Environments**: Dev, Staging, Prod (see `config/environments/`)
-
-## Testing Reality
-
-### Current Test Coverage
-
-- Unit Tests: 60% coverage (Jest)
-- Integration Tests: Minimal, in `tests/integration/`
-- E2E Tests: None
-- Manual Testing: Primary QA method
-
-### Running Tests
-
-```bash
-npm test           # Runs unit tests
-npm run test:integration  # Runs integration tests (requires local DB)
-```
-
-## If Enhancement PRD Provided - Impact Analysis
-
-### Files That Will Need Modification
-
-Based on the enhancement requirements, these files will be affected:
-
-- `src/services/userService.js` - Add new user fields
-- `src/models/User.js` - Update schema
-- `src/routes/userRoutes.js` - New endpoints
-- [etc...]
-
-### New Files/Modules Needed
-
-- `src/services/newFeatureService.js` - New business logic
-- `src/models/NewFeature.js` - New data model
-- [etc...]
-
-### Integration Considerations
-
-- Will need to integrate with existing auth middleware
-- Must follow existing response format in `src/utils/responseFormatter.js`
-- [Other integration points]
-
-## Appendix - Useful Commands and Scripts
-
-### Frequently Used Commands
-
-```bash
-npm run dev         # Start development server
-npm run build       # Production build
-npm run migrate     # Run database migrations
-npm run seed        # Seed test data
-```
-
-### Debugging and Troubleshooting
-
-- **Logs**: Check `logs/app.log` for application logs
-- **Debug Mode**: Set `DEBUG=app:*` for verbose logging
-- **Common Issues**: See `docs/troubleshooting.md`]]
-
-### 4. Document Delivery
-
-1. **In Web UI (Gemini, ChatGPT, Claude)**:
-   - Present the entire document in one response (or multiple if too long)
-   - Tell user to copy and save as `docs/brownfield-architecture.md` or `docs/project-architecture.md`
-   - Mention it can be sharded later in IDE if needed
-
-2. **In IDE Environment**:
-   - Create the document as `docs/brownfield-architecture.md`
-   - Inform user this single document contains all architectural information
-   - Can be sharded later using PO agent if desired
-
-The document should be comprehensive enough that future agents can understand:
-
-- The actual state of the system (not idealized)
-- Where to find key files and logic
-- What technical debt exists
-- What constraints must be respected
-- If PRD provided: What needs to change for the enhancement]]
-
-### 5. Quality Assurance
-
-CRITICAL: Before finalizing the document:
-
-1. **Accuracy Check**: Verify all technical details match the actual codebase
-2. **Completeness Review**: Ensure all major system components are documented
-3. **Focus Validation**: If user provided scope, verify relevant areas are emphasized
-4. **Clarity Assessment**: Check that explanations are clear for AI agents
-5. **Navigation**: Ensure document has clear section structure for easy reference
-
-Apply the advanced elicitation task after major sections to refine based on user feedback.
-
-## Success Criteria
-
-- Single comprehensive brownfield architecture document created
-- Document reflects REALITY including technical debt and workarounds
-- Key files and modules are referenced with actual paths
-- Models/APIs reference source files rather than duplicating content
-- If PRD provided: Clear impact analysis showing what needs to change
-- Document enables AI agents to navigate and understand the actual codebase
-- Technical constraints and "gotchas" are clearly documented
-
-## Notes
-
-- This task creates ONE document that captures the TRUE state of the system
-- References actual files rather than duplicating content when possible
-- Documents technical debt, workarounds, and constraints honestly
-- For brownfield projects with PRD: Provides clear enhancement impact analysis
-- The goal is PRACTICAL documentation for AI agents doing real work

bmad-core/tasks/facilitate-brainstorming-session.md

@@ -1,136 +0,0 @@
----
-docOutputLocation: docs/brainstorming-session-results.md
-template: "{root}/templates/brainstorming-output-tmpl.yaml"
----
-
-# Facilitate Brainstorming Session Task
-
-Facilitate interactive brainstorming sessions with users. Be creative and adaptive in applying techniques.
-
-## Process
-
-### Step 1: Session Setup
-
-Ask 4 context questions (don't preview what happens next):
-
-1. What are we brainstorming about?
-2. Any constraints or parameters?
-3. Goal: broad exploration or focused ideation?
-4. Do you want a structured document output to reference later? (Default Yes)
-
-### Step 2: Present Approach Options
-
-After getting answers to Step 1, present 4 approach options (numbered):
-
-1. User selects specific techniques
-2. Analyst recommends techniques based on context
-3. Random technique selection for creative variety
-4. Progressive technique flow (start broad, narrow down)
-
-### Step 3: Execute Techniques Interactively
-
-**KEY PRINCIPLES:**
-
-- **FACILITATOR ROLE**: Guide user to generate their own ideas through questions, prompts, and examples
-- **CONTINUOUS ENGAGEMENT**: Keep user engaged with chosen technique until they want to switch or are satisfied
-- **CAPTURE OUTPUT**: If (default) document output requested, capture all ideas generated in each technique section to the document from the beginning.
-
-**Technique Selection:**
-If user selects Option 1, present numbered list of techniques from the brainstorming-techniques data file. User can select by number..
-
-**Technique Execution:**
-
-1. Apply selected technique according to data file description
-2. Keep engaging with technique until user indicates they want to:
-   - Choose a different technique
-   - Apply current ideas to a new technique
-   - Move to convergent phase
-   - End session
-
-**Output Capture (if requested):**
-For each technique used, capture:
-
-- Technique name and duration
-- Key ideas generated by user
-- Insights and patterns identified
-- User's reflections on the process
-
-### Step 4: Session Flow
-
-1. **Warm-up** (5-10 min) - Build creative confidence
-2. **Divergent** (20-30 min) - Generate quantity over quality
-3. **Convergent** (15-20 min) - Group and categorize ideas
-4. **Synthesis** (10-15 min) - Refine and develop concepts
-
-### Step 5: Document Output (if requested)
-
-Generate structured document with these sections:
-
-**Executive Summary**
-
-- Session topic and goals
-- Techniques used and duration
-- Total ideas generated
-- Key themes and patterns identified
-
-**Technique Sections** (for each technique used)
-
-- Technique name and description
-- Ideas generated (user's own words)
-- Insights discovered
-- Notable connections or patterns
-
-**Idea Categorization**
-
-- **Immediate Opportunities** - Ready to implement now
-- **Future Innovations** - Requires development/research
-- **Moonshots** - Ambitious, transformative concepts
-- **Insights & Learnings** - Key realizations from session
-
-**Action Planning**
-
-- Top 3 priority ideas with rationale
-- Next steps for each priority
-- Resources/research needed
-- Timeline considerations
-
-**Reflection & Follow-up**
-
-- What worked well in this session
-- Areas for further exploration
-- Recommended follow-up techniques
-- Questions that emerged for future sessions
-
-## Key Principles
-
-- **YOU ARE A FACILITATOR**: Guide the user to brainstorm, don't brainstorm for them (unless they request it persistently)
-- **INTERACTIVE DIALOGUE**: Ask questions, wait for responses, build on their ideas
-- **ONE TECHNIQUE AT A TIME**: Don't mix multiple techniques in one response
-- **CONTINUOUS ENGAGEMENT**: Stay with one technique until user wants to switch
-- **DRAW IDEAS OUT**: Use prompts and examples to help them generate their own ideas
-- **REAL-TIME ADAPTATION**: Monitor engagement and adjust approach as needed
-- Maintain energy and momentum
-- Defer judgment during generation
-- Quantity leads to quality (aim for 100 ideas in 60 minutes)
-- Build on ideas collaboratively
-- Document everything in output document
-
-## Advanced Engagement Strategies
-
-**Energy Management**
-
-- Check engagement levels: "How are you feeling about this direction?"
-- Offer breaks or technique switches if energy flags
-- Use encouraging language and celebrate idea generation
-
-**Depth vs. Breadth**
-
-- Ask follow-up questions to deepen ideas: "Tell me more about that..."
-- Use "Yes, and..." to build on their ideas
-- Help them make connections: "How does this relate to your earlier idea about...?"
-
-**Transition Management**
-
-- Always ask before switching techniques: "Ready to try a different approach?"
-- Offer options: "Should we explore this idea deeper or generate more alternatives?"
-- Respect their process and timing

bmad-core/tasks/generate-ai-frontend-prompt.md

@@ -1,51 +0,0 @@
-# Create AI Frontend Prompt Task
-
-## Purpose
-
-To generate a masterful, comprehensive, and optimized prompt that can be used with any AI-driven frontend development tool (e.g., Vercel v0, Lovable.ai, or similar) to scaffold or generate significant portions of a frontend application.
-
-## Inputs
-
-- Completed UI/UX Specification (`front-end-spec.md`)
-- Completed Frontend Architecture Document (`front-end-architecture`) or a full stack combined architecture such as `architecture.md`
-- Main System Architecture Document (`architecture` - for API contracts and tech stack to give further context)
-
-## Key Activities & Instructions
-
-### 1. Core Prompting Principles
-
-Before generating the prompt, you must understand these core principles for interacting with a generative AI for code.
-
-- **Be Explicit and Detailed**: The AI cannot read your mind. Provide as much detail and context as possible. Vague requests lead to generic or incorrect outputs.
-- **Iterate, Don't Expect Perfection**: Generating an entire complex application in one go is rare. The most effective method is to prompt for one component or one section at a time, then build upon the results.
-- **Provide Context First**: Always start by providing the AI with the necessary context, such as the tech stack, existing code snippets, and overall project goals.
-- **Mobile-First Approach**: Frame all UI generation requests with a mobile-first design mindset. Describe the mobile layout first, then provide separate instructions for how it should adapt for tablet and desktop.
-
-### 2. The Structured Prompting Framework
-
-To ensure the highest quality output, you MUST structure every prompt using the following four-part framework.
-
-1. **High-Level Goal**: Start with a clear, concise summary of the overall objective. This orients the AI on the primary task.
-   - _Example: "Create a responsive user registration form with client-side validation and API integration."_
-2. **Detailed, Step-by-Step Instructions**: Provide a granular, numbered list of actions the AI should take. Break down complex tasks into smaller, sequential steps. This is the most critical part of the prompt.
-   - _Example: "1. Create a new file named `RegistrationForm.js`. 2. Use React hooks for state management. 3. Add styled input fields for 'Name', 'Email', and 'Password'. 4. For the email field, ensure it is a valid email format. 5. On submission, call the API endpoint defined below."_
-3. **Code Examples, Data Structures & Constraints**: Include any relevant snippets of existing code, data structures, or API contracts. This gives the AI concrete examples to work with. Crucially, you must also state what _not_ to do.
-   - _Example: "Use this API endpoint: `POST /api/register`. The expected JSON payload is `{ "name": "string", "email": "string", "password": "string" }`. Do NOT include a 'confirm password' field. Use Tailwind CSS for all styling."_
-4. **Define a Strict Scope**: Explicitly define the boundaries of the task. Tell the AI which files it can modify and, more importantly, which files to leave untouched to prevent unintended changes across the codebase.
-   - _Example: "You should only create the `RegistrationForm.js` component and add it to the `pages/register.js` file. Do NOT alter the `Navbar.js` component or any other existing page or component."_
-
-### 3. Assembling the Master Prompt
-
-You will now synthesize the inputs and the above principles into a final, comprehensive prompt.
-
-1. **Gather Foundational Context**:
-   - Start the prompt with a preamble describing the overall project purpose, the full tech stack (e.g., Next.js, TypeScript, Tailwind CSS), and the primary UI component library being used.
-2. **Describe the Visuals**:
-   - If the user has design files (Figma, etc.), instruct them to provide links or screenshots.
-   - If not, describe the visual style: color palette, typography, spacing, and overall aesthetic (e.g., "minimalist", "corporate", "playful").
-3. **Build the Prompt using the Structured Framework**:
-   - Follow the four-part framework from Section 2 to build out the core request, whether it's for a single component or a full page.
-4. **Present and Refine**:
-   - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
-   - Explain the structure of the prompt and why certain information was included, referencing the principles above.
-   - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>

bmad-core/tasks/index-docs.md

@@ -1,173 +0,0 @@
-# Index Documentation Task
-
-## Purpose
-
-This task maintains the integrity and completeness of the `docs/index.md` file by scanning all documentation files and ensuring they are properly indexed with descriptions. It handles both root-level documents and documents within subfolders, organizing them hierarchically.
-
-## Task Instructions
-
-You are now operating as a Documentation Indexer. Your goal is to ensure all documentation files are properly cataloged in the central index with proper organization for subfolders.
-
-### Required Steps
-
-1. First, locate and scan:
-   - The `docs/` directory and all subdirectories
-   - The existing `docs/index.md` file (create if absent)
-   - All markdown (`.md`) and text (`.txt`) files in the documentation structure
-   - Note the folder structure for hierarchical organization
-
-2. For the existing `docs/index.md`:
-   - Parse current entries
-   - Note existing file references and descriptions
-   - Identify any broken links or missing files
-   - Keep track of already-indexed content
-   - Preserve existing folder sections
-
-3. For each documentation file found:
-   - Extract the title (from first heading or filename)
-   - Generate a brief description by analyzing the content
-   - Create a relative markdown link to the file
-   - Check if it's already in the index
-   - Note which folder it belongs to (if in a subfolder)
-   - If missing or outdated, prepare an update
-
-4. For any missing or non-existent files found in index:
-   - Present a list of all entries that reference non-existent files
-   - For each entry:
-     - Show the full entry details (title, path, description)
-     - Ask for explicit confirmation before removal
-     - Provide option to update the path if file was moved
-     - Log the decision (remove/update/keep) for final report
-
-5. Update `docs/index.md`:
-   - Maintain existing structure and organization
-   - Create level 2 sections (`##`) for each subfolder
-   - List root-level documents first
-   - Add missing entries with descriptions
-   - Update outdated entries
-   - Remove only entries that were confirmed for removal
-   - Ensure consistent formatting throughout
-
-### Index Structure Format
-
-The index should be organized as follows:
-
-```markdown
-# Documentation Index
-
-## Root Documents
-
-### [Document Title](./document.md)
-
-Brief description of the document's purpose and contents.
-
-### [Another Document](./another.md)
-
-Description here.
-
-## Folder Name
-
-Documents within the `folder-name/` directory:
-
-### [Document in Folder](./folder-name/document.md)
-
-Description of this document.
-
-### [Another in Folder](./folder-name/another.md)
-
-Description here.
-
-## Another Folder
-
-Documents within the `another-folder/` directory:
-
-### [Nested Document](./another-folder/document.md)
-
-Description of nested document.
-```
-
-### Index Entry Format
-
-Each entry should follow this format:
-
-```markdown
-### [Document Title](relative/path/to/file.md)
-
-Brief description of the document's purpose and contents.
-```
-
-### Rules of Operation
-
-1. NEVER modify the content of indexed files
-2. Preserve existing descriptions in index.md when they are adequate
-3. Maintain any existing categorization or grouping in the index
-4. Use relative paths for all links (starting with `./`)
-5. Ensure descriptions are concise but informative
-6. NEVER remove entries without explicit confirmation
-7. Report any broken links or inconsistencies found
-8. Allow path updates for moved files before considering removal
-9. Create folder sections using level 2 headings (`##`)
-10. Sort folders alphabetically, with root documents listed first
-11. Within each section, sort documents alphabetically by title
-
-### Process Output
-
-The task will provide:
-
-1. A summary of changes made to index.md
-2. List of newly indexed files (organized by folder)
-3. List of updated entries
-4. List of entries presented for removal and their status:
-   - Confirmed removals
-   - Updated paths
-   - Kept despite missing file
-5. Any new folders discovered
-6. Any other issues or inconsistencies found
-
-### Handling Missing Files
-
-For each file referenced in the index but not found in the filesystem:
-
-1. Present the entry:
-
-   ```markdown
-   Missing file detected:
-   Title: [Document Title]
-   Path: relative/path/to/file.md
-   Description: Existing description
-   Section: [Root Documents | Folder Name]
-
-   Options:
-
-   1. Remove this entry
-   2. Update the file path
-   3. Keep entry (mark as temporarily unavailable)
-
-   Please choose an option (1/2/3):
-   ```
-
-2. Wait for user confirmation before taking any action
-3. Log the decision for the final report
-
-### Special Cases
-
-1. **Sharded Documents**: If a folder contains an `index.md` file, treat it as a sharded document:
-   - Use the folder's `index.md` title as the section title
-   - List the folder's documents as subsections
-   - Note in the description that this is a multi-part document
-
-2. **README files**: Convert `README.md` to more descriptive titles based on content
-
-3. **Nested Subfolders**: For deeply nested folders, maintain the hierarchy but limit to 2 levels in the main index. Deeper structures should have their own index files.
-
-## Required Input
-
-Please provide:
-
-1. Location of the `docs/` directory (default: `./docs`)
-2. Confirmation of write access to `docs/index.md`
-3. Any specific categorization preferences
-4. Any files or directories to exclude from indexing (e.g., `.git`, `node_modules`)
-5. Whether to include hidden files/folders (starting with `.`)
-
-Would you like to proceed with documentation indexing? Please provide the required input above.

bmad-core/tasks/kb-mode-interaction.md

@@ -1,75 +0,0 @@
-# KB Mode Interaction Task
-
-## Purpose
-
-Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.
-
-## Instructions
-
-When entering KB mode (\*kb-mode), follow these steps:
-
-### 1. Welcome and Guide
-
-Announce entering KB mode with a brief, friendly introduction.
-
-### 2. Present Topic Areas
-
-Offer a concise list of main topic areas the user might want to explore:
-
-**What would you like to know more about?**
-
-1. **Setup & Installation** - Getting started with BMad
-2. **Workflows** - Choosing the right workflow for your project
-3. **Web vs IDE** - When to use each environment
-4. **Agents** - Understanding specialized agents and their roles
-5. **Documents** - PRDs, Architecture, Stories, and more
-6. **Agile Process** - How BMad implements Agile methodologies
-7. **Configuration** - Customizing BMad for your needs
-8. **Best Practices** - Tips for effective BMad usage
-
-Or ask me about anything else related to BMad-Method!
-
-### 3. Respond Contextually
-
-- Wait for user's specific question or topic selection
-- Provide focused, relevant information from the knowledge base
-- Offer to dive deeper or explore related topics
-- Keep responses concise unless user asks for detailed explanations
-
-### 4. Interactive Exploration
-
-- After answering, suggest related topics they might find helpful
-- Maintain conversational flow rather than data dumping
-- Use examples when appropriate
-- Reference specific documentation sections when relevant
-
-### 5. Exit Gracefully
-
-When user is done or wants to exit KB mode:
-
-- Summarize key points discussed if helpful
-- Remind them they can return to KB mode anytime with \*kb-mode
-- Suggest next steps based on what was discussed
-
-## Example Interaction
-
-**User**: \*kb-mode
-
-**Assistant**: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.
-
-**What would you like to know more about?**
-
-1. **Setup & Installation** - Getting started with BMad
-2. **Workflows** - Choosing the right workflow for your project
-3. **Web vs IDE** - When to use each environment
-4. **Agents** - Understanding specialized agents and their roles
-5. **Documents** - PRDs, Architecture, Stories, and more
-6. **Agile Process** - How BMad implements Agile methodologies
-7. **Configuration** - Customizing BMad for your needs
-8. **Best Practices** - Tips for effective BMad usage
-
-Or ask me about anything else related to BMad-Method!
-
-**User**: Tell me about workflows
-
-**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]

bmad-core/tasks/nfr-assess.md

@@ -1,315 +0,0 @@
-# nfr-assess
-
-Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
-
-## Inputs
-
-```yaml
-required:
-  - story_id: "{epic}.{story}"  # e.g., "1.3"
-  - story_path: "docs/stories/{epic}.{story}.*.md"
-  
-optional:
-  - architecture_refs: "docs/architecture/*.md"
-  - technical_preferences: "docs/technical-preferences.md"
-  - acceptance_criteria: From story file
-```
-
-## Purpose
-
-Assess non-functional requirements for a story and generate:
-1. YAML block for the gate file's `nfr_validation` section
-2. Brief markdown assessment saved to `docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`
-
-## Process
-
-### 0. Fail-safe for Missing Inputs
-
-If story_path or story file can't be found:
-- Still create assessment file with note: "Source story not found"
-- Set all selected NFRs to CONCERNS with notes: "Target unknown / evidence missing"
-- Continue with assessment to provide value
-
-### 1. Elicit Scope
-
-**Interactive mode:** Ask which NFRs to assess
-**Non-interactive mode:** Default to core four (security, performance, reliability, maintainability)
-
-```text
-Which NFRs should I assess? (Enter numbers or press Enter for default)
-[1] Security (default)
-[2] Performance (default)  
-[3] Reliability (default)
-[4] Maintainability (default)
-[5] Usability
-[6] Compatibility
-[7] Portability
-[8] Functional Suitability
-
-> [Enter for 1-4]
-```
-
-### 2. Check for Thresholds
-
-Look for NFR requirements in:
-- Story acceptance criteria
-- `docs/architecture/*.md` files
-- `docs/technical-preferences.md`
-
-**Interactive mode:** Ask for missing thresholds
-**Non-interactive mode:** Mark as CONCERNS with "Target unknown"
-
-```text
-No performance requirements found. What's your target response time?
-> 200ms for API calls
-
-No security requirements found. Required auth method?
-> JWT with refresh tokens
-```
-
-**Unknown targets policy:** If a target is missing and not provided, mark status as CONCERNS with notes: "Target unknown"
-
-### 3. Quick Assessment
-
-For each selected NFR, check:
-- Is there evidence it's implemented?
-- Can we validate it?
-- Are there obvious gaps?
-
-### 4. Generate Outputs
-
-## Output 1: Gate YAML Block
-
-Generate ONLY for NFRs actually assessed (no placeholders):
-
-```yaml
-# Gate YAML (copy/paste):
-nfr_validation:
-  _assessed: [security, performance, reliability, maintainability]
-  security: 
-    status: CONCERNS
-    notes: "No rate limiting on auth endpoints"
-  performance:
-    status: PASS
-    notes: "Response times < 200ms verified"
-  reliability:
-    status: PASS
-    notes: "Error handling and retries implemented"
-  maintainability:
-    status: CONCERNS
-    notes: "Test coverage at 65%, target is 80%"
-```
-
-## Deterministic Status Rules
-
-- **FAIL**: Any selected NFR has critical gap or target clearly not met
-- **CONCERNS**: No FAILs, but any NFR is unknown/partial/missing evidence  
-- **PASS**: All selected NFRs meet targets with evidence
-
-## Quality Score Calculation
-
-```
-quality_score = 100
-- 20 for each FAIL attribute
-- 10 for each CONCERNS attribute
-Floor at 0, ceiling at 100
-```
-
-If `technical-preferences.md` defines custom weights, use those instead.
-
-## Output 2: Brief Assessment Report
-
-**ALWAYS save to:** `docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`
-
-```markdown
-# NFR Assessment: {epic}.{story}
-Date: {date}
-Reviewer: Quinn
-
-<!-- Note: Source story not found (if applicable) -->
-
-## Summary
-- Security: CONCERNS - Missing rate limiting
-- Performance: PASS - Meets <200ms requirement
-- Reliability: PASS - Proper error handling
-- Maintainability: CONCERNS - Test coverage below target
-
-## Critical Issues
-1. **No rate limiting** (Security)
-   - Risk: Brute force attacks possible
-   - Fix: Add rate limiting middleware to auth endpoints
-
-2. **Test coverage 65%** (Maintainability)
-   - Risk: Untested code paths
-   - Fix: Add tests for uncovered branches
-
-## Quick Wins
-- Add rate limiting: ~2 hours
-- Increase test coverage: ~4 hours
-- Add performance monitoring: ~1 hour
-```
-
-## Output 3: Story Update Line
-
-**End with this line for the review task to quote:**
-```
-NFR assessment: docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
-```
-
-## Output 4: Gate Integration Line
-
-**Always print at the end:**
-```
-Gate NFR block ready → paste into docs/qa/gates/{epic}.{story}-{slug}.yml under nfr_validation
-```
-
-## Assessment Criteria
-
-### Security
-**PASS if:**
-- Authentication implemented
-- Authorization enforced
-- Input validation present
-- No hardcoded secrets
-
-**CONCERNS if:**
-- Missing rate limiting
-- Weak encryption
-- Incomplete authorization
-
-**FAIL if:**
-- No authentication
-- Hardcoded credentials
-- SQL injection vulnerabilities
-
-### Performance
-**PASS if:**
-- Meets response time targets
-- No obvious bottlenecks
-- Reasonable resource usage
-
-**CONCERNS if:**
-- Close to limits
-- Missing indexes
-- No caching strategy
-
-**FAIL if:**
-- Exceeds response time limits
-- Memory leaks
-- Unoptimized queries
-
-### Reliability
-**PASS if:**
-- Error handling present
-- Graceful degradation
-- Retry logic where needed
-
-**CONCERNS if:**
-- Some error cases unhandled
-- No circuit breakers
-- Missing health checks
-
-**FAIL if:**
-- No error handling
-- Crashes on errors
-- No recovery mechanisms
-
-### Maintainability
-**PASS if:**
-- Test coverage meets target
-- Code well-structured
-- Documentation present
-
-**CONCERNS if:**
-- Test coverage below target
-- Some code duplication
-- Missing documentation
-
-**FAIL if:**
-- No tests
-- Highly coupled code
-- No documentation
-
-## Quick Reference
-
-### What to Check
-
-```yaml
-security:
-  - Authentication mechanism
-  - Authorization checks
-  - Input validation
-  - Secret management
-  - Rate limiting
-
-performance:
-  - Response times
-  - Database queries
-  - Caching usage
-  - Resource consumption
-
-reliability:
-  - Error handling
-  - Retry logic
-  - Circuit breakers
-  - Health checks
-  - Logging
-
-maintainability:
-  - Test coverage
-  - Code structure
-  - Documentation
-  - Dependencies
-```
-
-## Key Principles
-
-- Focus on the core four NFRs by default
-- Quick assessment, not deep analysis
-- Gate-ready output format
-- Brief, actionable findings
-- Skip what doesn't apply
-- Deterministic status rules for consistency
-- Unknown targets → CONCERNS, not guesses
-
----
-
-## Appendix: ISO 25010 Reference
-
-<details>
-<summary>Full ISO 25010 Quality Model (click to expand)</summary>
-
-### All 8 Quality Characteristics
-
-1. **Functional Suitability**: Completeness, correctness, appropriateness
-2. **Performance Efficiency**: Time behavior, resource use, capacity
-3. **Compatibility**: Co-existence, interoperability  
-4. **Usability**: Learnability, operability, accessibility
-5. **Reliability**: Maturity, availability, fault tolerance
-6. **Security**: Confidentiality, integrity, authenticity
-7. **Maintainability**: Modularity, reusability, testability
-8. **Portability**: Adaptability, installability
-
-Use these when assessing beyond the core four.
-</details>
-
-<details>
-<summary>Example: Deep Performance Analysis (click to expand)</summary>
-
-```yaml
-performance_deep_dive:
-  response_times:
-    p50: 45ms
-    p95: 180ms
-    p99: 350ms
-  database:
-    slow_queries: 2
-    missing_indexes: ["users.email", "orders.user_id"]
-  caching:
-    hit_rate: 0%
-    recommendation: "Add Redis for session data"
-  load_test:
-    max_rps: 150
-    breaking_point: 200 rps
-```
-</details>

bmad-core/tasks/qa-gate.md

@@ -1,159 +0,0 @@
-# qa-gate
-
-Create or update a quality gate decision file for a story based on review findings.
-
-## Purpose
-
-Generate a standalone quality gate file that provides a clear pass/fail decision with actionable feedback. This gate serves as an advisory checkpoint for teams to understand quality status.
-
-## Prerequisites
-
-- Story has been reviewed (manually or via review-story task)
-- Review findings are available
-- Understanding of story requirements and implementation
-
-## Gate File Location
-
-**ALWAYS** create file at: `docs/qa/gates/{epic}.{story}-{slug}.yml`
-
-Slug rules:
-
-- Convert to lowercase
-- Replace spaces with hyphens
-- Strip punctuation
-- Example: "User Auth - Login!" becomes "user-auth-login"
-
-## Minimal Required Schema
-
-```yaml
-schema: 1
-story: "{epic}.{story}"
-gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: "1-2 sentence explanation of gate decision"
-reviewer: "Quinn"
-updated: "{ISO-8601 timestamp}"
-top_issues: [] # Empty array if no issues
-waiver: { active: false } # Only set active: true if WAIVED
-```
-
-## Schema with Issues
-
-```yaml
-schema: 1
-story: "1.3"
-gate: CONCERNS
-status_reason: "Missing rate limiting on auth endpoints poses security risk."
-reviewer: "Quinn"
-updated: "2025-01-12T10:15:00Z"
-top_issues:
-  - id: "SEC-001"
-    severity: high # ONLY: low|medium|high
-    finding: "No rate limiting on login endpoint"
-    suggested_action: "Add rate limiting middleware before production"
-  - id: "TEST-001"
-    severity: medium
-    finding: "No integration tests for auth flow"
-    suggested_action: "Add integration test coverage"
-waiver: { active: false }
-```
-
-## Schema when Waived
-
-```yaml
-schema: 1
-story: "1.3"
-gate: WAIVED
-status_reason: "Known issues accepted for MVP release."
-reviewer: "Quinn"
-updated: "2025-01-12T10:15:00Z"
-top_issues:
-  - id: "PERF-001"
-    severity: low
-    finding: "Dashboard loads slowly with 1000+ items"
-    suggested_action: "Implement pagination in next sprint"
-waiver:
-  active: true
-  reason: "MVP release - performance optimization deferred"
-  approved_by: "Product Owner"
-```
-
-## Gate Decision Criteria
-
-### PASS
-
-- All acceptance criteria met
-- No high-severity issues
-- Test coverage meets project standards
-
-### CONCERNS
-
-- Non-blocking issues present
-- Should be tracked and scheduled
-- Can proceed with awareness
-
-### FAIL
-
-- Acceptance criteria not met
-- High-severity issues present
-- Recommend return to InProgress
-
-### WAIVED
-
-- Issues explicitly accepted
-- Requires approval and reason
-- Proceed despite known issues
-
-## Severity Scale
-
-**FIXED VALUES - NO VARIATIONS:**
-
-- `low`: Minor issues, cosmetic problems
-- `medium`: Should fix soon, not blocking
-- `high`: Critical issues, should block release
-
-## Issue ID Prefixes
-
-- `SEC-`: Security issues
-- `PERF-`: Performance issues
-- `REL-`: Reliability issues
-- `TEST-`: Testing gaps
-- `MNT-`: Maintainability concerns
-- `ARCH-`: Architecture issues
-- `DOC-`: Documentation gaps
-- `REQ-`: Requirements issues
-
-## Output Requirements
-
-1. **ALWAYS** create gate file at: `docs/qa/gates/{epic}.{story}-{slug}.yml`
-2. **ALWAYS** append this exact format to story's QA Results section:
-   ```
-   Gate: {STATUS} → docs/qa/gates/{epic}.{story}-{slug}.yml
-   ```
-3. Keep status_reason to 1-2 sentences maximum
-4. Use severity values exactly: `low`, `medium`, or `high`
-
-## Example Story Update
-
-After creating gate file, append to story's QA Results section:
-
-```markdown
-## QA Results
-
-### Review Date: 2025-01-12
-
-### Reviewed By: Quinn (Test Architect)
-
-[... existing review content ...]
-
-### Gate Status
-
-Gate: CONCERNS → docs/qa/gates/1.3-user-auth-login.yml
-```
-
-## Key Principles
-
-- Keep it minimal and predictable
-- Fixed severity scale (low/medium/high)
-- Always write to standard path
-- Always update story with gate reference
-- Clear, actionable findings

bmad-core/tasks/review-story.md

@@ -1,314 +0,0 @@
-# review-story
-
-Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
-
-## Inputs
-
-```yaml
-required:
-  - story_id: "{epic}.{story}" # e.g., "1.3"
-  - story_path: "{devStoryLocation}/{epic}.{story}.*.md" # Path from core-config.yaml
-  - story_title: "{title}" # If missing, derive from story file H1
-  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
-```
-
-## Prerequisites
-
-- Story status must be "Review"
-- Developer has completed all tasks and updated the File List
-- All automated tests are passing
-
-## Review Process - Adaptive Test Architecture
-
-### 1. Risk Assessment (Determines Review Depth)
-
-**Auto-escalate to deep review when:**
-
-- Auth/payment/security files touched
-- No tests added to story
-- Diff > 500 lines
-- Previous gate was FAIL/CONCERNS
-- Story has > 5 acceptance criteria
-
-### 2. Comprehensive Analysis
-
-**A. Requirements Traceability**
-
-- Map each acceptance criteria to its validating tests (document mapping with Given-When-Then, not test code)
-- Identify coverage gaps
-- Verify all requirements have corresponding test cases
-
-**B. Code Quality Review**
-
-- Architecture and design patterns
-- Refactoring opportunities (and perform them)
-- Code duplication or inefficiencies
-- Performance optimizations
-- Security vulnerabilities
-- Best practices adherence
-
-**C. Test Architecture Assessment**
-
-- Test coverage adequacy at appropriate levels
-- Test level appropriateness (what should be unit vs integration vs e2e)
-- Test design quality and maintainability
-- Test data management strategy
-- Mock/stub usage appropriateness
-- Edge case and error scenario coverage
-- Test execution time and reliability
-
-**D. Non-Functional Requirements (NFRs)**
-
-- Security: Authentication, authorization, data protection
-- Performance: Response times, resource usage
-- Reliability: Error handling, recovery mechanisms
-- Maintainability: Code clarity, documentation
-
-**E. Testability Evaluation**
-
-- Controllability: Can we control the inputs?
-- Observability: Can we observe the outputs?
-- Debuggability: Can we debug failures easily?
-
-**F. Technical Debt Identification**
-
-- Accumulated shortcuts
-- Missing tests
-- Outdated dependencies
-- Architecture violations
-
-### 3. Active Refactoring
-
-- Refactor code where safe and appropriate
-- Run tests to ensure changes don't break functionality
-- Document all changes in QA Results section with clear WHY and HOW
-- Do NOT alter story content beyond QA Results section
-- Do NOT change story Status or File List; recommend next status only
-
-### 4. Standards Compliance Check
-
-- Verify adherence to `docs/coding-standards.md`
-- Check compliance with `docs/unified-project-structure.md`
-- Validate testing approach against `docs/testing-strategy.md`
-- Ensure all guidelines mentioned in the story are followed
-
-### 5. Acceptance Criteria Validation
-
-- Verify each AC is fully implemented
-- Check for any missing functionality
-- Validate edge cases are handled
-
-### 6. Documentation and Comments
-
-- Verify code is self-documenting where possible
-- Add comments for complex logic if missing
-- Ensure any API changes are documented
-
-## Output 1: Update Story File - QA Results Section ONLY
-
-**CRITICAL**: You are ONLY authorized to update the "QA Results" section of the story file. DO NOT modify any other sections.
-
-**QA Results Anchor Rule:**
-
-- If `## QA Results` doesn't exist, append it at end of file
-- If it exists, append a new dated entry below existing entries
-- Never edit other sections
-
-After review and any refactoring, append your results to the story file in the QA Results section:
-
-```markdown
-## QA Results
-
-### Review Date: [Date]
-
-### Reviewed By: Quinn (Test Architect)
-
-### Code Quality Assessment
-
-[Overall assessment of implementation quality]
-
-### Refactoring Performed
-
-[List any refactoring you performed with explanations]
-
-- **File**: [filename]
-  - **Change**: [what was changed]
-  - **Why**: [reason for change]
-  - **How**: [how it improves the code]
-
-### Compliance Check
-
-- Coding Standards: [✓/✗] [notes if any]
-- Project Structure: [✓/✗] [notes if any]
-- Testing Strategy: [✓/✗] [notes if any]
-- All ACs Met: [✓/✗] [notes if any]
-
-### Improvements Checklist
-
-[Check off items you handled yourself, leave unchecked for dev to address]
-
-- [x] Refactored user service for better error handling (services/user.service.ts)
-- [x] Added missing edge case tests (services/user.service.test.ts)
-- [ ] Consider extracting validation logic to separate validator class
-- [ ] Add integration test for error scenarios
-- [ ] Update API documentation for new error codes
-
-### Security Review
-
-[Any security concerns found and whether addressed]
-
-### Performance Considerations
-
-[Any performance issues found and whether addressed]
-
-### Files Modified During Review
-
-[If you modified files, list them here - ask Dev to update File List]
-
-### Gate Status
-
-Gate: {STATUS} → docs/qa/gates/{epic}.{story}-{slug}.yml
-Risk profile: docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
-NFR assessment: docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
-
-# Note: Paths should reference core-config.yaml for custom configurations
-
-### Recommended Status
-
-[✓ Ready for Done] / [✗ Changes Required - See unchecked items above]
-(Story owner decides final status)
-```
-
-## Output 2: Create Quality Gate File
-
-**Template and Directory:**
-
-- Render from `templates/qa-gate-tmpl.yaml`
-- Create `docs/qa/gates/` directory if missing (or configure in core-config.yaml)
-- Save to: `docs/qa/gates/{epic}.{story}-{slug}.yml`
-
-Gate file structure:
-
-```yaml
-schema: 1
-story: "{epic}.{story}"
-story_title: "{story title}"
-gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: "1-2 sentence explanation of gate decision"
-reviewer: "Quinn (Test Architect)"
-updated: "{ISO-8601 timestamp}"
-
-top_issues: [] # Empty if no issues
-waiver: { active: false } # Set active: true only if WAIVED
-
-# Extended fields (optional but recommended):
-quality_score: 0-100 # 100 - (20*FAILs) - (10*CONCERNS) or use technical-preferences.md weights
-expires: "{ISO-8601 timestamp}" # Typically 2 weeks from review
-
-evidence:
-  tests_reviewed: { count }
-  risks_identified: { count }
-  trace:
-    ac_covered: [1, 2, 3] # AC numbers with test coverage
-    ac_gaps: [4] # AC numbers lacking coverage
-
-nfr_validation:
-  security:
-    status: PASS|CONCERNS|FAIL
-    notes: "Specific findings"
-  performance:
-    status: PASS|CONCERNS|FAIL
-    notes: "Specific findings"
-  reliability:
-    status: PASS|CONCERNS|FAIL
-    notes: "Specific findings"
-  maintainability:
-    status: PASS|CONCERNS|FAIL
-    notes: "Specific findings"
-
-recommendations:
-  immediate: # Must fix before production
-    - action: "Add rate limiting"
-      refs: ["api/auth/login.ts"]
-  future: # Can be addressed later
-    - action: "Consider caching"
-      refs: ["services/data.ts"]
-```
-
-### Gate Decision Criteria
-
-**Deterministic rule (apply in order):**
-
-If risk_summary exists, apply its thresholds first (≥9 → FAIL, ≥6 → CONCERNS), then NFR statuses, then top_issues severity.
-
-1. **Risk thresholds (if risk_summary present):**
-   - If any risk score ≥ 9 → Gate = FAIL (unless waived)
-   - Else if any score ≥ 6 → Gate = CONCERNS
-
-2. **Test coverage gaps (if trace available):**
-   - If any P0 test from test-design is missing → Gate = CONCERNS
-   - If security/data-loss P0 test missing → Gate = FAIL
-
-3. **Issue severity:**
-   - If any `top_issues.severity == high` → Gate = FAIL (unless waived)
-   - Else if any `severity == medium` → Gate = CONCERNS
-
-4. **NFR statuses:**
-   - If any NFR status is FAIL → Gate = FAIL
-   - Else if any NFR status is CONCERNS → Gate = CONCERNS
-   - Else → Gate = PASS
-
-- WAIVED only when waiver.active: true with reason/approver
-
-Detailed criteria:
-
-- **PASS**: All critical requirements met, no blocking issues
-- **CONCERNS**: Non-critical issues found, team should review
-- **FAIL**: Critical issues that should be addressed
-- **WAIVED**: Issues acknowledged but explicitly waived by team
-
-### Quality Score Calculation
-
-```text
-quality_score = 100 - (20 × number of FAILs) - (10 × number of CONCERNS)
-Bounded between 0 and 100
-```
-
-If `technical-preferences.md` defines custom weights, use those instead.
-
-### Suggested Owner Convention
-
-For each issue in `top_issues`, include a `suggested_owner`:
-
-- `dev`: Code changes needed
-- `sm`: Requirements clarification needed
-- `po`: Business decision needed
-
-## Key Principles
-
-- You are a Test Architect providing comprehensive quality assessment
-- You have the authority to improve code directly when appropriate
-- Always explain your changes for learning purposes
-- Balance between perfection and pragmatism
-- Focus on risk-based prioritization
-- Provide actionable recommendations with clear ownership
-
-## Blocking Conditions
-
-Stop the review and request clarification if:
-
-- Story file is incomplete or missing critical sections
-- File List is empty or clearly incomplete
-- No tests exist when they were required
-- Code changes don't align with story requirements
-- Critical architectural issues that require discussion
-
-## Completion
-
-After review:
-
-1. Update the QA Results section in the story file
-2. Create the gate file in `docs/qa/gates/`
-3. Recommend status: "Ready for Done" or "Changes Required" (owner decides)
-4. If files were modified, list them in QA Results and ask Dev to update File List
-5. Always provide constructive feedback and actionable recommendations

bmad-core/tasks/risk-profile.md

@@ -1,353 +0,0 @@
-# risk-profile
-
-Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
-
-## Inputs
-
-```yaml
-required:
-  - story_id: "{epic}.{story}" # e.g., "1.3"
-  - story_path: "docs/stories/{epic}.{story}.*.md"
-  - story_title: "{title}" # If missing, derive from story file H1
-  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
-```
-
-## Purpose
-
-Identify, assess, and prioritize risks in the story implementation. Provide risk mitigation strategies and testing focus areas based on risk levels.
-
-## Risk Assessment Framework
-
-### Risk Categories
-
-**Category Prefixes:**
-
-- `TECH`: Technical Risks
-- `SEC`: Security Risks
-- `PERF`: Performance Risks
-- `DATA`: Data Risks
-- `BUS`: Business Risks
-- `OPS`: Operational Risks
-
-1. **Technical Risks (TECH)**
-   - Architecture complexity
-   - Integration challenges
-   - Technical debt
-   - Scalability concerns
-   - System dependencies
-
-2. **Security Risks (SEC)**
-   - Authentication/authorization flaws
-   - Data exposure vulnerabilities
-   - Injection attacks
-   - Session management issues
-   - Cryptographic weaknesses
-
-3. **Performance Risks (PERF)**
-   - Response time degradation
-   - Throughput bottlenecks
-   - Resource exhaustion
-   - Database query optimization
-   - Caching failures
-
-4. **Data Risks (DATA)**
-   - Data loss potential
-   - Data corruption
-   - Privacy violations
-   - Compliance issues
-   - Backup/recovery gaps
-
-5. **Business Risks (BUS)**
-   - Feature doesn't meet user needs
-   - Revenue impact
-   - Reputation damage
-   - Regulatory non-compliance
-   - Market timing
-
-6. **Operational Risks (OPS)**
-   - Deployment failures
-   - Monitoring gaps
-   - Incident response readiness
-   - Documentation inadequacy
-   - Knowledge transfer issues
-
-## Risk Analysis Process
-
-### 1. Risk Identification
-
-For each category, identify specific risks:
-
-```yaml
-risk:
-  id: "SEC-001" # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
-  category: security
-  title: "Insufficient input validation on user forms"
-  description: "Form inputs not properly sanitized could lead to XSS attacks"
-  affected_components:
-    - "UserRegistrationForm"
-    - "ProfileUpdateForm"
-  detection_method: "Code review revealed missing validation"
-```
-
-### 2. Risk Assessment
-
-Evaluate each risk using probability × impact:
-
-**Probability Levels:**
-
-- `High (3)`: Likely to occur (>70% chance)
-- `Medium (2)`: Possible occurrence (30-70% chance)
-- `Low (1)`: Unlikely to occur (<30% chance)
-
-**Impact Levels:**
-
-- `High (3)`: Severe consequences (data breach, system down, major financial loss)
-- `Medium (2)`: Moderate consequences (degraded performance, minor data issues)
-- `Low (1)`: Minor consequences (cosmetic issues, slight inconvenience)
-
-**Risk Score = Probability × Impact**
-
-- 9: Critical Risk (Red)
-- 6: High Risk (Orange)
-- 4: Medium Risk (Yellow)
-- 2-3: Low Risk (Green)
-- 1: Minimal Risk (Blue)
-
-### 3. Risk Prioritization
-
-Create risk matrix:
-
-```markdown
-## Risk Matrix
-
-| Risk ID  | Description             | Probability | Impact     | Score | Priority |
-| -------- | ----------------------- | ----------- | ---------- | ----- | -------- |
-| SEC-001  | XSS vulnerability       | High (3)    | High (3)   | 9     | Critical |
-| PERF-001 | Slow query on dashboard | Medium (2)  | Medium (2) | 4     | Medium   |
-| DATA-001 | Backup failure          | Low (1)     | High (3)   | 3     | Low      |
-```
-
-### 4. Risk Mitigation Strategies
-
-For each identified risk, provide mitigation:
-
-```yaml
-mitigation:
-  risk_id: "SEC-001"
-  strategy: "preventive" # preventive|detective|corrective
-  actions:
-    - "Implement input validation library (e.g., validator.js)"
-    - "Add CSP headers to prevent XSS execution"
-    - "Sanitize all user inputs before storage"
-    - "Escape all outputs in templates"
-  testing_requirements:
-    - "Security testing with OWASP ZAP"
-    - "Manual penetration testing of forms"
-    - "Unit tests for validation functions"
-  residual_risk: "Low - Some zero-day vulnerabilities may remain"
-  owner: "dev"
-  timeline: "Before deployment"
-```
-
-## Outputs
-
-### Output 1: Gate YAML Block
-
-Generate for pasting into gate file under `risk_summary`:
-
-**Output rules:**
-
-- Only include assessed risks; do not emit placeholders
-- Sort risks by score (desc) when emitting highest and any tabular lists
-- If no risks: totals all zeros, omit highest, keep recommendations arrays empty
-
-```yaml
-# risk_summary (paste into gate file):
-risk_summary:
-  totals:
-    critical: X # score 9
-    high: Y # score 6
-    medium: Z # score 4
-    low: W # score 2-3
-  highest:
-    id: SEC-001
-    score: 9
-    title: "XSS on profile form"
-  recommendations:
-    must_fix:
-      - "Add input sanitization & CSP"
-    monitor:
-      - "Add security alerts for auth endpoints"
-```
-
-### Output 2: Markdown Report
-
-**Save to:** `docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`
-
-```markdown
-# Risk Profile: Story {epic}.{story}
-
-Date: {date}
-Reviewer: Quinn (Test Architect)
-
-## Executive Summary
-
-- Total Risks Identified: X
-- Critical Risks: Y
-- High Risks: Z
-- Risk Score: XX/100 (calculated)
-
-## Critical Risks Requiring Immediate Attention
-
-### 1. [ID]: Risk Title
-
-**Score: 9 (Critical)**
-**Probability**: High - Detailed reasoning
-**Impact**: High - Potential consequences
-**Mitigation**:
-
-- Immediate action required
-- Specific steps to take
-  **Testing Focus**: Specific test scenarios needed
-
-## Risk Distribution
-
-### By Category
-
-- Security: X risks (Y critical)
-- Performance: X risks (Y critical)
-- Data: X risks (Y critical)
-- Business: X risks (Y critical)
-- Operational: X risks (Y critical)
-
-### By Component
-
-- Frontend: X risks
-- Backend: X risks
-- Database: X risks
-- Infrastructure: X risks
-
-## Detailed Risk Register
-
-[Full table of all risks with scores and mitigations]
-
-## Risk-Based Testing Strategy
-
-### Priority 1: Critical Risk Tests
-
-- Test scenarios for critical risks
-- Required test types (security, load, chaos)
-- Test data requirements
-
-### Priority 2: High Risk Tests
-
-- Integration test scenarios
-- Edge case coverage
-
-### Priority 3: Medium/Low Risk Tests
-
-- Standard functional tests
-- Regression test suite
-
-## Risk Acceptance Criteria
-
-### Must Fix Before Production
-
-- All critical risks (score 9)
-- High risks affecting security/data
-
-### Can Deploy with Mitigation
-
-- Medium risks with compensating controls
-- Low risks with monitoring in place
-
-### Accepted Risks
-
-- Document any risks team accepts
-- Include sign-off from appropriate authority
-
-## Monitoring Requirements
-
-Post-deployment monitoring for:
-
-- Performance metrics for PERF risks
-- Security alerts for SEC risks
-- Error rates for operational risks
-- Business KPIs for business risks
-
-## Risk Review Triggers
-
-Review and update risk profile when:
-
-- Architecture changes significantly
-- New integrations added
-- Security vulnerabilities discovered
-- Performance issues reported
-- Regulatory requirements change
-```
-
-## Risk Scoring Algorithm
-
-Calculate overall story risk score:
-
-```
-Base Score = 100
-For each risk:
-  - Critical (9): Deduct 20 points
-  - High (6): Deduct 10 points
-  - Medium (4): Deduct 5 points
-  - Low (2-3): Deduct 2 points
-
-Minimum score = 0 (extremely risky)
-Maximum score = 100 (minimal risk)
-```
-
-## Risk-Based Recommendations
-
-Based on risk profile, recommend:
-
-1. **Testing Priority**
-   - Which tests to run first
-   - Additional test types needed
-   - Test environment requirements
-
-2. **Development Focus**
-   - Code review emphasis areas
-   - Additional validation needed
-   - Security controls to implement
-
-3. **Deployment Strategy**
-   - Phased rollout for high-risk changes
-   - Feature flags for risky features
-   - Rollback procedures
-
-4. **Monitoring Setup**
-   - Metrics to track
-   - Alerts to configure
-   - Dashboard requirements
-
-## Integration with Quality Gates
-
-**Deterministic gate mapping:**
-
-- Any risk with score ≥ 9 → Gate = FAIL (unless waived)
-- Else if any score ≥ 6 → Gate = CONCERNS
-- Else → Gate = PASS
-- Unmitigated risks → Document in gate
-
-### Output 3: Story Hook Line
-
-**Print this line for review task to quote:**
-
-```
-Risk profile: docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
-```
-
-## Key Principles
-
-- Identify risks early and systematically
-- Use consistent probability × impact scoring
-- Provide actionable mitigation strategies
-- Link risks to specific test requirements
-- Track residual risk after mitigation
-- Update risk profile as story evolves

bmad-core/tasks/shard-doc.md

@@ -1,185 +0,0 @@
-# Document Sharding Task
-
-## Purpose
-
-- Split a large document into multiple smaller documents based on level 2 sections
-- Create a folder structure to organize the sharded documents
-- Maintain all content integrity including code blocks, diagrams, and markdown formatting
-
-## Primary Method: Automatic with markdown-tree
-
-[[LLM: First, check if markdownExploder is set to true in {root}/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
-
-If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
-
-If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
-
-1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in {root}/core-config.yaml
-
-**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
-
-If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
-
-1. Set markdownExploder to true in {root}/core-config.yaml
-2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-
-I will now proceed with the manual sharding process."
-
-Then proceed with the manual method below ONLY if markdownExploder is false.]]
-
-### Installation and Usage
-
-1. **Install globally**:
-
-   ```bash
-   npm install -g @kayvan/markdown-tree-parser
-   ```
-
-2. **Use the explode command**:
-
-   ```bash
-   # For PRD
-   md-tree explode docs/prd.md docs/prd
-
-   # For Architecture
-   md-tree explode docs/architecture.md docs/architecture
-
-   # For any document
-   md-tree explode [source-document] [destination-folder]
-   ```
-
-3. **What it does**:
-   - Automatically splits the document by level 2 sections
-   - Creates properly named files
-   - Adjusts heading levels appropriately
-   - Handles all edge cases with code blocks and special markdown
-
-If the user has @kayvan/markdown-tree-parser installed, use it and skip the manual process below.
-
----
-
-## Manual Method (if @kayvan/markdown-tree-parser is not available or user indicated manual method)
-
-### Task Instructions
-
-1. Identify Document and Target Location
-
-- Determine which document to shard (user-provided path)
-- Create a new folder under `docs/` with the same name as the document (without extension)
-- Example: `docs/prd.md` → create folder `docs/prd/`
-
-2. Parse and Extract Sections
-
-CRITICAL AEGNT SHARDING RULES:
-
-1. Read the entire document content
-2. Identify all level 2 sections (## headings)
-3. For each level 2 section:
-   - Extract the section heading and ALL content until the next level 2 section
-   - Include all subsections, code blocks, diagrams, lists, tables, etc.
-   - Be extremely careful with:
-     - Fenced code blocks (```) - ensure you capture the full block including closing backticks and account for potential misleading level 2's that are actually part of a fenced section example
-     - Mermaid diagrams - preserve the complete diagram syntax
-     - Nested markdown elements
-     - Multi-line content that might contain ## inside code blocks
-
-CRITICAL: Use proper parsing that understands markdown context. A ## inside a code block is NOT a section header.]]
-
-### 3. Create Individual Files
-
-For each extracted section:
-
-1. **Generate filename**: Convert the section heading to lowercase-dash-case
-   - Remove special characters
-   - Replace spaces with dashes
-   - Example: "## Tech Stack" → `tech-stack.md`
-
-2. **Adjust heading levels**:
-   - The level 2 heading becomes level 1 (# instead of ##) in the sharded new document
-   - All subsection levels decrease by 1:
-
-   ```txt
-     - ### → ##
-     - #### → ###
-     - ##### → ####
-     - etc.
-   ```
-
-3. **Write content**: Save the adjusted content to the new file
-
-### 4. Create Index File
-
-Create an `index.md` file in the sharded folder that:
-
-1. Contains the original level 1 heading and any content before the first level 2 section
-2. Lists all the sharded files with links:
-
-```markdown
-# Original Document Title
-
-[Original introduction content if any]
-
-## Sections
-
-- [Section Name 1](./section-name-1.md)
-- [Section Name 2](./section-name-2.md)
-- [Section Name 3](./section-name-3.md)
-  ...
-```
-
-### 5. Preserve Special Content
-
-1. **Code blocks**: Must capture complete blocks including:
-
-   ```language
-   content
-   ```
-
-2. **Mermaid diagrams**: Preserve complete syntax:
-
-   ```mermaid
-   graph TD
-   ...
-   ```
-
-3. **Tables**: Maintain proper markdown table formatting
-
-4. **Lists**: Preserve indentation and nesting
-
-5. **Inline code**: Preserve backticks
-
-6. **Links and references**: Keep all markdown links intact
-
-7. **Template markup**: If documents contain {{placeholders}} ,preserve exactly
-
-### 6. Validation
-
-After sharding:
-
-1. Verify all sections were extracted
-2. Check that no content was lost
-3. Ensure heading levels were properly adjusted
-4. Confirm all files were created successfully
-
-### 7. Report Results
-
-Provide a summary:
-
-```text
-Document sharded successfully:
-- Source: [original document path]
-- Destination: docs/[folder-name]/
-- Files created: [count]
-- Sections:
-  - section-name-1.md: "Section Title 1"
-  - section-name-2.md: "Section Title 2"
-  ...
-```
-
-## Important Notes
-
-- Never modify the actual content, only adjust heading levels
-- Preserve ALL formatting, including whitespace where significant
-- Handle edge cases like sections with code blocks containing ## symbols
-- Ensure the sharding is reversible (could reconstruct the original from shards)

bmad-core/tasks/test-design.md

@@ -1,174 +0,0 @@
-# test-design
-
-Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
-
-## Inputs
-
-```yaml
-required:
-  - story_id: "{epic}.{story}" # e.g., "1.3"
-  - story_path: "{devStoryLocation}/{epic}.{story}.*.md" # Path from core-config.yaml
-  - story_title: "{title}" # If missing, derive from story file H1
-  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
-```
-
-## Purpose
-
-Design a complete test strategy that identifies what to test, at which level (unit/integration/e2e), and why. This ensures efficient test coverage without redundancy while maintaining appropriate test boundaries.
-
-## Dependencies
-
-```yaml
-data:
-  - test-levels-framework.md # Unit/Integration/E2E decision criteria
-  - test-priorities-matrix.md # P0/P1/P2/P3 classification system
-```
-
-## Process
-
-### 1. Analyze Story Requirements
-
-Break down each acceptance criterion into testable scenarios. For each AC:
-
-- Identify the core functionality to test
-- Determine data variations needed
-- Consider error conditions
-- Note edge cases
-
-### 2. Apply Test Level Framework
-
-**Reference:** Load `test-levels-framework.md` for detailed criteria
-
-Quick rules:
-
-- **Unit**: Pure logic, algorithms, calculations
-- **Integration**: Component interactions, DB operations
-- **E2E**: Critical user journeys, compliance
-
-### 3. Assign Priorities
-
-**Reference:** Load `test-priorities-matrix.md` for classification
-
-Quick priority assignment:
-
-- **P0**: Revenue-critical, security, compliance
-- **P1**: Core user journeys, frequently used
-- **P2**: Secondary features, admin functions
-- **P3**: Nice-to-have, rarely used
-
-### 4. Design Test Scenarios
-
-For each identified test need, create:
-
-```yaml
-test_scenario:
-  id: "{epic}.{story}-{LEVEL}-{SEQ}"
-  requirement: "AC reference"
-  priority: P0|P1|P2|P3
-  level: unit|integration|e2e
-  description: "What is being tested"
-  justification: "Why this level was chosen"
-  mitigates_risks: ["RISK-001"] # If risk profile exists
-```
-
-### 5. Validate Coverage
-
-Ensure:
-
-- Every AC has at least one test
-- No duplicate coverage across levels
-- Critical paths have multiple levels
-- Risk mitigations are addressed
-
-## Outputs
-
-### Output 1: Test Design Document
-
-**Save to:** `docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md`
-
-```markdown
-# Test Design: Story {epic}.{story}
-
-Date: {date}
-Designer: Quinn (Test Architect)
-
-## Test Strategy Overview
-
-- Total test scenarios: X
-- Unit tests: Y (A%)
-- Integration tests: Z (B%)
-- E2E tests: W (C%)
-- Priority distribution: P0: X, P1: Y, P2: Z
-
-## Test Scenarios by Acceptance Criteria
-
-### AC1: {description}
-
-#### Scenarios
-
-| ID           | Level       | Priority | Test                      | Justification            |
-| ------------ | ----------- | -------- | ------------------------- | ------------------------ |
-| 1.3-UNIT-001 | Unit        | P0       | Validate input format     | Pure validation logic    |
-| 1.3-INT-001  | Integration | P0       | Service processes request | Multi-component flow     |
-| 1.3-E2E-001  | E2E         | P1       | User completes journey    | Critical path validation |
-
-[Continue for all ACs...]
-
-## Risk Coverage
-
-[Map test scenarios to identified risks if risk profile exists]
-
-## Recommended Execution Order
-
-1. P0 Unit tests (fail fast)
-2. P0 Integration tests
-3. P0 E2E tests
-4. P1 tests in order
-5. P2+ as time permits
-```
-
-### Output 2: Gate YAML Block
-
-Generate for inclusion in quality gate:
-
-```yaml
-test_design:
-  scenarios_total: X
-  by_level:
-    unit: Y
-    integration: Z
-    e2e: W
-  by_priority:
-    p0: A
-    p1: B
-    p2: C
-  coverage_gaps: [] # List any ACs without tests
-```
-
-### Output 3: Trace References
-
-Print for use by trace-requirements task:
-
-```text
-Test design matrix: docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md
-P0 tests identified: {count}
-```
-
-## Quality Checklist
-
-Before finalizing, verify:
-
-- [ ] Every AC has test coverage
-- [ ] Test levels are appropriate (not over-testing)
-- [ ] No duplicate coverage across levels
-- [ ] Priorities align with business risk
-- [ ] Test IDs follow naming convention
-- [ ] Scenarios are atomic and independent
-
-## Key Principles
-
-- **Shift left**: Prefer unit over integration, integration over E2E
-- **Risk-based**: Focus on what could go wrong
-- **Efficient coverage**: Test once at the right level
-- **Maintainability**: Consider long-term test maintenance
-- **Fast feedback**: Quick tests run first

bmad-core/tasks/trace-requirements.md

@@ -1,264 +0,0 @@
-# trace-requirements
-
-Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
-
-## Purpose
-
-Create a requirements traceability matrix that ensures every acceptance criterion has corresponding test coverage. This task helps identify gaps in testing and ensures all requirements are validated.
-
-**IMPORTANT**: Given-When-Then is used here for documenting the mapping between requirements and tests, NOT for writing the actual test code. Tests should follow your project's testing standards (no BDD syntax in test code).
-
-## Prerequisites
-
-- Story file with clear acceptance criteria
-- Access to test files or test specifications
-- Understanding of the implementation
-
-## Traceability Process
-
-### 1. Extract Requirements
-
-Identify all testable requirements from:
-
-- Acceptance Criteria (primary source)
-- User story statement
-- Tasks/subtasks with specific behaviors
-- Non-functional requirements mentioned
-- Edge cases documented
-
-### 2. Map to Test Cases
-
-For each requirement, document which tests validate it. Use Given-When-Then to describe what the test validates (not how it's written):
-
-```yaml
-requirement: "AC1: User can login with valid credentials"
-test_mappings:
-  - test_file: "auth/login.test.ts"
-    test_case: "should successfully login with valid email and password"
-    # Given-When-Then describes WHAT the test validates, not HOW it's coded
-    given: "A registered user with valid credentials"
-    when: "They submit the login form"
-    then: "They are redirected to dashboard and session is created"
-    coverage: full
-
-  - test_file: "e2e/auth-flow.test.ts"
-    test_case: "complete login flow"
-    given: "User on login page"
-    when: "Entering valid credentials and submitting"
-    then: "Dashboard loads with user data"
-    coverage: integration
-```
-
-### 3. Coverage Analysis
-
-Evaluate coverage for each requirement:
-
-**Coverage Levels:**
-
-- `full`: Requirement completely tested
-- `partial`: Some aspects tested, gaps exist
-- `none`: No test coverage found
-- `integration`: Covered in integration/e2e tests only
-- `unit`: Covered in unit tests only
-
-### 4. Gap Identification
-
-Document any gaps found:
-
-```yaml
-coverage_gaps:
-  - requirement: "AC3: Password reset email sent within 60 seconds"
-    gap: "No test for email delivery timing"
-    severity: medium
-    suggested_test:
-      type: integration
-      description: "Test email service SLA compliance"
-
-  - requirement: "AC5: Support 1000 concurrent users"
-    gap: "No load testing implemented"
-    severity: high
-    suggested_test:
-      type: performance
-      description: "Load test with 1000 concurrent connections"
-```
-
-## Outputs
-
-### Output 1: Gate YAML Block
-
-**Generate for pasting into gate file under `trace`:**
-
-```yaml
-trace:
-  totals:
-    requirements: X
-    full: Y
-    partial: Z
-    none: W
-  planning_ref: "docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md"
-  uncovered:
-    - ac: "AC3"
-      reason: "No test found for password reset timing"
-  notes: "See docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md"
-```
-
-### Output 2: Traceability Report
-
-**Save to:** `docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`
-
-Create a traceability report with:
-
-```markdown
-# Requirements Traceability Matrix
-
-## Story: {epic}.{story} - {title}
-
-### Coverage Summary
-
-- Total Requirements: X
-- Fully Covered: Y (Z%)
-- Partially Covered: A (B%)
-- Not Covered: C (D%)
-
-### Requirement Mappings
-
-#### AC1: {Acceptance Criterion 1}
-
-**Coverage: FULL**
-
-Given-When-Then Mappings:
-
-- **Unit Test**: `auth.service.test.ts::validateCredentials`
-  - Given: Valid user credentials
-  - When: Validation method called
-  - Then: Returns true with user object
-
-- **Integration Test**: `auth.integration.test.ts::loginFlow`
-  - Given: User with valid account
-  - When: Login API called
-  - Then: JWT token returned and session created
-
-#### AC2: {Acceptance Criterion 2}
-
-**Coverage: PARTIAL**
-
-[Continue for all ACs...]
-
-### Critical Gaps
-
-1. **Performance Requirements**
-   - Gap: No load testing for concurrent users
-   - Risk: High - Could fail under production load
-   - Action: Implement load tests using k6 or similar
-
-2. **Security Requirements**
-   - Gap: Rate limiting not tested
-   - Risk: Medium - Potential DoS vulnerability
-   - Action: Add rate limit tests to integration suite
-
-### Test Design Recommendations
-
-Based on gaps identified, recommend:
-
-1. Additional test scenarios needed
-2. Test types to implement (unit/integration/e2e/performance)
-3. Test data requirements
-4. Mock/stub strategies
-
-### Risk Assessment
-
-- **High Risk**: Requirements with no coverage
-- **Medium Risk**: Requirements with only partial coverage
-- **Low Risk**: Requirements with full unit + integration coverage
-```
-
-## Traceability Best Practices
-
-### Given-When-Then for Mapping (Not Test Code)
-
-Use Given-When-Then to document what each test validates:
-
-**Given**: The initial context the test sets up
-
-- What state/data the test prepares
-- User context being simulated
-- System preconditions
-
-**When**: The action the test performs
-
-- What the test executes
-- API calls or user actions tested
-- Events triggered
-
-**Then**: What the test asserts
-
-- Expected outcomes verified
-- State changes checked
-- Values validated
-
-**Note**: This is for documentation only. Actual test code follows your project's standards (e.g., describe/it blocks, no BDD syntax).
-
-### Coverage Priority
-
-Prioritize coverage based on:
-
-1. Critical business flows
-2. Security-related requirements
-3. Data integrity requirements
-4. User-facing features
-5. Performance SLAs
-
-### Test Granularity
-
-Map at appropriate levels:
-
-- Unit tests for business logic
-- Integration tests for component interaction
-- E2E tests for user journeys
-- Performance tests for NFRs
-
-## Quality Indicators
-
-Good traceability shows:
-
-- Every AC has at least one test
-- Critical paths have multiple test levels
-- Edge cases are explicitly covered
-- NFRs have appropriate test types
-- Clear Given-When-Then for each test
-
-## Red Flags
-
-Watch for:
-
-- ACs with no test coverage
-- Tests that don't map to requirements
-- Vague test descriptions
-- Missing edge case coverage
-- NFRs without specific tests
-
-## Integration with Gates
-
-This traceability feeds into quality gates:
-
-- Critical gaps → FAIL
-- Minor gaps → CONCERNS
-- Missing P0 tests from test-design → CONCERNS
-
-### Output 3: Story Hook Line
-
-**Print this line for review task to quote:**
-
-```text
-Trace matrix: docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
-```
-
-- Full coverage → PASS contribution
-
-## Key Principles
-
-- Every requirement must be testable
-- Use Given-When-Then for clarity
-- Identify both presence and absence
-- Prioritize based on risk
-- Make recommendations actionable

bmad-core/tasks/validate-next-story.md

@@ -1,134 +0,0 @@
-# Validate Next Story Task
-
-## Purpose
-
-To comprehensively validate a story draft before implementation begins, ensuring it is complete, accurate, and provides sufficient context for successful development. This task identifies issues and gaps that need to be addressed, preventing hallucinations and ensuring implementation readiness.
-
-## SEQUENTIAL Task Execution (Do not proceed until current Task is complete)
-
-### 0. Load Core Configuration and Inputs
-
-- Load `.bmad-core/core-config.yaml`
-- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
-- Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
-- Identify and load the following inputs:
-  - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
-  - **Parent epic**: The epic containing this story's requirements
-  - **Architecture documents**: Based on configuration (sharded or monolithic)
-  - **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation
-
-### 1. Template Completeness Validation
-
-- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
-- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
-- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
-- **Agent section verification**: Confirm all sections from template exist for future agent use
-- **Structure compliance**: Verify story follows template structure and formatting
-
-### 2. File Structure and Source Tree Validation
-
-- **File paths clarity**: Are new/existing files to be created/modified clearly specified?
-- **Source tree relevance**: Is relevant project structure included in Dev Notes?
-- **Directory structure**: Are new directories/components properly located according to project structure?
-- **File creation sequence**: Do tasks specify where files should be created in logical order?
-- **Path accuracy**: Are file paths consistent with project structure from architecture docs?
-
-### 3. UI/Frontend Completeness Validation (if applicable)
-
-- **Component specifications**: Are UI components sufficiently detailed for implementation?
-- **Styling/design guidance**: Is visual implementation guidance clear?
-- **User interaction flows**: Are UX patterns and behaviors specified?
-- **Responsive/accessibility**: Are these considerations addressed if required?
-- **Integration points**: Are frontend-backend integration points clear?
-
-### 4. Acceptance Criteria Satisfaction Assessment
-
-- **AC coverage**: Will all acceptance criteria be satisfied by the listed tasks?
-- **AC testability**: Are acceptance criteria measurable and verifiable?
-- **Missing scenarios**: Are edge cases or error conditions covered?
-- **Success definition**: Is "done" clearly defined for each AC?
-- **Task-AC mapping**: Are tasks properly linked to specific acceptance criteria?
-
-### 5. Validation and Testing Instructions Review
-
-- **Test approach clarity**: Are testing methods clearly specified?
-- **Test scenarios**: Are key test cases identified?
-- **Validation steps**: Are acceptance criteria validation steps clear?
-- **Testing tools/frameworks**: Are required testing tools specified?
-- **Test data requirements**: Are test data needs identified?
-
-### 6. Security Considerations Assessment (if applicable)
-
-- **Security requirements**: Are security needs identified and addressed?
-- **Authentication/authorization**: Are access controls specified?
-- **Data protection**: Are sensitive data handling requirements clear?
-- **Vulnerability prevention**: Are common security issues addressed?
-- **Compliance requirements**: Are regulatory/compliance needs addressed?
-
-### 7. Tasks/Subtasks Sequence Validation
-
-- **Logical order**: Do tasks follow proper implementation sequence?
-- **Dependencies**: Are task dependencies clear and correct?
-- **Granularity**: Are tasks appropriately sized and actionable?
-- **Completeness**: Do tasks cover all requirements and acceptance criteria?
-- **Blocking issues**: Are there any tasks that would block others?
-
-### 8. Anti-Hallucination Verification
-
-- **Source verification**: Every technical claim must be traceable to source documents
-- **Architecture alignment**: Dev Notes content matches architecture specifications
-- **No invented details**: Flag any technical decisions not supported by source documents
-- **Reference accuracy**: Verify all source references are correct and accessible
-- **Fact checking**: Cross-reference claims against epic and architecture documents
-
-### 9. Dev Agent Implementation Readiness
-
-- **Self-contained context**: Can the story be implemented without reading external docs?
-- **Clear instructions**: Are implementation steps unambiguous?
-- **Complete technical context**: Are all required technical details present in Dev Notes?
-- **Missing information**: Identify any critical information gaps
-- **Actionability**: Are all tasks actionable by a development agent?
-
-### 10. Generate Validation Report
-
-Provide a structured validation report including:
-
-#### Template Compliance Issues
-
-- Missing sections from story template
-- Unfilled placeholders or template variables
-- Structural formatting issues
-
-#### Critical Issues (Must Fix - Story Blocked)
-
-- Missing essential information for implementation
-- Inaccurate or unverifiable technical claims
-- Incomplete acceptance criteria coverage
-- Missing required sections
-
-#### Should-Fix Issues (Important Quality Improvements)
-
-- Unclear implementation guidance
-- Missing security considerations
-- Task sequencing problems
-- Incomplete testing instructions
-
-#### Nice-to-Have Improvements (Optional Enhancements)
-
-- Additional context that would help implementation
-- Clarifications that would improve efficiency
-- Documentation improvements
-
-#### Anti-Hallucination Findings
-
-- Unverifiable technical claims
-- Missing source references
-- Inconsistencies with architecture documents
-- Invented libraries, patterns, or standards
-
-#### Final Assessment
-
-- **GO**: Story is ready for implementation
-- **NO-GO**: Story requires fixes before implementation
-- **Implementation Readiness Score**: 1-10 scale
-- **Confidence Level**: High/Medium/Low for successful implementation

bmad-core/templates/architecture-tmpl.yaml

@@ -1,650 +0,0 @@
-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.yaml

@@ -1,156 +0,0 @@
-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.yaml

@@ -1,476 +0,0 @@
-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.yaml

@@ -1,280 +0,0 @@
-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.yaml

@@ -1,293 +0,0 @@
-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.yaml

@@ -1,206 +0,0 @@
-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.yaml

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

@@ -1,805 +0,0 @@
-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.yaml

@@ -1,252 +0,0 @@
-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.yaml

@@ -1,202 +0,0 @@
-template:
-  id: prd-template-v2
-  name: Product Requirements Document
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/prd.md
-    title: "{{project_name}} Product Requirements Document (PRD)"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-
-sections:
-  - id: goals-context
-    title: Goals and Background Context
-    instruction: |
-      Ask if Project Brief document is available. If NO Project Brief exists, STRONGLY recommend creating one first using project-brief-tmpl (it provides essential foundation: problem statement, target users, success metrics, MVP scope, constraints). If user insists on PRD without brief, gather this information during Goals section. If Project Brief exists, review and use it to populate Goals (bullet list of desired outcomes) and Background Context (1-2 paragraphs on what this solves and why) so we can determine what is and is not in scope for PRD mvp. Either way this is critical to determine the requirements. Include Change Log table.
-    sections:
-      - id: goals
-        title: Goals
-        type: bullet-list
-        instruction: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires
-      - id: background
-        title: Background Context
-        type: paragraphs
-        instruction: 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
-      - id: changelog
-        title: Change Log
-        type: table
-        columns: [Date, Version, Description, Author]
-        instruction: Track document versions and changes
-
-  - id: requirements
-    title: Requirements
-    instruction: Draft the list of functional and non functional requirements under the two child sections
-    elicit: true
-    sections:
-      - id: functional
-        title: Functional
-        type: numbered-list
-        prefix: FR
-        instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR
-        examples:
-          - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently."
-      - id: non-functional
-        title: Non Functional
-        type: numbered-list
-        prefix: NFR
-        instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR
-        examples:
-          - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible."
-
-  - id: ui-goals
-    title: User Interface Design Goals
-    condition: PRD has UX/UI requirements
-    instruction: |
-      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
-    elicit: true
-    choices:
-      accessibility: [None, WCAG AA, WCAG AAA]
-      platforms: [Web Responsive, Mobile Only, Desktop Only, Cross-Platform]
-    sections:
-      - id: ux-vision
-        title: Overall UX Vision
-      - id: interaction-paradigms
-        title: Key Interaction Paradigms
-      - id: core-screens
-        title: Core Screens and Views
-        instruction: 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
-        examples:
-          - "Login Screen"
-          - "Main Dashboard"
-          - "Item Detail Page"
-          - "Settings Page"
-      - id: accessibility
-        title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}"
-      - id: branding
-        title: Branding
-        instruction: Any known branding elements or style guides that must be incorporated?
-        examples:
-          - "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."
-      - id: target-platforms
-        title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}"
-        examples:
-          - "Web Responsive, and all mobile platforms"
-          - "iPhone Only"
-          - "ASCII Windows Desktop"
-
-  - id: technical-assumptions
-    title: Technical Assumptions
-    instruction: |
-      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
-    elicit: true
-    choices:
-      repository: [Monorepo, Polyrepo]
-      architecture: [Monolith, Microservices, Serverless]
-      testing: [Unit Only, Unit + Integration, Full Testing Pyramid]
-    sections:
-      - id: repository-structure
-        title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}"
-      - id: service-architecture
-        title: Service Architecture
-        instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)."
-      - id: testing-requirements
-        title: Testing Requirements
-        instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)."
-      - id: additional-assumptions
-        title: Additional Technical Assumptions and Requests
-        instruction: 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
-
-  - id: epic-list
-    title: Epic List
-    instruction: |
-      Present a high-level list of all epics for user approval. 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.
-    elicit: true
-    examples:
-      - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management"
-      - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations"
-      - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes"
-      - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users"
-
-  - id: epic-details
-    title: Epic {{epic_number}} {{epic_title}}
-    repeatable: true
-    instruction: |
-      After the epic list is approved, present each epic with all its stories and acceptance criteria as a complete review unit.
-      
-      For each epic provide expanded goal (2-3 sentences describing the objective and value all the stories will achieve).
-      
-      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
-    elicit: true
-    template: "{{epic_goal}}"
-    sections:
-      - id: story
-        title: Story {{epic_number}}.{{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
-            item_template: "{{criterion_number}}: {{criteria}}"
-            repeatable: true
-            instruction: |
-              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
-
-  - id: checklist-results
-    title: Checklist Results Report
-    instruction: 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.
-
-  - id: next-steps
-    title: Next Steps
-    sections:
-      - 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.yaml

@@ -1,221 +0,0 @@
-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/qa-gate-tmpl.yaml

@@ -1,102 +0,0 @@
-template:
-  id: qa-gate-template-v1
-  name: Quality Gate Decision
-  version: 1.0
-  output:
-    format: yaml
-    filename: docs/qa/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml
-    title: "Quality Gate: {{epic_num}}.{{story_num}}"
-
-# Required fields (keep these first)
-schema: 1
-story: "{{epic_num}}.{{story_num}}"
-story_title: "{{story_title}}"
-gate: "{{gate_status}}"  # PASS|CONCERNS|FAIL|WAIVED
-status_reason: "{{status_reason}}"  # 1-2 sentence summary of why this gate decision
-reviewer: "Quinn (Test Architect)"
-updated: "{{iso_timestamp}}"
-
-# Always present but only active when WAIVED
-waiver: { active: false }
-
-# Issues (if any) - Use fixed severity: low | medium | high
-top_issues: []
-
-# Risk summary (from risk-profile task if run)
-risk_summary:
-  totals: { critical: 0, high: 0, medium: 0, low: 0 }
-  recommendations:
-    must_fix: []
-    monitor: []
-
-# Examples section using block scalars for clarity
-examples:
-  with_issues: |
-    top_issues:
-      - id: "SEC-001"
-        severity: high  # ONLY: low|medium|high
-        finding: "No rate limiting on login endpoint"
-        suggested_action: "Add rate limiting middleware before production"
-      - id: "TEST-001"  
-        severity: medium
-        finding: "Missing integration tests for auth flow"
-        suggested_action: "Add test coverage for critical paths"
-  
-  when_waived: |
-    waiver:
-      active: true
-      reason: "Accepted for MVP release - will address in next sprint"
-      approved_by: "Product Owner"
-
-# ============ Optional Extended Fields ============
-# Uncomment and use if your team wants more detail
-
-optional_fields_examples:
-  quality_and_expiry: |
-    quality_score: 75  # 0-100 (optional scoring)
-    expires: "2025-01-26T00:00:00Z"  # Optional gate freshness window
-  
-  evidence: |
-    evidence:
-      tests_reviewed: 15
-      risks_identified: 3
-      trace:
-        ac_covered: [1, 2, 3]  # AC numbers with test coverage
-        ac_gaps: [4]  # AC numbers lacking coverage
-  
-  nfr_validation: |
-    nfr_validation:
-      security: { status: CONCERNS, notes: "Rate limiting missing" }
-      performance: { status: PASS, notes: "" }
-      reliability: { status: PASS, notes: "" }
-      maintainability: { status: PASS, notes: "" }
-  
-  history: |
-    history:  # Append-only audit trail
-      - at: "2025-01-12T10:00:00Z"
-        gate: FAIL
-        note: "Initial review - missing tests"
-      - at: "2025-01-12T15:00:00Z"  
-        gate: CONCERNS
-        note: "Tests added but rate limiting still missing"
-  
-  risk_summary: |
-    risk_summary:  # From risk-profile task
-      totals:
-        critical: 0
-        high: 0
-        medium: 0
-        low: 0
-      # 'highest' is emitted only when risks exist
-      recommendations:
-        must_fix: []
-        monitor: []
-  
-  recommendations: |
-    recommendations:
-      immediate:  # Must fix before production
-        - action: "Add rate limiting to auth endpoints"
-          refs: ["api/auth/login.ts:42-68"]
-      future:  # Can be addressed later
-        - action: "Consider caching for better performance"
-          refs: ["services/data.service.ts"]

bmad-core/templates/story-tmpl.yaml

@@ -1,137 +0,0 @@
-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]

bmad-core/workflows/brownfield-fullstack.yaml

@@ -1,297 +0,0 @@
-workflow:
-  id: brownfield-fullstack
-  name: Brownfield Full-Stack Enhancement
-  description: >-
-    Agent workflow for enhancing existing full-stack applications with new features,
-    modernization, or significant changes. Handles existing system analysis and safe integration.
-  type: brownfield
-  project_types:
-    - feature-addition
-    - refactoring
-    - modernization
-    - integration-enhancement
-
-  sequence:
-    - step: enhancement_classification
-      agent: analyst
-      action: classify enhancement scope
-      notes: |
-        Determine enhancement complexity to route to appropriate path:
-        - Single story (< 4 hours) → Use brownfield-create-story task
-        - Small feature (1-3 stories) → Use brownfield-create-epic task  
-        - Major enhancement (multiple epics) → Continue with full workflow
-        
-        Ask user: "Can you describe the enhancement scope? Is this a small fix, a feature addition, or a major enhancement requiring architectural changes?"
-
-    - step: routing_decision
-      condition: based_on_classification
-      routes:
-        single_story:
-          agent: pm
-          uses: brownfield-create-story
-          notes: "Create single story for immediate implementation. Exit workflow after story creation."
-        small_feature:
-          agent: pm
-          uses: brownfield-create-epic
-          notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation."
-        major_enhancement:
-          continue: to_next_step
-          notes: "Continue with comprehensive planning workflow below."
-
-    - step: documentation_check
-      agent: analyst
-      action: check existing documentation
-      condition: major_enhancement_path
-      notes: |
-        Check if adequate project documentation exists:
-        - Look for existing architecture docs, API specs, coding standards
-        - Assess if documentation is current and comprehensive
-        - If adequate: Skip document-project, proceed to PRD
-        - If inadequate: Run document-project first
-
-    - step: project_analysis
-      agent: architect
-      action: analyze existing project and use task document-project
-      creates: brownfield-architecture.md (or multiple documents)
-      condition: documentation_inadequate
-      notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation."
-
-    - agent: pm
-      creates: prd.md
-      uses: brownfield-prd-tmpl
-      requires: existing_documentation_or_analysis
-      notes: |
-        Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.
-        If skipped, use existing project documentation.
-        SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
-
-    - step: architecture_decision
-      agent: pm/architect
-      action: determine if architecture document needed
-      condition: after_prd_creation
-      notes: |
-        Review PRD to determine if architectural planning is needed:
-        - New architectural patterns → Create architecture doc
-        - New libraries/frameworks → Create architecture doc
-        - Platform/infrastructure changes → Create architecture doc
-        - Following existing patterns → Skip to story creation
-
-    - agent: architect
-      creates: architecture.md
-      uses: brownfield-architecture-tmpl
-      requires: prd.md
-      condition: architecture_changes_needed
-      notes: "Creates architecture ONLY for significant architectural changes. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
-
-    - agent: po
-      validates: all_artifacts
-      uses: po-master-checklist
-      notes: "Validates all documents for integration safety and completeness. May require updates to any document."
-
-    - agent: various
-      updates: any_flagged_documents
-      condition: po_checklist_issues
-      notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
-
-    - agent: po
-      action: shard_documents
-      creates: sharded_docs
-      requires: all_artifacts_in_project
-      notes: |
-        Shard documents for IDE development:
-        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-        - Creates docs/prd/ and docs/architecture/ folders with sharded content
-
-    - agent: sm
-      action: create_story
-      creates: story.md
-      requires: sharded_docs_or_brownfield_docs
-      repeats: for_each_epic_or_enhancement
-      notes: |
-        Story creation cycle:
-        - For sharded PRD: @sm → *create (uses create-next-story)
-        - For brownfield docs: @sm → use create-brownfield-story task
-        - Creates story from available documentation
-        - Story starts in "Draft" status
-        - May require additional context gathering for brownfield
-
-    - agent: analyst/pm
-      action: review_draft_story
-      updates: story.md
-      requires: story.md
-      optional: true
-      condition: user_wants_story_review
-      notes: |
-        OPTIONAL: Review and approve draft story
-        - NOTE: story-review task coming soon
-        - Review story completeness and alignment
-        - Update story status: Draft → Approved
-
-    - agent: dev
-      action: implement_story
-      creates: implementation_files
-      requires: story.md
-      notes: |
-        Dev Agent (New Chat): @dev
-        - Implements approved story
-        - Updates File List with all changes
-        - Marks story as "Review" when complete
-
-    - agent: qa
-      action: review_implementation
-      updates: implementation_files
-      requires: implementation_files
-      optional: true
-      notes: |
-        OPTIONAL: QA Agent (New Chat): @qa → review-story
-        - Senior dev review with refactoring ability
-        - Fixes small issues directly
-        - Leaves checklist for remaining items
-        - Updates story status (Review → Done or stays Review)
-
-    - agent: dev
-      action: address_qa_feedback
-      updates: implementation_files
-      condition: qa_left_unchecked_items
-      notes: |
-        If QA left unchecked items:
-        - Dev Agent (New Chat): Address remaining items
-        - Return to QA for final approval
-
-    - repeat_development_cycle:
-      action: continue_for_all_stories
-      notes: |
-        Repeat story cycle (SM → Dev → QA) for all epic stories
-        Continue until all stories in PRD are complete
-
-    - agent: po
-      action: epic_retrospective
-      creates: epic-retrospective.md
-      condition: epic_complete
-      optional: true
-      notes: |
-        OPTIONAL: After epic completion
-        - NOTE: epic-retrospective task coming soon
-        - Validate epic was completed correctly
-        - Document learnings and improvements
-
-    - workflow_end:
-      action: project_complete
-      notes: |
-        All stories implemented and reviewed!
-        Project development phase complete.
-        
-        Reference: {root}/data/bmad-kb.md#IDE Development Workflow
-
-  flow_diagram: |
-    ```mermaid
-    graph TD
-        A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]
-        B --> C{Enhancement Size?}
-        
-        C -->|Single Story| D[pm: brownfield-create-story]
-        C -->|1-3 Stories| E[pm: brownfield-create-epic]
-        C -->|Major Enhancement| F[analyst: check documentation]
-        
-        D --> END1[To Dev Implementation]
-        E --> END2[To Story Creation]
-        
-        F --> G{Docs Adequate?}
-        G -->|No| H[architect: document-project]
-        G -->|Yes| I[pm: brownfield PRD]
-        H --> I
-        
-        I --> J{Architecture Needed?}
-        J -->|Yes| K[architect: architecture.md]
-        J -->|No| L[po: validate artifacts]
-        K --> L
-        
-        L --> M{PO finds issues?}
-        M -->|Yes| N[Fix issues]
-        M -->|No| O[po: shard documents]
-        N --> L
-        
-        O --> P[sm: create story]
-        P --> Q{Story Type?}
-        Q -->|Sharded PRD| R[create-next-story]
-        Q -->|Brownfield Docs| S[create-brownfield-story]
-        
-        R --> T{Review draft?}
-        S --> T
-        T -->|Yes| U[review & approve]
-        T -->|No| V[dev: implement]
-        U --> V
-        
-        V --> W{QA review?}
-        W -->|Yes| X[qa: review]
-        W -->|No| Y{More stories?}
-        X --> Z{Issues?}
-        Z -->|Yes| AA[dev: fix]
-        Z -->|No| Y
-        AA --> X
-        Y -->|Yes| P
-        Y -->|No| AB{Retrospective?}
-        AB -->|Yes| AC[po: retrospective]
-        AB -->|No| AD[Complete]
-        AC --> AD
-
-        style AD fill:#90EE90
-        style END1 fill:#90EE90
-        style END2 fill:#90EE90
-        style D fill:#87CEEB
-        style E fill:#87CEEB
-        style I fill:#FFE4B5
-        style K fill:#FFE4B5
-        style O fill:#ADD8E6
-        style P fill:#ADD8E6
-        style V fill:#ADD8E6
-        style U fill:#F0E68C
-        style X fill:#F0E68C
-        style AC fill:#F0E68C
-    ```
-
-  decision_guidance:
-    when_to_use:
-      - Enhancement requires coordinated stories
-      - Architectural changes are needed
-      - Significant integration work required
-      - Risk assessment and mitigation planning necessary
-      - Multiple team members will work on related changes
-
-  handoff_prompts:
-    classification_complete: |
-      Enhancement classified as: {{enhancement_type}}
-      {{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.
-      {{if small_feature}}: Creating focused epic with brownfield-create-epic task.
-      {{if major_enhancement}}: Continuing with comprehensive planning workflow.
-    
-    documentation_assessment: |
-      Documentation assessment complete:
-      {{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.
-      {{if inadequate}}: Running document-project to capture current system state before PRD.
-    
-    document_project_to_pm: |
-      Project analysis complete. Key findings documented in:
-      - {{document_list}}
-      Use these findings to inform PRD creation and avoid re-analyzing the same aspects.
-    
-    pm_to_architect_decision: |
-      PRD complete and saved as docs/prd.md. 
-      Architectural changes identified: {{yes/no}}
-      {{if yes}}: Proceeding to create architecture document for: {{specific_changes}}
-      {{if no}}: No architectural changes needed. Proceeding to validation.
-    
-    architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety."
-    
-    po_to_sm: |
-      All artifacts validated. 
-      Documentation type available: {{sharded_prd / brownfield_docs}}
-      {{if sharded}}: Use standard create-next-story task.
-      {{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.
-    
-    sm_story_creation: |
-      Creating story from {{documentation_type}}.
-      {{if missing_context}}: May need to gather additional context from user during story creation.
-    
-    complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."