chore: configure changelog file path in semantic-release config

.github/FORK_GUIDE.md

@@ -1,106 +0,0 @@
-# Fork Guide - CI/CD Configuration
-
-## CI/CD in Forks
-
-By default, CI/CD workflows are **disabled in forks** to conserve GitHub Actions resources and provide a cleaner fork experience.
-
-### Why This Approach?
-
-- **Resource efficiency**: Prevents unnecessary GitHub Actions usage across 1,600+ forks
-- **Clean fork experience**: No failed workflow notifications in your fork
-- **Full control**: Enable CI/CD only when you actually need it
-- **PR validation**: Your changes are still fully tested when submitting PRs to the main repository
-
-## Enabling CI/CD in Your Fork
-
-If you need to run CI/CD workflows in your fork, follow these steps:
-
-1. Navigate to your fork's **Settings** tab
-2. Go to **Secrets and variables** → **Actions** → **Variables**
-3. Click **New repository variable**
-4. Create a new variable:
-   - **Name**: `ENABLE_CI_IN_FORK`
-   - **Value**: `true`
-5. Click **Add variable**
-
-That's it! CI/CD workflows will now run in your fork.
-
-## Disabling CI/CD Again
-
-To disable CI/CD workflows in your fork, you can either:
-
-- **Delete the variable**: Remove the `ENABLE_CI_IN_FORK` variable entirely, or
-- **Set to false**: Change the `ENABLE_CI_IN_FORK` value to `false`
-
-## Alternative Testing Options
-
-You don't always need to enable CI/CD in your fork. Here are alternatives:
-
-### Local Testing
-
-Run tests locally before pushing:
-
-```bash
-# Install dependencies
-npm ci
-
-# Run linting
-npm run lint
-
-# Run format check
-npm run format:check
-
-# Run validation
-npm run validate
-
-# Build the project
-npm run build
-```
-
-### Pull Request CI
-
-When you open a Pull Request to the main repository:
-
-- All CI/CD workflows automatically run
-- You get full validation of your changes
-- No configuration needed
-
-### GitHub Codespaces
-
-Use GitHub Codespaces for a full development environment:
-
-- All tools pre-configured
-- Same environment as CI/CD
-- No local setup required
-
-## Frequently Asked Questions
-
-### Q: Will my PR be tested even if CI is disabled in my fork?
-
-**A:** Yes! When you open a PR to the main repository, all CI/CD workflows run automatically, regardless of your fork's settings.
-
-### Q: Can I selectively enable specific workflows?
-
-**A:** The `ENABLE_CI_IN_FORK` variable enables all workflows. For selective control, you'd need to modify individual workflow files.
-
-### Q: Do I need to enable CI in my fork to contribute?
-
-**A:** No! Most contributors never need to enable CI in their forks. Local testing and PR validation are sufficient for most contributions.
-
-### Q: Will disabling CI affect my ability to merge PRs?
-
-**A:** No! PR merge requirements are based on CI runs in the main repository, not your fork.
-
-### Q: Why was this implemented?
-
-**A:** With over 1,600 forks of BMAD-METHOD, this saves thousands of GitHub Actions minutes monthly while maintaining code quality standards.
-
-## Need Help?
-
-- Join our [Discord Community](https://discord.gg/gk8jAdXWmj) for support
-- Check the [Contributing Guide](../README.md#contributing) for more information
-- Open an issue if you encounter any problems
-
----
-
-> 💡 **Pro Tip**: This fork-friendly approach is particularly valuable for projects using AI/LLM tools that create many experimental commits, as it prevents unnecessary CI runs while maintaining code quality standards.

.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.yml

@@ -1,5 +0,0 @@
-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,9 +1,9 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Did you discuss the idea first in Discord Server (#general-dev)**

.github/workflows/discord.yaml

@@ -1,20 +1,10 @@
 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:
     runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
     steps:
       - name: Notify Discord
         uses: sarisia/actions-status-discord@v1
@@ -23,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

@@ -1,44 +0,0 @@
-name: format-check
-
-"on":
-  pull_request:
-    branches: ["**"]
-
-jobs:
-  prettier:
-    runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Prettier format check
-        run: npm run format:check
-
-  eslint:
-    runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: ESLint
-        run: npm run lint

.github/workflows/manual-release.yaml

@@ -1,174 +0,0 @@
-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
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GH_PAT }}
-
-      - 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: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/bmadcode/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/pr-validation.yaml

@@ -1,55 +0,0 @@
-name: PR Validation
-
-on:
-  pull_request:
-    branches: [main]
-    types: [opened, synchronize, reopened]
-
-jobs:
-  validate:
-    runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run validation
-        run: npm run validate
-
-      - name: Check formatting
-        run: npm run format:check
-
-      - name: Run linter
-        run: npm run lint
-
-      - name: Run tests (if available)
-        run: npm test --if-present
-
-      - name: Comment on PR if checks fail
-        if: failure()
-        uses: actions/github-script@v7
-        with:
-          script: |
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: `❌ **PR Validation Failed**
-              
-              This PR has validation errors that must be fixed before merging:
-              - Run \`npm run validate\` to check agent/team configs
-              - Run \`npm run format:check\` to check formatting (fix with \`npm run format\`)
-              - Run \`npm run lint\` to check linting issues (fix with \`npm run lint:fix\`)
-              
-              Please fix these issues and push the changes.`
-            })

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

@@ -0,0 +1,144 @@
+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"
+          git config --global url."https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/".insteadOf "https://github.com/"
+
+      - name: Switch to stable branch
+        run: |
+          git checkout stable
+          git pull origin stable
+
+      - name: Merge main into stable
+        run: |
+          git merge origin/main --no-edit
+
+      - 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 on NPM and increment if necessary
+          while npm view bmad-method@$NEW_VERSION version >/dev/null 2>&1; 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 "feat: promote to stable ${{ steps.version.outputs.new_version }}
+
+          BREAKING CHANGE: Promote beta features to stable release
+
+          - Update version from ${{ steps.version.outputs.current_version }} to ${{ steps.version.outputs.new_version }}
+          - Automated promotion via GitHub Actions"
+
+      - name: Push stable release
+        run: |
+          git remote set-url origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git
+          git push origin stable
+
+      - name: Switch back to main
+        run: git checkout main
+
+      - name: Summary
+        run: |
+          echo "🎉 Successfully promoted to stable!"
+          echo "📦 Version: ${{ steps.version.outputs.new_version }}"
+          echo "🚀 The stable release will be automatically published to NPM via semantic-release"
+          echo "✅ Users running 'npx bmad-method install' will now get version ${{ steps.version.outputs.new_version }}"

.github/workflows/release.yaml

@@ -0,0 +1,60 @@
+name: Release
+'on':
+  push:
+    branches:
+      - main
+      - stable
+  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

@@ -25,19 +25,18 @@ Thumbs.db
 # Development tools and configs
 .prettierignore
 .prettierrc
+.husky/
 
 # IDE and editor configs
 .windsurf/
 .trae/
-.bmad*/
-.cursor/
+.bmad*/.cursor/
 
 # AI assistant files
 CLAUDE.md
 .ai/*
 .claude
 .gemini
-.iflow
 
 # Project-specific
 .bmad-core

.husky/pre-commit

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

.releaserc.json

@@ -0,0 +1,26 @@
+{
+  "branches": [
+    {
+      "name": "main",
+      "prerelease": "beta",
+      "channel": "beta"
+    },
+    {
+      "name": "stable",
+      "channel": "latest"
+    }
+  ],
+  "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

@@ -40,30 +40,5 @@
     "tileset",
     "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": "esbenp.prettier-vscode" },
-  "[yaml]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
-  "[markdown]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
-  "prettier.prettierPath": "node_modules/prettier",
-  "prettier.requireConfig": true,
-  "yaml.format.enable": false,
-  "eslint.useFlatConfig": true,
-  "eslint.validate": ["javascript", "yaml"],
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": "explicit"
-  },
-  "editor.rulers": [100]
+  ]
 }

CHANGELOG.md

@@ -574,6 +574,10 @@
 
 - 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
@@ -682,5 +686,4 @@
 ### Features
 
 - add versioning and release automation ([0ea5e50](https://github.com/bmadcode/BMAD-METHOD/commit/0ea5e50aa7ace5946d0100c180dd4c0da3e2fd8c))
-
 # Promote to stable release 5.0.0

CLAUDE.md

@@ -0,0 +1,196 @@
+# 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,6 +1,6 @@
 # Contributing to this project
 
-Thank you for contributing to this project! This document outlines the process for contributing and some guidelines to follow.
+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!
 
@@ -8,53 +8,15 @@ Thank you for contributing to this project! This document outlines the process f
 
 Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
 
-💬 **Discord Community**: Join our [Discord server](https://discord.gg/gk8jAdXWmj) for real-time discussions or search past discussions or ideas.
+💬 **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
 
 By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
 
-## Before Submitting a PR
-
-**IMPORTANT**: All PRs must pass validation checks before they can be merged.
-
-### Required Checks
-
-Before submitting your PR, run these commands locally:
-
-```bash
-# Run all validation checks
-npm run pre-release
-
-# Or run them individually:
-npm run validate     # Validate agent/team configs
-npm run format:check # Check code formatting
-npm run lint        # Check for linting issues
-```
-
-### Fixing Issues
-
-If any checks fail, use these commands to fix them:
-
-```bash
-# Fix all issues automatically
-npm run fix
-
-# Or fix individually:
-npm run format      # Fix formatting issues
-npm run lint:fix    # Fix linting issues
-```
-
-### Setup Git Hooks (Optional but Recommended)
-
-To catch issues before committing:
-
-```bash
-# Run this once after cloning
-chmod +x tools/setup-hooks.sh
-./tools/setup-hooks.sh
-```
-
 ## How to Contribute
 
 ### Reporting Bugs
@@ -188,6 +150,10 @@ Fixes #[issue number] (if applicable)
 
 [2-3 bullets listing HOW you implemented it]
 
+-
+-
+-
+
 ## Testing
 
 [1-2 sentences on how you tested this]
@@ -240,4 +206,4 @@ Each commit should represent one logical change:
 
 ## License
 
-By contributing to this project, you agree that your contributions will be licensed under the MIT License.
+By contributing to this project, you agree that your contributions will be licensed under the same license as the project.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 BMad Code, LLC
+Copyright (c) 2025 Brian AKA BMad AKA BMad Code
 
 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,8 +19,3 @@ 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™ 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.

PR-opencode-agents-generator.md

@@ -1,40 +0,0 @@
-# feat(opencode): compact AGENTS.md generator and JSON-only integration
-
-## What
-
-Add JSON-only OpenCode integration and a compact AGENTS.md generator (no large embeds; clickable file links) with idempotent merges for BMAD instructions, agents, and commands.
-
-## Why
-
-Keep OpenCode config schema‑compliant and small, avoid key collisions, and provide a readable agents/tasks index without inflating AGENTS.md.
-
-## How
-
-- Ensure `.bmad-core/core-config.yaml` in `instructions`
-- Merge only selected packages’ agents/commands into opencode.json file
-- Orchestrators `mode: primary`; all agents enable `write`, `edit`, `bash`
-- Descriptions from `whenToUse`/task `Purpose` with sanitization + fallbacks
-- Explicit warnings for non‑BMAD collisions; AGENTS.md uses a strict 3‑column table with links
-
-## Testing
-
-- Run: `npx bmad-method install -f -i opencode`
-- Verify: `opencode.json[c]` updated/created as expected, `AGENTS.md` OpenCode section is compact with links
-- Pre‑push checks:
-
-```bash
-npm run pre-release
-# or individually
-npm run validate
-npm run format:check
-npm run lint
-# if anything fails
-npm run fix
-# or
-npm run format
-npm run lint:fix
-```
-
-Fixes #<issue-number>
-
-Targets: `next` branch

README.md

@@ -1,35 +1,4 @@
-# BMAD-METHOD™: Universal AI Agent Framework
-
-> ## 🚨 **IMPORTANT VERSION ANNOUNCEMENT** 🚨
->
-> ### Current Stable: v4.x | Next Major: v6 Alpha
->
-> - **v4.x** - The current stable release version available via npm
-> - **v5** - Skipped (replaced by v6)
-> - **[v6-alpha](https://github.com/bmad-code-org/BMAD-METHOD/tree/v6-alpha)** - **NOW AVAILABLE FOR EARLY TESTING!**
->
-> ### 🧪 Try v6 Alpha (Early Adopters Only)
->
-> The next major version of BMAD-METHOD is now available for early experimentation and testing. This is a complete rewrite with significant architectural changes.
->
-> **⚠️ WARNING: v6-alpha is for early adopters who are comfortable with:**
->
-> - Potential breaking changes
-> - Daily updates and instability
-> - Incomplete features
-> - Experimental functionality
->
-> **📅 Timeline:** Official beta version will be merged mid-October 2025
->
-> **To try v6-alpha:**
->
-> ```bash
-> git clone https://github.com/bmad-code-org/BMAD-METHOD.git
-> cd BMAD-METHOD
-> git checkout v6-alpha
-> ```
->
-> ---
+# BMad-Method: Universal AI Agent Framework
 
 [![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)
@@ -42,11 +11,11 @@ Foundations in Agentic Agile Driven Development, known as the Breakthrough Metho
 
 **[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.**
 
-⭐ **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!
+⭐ **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:**
+**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.
 
@@ -71,7 +40,7 @@ This two-phase approach eliminates both **planning inconsistency** and **context
 
 - **[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
+- **[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
@@ -80,7 +49,7 @@ This two-phase approach eliminates both **planning inconsistency** and **context
 
 ## Important: Keep Your BMad Installation Updated
 
-**Stay up-to-date effortlessly!** If you already have BMAD-METHOD™ installed in your project, simply run:
+**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
 
 ```bash
 npx bmad-method install
@@ -139,7 +108,87 @@ npm run install:bmad # build and install all to a destination folder
 
 ## 🌟 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!
+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
+
+```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
+```
+
+### Example Output
+
+The tool will display progress and provide a comprehensive summary:
+
+```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
+```
+
+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.
+
+#### Advanced Usage & Options
+
+- 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.
+
+#### Minimal XML example
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<files>
+  <file path="src/index.js"><![CDATA[
+    // your source content
+  ]]></file>
+</files>
+```
 
 ## Documentation & Resources
 
@@ -161,34 +210,10 @@ BMAD™'s natural language framework works in ANY domain. Expansion packs provid
 
 📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete guide to contributing, including guidelines, process, and requirements
 
-### Working with Forks
-
-When you fork this repository, CI/CD workflows are **disabled by default** to save resources. This is intentional and helps keep your fork clean.
-
-#### Need CI/CD in Your Fork?
-
-See our [Fork CI/CD Guide](.github/FORK_GUIDE.md) for instructions on enabling workflows in your fork.
-
-#### Contributing Workflow
-
-1. **Fork the repository** - Click the Fork button on GitHub
-2. **Clone your fork** - `git clone https://github.com/YOUR-USERNAME/BMAD-METHOD.git`
-3. **Create a feature branch** - `git checkout -b feature/amazing-feature`
-4. **Make your changes** - Test locally with `npm test`
-5. **Commit your changes** - `git commit -m 'feat: add amazing feature'`
-6. **Push to your fork** - `git push origin feature/amazing-feature`
-7. **Open a Pull Request** - CI/CD will run automatically on the PR
-
-Your contributions are tested when you submit a PR - no need to enable CI in your fork!
-
 ## License
 
 MIT License - see [LICENSE](LICENSE) for details.
 
-## Trademark Notice
-
-BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
-
 [![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>

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

@@ -1,11 +1,10 @@
-# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team All
   icon: 👥
   description: Includes every core system agent.
 agents:
   - bmad-orchestrator
-  - "*"
+  - '*'
 workflows:
   - brownfield-fullstack.yaml
   - brownfield-service.yaml

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team Fullstack
   icon: 🚀

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team IDE Minimal
   icon: ⚡

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team No UI
   icon: 🔧

bmad-core/agents/analyst.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,7 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -57,28 +54,28 @@ persona:
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
-  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
   - create-project-brief: use task create-doc with project-brief-tmpl.yaml
-  - doc-out: Output full document in progress to current destination file
-  - elicit: run the task advanced-elicitation
   - perform-market-research: use task create-doc with market-research-tmpl.yaml
-  - research-prompt {topic}: execute task create-deep-research-prompt.md
+  - 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
-  tasks:
-    - advanced-elicitation.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - document-project.md
-    - facilitate-brainstorming-session.md
-  templates:
-    - brainstorming-output-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - market-research-tmpl.yaml
-    - project-brief-tmpl.yaml
 ```

bmad-core/agents/architect.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,8 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -56,10 +54,10 @@ persona:
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - create-backend-architecture: use create-doc with architecture-tmpl.yaml
-  - create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
-  - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
   - 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)
@@ -68,18 +66,18 @@ commands:
   - yolo: Toggle Yolo Mode
   - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
-  checklists:
-    - architect-checklist.md
-  data:
-    - technical-preferences.md
   tasks:
-    - create-deep-research-prompt.md
     - create-doc.md
+    - create-deep-research-prompt.md
     - document-project.md
     - execute-checklist.md
   templates:
     - architecture-tmpl.yaml
-    - brownfield-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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,10 +26,10 @@ activation-instructions:
   - 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 (Exception: Read bmad-core/core-config.yaml during activation)'
+  - 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, auto-run *help, 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.
+  - 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
@@ -51,40 +48,28 @@ persona:
 
 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)
-  - 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
   - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
-  - task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
   - yolo: Toggle Yolo Mode
   - exit: Exit (confirm)
 
 dependencies:
-  checklists:
-    - architect-checklist.md
-    - change-checklist.md
-    - pm-checklist.md
-    - po-master-checklist.md
-    - story-dod-checklist.md
-    - story-draft-checklist.md
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-    - elicitation-methods.md
-    - technical-preferences.md
   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
-    - create-next-story.md
     - document-project.md
+    - create-next-story.md
     - execute-checklist.md
-    - facilitate-brainstorming-session.md
     - generate-ai-frontend-prompt.md
     - index-docs.md
     - shard-doc.md
@@ -100,11 +85,23 @@ dependencies:
     - 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.yaml
-    - brownfield-service.yaml
-    - brownfield-ui.yaml
-    - greenfield-fullstack.yaml
-    - greenfield-service.yaml
-    - greenfield-ui.yaml
+    - 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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -31,8 +28,8 @@ activation-instructions:
   - 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 (Exception: Read `.bmad-core/core-config.yaml` during activation)
-  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, 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.
+  - 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
@@ -56,16 +53,21 @@ persona:
     - 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
-  agent: Transform into a specialized agent (list if name not specified)
   chat-mode: Start conversational mode for detailed assistance
-  checklist: Execute a checklist (list if name not specified)
-  doc-out: Output full document
   kb-mode: Load full BMad knowledge base
-  party-mode: Group chat with all agents
   status: Show current context, active agent, and progress
-  task: Run a specific task (list if name not specified)
-  yolo: Toggle skip confirmations mode
+  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)
@@ -129,19 +131,19 @@ workflow-guidance:
   - 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?'
+  - 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:
-  data:
-    - bmad-kb.md
-    - elicitation-methods.md
   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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -32,13 +29,13 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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'
+  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
   customization:
 
 persona:
@@ -49,7 +46,6 @@ persona:
 
 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: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
   - 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
@@ -57,25 +53,23 @@ core_principles:
 # 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'
+      - 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'
+      - 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"
-  - 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.
-  - review-qa: run task `apply-qa-fixes.md'
-  - run-tests: Execute linting and tests
-  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
 
 dependencies:
-  checklists:
-    - story-dod-checklist.md
   tasks:
-    - apply-qa-fixes.md
     - execute-checklist.md
     - validate-next-story.md
+  checklists:
+    - story-dod-checklist.md
 ```

bmad-core/agents/pm.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,7 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -53,32 +50,32 @@ persona:
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - correct-course: execute the correct-course task
-  - create-brownfield-epic: run task brownfield-create-epic.md
+  - 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-prd: run task create-doc.md with template prd-tmpl.yaml
   - 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:
-  checklists:
-    - change-checklist.md
-    - pm-checklist.md
-  data:
-    - technical-preferences.md
   tasks:
-    - brownfield-create-epic.md
-    - brownfield-create-story.md
+    - create-doc.md
     - correct-course.md
     - create-deep-research-prompt.md
-    - create-doc.md
+    - brownfield-create-epic.md
+    - brownfield-create-story.md
     - execute-checklist.md
     - shard-doc.md
   templates:
-    - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml
+    - brownfield-prd-tmpl.yaml
+  checklists:
+    - pm-checklist.md
+    - change-checklist.md
+  data:
+    - technical-preferences.md
 ```

bmad-core/agents/po.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,7 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -56,24 +53,24 @@ persona:
 # 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
-  - 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
   - 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:
-  checklists:
-    - change-checklist.md
-    - po-master-checklist.md
   tasks:
-    - correct-course.md
     - 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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,13 +26,17 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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.
+  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
@@ -60,28 +61,28 @@ story-file-permissions:
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - gate {story}: Execute qa-gate task to write/update quality gate decision in directory from qa.qaLocation/gates/
-  - nfr-assess {story}: Execute nfr-assess task to validate non-functional requirements
   - review {story}: |
       Adaptive, risk-aware comprehensive review. 
       Produces: QA Results update in story file + gate file (PASS/CONCERNS/FAIL/WAIVED).
-      Gate file location: qa.qaLocation/gates/{epic}.{story}-{slug}.yml
+      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
-  - trace {story}: Execute trace-requirements task to map requirements to tests using Given-When-Then
+  - 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:
-  data:
-    - technical-preferences.md
   tasks:
-    - nfr-assess.md
-    - qa-gate.md
     - review-story.md
+    - qa-gate.md
+    - trace-requirements.md
     - risk-profile.md
     - test-design.md
-    - trace-requirements.md
+    - nfr-assess.md
+  data:
+    - technical-preferences.md
   templates:
-    - qa-gate-tmpl.yaml
     - story-tmpl.yaml
+    - qa-gate-tmpl.yaml
 ```

bmad-core/agents/sm.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,7 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -49,17 +46,17 @@ persona:
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - correct-course: Execute task correct-course.md
   - 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:
-  checklists:
-    - story-draft-checklist.md
   tasks:
-    - correct-course.md
     - 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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -19,8 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 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: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - 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
@@ -29,7 +26,7 @@ activation-instructions:
   - 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, auto-run `*help`, 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.
+  - 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
@@ -58,12 +55,12 @@ commands:
   - generate-ui-prompt: Run task generate-ai-frontend-prompt.md
   - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
-  data:
-    - technical-preferences.md
   tasks:
+    - generate-ai-frontend-prompt.md
     - create-doc.md
     - execute-checklist.md
-    - generate-ai-frontend-prompt.md
   templates:
     - front-end-spec-tmpl.yaml
+  data:
+    - technical-preferences.md
 ```

bmad-core/checklists/architect-checklist.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.

bmad-core/checklists/change-checklist.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.

bmad-core/checklists/pm-checklist.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -15,7 +13,7 @@ First, determine the project type by checking:
 
 2. Is this a BROWNFIELD project (enhancing existing system)?
    - Look for: References to existing codebase, enhancement/modification language
-   - Check for: prd.md, architecture.md, existing system analysis
+   - 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
@@ -33,8 +31,8 @@ For GREENFIELD projects:
 
 For BROWNFIELD projects:
 
-- prd.md - The brownfield enhancement requirements
-- architecture.md - The enhancement architecture
+- 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

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.

bmad-core/core-config.yaml

@@ -1,7 +1,4 @@
-# <!-- Powered by BMAD™ Core -->
 markdownExploder: true
-qa:
-  qaLocation: docs/qa
 prd:
   prdFile: docs/prd.md
   prdVersion: v4

bmad-core/data/bmad-kb.md

@@ -1,10 +1,8 @@
-<!-- Powered by BMAD™ Core -->
-
-# BMAD™ Knowledge Base
+# 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.
+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
 
@@ -102,9 +100,8 @@ npx bmad-method install
   - **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
-  - **Auggie CLI (Augment Code)**: AI-powered development environment
 
-**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.
+**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**:
 
@@ -112,7 +109,7 @@ npx bmad-method install
 - 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
+**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
 
@@ -181,7 +178,7 @@ npx bmad-method install
 
 ## 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.
+**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?
 
@@ -301,7 +298,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 - **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
-- **Windsurf**: `/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.
@@ -356,7 +353,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### 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).
+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
 
@@ -711,7 +708,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMAD-METHOD™
+## Contributing to BMad-Method
 
 ### Quick Contribution Guidelines
 
@@ -743,7 +740,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### 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.
+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?
 

bmad-core/data/brainstorming-techniques.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Brainstorming Techniques Data
 
 ## Creative Expansion

bmad-core/data/elicitation-methods.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Elicitation Methods Data
 
 ## Core Reflective Methods

bmad-core/data/technical-preferences.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # User-Defined Preferred Patterns and Preferences
 
 None Listed

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Test Levels Framework
 
 Comprehensive guide for determining appropriate test levels (unit, integration, E2E) for different scenarios.
@@ -27,10 +25,10 @@ Comprehensive guide for determining appropriate test levels (unit, integration,
 
 ```yaml
 unit_test:
-  component: 'PriceCalculator'
-  scenario: 'Calculate discount with multiple rules'
-  justification: 'Complex business logic with multiple branches'
-  mock_requirements: 'None - pure function'
+  component: "PriceCalculator"
+  scenario: "Calculate discount with multiple rules"
+  justification: "Complex business logic with multiple branches"
+  mock_requirements: "None - pure function"
 ```
 
 ### Integration Tests
@@ -54,10 +52,10 @@ unit_test:
 
 ```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'
+  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
@@ -81,10 +79,10 @@ integration_test:
 
 ```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'
+  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

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Test Priorities Matrix
 
 Guide for prioritizing test scenarios based on risk, criticality, and business impact.

bmad-core/tasks/advanced-elicitation.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Advanced Elicitation Task
 
 ## Purpose

bmad-core/tasks/apply-qa-fixes.md

@@ -1,150 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# apply-qa-fixes
-
-Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
-
-## Purpose
-
-- Read QA outputs for a story (gate YAML + assessment markdowns)
-- Create a prioritized, deterministic fix plan
-- Apply code and test changes to close gaps and address issues
-- Update only the allowed story sections for the Dev agent
-
-## Inputs
-
-```yaml
-required:
-  - story_id: '{epic}.{story}' # e.g., "2.2"
-  - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
-  - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
-
-optional:
-  - story_title: '{title}' # derive from story H1 if missing
-  - story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
-```
-
-## QA Sources to Read
-
-- Gate (YAML): `{qa_root}/gates/{epic}.{story}-*.yml`
-  - If multiple, use the most recent by modified time
-- Assessments (Markdown):
-  - Test Design: `{qa_root}/assessments/{epic}.{story}-test-design-*.md`
-  - Traceability: `{qa_root}/assessments/{epic}.{story}-trace-*.md`
-  - Risk Profile: `{qa_root}/assessments/{epic}.{story}-risk-*.md`
-  - NFR Assessment: `{qa_root}/assessments/{epic}.{story}-nfr-*.md`
-
-## Prerequisites
-
-- Repository builds and tests run locally (Deno 2)
-- Lint and test commands available:
-  - `deno lint`
-  - `deno test -A`
-
-## Process (Do not skip steps)
-
-### 0) Load Core Config & Locate Story
-
-- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
-- Locate story file in `{story_root}/{epic}.{story}.*.md`
-  - HALT if missing and ask for correct story id/path
-
-### 1) Collect QA Findings
-
-- Parse the latest gate YAML:
-  - `gate` (PASS|CONCERNS|FAIL|WAIVED)
-  - `top_issues[]` with `id`, `severity`, `finding`, `suggested_action`
-  - `nfr_validation.*.status` and notes
-  - `trace` coverage summary/gaps
-  - `test_design.coverage_gaps[]`
-  - `risk_summary.recommendations.must_fix[]` (if present)
-- Read any present assessment markdowns and extract explicit gaps/recommendations
-
-### 2) Build Deterministic Fix Plan (Priority Order)
-
-Apply in order, highest priority first:
-
-1. High severity items in `top_issues` (security/perf/reliability/maintainability)
-2. NFR statuses: all FAIL must be fixed → then CONCERNS
-3. Test Design `coverage_gaps` (prioritize P0 scenarios if specified)
-4. Trace uncovered requirements (AC-level)
-5. Risk `must_fix` recommendations
-6. Medium severity issues, then low
-
-Guidance:
-
-- Prefer tests closing coverage gaps before/with code changes
-- Keep changes minimal and targeted; follow project architecture and TS/Deno rules
-
-### 3) Apply Changes
-
-- Implement code fixes per plan
-- Add missing tests to close coverage gaps (unit first; integration where required by AC)
-- Keep imports centralized via `deps.ts` (see `docs/project/typescript-rules.md`)
-- Follow DI boundaries in `src/core/di.ts` and existing patterns
-
-### 4) Validate
-
-- Run `deno lint` and fix issues
-- Run `deno test -A` until all tests pass
-- Iterate until clean
-
-### 5) Update Story (Allowed Sections ONLY)
-
-CRITICAL: Dev agent is ONLY authorized to update these sections of the story file. Do not modify any other sections (e.g., QA Results, Story, Acceptance Criteria, Dev Notes, Testing):
-
-- Tasks / Subtasks Checkboxes (mark any fix subtask you added as done)
-- Dev Agent Record →
-  - Agent Model Used (if changed)
-  - Debug Log References (commands/results, e.g., lint/tests)
-  - Completion Notes List (what changed, why, how)
-  - File List (all added/modified/deleted files)
-- Change Log (new dated entry describing applied fixes)
-- Status (see Rule below)
-
-Status Rule:
-
-- If gate was PASS and all identified gaps are closed → set `Status: Ready for Done`
-- Otherwise → set `Status: Ready for Review` and notify QA to re-run the review
-
-### 6) Do NOT Edit Gate Files
-
-- Dev does not modify gate YAML. If fixes address issues, request QA to re-run `review-story` to update the gate
-
-## Blocking Conditions
-
-- Missing `.bmad-core/core-config.yaml`
-- Story file not found for `story_id`
-- No QA artifacts found (neither gate nor assessments)
-  - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
-
-## Completion Checklist
-
-- deno lint: 0 problems
-- deno test -A: all tests pass
-- All high severity `top_issues` addressed
-- NFR FAIL → resolved; CONCERNS minimized or documented
-- Coverage gaps closed or explicitly documented with rationale
-- Story updated (allowed sections only) including File List and Change Log
-- Status set according to Status Rule
-
-## Example: Story 2.2
-
-Given gate `docs/project/qa/gates/2.2-*.yml` shows
-
-- `coverage_gaps`: Back action behavior untested (AC2)
-- `coverage_gaps`: Centralized dependencies enforcement untested (AC4)
-
-Fix plan:
-
-- Add a test ensuring the Toolkit Menu "Back" action returns to Main Menu
-- Add a static test verifying imports for service/view go through `deps.ts`
-- Re-run lint/tests and update Dev Agent Record + File List accordingly
-
-## Key Principles
-
-- Deterministic, risk-first prioritization
-- Minimal, maintainable changes
-- Tests validate behavior and close gaps
-- Strict adherence to allowed story update areas
-- Gate ownership remains with QA; Dev signals readiness via Status

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create Brownfield Epic Task
 
 ## Purpose

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create Brownfield Story Task
 
 ## Purpose

bmad-core/tasks/correct-course.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Correct Course Task
 
 ## Purpose

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create Brownfield Story Task
 
 ## Purpose

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create Next Story Task
 
 ## Purpose

bmad-core/tasks/document-project.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Document an Existing Project
 
 ## Purpose

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

@@ -1,8 +1,6 @@
-## <!-- Powered by BMAD™ Core -->
-
+---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '{root}/templates/brainstorming-output-tmpl.yaml'
-
+template: "{root}/templates/brainstorming-output-tmpl.yaml"
 ---
 
 # Facilitate Brainstorming Session Task

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create AI Frontend Prompt Task
 
 ## Purpose

bmad-core/tasks/index-docs.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Index Documentation Task
 
 ## Purpose

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # KB Mode Interaction Task
 
 ## Purpose

bmad-core/tasks/nfr-assess.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # nfr-assess
 
 Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
@@ -8,28 +6,26 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
 
 ```yaml
 required:
-  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
-
+  - story_id: "{epic}.{story}"  # e.g., "1.3"
+  - story_path: "docs/stories/{epic}.{story}.*.md"
+  
 optional:
-  - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
-  - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
+  - 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 `qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`
+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
@@ -42,7 +38,7 @@ If story_path or story file can't be found:
 ```text
 Which NFRs should I assess? (Enter numbers or press Enter for default)
 [1] Security (default)
-[2] Performance (default)
+[2] Performance (default)  
 [3] Reliability (default)
 [4] Maintainability (default)
 [5] Usability
@@ -56,7 +52,6 @@ Which NFRs should I assess? (Enter numbers or press Enter for default)
 ### 2. Check for Thresholds
 
 Look for NFR requirements in:
-
 - Story acceptance criteria
 - `docs/architecture/*.md` files
 - `docs/technical-preferences.md`
@@ -77,7 +72,6 @@ No security requirements found. Required auth method?
 ### 3. Quick Assessment
 
 For each selected NFR, check:
-
 - Is there evidence it's implemented?
 - Can we validate it?
 - Are there obvious gaps?
@@ -92,24 +86,24 @@ Generate ONLY for NFRs actually assessed (no placeholders):
 # Gate YAML (copy/paste):
 nfr_validation:
   _assessed: [security, performance, reliability, maintainability]
-  security:
+  security: 
     status: CONCERNS
-    notes: 'No rate limiting on auth endpoints'
+    notes: "No rate limiting on auth endpoints"
   performance:
     status: PASS
-    notes: 'Response times < 200ms verified'
+    notes: "Response times < 200ms verified"
   reliability:
     status: PASS
-    notes: 'Error handling and retries implemented'
+    notes: "Error handling and retries implemented"
   maintainability:
     status: CONCERNS
-    notes: 'Test coverage at 65%, target is 80%'
+    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
+- **CONCERNS**: No FAILs, but any NFR is unknown/partial/missing evidence  
 - **PASS**: All selected NFRs meet targets with evidence
 
 ## Quality Score Calculation
@@ -125,25 +119,22 @@ If `technical-preferences.md` defines custom weights, use those instead.
 
 ## Output 2: Brief Assessment Report
 
-**ALWAYS save to:** `qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`
+**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
@@ -153,7 +144,6 @@ Reviewer: Quinn
    - Fix: Add tests for uncovered branches
 
 ## Quick Wins
-
 - Add rate limiting: ~2 hours
 - Increase test coverage: ~4 hours
 - Add performance monitoring: ~1 hour
@@ -162,98 +152,80 @@ Reviewer: Quinn
 ## Output 3: Story Update Line
 
 **End with this line for the review task to quote:**
-
 ```
-NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
+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 qa.qaLocation/gates/{epic}.{story}-{slug}.yml under nfr_validation
+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
@@ -311,7 +283,7 @@ maintainability:
 
 1. **Functional Suitability**: Completeness, correctness, appropriateness
 2. **Performance Efficiency**: Time behavior, resource use, capacity
-3. **Compatibility**: Co-existence, interoperability
+3. **Compatibility**: Co-existence, interoperability  
 4. **Usability**: Learnability, operability, accessibility
 5. **Reliability**: Maturity, availability, fault tolerance
 6. **Security**: Confidentiality, integrity, authenticity
@@ -319,7 +291,6 @@ maintainability:
 8. **Portability**: Adaptability, installability
 
 Use these when assessing beyond the core four.
-
 </details>
 
 <details>
@@ -333,13 +304,12 @@ performance_deep_dive:
     p99: 350ms
   database:
     slow_queries: 2
-    missing_indexes: ['users.email', 'orders.user_id']
+    missing_indexes: ["users.email", "orders.user_id"]
   caching:
     hit_rate: 0%
-    recommendation: 'Add Redis for session data'
+    recommendation: "Add Redis for session data"
   load_test:
     max_rps: 150
     breaking_point: 200 rps
 ```
-
-</details>
+</details>

bmad-core/tasks/qa-gate.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # qa-gate
 
 Create or update a quality gate decision file for a story based on review findings.
@@ -16,7 +14,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
 
 ## Gate File Location
 
-**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
+**ALWAYS** create file at: `docs/qa/gates/{epic}.{story}-{slug}.yml`
 
 Slug rules:
 
@@ -29,11 +27,11 @@ Slug rules:
 
 ```yaml
 schema: 1
-story: '{epic}.{story}'
+story: "{epic}.{story}"
 gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: '1-2 sentence explanation of gate decision'
-reviewer: 'Quinn'
-updated: '{ISO-8601 timestamp}'
+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
 ```
@@ -42,20 +40,20 @@ waiver: { active: false } # Only set active: true if WAIVED
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: CONCERNS
-status_reason: 'Missing rate limiting on auth endpoints poses security risk.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Missing rate limiting on auth endpoints poses security risk."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'SEC-001'
+  - 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'
+    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'
+    finding: "No integration tests for auth flow"
+    suggested_action: "Add integration test coverage"
 waiver: { active: false }
 ```
 
@@ -63,20 +61,20 @@ waiver: { active: false }
 
 ```yaml
 schema: 1
-story: '1.3'
+story: "1.3"
 gate: WAIVED
-status_reason: 'Known issues accepted for MVP release.'
-reviewer: 'Quinn'
-updated: '2025-01-12T10:15:00Z'
+status_reason: "Known issues accepted for MVP release."
+reviewer: "Quinn"
+updated: "2025-01-12T10:15:00Z"
 top_issues:
-  - id: 'PERF-001'
+  - id: "PERF-001"
     severity: low
-    finding: 'Dashboard loads slowly with 1000+ items'
-    suggested_action: 'Implement pagination in next sprint'
+    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'
+  reason: "MVP release - performance optimization deferred"
+  approved_by: "Product Owner"
 ```
 
 ## Gate Decision Criteria
@@ -126,13 +124,11 @@ waiver:
 
 ## Output Requirements
 
-1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
+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:
-
-   ```text
-   Gate: {STATUS} → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
    ```
-
+   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`
 
@@ -151,7 +147,7 @@ After creating gate file, append to story's QA Results section:
 
 ### Gate Status
 
-Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
+Gate: CONCERNS → docs/qa/gates/1.3-user-auth-login.yml
 ```
 
 ## Key Principles

bmad-core/tasks/review-story.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # 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.
@@ -8,10 +6,10 @@ Perform a comprehensive test architecture review with quality gate decision. Thi
 
 ```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)
+  - 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
@@ -169,9 +167,9 @@ After review and any refactoring, append your results to the story file in the Q
 
 ### Gate Status
 
-Gate: {STATUS} → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
-Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
-NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
+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
 
@@ -185,27 +183,27 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 
 **Template and Directory:**
 
-- Render from `../templates/qa-gate-tmpl.yaml`
-- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
-- Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
+- 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}'
+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}'
+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
+expires: "{ISO-8601 timestamp}" # Typically 2 weeks from review
 
 evidence:
   tests_reviewed: { count }
@@ -217,24 +215,24 @@ evidence:
 nfr_validation:
   security:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   performance:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   reliability:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
   maintainability:
     status: PASS|CONCERNS|FAIL
-    notes: 'Specific findings'
+    notes: "Specific findings"
 
 recommendations:
   immediate: # Must fix before production
-    - action: 'Add rate limiting'
-      refs: ['api/auth/login.ts']
+    - action: "Add rate limiting"
+      refs: ["api/auth/login.ts"]
   future: # Can be addressed later
-    - action: 'Consider caching'
-      refs: ['services/data.ts']
+    - action: "Consider caching"
+      refs: ["services/data.ts"]
 ```
 
 ### Gate Decision Criteria
@@ -310,7 +308,7 @@ Stop the review and request clarification if:
 After review:
 
 1. Update the QA Results section in the story file
-2. Create the gate file in directory from `qa.qaLocation/gates`
+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,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # risk-profile
 
 Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
@@ -8,10 +6,10 @@ Generate a comprehensive risk assessment matrix for a story implementation using
 
 ```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)
+  - 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
@@ -81,14 +79,14 @@ For each category, identify specific risks:
 
 ```yaml
 risk:
-  id: 'SEC-001' # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
+  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'
+  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'
+    - "UserRegistrationForm"
+    - "ProfileUpdateForm"
+  detection_method: "Code review revealed missing validation"
 ```
 
 ### 2. Risk Assessment
@@ -107,7 +105,7 @@ Evaluate each risk using probability × impact:
 - `Medium (2)`: Moderate consequences (degraded performance, minor data issues)
 - `Low (1)`: Minor consequences (cosmetic issues, slight inconvenience)
 
-### Risk Score = Probability × Impact
+**Risk Score = Probability × Impact**
 
 - 9: Critical Risk (Red)
 - 6: High Risk (Orange)
@@ -135,20 +133,20 @@ For each identified risk, provide mitigation:
 
 ```yaml
 mitigation:
-  risk_id: 'SEC-001'
-  strategy: 'preventive' # preventive|detective|corrective
+  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'
+    - "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'
+    - "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
@@ -174,17 +172,17 @@ risk_summary:
   highest:
     id: SEC-001
     score: 9
-    title: 'XSS on profile form'
+    title: "XSS on profile form"
   recommendations:
     must_fix:
-      - 'Add input sanitization & CSP'
+      - "Add input sanitization & CSP"
     monitor:
-      - 'Add security alerts for auth endpoints'
+      - "Add security alerts for auth endpoints"
 ```
 
 ### Output 2: Markdown Report
 
-**Save to:** `qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`
+**Save to:** `docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`
 
 ```markdown
 # Risk Profile: Story {epic}.{story}
@@ -292,7 +290,7 @@ Review and update risk profile when:
 
 Calculate overall story risk score:
 
-```text
+```
 Base Score = 100
 For each risk:
   - Critical (9): Deduct 20 points
@@ -341,8 +339,8 @@ Based on risk profile, recommend:
 
 **Print this line for review task to quote:**
 
-```text
-Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
+```
+Risk profile: docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
 ```
 
 ## Key Principles

bmad-core/tasks/shard-doc.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Document Sharding Task
 
 ## Purpose

bmad-core/tasks/test-design.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # test-design
 
 Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
@@ -8,10 +6,10 @@ Create comprehensive test scenarios with appropriate test level recommendations
 
 ```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)
+  - 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
@@ -64,13 +62,13 @@ For each identified test need, create:
 
 ```yaml
 test_scenario:
-  id: '{epic}.{story}-{LEVEL}-{SEQ}'
-  requirement: 'AC reference'
+  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
+  description: "What is being tested"
+  justification: "Why this level was chosen"
+  mitigates_risks: ["RISK-001"] # If risk profile exists
 ```
 
 ### 5. Validate Coverage
@@ -86,7 +84,7 @@ Ensure:
 
 ### Output 1: Test Design Document
 
-**Save to:** `qa.qaLocation/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md`
+**Save to:** `docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md`
 
 ```markdown
 # Test Design: Story {epic}.{story}
@@ -152,7 +150,7 @@ test_design:
 Print for use by trace-requirements task:
 
 ```text
-Test design matrix: qa.qaLocation/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md
+Test design matrix: docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md
 P0 tests identified: {count}
 ```
 

bmad-core/tasks/trace-requirements.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # trace-requirements
 
 Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
@@ -33,21 +31,21 @@ Identify all testable requirements from:
 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'
+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'
+  - 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'
+    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'
+  - 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
 ```
 
@@ -69,19 +67,19 @@ Document any gaps found:
 
 ```yaml
 coverage_gaps:
-  - requirement: 'AC3: Password reset email sent within 60 seconds'
-    gap: 'No test for email delivery timing'
+  - 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'
+      description: "Test email service SLA compliance"
 
-  - requirement: 'AC5: Support 1000 concurrent users'
-    gap: 'No load testing implemented'
+  - requirement: "AC5: Support 1000 concurrent users"
+    gap: "No load testing implemented"
     severity: high
     suggested_test:
       type: performance
-      description: 'Load test with 1000 concurrent connections'
+      description: "Load test with 1000 concurrent connections"
 ```
 
 ## Outputs
@@ -97,16 +95,16 @@ trace:
     full: Y
     partial: Z
     none: W
-  planning_ref: 'qa.qaLocation/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md'
+  planning_ref: "docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md"
   uncovered:
-    - ac: 'AC3'
-      reason: 'No test found for password reset timing'
-  notes: 'See qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md'
+    - 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:** `qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`
+**Save to:** `docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`
 
 Create a traceability report with:
 
@@ -252,7 +250,7 @@ This traceability feeds into quality gates:
 **Print this line for review task to quote:**
 
 ```text
-Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
+Trace matrix: docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
 ```
 
 - Full coverage → PASS contribution

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

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Validate Next Story Task
 
 ## Purpose
@@ -21,7 +19,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 1. Template Completeness Validation
 
-- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
+- 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

bmad-core/templates/architecture-tmpl.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
   name: Architecture Document
@@ -21,20 +20,20 @@ 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
@@ -47,16 +46,16 @@ sections:
             - 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
@@ -84,7 +83,7 @@ sections:
         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
@@ -101,17 +100,17 @@ sections:
           - 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)
@@ -127,23 +126,23 @@ sections:
     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:
@@ -167,13 +166,13 @@ sections:
     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
@@ -182,11 +181,11 @@ sections:
         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}}
@@ -195,7 +194,7 @@ sections:
     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
@@ -204,7 +203,7 @@ sections:
       - Key interfaces/APIs exposed
       - Dependencies on other components
       - Technology specifics based on tech stack choices
-
+      
       5. Create component diagrams where helpful
     elicit: true
     sections:
@@ -213,13 +212,13 @@ sections:
         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
@@ -236,13 +235,13 @@ sections:
     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
@@ -255,10 +254,10 @@ sections:
           - **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
@@ -267,13 +266,13 @@ sections:
     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
 
@@ -284,13 +283,13 @@ sections:
     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: |
@@ -307,13 +306,13 @@ sections:
     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
 
@@ -323,14 +322,14 @@ sections:
     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:
@@ -348,13 +347,13 @@ sections:
     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:
@@ -390,13 +389,13 @@ sections:
     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:
@@ -443,13 +442,13 @@ sections:
     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:
@@ -471,7 +470,7 @@ sections:
           - "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}}"
@@ -489,14 +488,14 @@ sections:
     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:
@@ -517,7 +516,7 @@ sections:
               - **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
@@ -559,7 +558,7 @@ sections:
     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
@@ -628,16 +627,16 @@ sections:
     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

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

@@ -23,11 +23,11 @@ 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:"
@@ -152,5 +152,5 @@ sections:
   - id: footer
     content: |
       ---
-
-      *Session facilitated using the BMAD-METHOD™ brainstorming framework*
+      
+      *Session facilitated using the BMAD-METHOD brainstorming framework*

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
   name: Brownfield Enhancement Architecture
@@ -17,40 +16,40 @@ sections:
     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 prd.md
+         - 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:
@@ -79,12 +78,12 @@ sections:
     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:
@@ -109,11 +108,11 @@ sections:
           - **UI/UX Consistency:** {{ui_compatibility}}
           - **Performance Impact:** {{performance_constraints}}
 
-  - id: tech-stack
-    title: Tech Stack
+  - 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
@@ -136,7 +135,7 @@ sections:
     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)
@@ -152,11 +151,11 @@ sections:
             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}}
@@ -168,7 +167,7 @@ sections:
           - **Modified Tables:** {{modified_tables_list}}
           - **New Indexes:** {{new_indexes_list}}
           - **Migration Strategy:** {{migration_approach}}
-
+          
           **Backward Compatibility:**
           - {{compatibility_measure_1}}
           - {{compatibility_measure_2}}
@@ -177,12 +176,12 @@ sections:
     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:
@@ -195,15 +194,15 @@ sections:
             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
@@ -216,7 +215,7 @@ sections:
     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
@@ -266,17 +265,17 @@ sections:
           - **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
-    title: Source Tree
+  - 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
@@ -315,7 +314,7 @@ sections:
     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
@@ -342,10 +341,10 @@ sections:
           **Monitoring:** {{monitoring_approach}}
 
   - id: coding-standards
-    title: 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
@@ -376,7 +375,7 @@ sections:
     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
@@ -416,7 +415,7 @@ sections:
     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
@@ -451,7 +450,7 @@ sections:
     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
@@ -474,4 +473,4 @@ sections:
           - 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
+          - Clear sequencing of implementation to minimize risk to existing functionality

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
   name: Brownfield Enhancement PRD
@@ -17,19 +16,19 @@ sections:
     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
@@ -55,7 +54,7 @@ sections:
           - 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
@@ -179,7 +178,7 @@ sections:
           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}}
@@ -218,7 +217,7 @@ sections:
           - 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}}
@@ -241,7 +240,7 @@ sections:
     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
@@ -254,7 +253,7 @@ sections:
       - Each story must deliver value while maintaining system integrity
     template: |
       **Epic Goal**: {{epic_goal}}
-
+      
       **Integration Requirements**: {{integration_requirements}}
     sections:
       - id: story
@@ -278,4 +277,4 @@ sections:
             items:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
-              - template: "IV3: {{performance_impact_verification}}"
+              - template: "IV3: {{performance_impact_verification}}"

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
   name: Competitive Analysis Report
@@ -77,7 +76,7 @@ sections:
         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
@@ -142,14 +141,7 @@ sections:
         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}}",
-          ]
+        columns: ["Feature Category", "{{your_company}}", "{{competitor_1}}", "{{competitor_2}}", "{{competitor_3}}"]
         rows:
           - category: "Core Functionality"
             items:
@@ -161,13 +153,7 @@ sections:
               - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"]
           - category: "Integration & Ecosystem"
             items:
-              - [
-                  "API Availability",
-                  "{{availability}}",
-                  "{{availability}}",
-                  "{{availability}}",
-                  "{{availability}}",
-                ]
+              - ["API Availability", "{{availability}}", "{{availability}}", "{{availability}}", "{{availability}}"]
               - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"]
           - category: "Pricing & Plans"
             items:
@@ -194,7 +180,7 @@ sections:
         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
@@ -229,7 +215,7 @@ sections:
         title: Blue Ocean Opportunities
         instruction: |
           Identify uncontested market spaces
-
+          
           List opportunities to create new market space:
           - Underserved segments
           - Unaddressed use cases
@@ -304,4 +290,4 @@ sections:
           Recommended review schedule:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
-          - Quarterly: {{quarterly_analysis}}
+          - Quarterly: {{quarterly_analysis}}

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
   name: Frontend Architecture Document
@@ -17,16 +16,16 @@ sections:
     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
@@ -42,7 +41,7 @@ sections:
            - 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
@@ -50,11 +49,11 @@ sections:
            - 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
@@ -76,24 +75,12 @@ sections:
         rows:
           - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - [
-              "State Management",
-              "{{state_management}}",
-              "{{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}}",
-            ]
+          - ["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}}"]
@@ -216,4 +203,4 @@ sections:
           - Common commands (dev server, build, test)
           - Key import patterns
           - File naming conventions
-          - Project-specific patterns and utilities
+          - Project-specific patterns and utilities

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
   name: UI/UX Specification
@@ -17,7 +16,7 @@ sections:
     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.
@@ -26,7 +25,7 @@ sections:
         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
@@ -67,7 +66,7 @@ sections:
     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
@@ -97,22 +96,22 @@ sections:
         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
@@ -121,9 +120,9 @@ sections:
         title: "{{flow_name}}"
         template: |
           **User Goal:** {{flow_goal}}
-
+          
           **Entry Points:** {{entry_points}}
-
+          
           **Success Criteria:** {{success_criteria}}
         sections:
           - id: flow-diagram
@@ -154,14 +153,14 @@ sections:
             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
@@ -180,11 +179,11 @@ sections:
             title: "{{component_name}}"
             template: |
               **Purpose:** {{component_purpose}}
-
+              
               **Variants:** {{component_variants}}
-
+              
               **States:** {{component_states}}
-
+              
               **Usage Guidelines:** {{usage_guidelines}}
 
   - id: branding-style
@@ -230,13 +229,13 @@ sections:
         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
@@ -254,12 +253,12 @@ sections:
           - 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}}
@@ -286,11 +285,11 @@ sections:
         title: Adaptation Patterns
         template: |
           **Layout Changes:** {{layout_adaptations}}
-
+          
           **Navigation Changes:** {{nav_adaptations}}
-
+          
           **Content Priority:** {{content_adaptations}}
-
+          
           **Interaction Changes:** {{interaction_adaptations}}
 
   - id: animation
@@ -324,7 +323,7 @@ sections:
     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
@@ -347,4 +346,4 @@ sections:
 
   - id: checklist-results
     title: Checklist Results
-    instruction: If a UI/UX checklist exists, run it against this document and report results here.
+    instruction: If a UI/UX checklist exists, run it against this document and report results here.

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

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
   name: Fullstack Architecture Document
@@ -20,33 +19,33 @@ sections:
     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
@@ -72,17 +71,17 @@ sections:
         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}}
@@ -92,7 +91,7 @@ sections:
         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
@@ -114,7 +113,7 @@ sections:
           - Databases and storage
           - External integrations
           - CDN and caching layers
-
+          
           Use appropriate diagram type for clarity.
       - id: architectural-patterns
         title: Architectural Patterns
@@ -124,7 +123,7 @@ sections:
           - 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}}"
@@ -138,7 +137,7 @@ sections:
     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
@@ -147,7 +146,7 @@ sections:
       - Testing tools for both frontend and backend
       - Build and deployment tools
       - Monitoring and logging
-
+      
       Upon render, elicit feedback immediately.
     elicit: true
     sections:
@@ -157,29 +156,11 @@ sections:
         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}}",
-            ]
+          - ["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}}",
-            ]
+          - ["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}}"]
@@ -200,14 +181,14 @@ sections:
     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
@@ -216,7 +197,7 @@ sections:
         title: "{{model_name}}"
         template: |
           **Purpose:** {{model_purpose}}
-
+          
           **Key Attributes:**
           - {{attribute_1}}: {{type_1}} - {{description_1}}
           - {{attribute_2}}: {{type_2}} - {{description_2}}
@@ -235,7 +216,7 @@ sections:
     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
@@ -243,7 +224,7 @@ sections:
       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:
@@ -278,7 +259,7 @@ sections:
     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
@@ -287,7 +268,7 @@ sections:
       - Key interfaces/APIs exposed
       - Dependencies on other components
       - Technology specifics based on tech stack choices
-
+      
       5. Create component diagrams where helpful
     elicit: true
     sections:
@@ -296,13 +277,13 @@ sections:
         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
@@ -319,13 +300,13 @@ sections:
     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
@@ -338,10 +319,10 @@ sections:
           - **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
@@ -350,14 +331,14 @@ sections:
     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
 
@@ -365,13 +346,13 @@ sections:
     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
 
@@ -507,60 +488,60 @@ sections:
     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
+    - |
+      {{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
@@ -587,13 +568,13 @@ sections:
             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
@@ -606,10 +587,10 @@ sections:
             template: |
               # Frontend (.env.local)
               {{frontend_env_vars}}
-
+              
               # Backend (.env)
               {{backend_env_vars}}
-
+              
               # Shared
               {{shared_env_vars}}
 
@@ -626,7 +607,7 @@ sections:
           - **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}}
@@ -657,12 +638,12 @@ sections:
           - 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}}
@@ -674,7 +655,7 @@ sections:
           - 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}}
@@ -690,10 +671,10 @@ sections:
         type: code
         language: text
         template: |
-          E2E Tests
-          /        \
-          Integration Tests
-          /            \
+                  E2E Tests
+                 /        \
+            Integration Tests
+               /            \
           Frontend Unit  Backend Unit
       - id: test-organization
         title: Test Organization
@@ -812,7 +793,7 @@ sections:
           - JavaScript errors
           - API response times
           - User interactions
-
+          
           **Backend Metrics:**
           - Request rate
           - Error rate
@@ -821,4 +802,4 @@ sections:
 
   - 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.
+    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,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
   name: Market Research Report
@@ -131,7 +130,7 @@ sections:
         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}}
@@ -250,4 +249,4 @@ sections:
         instruction: Include any complex calculations or models
       - id: additional-analysis
         title: C. Additional Analysis
-        instruction: Any supplementary analysis not included in main body
+        instruction: Any supplementary analysis not included in main body

bmad-core/templates/prd-tmpl.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
   name: Product Requirements Document
@@ -57,7 +56,7 @@ sections:
     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
@@ -99,7 +98,7 @@ sections:
     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
@@ -127,9 +126,9 @@ sections:
     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
@@ -148,11 +147,11 @@ sections:
     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
@@ -180,7 +179,7 @@ sections:
             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
@@ -200,4 +199,4 @@ sections:
         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.
+        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,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
   name: Project Brief
@@ -29,12 +28,12 @@ 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
@@ -219,4 +218,4 @@ sections:
       - 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.
+          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,19 +1,18 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: qa-gate-template-v1
   name: Quality Gate Decision
   version: 1.0
   output:
     format: yaml
-    filename: qa.qaLocation/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml
+    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
+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}}"
 
@@ -42,7 +41,7 @@ examples:
         severity: medium
         finding: "Missing integration tests for auth flow"
         suggested_action: "Add test coverage for critical paths"
-
+  
   when_waived: |
     waiver:
       active: true
@@ -56,7 +55,7 @@ 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
@@ -64,14 +63,14 @@ optional_fields_examples:
       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"
@@ -80,7 +79,7 @@ optional_fields_examples:
       - 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:
@@ -92,7 +91,7 @@ optional_fields_examples:
       recommendations:
         must_fix: []
         monitor: []
-
+  
   recommendations: |
     recommendations:
       immediate:  # Must fix before production
@@ -100,4 +99,4 @@ optional_fields_examples:
           refs: ["api/auth/login.ts:42-68"]
       future:  # Can be addressed later
         - action: "Consider caching for better performance"
-          refs: ["services/data.service.ts"]
+          refs: ["services/data.service.ts"]

bmad-core/templates/story-tmpl.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
   name: Story Document
@@ -13,7 +12,7 @@ workflow:
   elicitation: advanced-elicitation
 
 agent_config:
-  editable_sections:
+  editable_sections: 
     - Status
     - Story
     - Acceptance Criteria
@@ -30,7 +29,7 @@ sections:
     instruction: Select the current status of the story
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: story
     title: Story
     type: template-text
@@ -42,7 +41,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: acceptance-criteria
     title: Acceptance Criteria
     type: numbered-list
@@ -50,7 +49,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: tasks-subtasks
     title: Tasks / Subtasks
     type: bullet-list
@@ -67,7 +66,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: dev-notes
     title: Dev Notes
     instruction: |
@@ -91,7 +90,7 @@ sections:
         elicit: true
         owner: scrum-master
         editors: [scrum-master]
-
+        
   - id: change-log
     title: Change Log
     type: table
@@ -99,7 +98,7 @@ sections:
     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
@@ -112,27 +111,27 @@ sections:
         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]
+    editors: [qa-agent]

bmad-core/workflows/brownfield-fullstack.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-fullstack
   name: Brownfield Full-Stack Enhancement
@@ -21,7 +20,7 @@ workflow:
         - 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
@@ -160,7 +159,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -177,12 +176,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - 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: |
@@ -266,33 +265,33 @@ workflow:
       {{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."

bmad-core/workflows/brownfield-service.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-service
   name: Brownfield Service/API Enhancement
@@ -106,7 +105,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -123,12 +122,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - 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: |

bmad-core/workflows/brownfield-ui.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-ui
   name: Brownfield UI/Frontend Enhancement
@@ -113,7 +112,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -130,12 +129,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - 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: |

bmad-core/workflows/greenfield-fullstack.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-fullstack
   name: Greenfield Full-Stack Application Development
@@ -65,12 +64,12 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - step: project_setup_guidance
+    - project_setup_guidance:
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
 
-    - step: development_order_guidance
+    - development_order_guidance:
       action: guide_development_sequence
       notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
 
@@ -138,7 +137,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -155,12 +154,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - 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: |

bmad-core/workflows/greenfield-service.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-service
   name: Greenfield Service/API Development
@@ -114,7 +113,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -131,12 +130,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!
         Service development phase complete.
-
+        
         Reference: {root}/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |

bmad-core/workflows/greenfield-ui.yaml

@@ -1,4 +1,3 @@
-# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-ui
   name: Greenfield UI/Frontend Development
@@ -64,7 +63,7 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - step: project_setup_guidance
+    - project_setup_guidance:
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
@@ -133,7 +132,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -150,12 +149,12 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - 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: |

common/tasks/create-doc.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️

common/tasks/execute-checklist.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.

common/utils/bmad-doc-template.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # BMad Document Template Specification
 
 ## Overview
@@ -16,7 +14,7 @@ template:
   output:
     format: markdown
     filename: default-path/to/{{filename}}.md
-    title: '{{variable}} Document Title'
+    title: "{{variable}} Document Title"
 
 workflow:
   mode: interactive
@@ -110,8 +108,8 @@ sections:
 Use `{{variable_name}}` in titles, templates, and content:
 
 ```yaml
-title: 'Epic {{epic_number}} {{epic_title}}'
-template: 'As a {{user_type}}, I want {{action}}, so that {{benefit}}.'
+title: "Epic {{epic_number}} {{epic_title}}"
+template: "As a {{user_type}}, I want {{action}}, so that {{benefit}}."
 ```
 
 ### Conditional Sections
@@ -214,7 +212,7 @@ choices:
         - id: criteria
           title: Acceptance Criteria
           type: numbered-list
-          item_template: '{{criterion_number}}: {{criteria}}'
+          item_template: "{{criterion_number}}: {{criteria}}"
           repeatable: true
 ```
 
@@ -222,7 +220,7 @@ choices:
 
 ````yaml
 examples:
-  - 'FR6: The system must authenticate users within 2 seconds'
+  - "FR6: The system must authenticate users within 2 seconds"
   - |
     ```mermaid
     sequenceDiagram

common/utils/workflow-management.md

@@ -1,5 +1,3 @@
-<!-- Powered by BMAD™ Core -->
-
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.

dist/agents/bmad-orchestrator.txt

@@ -53,6 +53,7 @@ activation-instructions:
   - Assess user goal against available agents and workflows in this bundle
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
+  - Load resources only when needed - never pre-load
 agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
@@ -76,16 +77,21 @@ persona:
     - Always remind users that commands require * prefix
 commands:
   help: Show this guide with available agents and workflows
-  agent: Transform into a specialized agent (list if name not specified)
   chat-mode: Start conversational mode for detailed assistance
-  checklist: Execute a checklist (list if name not specified)
-  doc-out: Output full document
   kb-mode: Load full BMad knowledge base
-  party-mode: Group chat with all agents
   status: Show current context, active agent, and progress
-  task: Run a specific task (list if name not specified)
-  yolo: Toggle skip confirmations mode
+  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)
@@ -154,20 +160,19 @@ workflow-guidance:
   - 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:
-  data:
-    - bmad-kb.md
-    - elicitation-methods.md
   tasks:
     - advanced-elicitation.md
     - create-doc.md
     - kb-mode-interaction.md
+  data:
+    - bmad-kb.md
+    - elicitation-methods.md
   utils:
     - workflow-management.md
 ```
 ==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
 
 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
-<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -288,7 +293,6 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-core/tasks/create-doc.md ====================
-<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -393,7 +397,6 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-core/tasks/create-doc.md ====================
 
 ==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
-<!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
 ## Purpose
@@ -472,12 +475,11 @@ Or ask me about anything else related to BMad-Method!
 ==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
 
 ==================== START: .bmad-core/data/bmad-kb.md ====================
-<!-- Powered by BMAD™ Core -->
-# BMAD™ Knowledge Base
+# 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.
+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
 
@@ -576,7 +578,7 @@ npx bmad-method install
   - **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.
+**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**:
 
@@ -584,7 +586,7 @@ npx bmad-method install
 - 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
+**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
 
@@ -653,7 +655,7 @@ npx bmad-method install
 
 ## 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.
+**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?
 
@@ -773,7 +775,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 - **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
-- **Windsurf**: `/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.
@@ -828,7 +830,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### 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).
+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
 
@@ -1183,7 +1185,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMAD-METHOD™
+## Contributing to BMad-Method
 
 ### Quick Contribution Guidelines
 
@@ -1215,7 +1217,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### 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.
+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?
 
@@ -1282,7 +1284,6 @@ Use the **expansion-creator** pack to build your own:
 ==================== END: .bmad-core/data/bmad-kb.md ====================
 
 ==================== START: .bmad-core/data/elicitation-methods.md ====================
-<!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
 ## Core Reflective Methods
@@ -1440,7 +1441,6 @@ Use the **expansion-creator** pack to build your own:
 ==================== END: .bmad-core/data/elicitation-methods.md ====================
 
 ==================== START: .bmad-core/utils/workflow-management.md ====================
-<!-- Powered by BMAD™ Core -->
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.

dist/agents/dev.txt

@@ -69,6 +69,9 @@ core_principles:
   - Numbered Options - Always use numbered lists when presenting choices to the user
 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:
@@ -78,174 +81,16 @@ commands:
       - 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'
-  - 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.
-  - review-qa: run task `apply-qa-fixes.md'
-  - run-tests: Execute linting and tests
-  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
 dependencies:
-  checklists:
-    - story-dod-checklist.md
   tasks:
-    - apply-qa-fixes.md
     - execute-checklist.md
     - validate-next-story.md
+  checklists:
+    - story-dod-checklist.md
 ```
 ==================== END: .bmad-core/agents/dev.md ====================
 
-==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
-<!-- Powered by BMAD™ Core -->
-# apply-qa-fixes
-
-Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
-
-## Purpose
-
-- Read QA outputs for a story (gate YAML + assessment markdowns)
-- Create a prioritized, deterministic fix plan
-- Apply code and test changes to close gaps and address issues
-- Update only the allowed story sections for the Dev agent
-
-## Inputs
-
-```yaml
-required:
-  - story_id: '{epic}.{story}' # e.g., "2.2"
-  - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
-  - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
-
-optional:
-  - story_title: '{title}' # derive from story H1 if missing
-  - story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
-```
-
-## QA Sources to Read
-
-- Gate (YAML): `{qa_root}/gates/{epic}.{story}-*.yml`
-  - If multiple, use the most recent by modified time
-- Assessments (Markdown):
-  - Test Design: `{qa_root}/assessments/{epic}.{story}-test-design-*.md`
-  - Traceability: `{qa_root}/assessments/{epic}.{story}-trace-*.md`
-  - Risk Profile: `{qa_root}/assessments/{epic}.{story}-risk-*.md`
-  - NFR Assessment: `{qa_root}/assessments/{epic}.{story}-nfr-*.md`
-
-## Prerequisites
-
-- Repository builds and tests run locally (Deno 2)
-- Lint and test commands available:
-  - `deno lint`
-  - `deno test -A`
-
-## Process (Do not skip steps)
-
-### 0) Load Core Config & Locate Story
-
-- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
-- Locate story file in `{story_root}/{epic}.{story}.*.md`
-  - HALT if missing and ask for correct story id/path
-
-### 1) Collect QA Findings
-
-- Parse the latest gate YAML:
-  - `gate` (PASS|CONCERNS|FAIL|WAIVED)
-  - `top_issues[]` with `id`, `severity`, `finding`, `suggested_action`
-  - `nfr_validation.*.status` and notes
-  - `trace` coverage summary/gaps
-  - `test_design.coverage_gaps[]`
-  - `risk_summary.recommendations.must_fix[]` (if present)
-- Read any present assessment markdowns and extract explicit gaps/recommendations
-
-### 2) Build Deterministic Fix Plan (Priority Order)
-
-Apply in order, highest priority first:
-
-1. High severity items in `top_issues` (security/perf/reliability/maintainability)
-2. NFR statuses: all FAIL must be fixed → then CONCERNS
-3. Test Design `coverage_gaps` (prioritize P0 scenarios if specified)
-4. Trace uncovered requirements (AC-level)
-5. Risk `must_fix` recommendations
-6. Medium severity issues, then low
-
-Guidance:
-
-- Prefer tests closing coverage gaps before/with code changes
-- Keep changes minimal and targeted; follow project architecture and TS/Deno rules
-
-### 3) Apply Changes
-
-- Implement code fixes per plan
-- Add missing tests to close coverage gaps (unit first; integration where required by AC)
-- Keep imports centralized via `deps.ts` (see `docs/project/typescript-rules.md`)
-- Follow DI boundaries in `src/core/di.ts` and existing patterns
-
-### 4) Validate
-
-- Run `deno lint` and fix issues
-- Run `deno test -A` until all tests pass
-- Iterate until clean
-
-### 5) Update Story (Allowed Sections ONLY)
-
-CRITICAL: Dev agent is ONLY authorized to update these sections of the story file. Do not modify any other sections (e.g., QA Results, Story, Acceptance Criteria, Dev Notes, Testing):
-
-- Tasks / Subtasks Checkboxes (mark any fix subtask you added as done)
-- Dev Agent Record →
-  - Agent Model Used (if changed)
-  - Debug Log References (commands/results, e.g., lint/tests)
-  - Completion Notes List (what changed, why, how)
-  - File List (all added/modified/deleted files)
-- Change Log (new dated entry describing applied fixes)
-- Status (see Rule below)
-
-Status Rule:
-
-- If gate was PASS and all identified gaps are closed → set `Status: Ready for Done`
-- Otherwise → set `Status: Ready for Review` and notify QA to re-run the review
-
-### 6) Do NOT Edit Gate Files
-
-- Dev does not modify gate YAML. If fixes address issues, request QA to re-run `review-story` to update the gate
-
-## Blocking Conditions
-
-- Missing `.bmad-core/core-config.yaml`
-- Story file not found for `story_id`
-- No QA artifacts found (neither gate nor assessments)
-  - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
-
-## Completion Checklist
-
-- deno lint: 0 problems
-- deno test -A: all tests pass
-- All high severity `top_issues` addressed
-- NFR FAIL → resolved; CONCERNS minimized or documented
-- Coverage gaps closed or explicitly documented with rationale
-- Story updated (allowed sections only) including File List and Change Log
-- Status set according to Status Rule
-
-## Example: Story 2.2
-
-Given gate `docs/project/qa/gates/2.2-*.yml` shows
-
-- `coverage_gaps`: Back action behavior untested (AC2)
-- `coverage_gaps`: Centralized dependencies enforcement untested (AC4)
-
-Fix plan:
-
-- Add a test ensuring the Toolkit Menu "Back" action returns to Main Menu
-- Add a static test verifying imports for service/view go through `deps.ts`
-- Re-run lint/tests and update Dev Agent Record + File List accordingly
-
-## Key Principles
-
-- Deterministic, risk-first prioritization
-- Minimal, maintainable changes
-- Tests validate behavior and close gaps
-- Strict adherence to allowed story update areas
-- Gate ownership remains with QA; Dev signals readiness via Status
-==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
-
 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -335,7 +180,6 @@ The LLM will:
 ==================== END: .bmad-core/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
-<!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
 ## Purpose
@@ -473,7 +317,6 @@ Provide a structured validation report including:
 ==================== END: .bmad-core/tasks/validate-next-story.md ====================
 
 ==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent

dist/agents/po.txt

@@ -75,105 +75,30 @@ persona:
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
 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
-  - 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
   - 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:
-  checklists:
-    - change-checklist.md
-    - po-master-checklist.md
   tasks:
-    - correct-course.md
     - 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
 ```
 ==================== END: .bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
-<!-- Powered by BMAD™ Core -->
-# Correct Course Task
-
-## Purpose
-
-- Guide a structured response to a change trigger using the `.bmad-core/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 `.bmad-core/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.
-==================== END: .bmad-core/tasks/correct-course.md ====================
-
 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -263,7 +188,6 @@ The LLM will:
 ==================== END: .bmad-core/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-core/tasks/shard-doc.md ====================
-<!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
 ## Purpose
@@ -451,8 +375,80 @@ Document sharded successfully:
 - Ensure the sharding is reversible (could reconstruct the original from shards)
 ==================== END: .bmad-core/tasks/shard-doc.md ====================
 
+==================== START: .bmad-core/tasks/correct-course.md ====================
+# Correct Course Task
+
+## Purpose
+
+- Guide a structured response to a change trigger using the `.bmad-core/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 `.bmad-core/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.
+==================== END: .bmad-core/tasks/correct-course.md ====================
+
 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
-<!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
 ## Purpose
@@ -590,7 +586,6 @@ Provide a structured validation report including:
 ==================== END: .bmad-core/tasks/validate-next-story.md ====================
 
 ==================== START: .bmad-core/templates/story-tmpl.yaml ====================
-# <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
   name: Story Document
@@ -605,7 +600,7 @@ workflow:
   elicitation: advanced-elicitation
 
 agent_config:
-  editable_sections:
+  editable_sections: 
     - Status
     - Story
     - Acceptance Criteria
@@ -622,7 +617,7 @@ sections:
     instruction: Select the current status of the story
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: story
     title: Story
     type: template-text
@@ -634,7 +629,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: acceptance-criteria
     title: Acceptance Criteria
     type: numbered-list
@@ -642,7 +637,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: tasks-subtasks
     title: Tasks / Subtasks
     type: bullet-list
@@ -659,7 +654,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: dev-notes
     title: Dev Notes
     instruction: |
@@ -683,7 +678,7 @@ sections:
         elicit: true
         owner: scrum-master
         editors: [scrum-master]
-
+        
   - id: change-log
     title: Change Log
     type: table
@@ -691,7 +686,7 @@ sections:
     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
@@ -704,25 +699,25 @@ sections:
         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
@@ -730,194 +725,7 @@ sections:
     editors: [qa-agent]
 ==================== END: .bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
-# 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.
-
----
-==================== END: .bmad-core/checklists/change-checklist.md ====================
-
 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # 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.
@@ -933,7 +741,7 @@ First, determine the project type by checking:
 
 2. Is this a BROWNFIELD project (enhancing existing system)?
    - Look for: References to existing codebase, enhancement/modification language
-   - Check for: prd.md, architecture.md, existing system analysis
+   - 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
@@ -951,8 +759,8 @@ For GREENFIELD projects:
 
 For BROWNFIELD projects:
 
-- prd.md - The brownfield enhancement requirements
-- architecture.md - The enhancement architecture
+- 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
@@ -1351,3 +1159,188 @@ After presenting the report, ask if the user wants:
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
 ==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+
+==================== START: .bmad-core/checklists/change-checklist.md ====================
+# 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.
+
+---
+==================== END: .bmad-core/checklists/change-checklist.md ====================

dist/agents/sm.txt

@@ -68,98 +68,23 @@ persona:
     - You are NOT allowed to implement stories or modify code EVER!
 commands:
   - help: Show numbered list of the following commands to allow selection
-  - correct-course: Execute task correct-course.md
   - 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:
-  checklists:
-    - story-draft-checklist.md
   tasks:
-    - correct-course.md
     - create-next-story.md
     - execute-checklist.md
+    - correct-course.md
   templates:
     - story-tmpl.yaml
+  checklists:
+    - story-draft-checklist.md
 ```
 ==================== END: .bmad-core/agents/sm.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
-<!-- Powered by BMAD™ Core -->
-# Correct Course Task
-
-## Purpose
-
-- Guide a structured response to a change trigger using the `.bmad-core/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 `.bmad-core/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.
-==================== END: .bmad-core/tasks/correct-course.md ====================
-
 ==================== START: .bmad-core/tasks/create-next-story.md ====================
-<!-- Powered by BMAD™ Core -->
 # Create Next Story Task
 
 ## Purpose
@@ -275,7 +200,6 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
 ==================== END: .bmad-core/tasks/create-next-story.md ====================
 
 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -364,8 +288,80 @@ The LLM will:
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
 ==================== END: .bmad-core/tasks/execute-checklist.md ====================
 
+==================== START: .bmad-core/tasks/correct-course.md ====================
+# Correct Course Task
+
+## Purpose
+
+- Guide a structured response to a change trigger using the `.bmad-core/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 `.bmad-core/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.
+==================== END: .bmad-core/tasks/correct-course.md ====================
+
 ==================== START: .bmad-core/templates/story-tmpl.yaml ====================
-# <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
   name: Story Document
@@ -380,7 +376,7 @@ workflow:
   elicitation: advanced-elicitation
 
 agent_config:
-  editable_sections:
+  editable_sections: 
     - Status
     - Story
     - Acceptance Criteria
@@ -397,7 +393,7 @@ sections:
     instruction: Select the current status of the story
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: story
     title: Story
     type: template-text
@@ -409,7 +405,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: acceptance-criteria
     title: Acceptance Criteria
     type: numbered-list
@@ -417,7 +413,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master]
-
+    
   - id: tasks-subtasks
     title: Tasks / Subtasks
     type: bullet-list
@@ -434,7 +430,7 @@ sections:
     elicit: true
     owner: scrum-master
     editors: [scrum-master, dev-agent]
-
+    
   - id: dev-notes
     title: Dev Notes
     instruction: |
@@ -458,7 +454,7 @@ sections:
         elicit: true
         owner: scrum-master
         editors: [scrum-master]
-
+        
   - id: change-log
     title: Change Log
     type: table
@@ -466,7 +462,7 @@ sections:
     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
@@ -479,25 +475,25 @@ sections:
         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
@@ -506,7 +502,6 @@ sections:
 ==================== END: .bmad-core/templates/story-tmpl.yaml ====================
 
 ==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
-<!-- Powered by BMAD™ Core -->
 # 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.