chore: remove deprecated CLAUDE.md documentation file

BREAKING CHANGE: Promote beta features to stable release for v5.0.0

This commit ensures the stable release gets properly published to NPM and GitHub releases.

.github/workflows/manual-release.yaml

@@ -1,173 +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
-    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: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/promote-to-stable.yaml

@@ -0,0 +1,122 @@
+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
+
+          echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
+          echo "Promoting from $CURRENT_VERSION to $NEW_VERSION"
+
+      - name: Update package.json versions
+        run: |
+          # Update main package.json
+          npm version ${{ steps.version.outputs.new_version }} --no-git-tag-version
+
+          # Update installer package.json
+          sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
+
+      - name: Update package-lock.json
+        run: npm install --package-lock-only
+
+      - name: Commit stable release
+        run: |
+          git add .
+          git commit -m "release: promote to stable ${{ steps.version.outputs.new_version }}
+
+          - 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,74 @@
+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: ${{ github.event_name != 'push' || !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
+      - name: Clean changelog formatting
+        if: github.event_name == 'push'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          # Remove any Claude Code attribution from changelog
+          sed -i '/🤖 Generated with \[Claude Code\]/,+2d' CHANGELOG.md || true
+          # Format and commit if changes exist
+          npm run format
+          if ! git diff --quiet CHANGELOG.md; then
+            git add CHANGELOG.md
+            git commit -m "chore: clean changelog formatting [skip ci]"
+            git push
+          fi

.gitignore

@@ -43,4 +43,4 @@ CLAUDE.md
 test-project-install/*
 sample-project/*
 flattened-codebase.xml
-*.stats.md
+

.releaserc.json

@@ -0,0 +1,27 @@
+{
+  "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",
+        "changelogTitle": ""
+      }
+    ],
+    "@semantic-release/npm",
+    "./tools/semantic-release-sync-installer.js",
+    "@semantic-release/github"
+  ]
+}

README.md

@@ -75,8 +75,6 @@ This makes it easy to benefit from the latest improvements, bug fixes, and new a
 
 ```bash
 npx bmad-method install
-# OR explicitly use stable tag:
-npx bmad-method@stable install
 # OR if you already have BMad installed:
 git pull
 npm run install:bmad

bmad-core/agents/analyst.md

@@ -17,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
@@ -27,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

bmad-core/agents/architect.md

@@ -17,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
@@ -27,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

bmad-core/agents/bmad-master.md

@@ -17,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
@@ -27,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: 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

bmad-core/agents/bmad-orchestrator.md

@@ -17,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,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

bmad-core/agents/dev.md

@@ -17,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
@@ -30,7 +29,7 @@ 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
@@ -66,13 +65,11 @@ 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"
-- review-qa: run task `apply-qa-fixes.md'
 
 dependencies:
   tasks:
     - execute-checklist.md
     - validate-next-story.md
-    - apply-qa-fixes.md
   checklists:
     - story-dod-checklist.md
 ```

bmad-core/agents/pm.md

@@ -17,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
@@ -27,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

bmad-core/agents/po.md

@@ -17,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
@@ -27,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

bmad-core/agents/qa.md

@@ -17,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
@@ -27,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: Quinn
   id: qa
@@ -65,9 +64,9 @@ commands:
   - 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 directory from qa.qaLocation/gates/
+  - 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

bmad-core/agents/sm.md

@@ -17,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
@@ -27,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

bmad-core/agents/ux-expert.md

@@ -17,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
@@ -27,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

bmad-core/core-config.yaml

@@ -1,6 +1,4 @@
 markdownExploder: true
-qa:
-  qaLocation: docs/qa
 prd:
   prdFile: docs/prd.md
   prdVersion: v4

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

@@ -1,148 +0,0 @@
-# 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/nfr-assess.md

@@ -7,11 +7,11 @@ 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_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
 ```
 
@@ -20,7 +20,7 @@ optional:
 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
 
@@ -123,7 +123,7 @@ 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}
@@ -162,7 +162,7 @@ Reviewer: Quinn
 **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
@@ -170,7 +170,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 **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

bmad-core/tasks/qa-gate.md

@@ -14,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:
 
@@ -124,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`
 
@@ -149,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

@@ -167,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
 
@@ -183,9 +183,9 @@ 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:
 
@@ -308,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

@@ -105,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)
@@ -182,7 +182,7 @@ risk_summary:
 
 ### 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}
@@ -290,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
@@ -339,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/test-design.md

@@ -84,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}
@@ -150,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

@@ -95,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'
+  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:
 
@@ -250,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/templates/qa-gate-tmpl.yaml

@@ -4,7 +4,7 @@ template:
   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)

docs/versioning-and-releases.md

@@ -1,155 +1,77 @@
-# Versioning and Releases
+# How to Release a New Version
 
-BMad Method uses a simplified release system with manual control and automatic release notes generation.
+## Automated Releases (Recommended)
 
-## 🚀 Release Workflow
+The easiest way to release new versions is through **automatic semantic releases**. Just commit with the right message format and push and everything else happens automatically.
 
-### Command Line Release (Recommended)
+### Commit Message Format
 
-The fastest way to create a release with beautiful release notes:
+Use these prefixes to control what type of release happens:
 
 ```bash
-# Preview what will be in the release
-npm run preview:release
-
-# Create a release
-npm run release:patch    # 5.1.0 → 5.1.1 (bug fixes)
-npm run release:minor    # 5.1.0 → 5.2.0 (new features)
-npm run release:major    # 5.1.0 → 6.0.0 (breaking changes)
-
-# Watch the release process
-npm run release:watch
+fix: resolve CLI argument parsing bug      # → patch release (4.1.0 → 4.1.1)
+feat: add new agent orchestration mode     # → minor release (4.1.0 → 4.2.0)
+feat!: redesign CLI interface              # → major release (4.1.0 → 5.0.0)
 ```
 
-### One-Liner Release
+### What Happens Automatically
+
+When you push commits with `fix:` or `feat:`, GitHub Actions will:
+
+1. ✅ Analyze your commit messages
+2. ✅ Bump version in `package.json`
+3. ✅ Generate changelog
+4. ✅ Create git tag
+5. ✅ **Publish to NPM automatically**
+6. ✅ Create GitHub release with notes
+
+### Your Simple Workflow
 
 ```bash
-npm run preview:release && npm run release:minor && npm run release:watch
+# Make your changes
+git add .
+git commit -m "feat: add team collaboration mode"
+git push
+
+# That's it! Release happens automatically 🎉
+# Users can now run: npx bmad-method (and get the new version)
 ```
 
-## 📝 What Happens Automatically
+### Commits That DON'T Trigger Releases
 
-When you trigger a release, the GitHub Actions workflow automatically:
-
-1. ✅ **Validates** - Runs tests, linting, and formatting checks
-2. ✅ **Bumps Version** - Updates `package.json` and installer version
-3. ✅ **Generates Release Notes** - Categorizes commits since last release:
-   - ✨ **New Features** (`feat:`, `Feature:`)
-   - 🐛 **Bug Fixes** (`fix:`, `Fix:`)
-   - 🔧 **Maintenance** (`chore:`, `Chore:`)
-   - 📦 **Other Changes** (everything else)
-4. ✅ **Creates Git Tag** - Tags the release version
-5. ✅ **Publishes to NPM** - With `@latest` tag for user installations
-6. ✅ **Creates GitHub Release** - With formatted release notes
-
-## 📋 Sample Release Notes
-
-The workflow automatically generates professional release notes like this:
-
-````markdown
-## 🚀 What's New in v5.2.0
-
-### ✨ New Features
-
-- feat: add team collaboration mode
-- feat: enhance CLI with interactive prompts
-
-### 🐛 Bug Fixes
-
-- fix: resolve installation path issues
-- fix: handle edge cases in agent loading
-
-### 🔧 Maintenance
-
-- chore: update dependencies
-- chore: improve error messages
-
-## 📦 Installation
+These commit types won't create releases (use them for maintenance):
 
 ```bash
-npx bmad-method install
+chore: update dependencies     # No release
+docs: fix typo in readme      # No release
+style: format code            # No release
+test: add unit tests          # No release
 ```
-````
 
-**Full Changelog**: https://github.com/bmadcode/BMAD-METHOD/compare/v5.1.0...v5.2.0
-
-````
-
-## 🎯 User Installation
-
-After any release, users can immediately get the new version with:
+### Test Your Setup
 
 ```bash
-npx bmad-method install    # Always gets latest release
+npm run release:test    # Safe to run locally - tests the config
 ```
 
-## 📊 Preview Before Release
+---
 
-Always preview what will be included in your release:
+## Manual Release Methods (Exceptions Only)
+
+⚠️ Only use these methods if you need to bypass the automatic system
+
+### Quick Manual Version Bump
 
 ```bash
-npm run preview:release
+npm run version:patch   # 4.1.0 → 4.1.1 (bug fixes)
+npm run version:minor   # 4.1.0 → 4.2.0 (new features)
+npm run version:major   # 4.1.0 → 5.0.0 (breaking changes)
+
+# Then manually publish:
+npm publish
+git push && git push --tags
 ```
 
-This shows:
+### Manual GitHub Actions Trigger
 
-- Commits since last release
-- Categorized changes
-- Estimated next version
-- Release notes preview
-
-## 🔧 Manual Release (GitHub UI)
-
-You can also trigger releases through GitHub Actions:
-
-1. Go to **GitHub Actions** → **Manual Release**
-2. Click **"Run workflow"**
-3. Choose version bump type (patch/minor/major)
-4. Everything else happens automatically
-
-## 📈 Version Strategy
-
-- **Patch** (5.1.0 → 5.1.1): Bug fixes, minor improvements
-- **Minor** (5.1.0 → 5.2.0): New features, enhancements
-- **Major** (5.1.0 → 6.0.0): Breaking changes, major redesigns
-
-## 🛠️ Development Workflow
-
-1. **Develop Freely** - Merge PRs to main without triggering releases
-2. **Test Unreleased Changes** - Clone repo to test latest main branch
-3. **Release When Ready** - Use command line or GitHub Actions to cut releases
-4. **Users Get Updates** - Via simple `npx bmad-method install` command
-
-This gives you complete control over when releases happen while automating all the tedious parts like version bumping, release notes, and publishing.
-
-## 🔍 Troubleshooting
-
-### Check Release Status
-
-```bash
-gh run list --workflow="Manual Release"
-npm view bmad-method dist-tags
-git tag -l | sort -V | tail -5
-```
-
-### View Latest Release
-
-```bash
-gh release view --web
-npm view bmad-method versions --json
-```
-
-### If Version Sync Needed
-
-If your local files don't match the published version after a release:
-
-```bash
-./sync-version.sh    # Automatically syncs local files with npm latest
-```
-
-### If Release Fails
-
-- Check GitHub Actions logs: `gh run view <run-id> --log-failed`
-- Verify NPM tokens are configured
-- Ensure branch protection allows workflow pushes
-````
+You can also trigger releases manually through GitHub Actions workflow dispatch if needed.

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.1 Agent Team Configuration Templates/2.1.1 - Blank Team Template.yaml

@@ -1,15 +0,0 @@
-bundle:
-  name: {{TEAM_DISPLAY_NAME}}
-  icon: {{TEAM_EMOJI}}
-  description: {{TEAM_DESCRIPTION}}
-
-agents:
-  - {{ORCHESTRATOR_AGENT_ID}}
-  - {{SPECIALIST_AGENT_1_ID}}
-  - {{SPECIALIST_AGENT_2_ID}}
-  - {{SPECIALIST_AGENT_N_ID}}
-
-workflows:
-  - {{PRIMARY_WORKFLOW_NAME}}
-  - {{SECONDARY_WORKFLOW_NAME}}
-  - {{SPECIALIZED_WORKFLOW_NAME}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.1 Agent Team Configuration Templates/2.1.2 - Team Structure Templates by Business Function/2.1.2.1 - Strategic Leadership Team Template.yaml

@@ -1,14 +0,0 @@
-bundle:
-  name: {{COMPANY_NAME}} Strategic Leadership Team
-  icon: 🎯
-  description: Executive leadership team providing strategic direction, operational oversight, and business planning for {{INDUSTRY}} {{BUSINESS_TYPE}}.
-
-agents:
-  - {{COMPANY_PREFIX}}-ceo-orchestrator
-  - operations-manager
-  - business-development-manager
-
-workflows:
-  - strategic-planning
-  - business-development
-  - operational-optimization

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.1 Agent Team Configuration Templates/2.1.2 - Team Structure Templates by Business Function/2.1.2.2 - Product Development Team Template.yaml

@@ -1,15 +0,0 @@
-bundle:
-  name: {{PRODUCT_TYPE}} Development Team
-  icon: 🔬
-  description: Product development team specializing in {{PRODUCT_TYPE}} innovation from concept through technical specification.
-
-agents:
-  - {{PRODUCT_PREFIX}}-development-orchestrator
-  - product-designer
-  - technical-specialist
-  - quality-engineer
-
-workflows:
-  - product-development-workflow
-  - innovation-process
-  - quality-validation-workflow

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.2 Individual Agent Definition Templates/2.2.1 - Master Agent Template.yaml

@@ -1,80 +0,0 @@
-CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-activation-instructions:
-  - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-  - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-  - The customization field ALWAYS takes precedence over any conflicting instructions
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-
-agent:
-  name: {{AGENT_CHARACTER_NAME}}
-  id: {{AGENT_ID}}
-  title: {{AGENT_PROFESSIONAL_TITLE}}
-  icon: {{AGENT_EMOJI}}
-  whenToUse: {{WHEN_TO_USE_DESCRIPTION}}
-  customization: null
-
-persona:
-  role: {{PROFESSIONAL_ROLE_DESCRIPTION}}
-  style: {{COMMUNICATION_STYLE}}
-  identity: |
-    I'm {{AGENT_CHARACTER_NAME}}, {{PROFESSIONAL_TITLE}} with {{YEARS_EXPERIENCE}}+ years in {{DOMAIN_EXPERTISE}}. 
-    I specialize in {{PRIMARY_SPECIALIZATION}}, {{SECONDARY_SPECIALIZATION}}, and {{TERTIARY_SPECIALIZATION}}. 
-    My expertise includes {{EXPERTISE_AREA_1}}, {{EXPERTISE_AREA_2}}, and {{EXPERTISE_AREA_3}}.
-  focus: |
-    {{PRIMARY_FOCUS}}, {{SECONDARY_FOCUS}}, {{TERTIARY_FOCUS}}, 
-    {{WORKFLOW_FOCUS}}, {{QUALITY_FOCUS}}, {{INNOVATION_FOCUS}}
-
-core_principles:
-  - {{PRINCIPLE_1}}
-  - {{PRINCIPLE_2}}
-  - {{PRINCIPLE_3}}
-  - {{PRINCIPLE_4}}
-  - {{PRINCIPLE_5}}
-
-startup:
-  - Greet as "{{AGENT_CHARACTER_NAME}}, {{PROFESSIONAL_TITLE}}"
-  - Explain {{DOMAIN_EXPERTISE}} background and readiness to help
-  - Present numbered options for {{PRIMARY_CAPABILITY_AREA}}
-  - CRITICAL: Do NOT automatically execute any commands during startup
-  - Ask about current {{DOMAIN_SPECIFIC_CHALLENGES}} or priorities
-
-commands:
-  - '*help' - Show numbered list of all available {{DOMAIN}} commands
-  - '*chat-mode' - Open discussion about {{DOMAIN_EXPERTISE}} and {{SPECIALIZATION_AREA}}
-  - '*create-doc {{PRIMARY_TEMPLATE}}' - Generate {{PRIMARY_DOCUMENT_TYPE}}
-  - '*create-doc {{SECONDARY_TEMPLATE}}' - Create {{SECONDARY_DOCUMENT_TYPE}}
-  - '*{{PRIMARY_TASK}}' - {{PRIMARY_TASK_DESCRIPTION}}
-  - '*{{SECONDARY_TASK}}' - {{SECONDARY_TASK_DESCRIPTION}}
-  - '*{{ANALYSIS_TASK}}' - {{ANALYSIS_TASK_DESCRIPTION}}
-  - '*exit' - Say goodbye as {{AGENT_CHARACTER_NAME}} and abandon this persona
-
-dependencies:
-  tasks:
-    - create-doc
-    - execute-checklist
-    - {{PRIMARY_TASK}}
-    - {{SECONDARY_TASK}}
-    - {{ANALYSIS_TASK}}
-    - {{COORDINATION_TASK}}
-    
-  templates:
-    - {{PRIMARY_TEMPLATE}}
-    - {{SECONDARY_TEMPLATE}}
-    - {{REPORTING_TEMPLATE}}
-    - {{ANALYSIS_TEMPLATE}}
-    
-  checklists:
-    - {{PRIMARY_CHECKLIST}}
-    - {{QUALITY_CHECKLIST}}
-    - {{COMPLIANCE_CHECKLIST}}
-    
-  data:
-    - {{DOMAIN_KNOWLEDGE_FILE}}
-    - {{STANDARDS_FILE}}
-    - {{BEST_PRACTICES_FILE}}
-    
-  utils:
-    - template-format
-    - workflow-management
-    - {{DOMAIN_SPECIFIC_UTILS}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.2 Individual Agent Definition Templates/2.2.2 - Orchestrator Agent Template.yaml

@@ -1,47 +0,0 @@
-agent:
-  name: {{ORCHESTRATOR_CHARACTER_NAME}}
-  id: {{COMPANY_PREFIX}}-{{DOMAIN}}-orchestrator
-  title: {{ORCHESTRATOR_TITLE}}
-  icon: {{ORCHESTRATOR_EMOJI}}
-  
-persona:
-  role: {{DOMAIN}} orchestration specialist with {{INDUSTRY}} expertise
-  style: {{LEADERSHIP_STYLE}}, {{COORDINATION_APPROACH}}, {{COMMUNICATION_STYLE}}
-  identity: |
-    I'm {{ORCHESTRATOR_CHARACTER_NAME}}, {{ORCHESTRATOR_TITLE}} with {{YEARS_EXPERIENCE}}+ years in {{DOMAIN}} {{INDUSTRY}}. 
-    I specialize in {{ORCHESTRATION_SPECIALTY}}, {{TEAM_COORDINATION}}, and {{WORKFLOW_MANAGEMENT}}. 
-    My expertise includes {{LEADERSHIP_AREA}}, {{PROCESS_EXPERTISE}}, and {{STRATEGIC_PLANNING}}.
-  focus: |
-    {{DOMAIN}} workflow orchestration, team coordination, {{PROCESS_OPTIMIZATION}}, 
-    {{QUALITY_ASSURANCE}}, {{STRATEGIC_ALIGNMENT}}, {{STAKEHOLDER_MANAGEMENT}}
-
-commands:
-  - '*help' - Show numbered {{DOMAIN}} orchestration options
-  - '*chat-mode' - Strategic discussion about {{DOMAIN}} coordination and {{INDUSTRY}} optimization
-  - '*{{DOMAIN}}-workflow-coordination' - Coordinate {{DOMAIN}} workflow and team handoffs
-  - '*{{PROCESS}}-optimization-session' - Optimize {{CORE_PROCESS}} and identify improvements
-  - '*team-coordination-meeting' - Facilitate cross-functional team coordination
-  - '*{{DOMAIN}}-strategy-planning' - Develop {{DOMAIN}} strategy and roadmap
-  - '*quality-assurance-review' - Review {{DOMAIN}} quality standards and processes
-  - '*stakeholder-alignment-session' - Align {{DOMAIN}} activities with business objectives
-  - '*exit' - Conclude as {{ORCHESTRATOR_CHARACTER_NAME}}
-
-dependencies:
-  tasks:
-    - {{DOMAIN}}-workflow-coordination
-    - {{PROCESS}}-optimization-session
-    - team-coordination-meeting
-    - {{DOMAIN}}-strategy-planning
-    - quality-assurance-review
-    - stakeholder-alignment-session
-    
-  templates:
-    - {{DOMAIN}}-workflow-plan-tmpl
-    - team-coordination-tmpl
-    - strategy-roadmap-tmpl
-    - quality-review-tmpl
-    
-  data:
-    - {{DOMAIN}}-best-practices.md
-    - {{INDUSTRY}}-standards.md
-    - workflow-optimization-guide.md

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.2 Individual Agent Definition Templates/2.2.3 - Specialist Agent Template.yaml

@@ -1,47 +0,0 @@
-agent:
-  name: {{SPECIALIST_CHARACTER_NAME}}
-  id: {{SPECIALIST_ID}}
-  title: {{SPECIALIST_TITLE}}
-  icon: {{SPECIALIST_EMOJI}}
-  
-persona:
-  role: {{SPECIALIZATION}} expert with {{DOMAIN}} focus
-  style: {{EXPERTISE_STYLE}}, {{APPROACH}}, {{METHODOLOGY}}
-  identity: |
-    I'm {{SPECIALIST_CHARACTER_NAME}}, {{SPECIALIST_TITLE}} with {{YEARS_EXPERIENCE}}+ years in {{SPECIALIZATION}}. 
-    I focus on {{SPECIALTY_AREA_1}}, {{SPECIALTY_AREA_2}}, and {{SPECIALTY_AREA_3}}. 
-    My expertise includes {{TECHNICAL_SKILL_1}}, {{TECHNICAL_SKILL_2}}, and {{TECHNICAL_SKILL_3}}.
-  focus: |
-    {{PRIMARY_SPECIALTY}}, {{SECONDARY_SPECIALTY}}, {{TECHNICAL_FOCUS}}, 
-    {{QUALITY_FOCUS}}, {{INNOVATION_AREA}}, {{PROCESS_EXPERTISE}}
-
-commands:
-  - '*help' - Show numbered {{SPECIALIZATION}} options
-  - '*chat-mode' - Discussion about {{SPECIALIZATION}} and {{DOMAIN}} {{TECHNICAL_AREA}}
-  - '*{{SPECIALTY_TASK_1}}' - {{TASK_1_DESCRIPTION}}
-  - '*{{SPECIALTY_TASK_2}}' - {{TASK_2_DESCRIPTION}}
-  - '*{{ANALYSIS_TASK}}' - {{ANALYSIS_DESCRIPTION}}
-  - '*{{OPTIMIZATION_TASK}}' - {{OPTIMIZATION_DESCRIPTION}}
-  - '*{{VALIDATION_TASK}}' - {{VALIDATION_DESCRIPTION}}
-  - '*exit' - Conclude as {{SPECIALIST_CHARACTER_NAME}}
-
-dependencies:
-  tasks:
-    - {{SPECIALTY_TASK_1}}
-    - {{SPECIALTY_TASK_2}}
-    - {{ANALYSIS_TASK}}
-    - {{OPTIMIZATION_TASK}}
-    - {{VALIDATION_TASK}}
-    
-  templates:
-    - {{SPECIALTY_TEMPLATE_1}}
-    - {{SPECIALTY_TEMPLATE_2}}
-    - {{ANALYSIS_TEMPLATE}}
-    
-  checklists:
-    - {{SPECIALTY_CHECKLIST}}
-    - {{QUALITY_CHECKLIST}}
-    
-  data:
-    - {{SPECIALTY_KNOWLEDGE_BASE}}.md
-    - {{TECHNICAL_STANDARDS}}.md

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.3 Task Templates/2.3.1 - Generic Task Template.md

@@ -1,43 +0,0 @@
-# {{TASK_NAME}} Task
-
-## Purpose
-{{TASK_PURPOSE_DESCRIPTION}}
-
-## Process
-1. **{{STEP_1_NAME}}**
-   - {{STEP_1_ACTION_1}}
-   - {{STEP_1_ACTION_2}}
-   - {{STEP_1_ACTION_3}}
-
-2. **{{STEP_2_NAME}}**
-   - {{STEP_2_ACTION_1}}
-   - {{STEP_2_ACTION_2}}
-   - {{STEP_2_ACTION_3}}
-
-3. **{{STEP_3_NAME}}**
-   - {{STEP_3_ACTION_1}}
-   - {{STEP_3_ACTION_2}}
-   - {{STEP_3_ACTION_3}}
-
-4. **{{FINAL_STEP_NAME}}**
-   - {{FINAL_ACTION_1}}
-   - {{FINAL_ACTION_2}}
-   - {{FINAL_ACTION_3}}
-
-## Required Inputs
-- {{INPUT_1}}
-- {{INPUT_2}}
-- {{INPUT_3}}
-- {{INPUT_4}}
-
-## Expected Outputs
-- {{OUTPUT_1}}
-- {{OUTPUT_2}}
-- {{OUTPUT_3}}
-- {{OUTPUT_4}}
-
-## Quality Validation
-- {{VALIDATION_CRITERIA_1}}
-- {{VALIDATION_CRITERIA_2}}
-- {{VALIDATION_CRITERIA_3}}
-- {{VALIDATION_CRITERIA_4}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.3 Task Templates/2.3.2 - Analysis Task Template.md

@@ -1,44 +0,0 @@
-# {{ANALYSIS_TYPE}} Analysis Task
-
-## Purpose
-Conduct comprehensive {{ANALYSIS_TYPE}} analysis for {{DOMAIN}} {{SUBJECT_AREA}}, evaluating {{PRIMARY_CRITERIA}} against {{EVALUATION_STANDARDS}}.
-
-## Process
-1. **Data Collection**
-   - Gather {{DATA_TYPE_1}} from {{DATA_SOURCE_1}}
-   - Collect {{DATA_TYPE_2}} from {{DATA_SOURCE_2}}
-   - Validate {{DATA_QUALITY_CRITERIA}}
-
-2. **{{ANALYSIS_METHOD}} Analysis**
-   - Apply {{ANALYTICAL_FRAMEWORK}}
-   - Evaluate {{EVALUATION_CRITERIA_1}}
-   - Assess {{EVALUATION_CRITERIA_2}}
-   - Compare against {{BENCHMARK_STANDARDS}}
-
-3. **{{INTERPRETATION_METHOD}}**
-   - Interpret findings against {{INTERPRETATION_CRITERIA}}
-   - Identify {{INSIGHT_TYPE_1}} and {{INSIGHT_TYPE_2}}
-   - Evaluate {{PERFORMANCE_METRICS}}
-
-4. **Recommendations Development**
-   - Develop {{RECOMMENDATION_TYPE_1}}
-   - Create {{RECOMMENDATION_TYPE_2}}
-   - Prioritize actions based on {{PRIORITIZATION_CRITERIA}}
-
-## Required Inputs
-- {{ANALYSIS_DATA_SOURCE}}
-- {{EVALUATION_STANDARDS}}
-- {{COMPARISON_BENCHMARKS}}
-- {{ANALYSIS_PARAMETERS}}
-
-## Expected Outputs
-- Comprehensive {{ANALYSIS_TYPE}} analysis report
-- {{INSIGHT_TYPE}} identification and evaluation
-- {{RECOMMENDATION_TYPE}} with implementation guidance
-- {{METRICS_TYPE}} and performance indicators
-
-## Quality Validation
-- {{ANALYSIS_ACCURACY_CRITERIA}}
-- {{METHODOLOGY_COMPLIANCE}}
-- {{INSIGHT_VALIDITY_CHECK}}
-- {{RECOMMENDATION_FEASIBILITY_ASSESSMENT}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.3 Task Templates/2.3.3 - Creation Task Template.md

@@ -1,43 +0,0 @@
-# {{CREATION_OBJECT}} Creation Task
-
-## Purpose
-Create comprehensive {{CREATION_OBJECT}} for {{TARGET_AUDIENCE}}, ensuring {{QUALITY_STANDARDS}} and {{COMPLIANCE_REQUIREMENTS}}.
-
-## Process
-1. **Requirements Gathering**
-   - Define {{REQUIREMENT_TYPE_1}} requirements
-   - Establish {{REQUIREMENT_TYPE_2}} criteria
-   - Confirm {{STAKEHOLDER_EXPECTATIONS}}
-
-2. **{{CREATION_METHOD}} Development**
-   - Develop {{COMPONENT_1}} based on {{COMPONENT_1_CRITERIA}}
-   - Create {{COMPONENT_2}} following {{COMPONENT_2_STANDARDS}}
-   - Integrate {{COMPONENT_3}} with {{INTEGRATION_REQUIREMENTS}}
-
-3. **Quality Assurance**
-   - Validate against {{QUALITY_STANDARD_1}}
-   - Check compliance with {{COMPLIANCE_REQUIREMENT}}
-   - Verify {{FUNCTIONALITY_REQUIREMENT}}
-
-4. **Finalization and Delivery**
-   - Format according to {{FORMATTING_STANDARDS}}
-   - Include {{SUPPORTING_DOCUMENTATION}}
-   - Prepare for {{DELIVERY_METHOD}}
-
-## Required Inputs
-- {{INPUT_SPECIFICATION_1}}
-- {{INPUT_SPECIFICATION_2}}
-- {{REFERENCE_MATERIALS}}
-- {{STAKEHOLDER_REQUIREMENTS}}
-
-## Expected Outputs
-- Complete {{CREATION_OBJECT}}
-- {{SUPPORTING_DOCUMENTATION_TYPE}}
-- {{QUALITY_VALIDATION_REPORT}}
-- {{DELIVERY_PACKAGE}}
-
-## Quality Validation
-- {{COMPLETENESS_CRITERIA}}
-- {{ACCURACY_STANDARDS}}
-- {{COMPLIANCE_VERIFICATION}}
-- {{STAKEHOLDER_APPROVAL}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.4 Document Templates/2.4.1 - Master Document Template.md

@@ -1,64 +0,0 @@
-# {{DOCUMENT_TITLE}}
-
-[[LLM: This template {{DOCUMENT_PURPOSE}}. Ensure {{LLM_GUIDANCE_1}} and {{LLM_GUIDANCE_2}} are thoroughly addressed.]]
-
-## {{SECTION_1_TITLE}}
-
-### {{SUBSECTION_1_1_TITLE}}
-**{{FIELD_1_LABEL}}**: {{FIELD_1_VARIABLE}}
-**{{FIELD_2_LABEL}}**: {{FIELD_2_VARIABLE}}
-**{{FIELD_3_LABEL}}**: {{FIELD_3_VARIABLE}}
-
-**{{DESCRIPTION_FIELD_LABEL}}**: {{DESCRIPTION_VARIABLE}}
-[[LLM: {{LLM_SECTION_1_GUIDANCE}}]]
-
-### {{SUBSECTION_1_2_TITLE}}
-**{{FIELD_4_LABEL}}**: {{FIELD_4_VARIABLE}}
-**{{FIELD_5_LABEL}}**: {{FIELD_5_VARIABLE}}
-**{{FIELD_6_LABEL}}**: {{FIELD_6_VARIABLE}}
-
-[[LLM: {{LLM_SUBSECTION_GUIDANCE}}]]
-
-## {{SECTION_2_TITLE}}
-
-### {{SUBSECTION_2_1_TITLE}}
-**{{SPECIFICATION_1_LABEL}}**: {{SPECIFICATION_1_VARIABLE}}
-**{{SPECIFICATION_2_LABEL}}**: {{SPECIFICATION_2_VARIABLE}}
-**{{SPECIFICATION_3_LABEL}}**: {{SPECIFICATION_3_VARIABLE}}
-
-### {{SUBSECTION_2_2_TITLE}}
-**{{REQUIREMENT_1_LABEL}}**: {{REQUIREMENT_1_VARIABLE}}
-**{{REQUIREMENT_2_LABEL}}**: {{REQUIREMENT_2_VARIABLE}}
-**{{REQUIREMENT_3_LABEL}}**: {{REQUIREMENT_3_VARIABLE}}
-
-[[LLM: {{LLM_REQUIREMENTS_GUIDANCE}}]]
-
-## {{SECTION_3_TITLE}}
-
-### {{CONDITIONAL_SECTION_TITLE}}
-^^CONDITION: {{CONDITION_VARIABLE}} == "{{CONDITION_VALUE}}"^^
-**{{CONDITIONAL_FIELD_1}}**: {{CONDITIONAL_VALUE_1}}
-**{{CONDITIONAL_FIELD_2}}**: {{CONDITIONAL_VALUE_2}}
-[[LLM: {{CONDITIONAL_LLM_GUIDANCE}}]]
-^^/CONDITION: {{CONDITION_VARIABLE}}^^
-
-### {{REPEATABLE_SECTION_TITLE}}
-<<REPEAT section="{{REPEAT_SECTION_NAME}}" count="{{REPEAT_COUNT_VARIABLE}}">>
-**{{REPEAT_FIELD_1}}**: {{REPEAT_VALUE_1}}
-**{{REPEAT_FIELD_2}}**: {{REPEAT_VALUE_2}}
-**{{REPEAT_FIELD_3}}**: {{REPEAT_VALUE_3}}
-<</REPEAT>>
-
-## {{APPROVAL_SECTION_TITLE}}
-
-### {{VALIDATION_SUBSECTION_TITLE}}
-- [ ] {{VALIDATION_ITEM_1}}
-- [ ] {{VALIDATION_ITEM_2}}
-- [ ] {{VALIDATION_ITEM_3}}
-
-### {{APPROVAL_SUBSECTION_TITLE}}
-**{{APPROVAL_TYPE_1}}**: {{APPROVAL_STATUS_1}} - {{APPROVAL_DATE_1}}
-**{{APPROVAL_TYPE_2}}**: {{APPROVAL_STATUS_2}} - {{APPROVAL_DATE_2}}
-**{{APPROVAL_TYPE_3}}**: {{APPROVAL_STATUS_3}} - {{APPROVAL_DATE_3}}
-
-[[LLM: {{FINAL_LLM_VALIDATION_GUIDANCE}}]]

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.4 Document Templates/2.4.2 - Strategic Planning Document Template.md

@@ -1,74 +0,0 @@
-# {{DOCUMENT_TYPE}} - {{COMPANY_NAME}}
-
-[[LLM: This template guides {{STAKEHOLDER_ROLE}} through comprehensive {{PLANNING_TYPE}} for {{BUSINESS_FOCUS}}. Ensure all {{DOMAIN_SPECIFIC_CONSIDERATIONS}} are thoroughly addressed.]]
-
-## {{PLANNING_SCOPE}} Overview
-
-### Core Information
-**{{PLAN_IDENTIFIER_LABEL}}**: {{PLAN_IDENTIFIER}}
-**{{PLANNING_PERIOD_LABEL}}**: {{PLANNING_PERIOD}}
-**{{RESPONSIBLE_PARTY_LABEL}}**: {{RESPONSIBLE_PARTY}}
-
-**{{VISION_STATEMENT_LABEL}}**: {{VISION_STATEMENT}}
-[[LLM: {{VISION_GUIDANCE}}]]
-
-### {{TARGET_DEFINITION_SECTION}}
-**{{PRIMARY_TARGET_LABEL}}**: {{PRIMARY_TARGET}}
-**{{SECONDARY_TARGET_LABEL}}**: {{SECONDARY_TARGET}}
-**{{SUCCESS_METRICS_LABEL}}**: {{SUCCESS_METRICS}}
-
-[[LLM: {{TARGET_GUIDANCE}}]]
-
-## {{STRATEGY_SECTION_TITLE}}
-
-### {{STRATEGIC_APPROACH_SUBSECTION}}
-**{{APPROACH_TYPE_1_LABEL}}**: {{APPROACH_TYPE_1}}
-**{{APPROACH_TYPE_2_LABEL}}**: {{APPROACH_TYPE_2}}
-**{{APPROACH_TYPE_3_LABEL}}**: {{APPROACH_TYPE_3}}
-
-### {{STRATEGIC_PRIORITIES_SUBSECTION}}
-{{#each strategic_priorities}}
-**{{priority_name}}**: {{priority_description}}
-- {{implementation_approach}}
-- {{success_criteria}}
-- {{timeline_estimate}}
-{{/each}}
-
-[[LLM: {{STRATEGY_GUIDANCE}}]]
-
-## {{IMPLEMENTATION_SECTION_TITLE}}
-
-### {{PHASE_PLANNING_SUBSECTION}}
-^^CONDITION: {{IMPLEMENTATION_TYPE}} == "{{PHASED_APPROACH}}"^^
-**{{PHASE_1_LABEL}}**: {{PHASE_1_DESCRIPTION}}
-- {{phase_1_deliverables}}
-- {{phase_1_timeline}}
-- {{phase_1_resources}}
-
-**{{PHASE_2_LABEL}}**: {{PHASE_2_DESCRIPTION}}
-- {{phase_2_deliverables}}
-- {{phase_2_timeline}}
-- {{phase_2_resources}}
-^^/CONDITION: {{IMPLEMENTATION_TYPE}}^^
-
-### {{RESOURCE_PLANNING_SUBSECTION}}
-**{{RESOURCE_TYPE_1_LABEL}}**: {{RESOURCE_TYPE_1_REQUIREMENTS}}
-**{{RESOURCE_TYPE_2_LABEL}}**: {{RESOURCE_TYPE_2_REQUIREMENTS}}
-**{{RESOURCE_TYPE_3_LABEL}}**: {{RESOURCE_TYPE_3_REQUIREMENTS}}
-
-## {{MEASUREMENT_SECTION_TITLE}}
-
-### {{KPI_SUBSECTION_TITLE}}
-{{#each key_performance_indicators}}
-**{{kpi_name}}**: 
-- Measurement: {{kpi_measurement_method}}
-- Target: {{kpi_target_value}}
-- Frequency: {{kpi_measurement_frequency}}
-{{/each}}
-
-### {{REVIEW_PROCESS_SUBSECTION}}
-**{{REVIEW_FREQUENCY_LABEL}}**: {{REVIEW_FREQUENCY}}
-**{{REVIEW_PARTICIPANTS_LABEL}}**: {{REVIEW_PARTICIPANTS}}
-**{{ADJUSTMENT_PROCESS_LABEL}}**: {{ADJUSTMENT_PROCESS}}
-
-[[LLM: {{MEASUREMENT_GUIDANCE}}]]

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.4 Document Templates/2.4.3 - Technical Specification Template.md

@@ -1,81 +0,0 @@
-# {{TECHNICAL_DOCUMENT_TYPE}} - {{PROJECT_NAME}}
-
-[[LLM: This comprehensive {{TECHNICAL_DOCUMENT_TYPE}} ensures all {{TECHNICAL_DOMAIN}} requirements are properly documented for {{TARGET_USE_CASE}}.]]
-
-## {{SPECIFICATION_OVERVIEW_SECTION}}
-
-### Basic Information
-**{{SPEC_IDENTIFIER_LABEL}}**: {{SPEC_IDENTIFIER}}
-**{{SPEC_VERSION_LABEL}}**: {{SPEC_VERSION}}
-**{{CREATION_DATE_LABEL}}**: {{CREATION_DATE}}
-**{{RESPONSIBLE_ENGINEER_LABEL}}**: {{RESPONSIBLE_ENGINEER}}
-
-### {{PROJECT_SCOPE_SUBSECTION}}
-**{{PROJECT_TYPE_LABEL}}**: {{PROJECT_TYPE}}
-**{{TARGET_APPLICATION_LABEL}}**: {{TARGET_APPLICATION}}
-**{{COMPLEXITY_LEVEL_LABEL}}**: {{COMPLEXITY_LEVEL}}
-**{{COMPLIANCE_REQUIREMENTS_LABEL}}**: {{COMPLIANCE_REQUIREMENTS}}
-
-[[LLM: {{SCOPE_DEFINITION_GUIDANCE}}]]
-
-## {{TECHNICAL_REQUIREMENTS_SECTION}}
-
-### {{FUNCTIONAL_REQUIREMENTS_SUBSECTION}}
-{{#each functional_requirements}}
-**{{requirement_id}}**: {{requirement_description}}
-- Priority: {{requirement_priority}}
-- Acceptance Criteria: {{acceptance_criteria}}
-- Testing Method: {{testing_method}}
-{{/each}}
-
-### {{PERFORMANCE_REQUIREMENTS_SUBSECTION}}
-**{{PERFORMANCE_METRIC_1_LABEL}}**: {{PERFORMANCE_METRIC_1_VALUE}}
-**{{PERFORMANCE_METRIC_2_LABEL}}**: {{PERFORMANCE_METRIC_2_VALUE}}
-**{{PERFORMANCE_METRIC_3_LABEL}}**: {{PERFORMANCE_METRIC_3_VALUE}}
-
-[[LLM: {{PERFORMANCE_GUIDANCE}}]]
-
-## {{TECHNICAL_ARCHITECTURE_SECTION}}
-
-### {{SYSTEM_DESIGN_SUBSECTION}}
-**{{ARCHITECTURE_PATTERN_LABEL}}**: {{ARCHITECTURE_PATTERN}}
-**{{TECHNOLOGY_STACK_LABEL}}**: {{TECHNOLOGY_STACK}}
-**{{INTEGRATION_APPROACH_LABEL}}**: {{INTEGRATION_APPROACH}}
-
-### {{COMPONENT_SPECIFICATIONS_SUBSECTION}}
-<<REPEAT section="{{COMPONENT_SECTION_NAME}}" count="{{COMPONENT_COUNT}}">>
-**{{component_name}}**: 
-- Function: {{component_function}}
-- Technology: {{component_technology}}
-- Interface: {{component_interface}}
-- Dependencies: {{component_dependencies}}
-<</REPEAT>>
-
-## {{QUALITY_STANDARDS_SECTION}}
-
-### {{TESTING_REQUIREMENTS_SUBSECTION}}
-**{{TEST_TYPE_1_LABEL}}**: {{TEST_TYPE_1_REQUIREMENTS}}
-**{{TEST_TYPE_2_LABEL}}**: {{TEST_TYPE_2_REQUIREMENTS}}
-**{{TEST_TYPE_3_LABEL}}**: {{TEST_TYPE_3_REQUIREMENTS}}
-
-### {{VALIDATION_CRITERIA_SUBSECTION}}
-^^CONDITION: {{VALIDATION_TYPE}} == "{{COMPREHENSIVE_VALIDATION}}"^^
-- [ ] {{VALIDATION_ITEM_1}}
-- [ ] {{VALIDATION_ITEM_2}}
-- [ ] {{VALIDATION_ITEM_3}}
-- [ ] {{VALIDATION_ITEM_4}}
-^^/CONDITION: {{VALIDATION_TYPE}}^^
-
-## {{IMPLEMENTATION_GUIDANCE_SECTION}}
-
-### {{DEVELOPMENT_PROCESS_SUBSECTION}}
-**{{DEVELOPMENT_METHODOLOGY_LABEL}}**: {{DEVELOPMENT_METHODOLOGY}}
-**{{TIMELINE_ESTIMATE_LABEL}}**: {{TIMELINE_ESTIMATE}}
-**{{RESOURCE_REQUIREMENTS_LABEL}}**: {{RESOURCE_REQUIREMENTS}}
-
-### {{DEPLOYMENT_SPECIFICATIONS_SUBSECTION}}
-**{{DEPLOYMENT_ENVIRONMENT_LABEL}}**: {{DEPLOYMENT_ENVIRONMENT}}
-**{{DEPLOYMENT_PROCESS_LABEL}}**: {{DEPLOYMENT_PROCESS}}
-**{{MONITORING_REQUIREMENTS_LABEL}}**: {{MONITORING_REQUIREMENTS}}
-
-[[LLM: {{IMPLEMENTATION_VALIDATION_GUIDANCE}}]]

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.5 Checklist Templates/2.5.1 - Master Checklist Template.md

@@ -1,84 +0,0 @@
-# {{CHECKLIST_TITLE}}
-
-## Pre-{{PROCESS_NAME}} Setup ✓
-- [ ] {{SETUP_ITEM_1}}
-- [ ] {{SETUP_ITEM_2}}
-- [ ] {{SETUP_ITEM_3}}
-- [ ] {{SETUP_ITEM_4}}
-- [ ] {{SETUP_ITEM_5}}
-
-## {{MAIN_PROCESS_SECTION_1}} ✓
-### {{SUBSECTION_1_1_TITLE}}
-- [ ] {{VALIDATION_ITEM_1_1}}
-- [ ] {{VALIDATION_ITEM_1_2}}
-- [ ] {{VALIDATION_ITEM_1_3}}
-- [ ] {{VALIDATION_ITEM_1_4}}
-
-### {{SUBSECTION_1_2_TITLE}}
-- [ ] {{VALIDATION_ITEM_1_5}}
-- [ ] {{VALIDATION_ITEM_1_6}}
-- [ ] {{VALIDATION_ITEM_1_7}}
-- [ ] {{VALIDATION_ITEM_1_8}}
-
-## {{MAIN_PROCESS_SECTION_2}} ✓
-### {{QUALITY_ASSESSMENT_SUBSECTION}}
-- [ ] {{QUALITY_ITEM_1}} within {{TOLERANCE_1}} tolerance
-- [ ] {{QUALITY_ITEM_2}} meets {{STANDARD_2}} requirements
-- [ ] {{QUALITY_ITEM_3}} achieves {{TARGET_3}} performance
-- [ ] {{QUALITY_ITEM_4}} complies with {{REGULATION_4}} standards
-
-### {{DOMAIN_SPECIFIC_ASSESSMENT}}
-- [ ] {{DOMAIN_REQUIREMENT_1}}
-- [ ] {{DOMAIN_REQUIREMENT_2}}
-- [ ] {{DOMAIN_REQUIREMENT_3}}
-- [ ] {{DOMAIN_REQUIREMENT_4}}
-
-## {{VALIDATION_SECTION}} ✓
-### {{CRITERION_TYPE_1}} Analysis
-- [ ] {{ANALYSIS_ITEM_1}}
-- [ ] {{ANALYSIS_ITEM_2}}
-- [ ] {{ANALYSIS_ITEM_3}}
-- [ ] {{ANALYSIS_ITEM_4}}
-
-### {{CRITERION_TYPE_2}} Assessment
-- [ ] {{ASSESSMENT_ITEM_1}}
-- [ ] {{ASSESSMENT_ITEM_2}}
-- [ ] {{ASSESSMENT_ITEM_3}}
-- [ ] {{ASSESSMENT_ITEM_4}}
-
-## {{COMPLIANCE_SECTION}} ✓
-### {{COMPLIANCE_TYPE_1}}
-- [ ] {{COMPLIANCE_ITEM_1}}
-- [ ] {{COMPLIANCE_ITEM_2}}
-- [ ] {{COMPLIANCE_ITEM_3}}
-
-### {{COMPLIANCE_TYPE_2}}
-- [ ] {{COMPLIANCE_ITEM_4}}
-- [ ] {{COMPLIANCE_ITEM_5}}
-- [ ] {{COMPLIANCE_ITEM_6}}
-
-## Quality Gates ✓
-### Approval Criteria (All must pass)
-- [ ] **{{QUALITY_GATE_1}}**: 4+ stars - {{GATE_1_DESCRIPTION}}
-- [ ] **{{QUALITY_GATE_2}}**: 4+ stars - {{GATE_2_DESCRIPTION}}
-- [ ] **{{QUALITY_GATE_3}}**: 4+ stars - {{GATE_3_DESCRIPTION}}
-- [ ] **{{QUALITY_GATE_4}}**: 4+ stars - {{GATE_4_DESCRIPTION}}
-
-### Decision Matrix
-- [ ] **Approve**: All criteria 4+ stars, ready for {{NEXT_PHASE}}
-- [ ] **Revise**: 1-2 criteria below 4 stars, specific improvements needed
-- [ ] **Reject**: 3+ criteria below 4 stars, major revision required
-
-## Documentation Requirements ✓
-- [ ] All {{PROCESS_NAME}} criteria completed and rated
-- [ ] Issues and recommendations clearly documented
-- [ ] {{DOMAIN_SPECIFIC}} observations recorded
-- [ ] Visual documentation captured (if applicable)
-- [ ] {{PROCESS_NAME}} summary completed with clear next steps
-
-## Final Approval ✓
-**{{PROCESS_NAME}} Complete**: {{COMPLETION_DATE}}
-**{{ROLE_1}} Signature**: {{SIGNATURE_1}}
-**{{ROLE_2}} Review**: {{APPROVAL_2}}
-**{{ROLE_3}} Consultation**: {{APPROVAL_3}}
-**Ready for Next Phase**: {{NEXT_PHASE_AUTHORIZATION}}

expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/PART 2 - Agent System Templates/2.5 Checklist Templates/2.5.2 - Quality Validation Checklist Template.md

@@ -1,106 +0,0 @@
-# {{QUALITY_VALIDATION_TYPE}} Quality Checklist
-
-## Pre-Validation Preparation ✓
-- [ ] {{VALIDATION_SUBJECT}} properly configured with {{DOMAIN_REQUIREMENTS}}
-- [ ] {{VALIDATION_CRITERIA}} validated and appropriate for {{TARGET_STANDARD}}
-- [ ] {{DOMAIN_SPECIFIC_PARAMETERS}} accurately input
-- [ ] All {{VALIDATION_COMPONENTS}} properly configured
-- [ ] {{INITIAL_SETUP_REQUIREMENT}} completed
-
-## {{DOMAIN_VALIDATION_SECTION}} ✓
-- [ ] {{DOMAIN_REQUIREMENT_1}} accurately reflects {{STANDARD_1}}
-- [ ] {{DOMAIN_REQUIREMENT_2}} realistic for {{CHARACTERISTIC_2}}
-- [ ] {{DOMAIN_REQUIREMENT_3}} appropriate for {{APPLICATION_3}}
-- [ ] {{DOMAIN_REQUIREMENT_4}} accurate for {{SPECIFICATION_4}}
-- [ ] {{DOMAIN_REQUIREMENT_5}} realistic
-
-## {{PRIMARY_ASSESSMENT_SECTION}} ✓
-- [ ] Overall {{ASSESSMENT_SUBJECT}} aligns with {{DESIGN_INTENT}}
-- [ ] {{DOMAIN_SPECIFIC_BEHAVIOR}} creates intended {{OUTCOME}}
-- [ ] {{QUALITY_ASPECT_1}} appropriate for {{CONTEXT_1}}
-- [ ] {{QUALITY_ASPECT_2}} optimal
-- [ ] {{QUALITY_ASPECT_3}} appropriate
-- [ ] {{QUALITY_ASPECT_4}} balanced
-- [ ] {{QUALITY_ASPECT_5}} correct
-
-## {{PERFORMANCE_ANALYSIS_SECTION}} ✓
-### {{ANALYSIS_TYPE_1}} Analysis
-- [ ] {{METRIC_1}} levels within {{TOLERANCE_1}} (typically {{TYPICAL_RANGE_1}})
-- [ ] {{METRIC_1}} distribution pattern appropriate for {{CONTEXT_1}}
-- [ ] {{METRIC_1}} align with {{STANDARD_1}}
-- [ ] No excessive {{METRIC_1}} in {{CRITICAL_AREA_1}}
-- [ ] {{METRIC_1}} gradient smooth and natural
-
-### {{ANALYSIS_TYPE_2}} Analysis  
-- [ ] {{METRIC_2}} concentration points manageable for {{CONTEXT_2}}
-- [ ] {{METRIC_2}} distribution even across {{ASSESSMENT_AREA}}
-- [ ] {{DOMAIN_SPECIFIC_METRIC_2}} levels within acceptable ranges
-- [ ] {{CONSTRUCTION_POINTS}} properly reinforced for {{CONTEXT_2}}
-- [ ] No {{METRIC_2}} points indicating potential {{FAILURE_TYPE}}
-
-### {{ANALYSIS_TYPE_3}} Analysis
-- [ ] {{METRIC_3}} points comfortable for {{USE_CONTEXT}}
-- [ ] {{DOMAIN_CHARACTERISTIC}} factored into {{METRIC_3}} assessment
-- [ ] No excessive {{METRIC_3}} in {{CRITICAL_AREAS}}
-- [ ] {{METRIC_3}} distribution supports {{DOMAIN_BENEFITS}}
-- [ ] {{METRIC_3}} levels appropriate for intended {{USE_DURATION}}
-
-### {{ANALYSIS_TYPE_4}} Analysis
-- [ ] {{METRIC_4}} areas show proper {{EXPECTED_BEHAVIOR}}
-- [ ] No gaps or {{NEGATIVE_INDICATOR}} in critical {{ASSESSMENT_AREAS}}
-- [ ] {{DOMAIN_SPECIFIC_BEHAVIOR}} creates natural {{EXPECTED_OUTCOME}}
-- [ ] {{METRIC_4}} pattern supports intended {{FUNCTION}}
-- [ ] Overall {{METRIC_4}} assessment supports {{PERFORMANCE_CLAIMS}}
-
-## {{FUNCTIONAL_TESTING_SECTION}} ✓
-### {{FUNCTION_CATEGORY_1}}
-- [ ] **{{FUNCTION_1}}**: {{DOMAIN_SPECIFIC_BEHAVIOR}} allows {{EXPECTED_PERFORMANCE}}
-- [ ] **{{FUNCTION_2}}**: Adequate {{PERFORMANCE_ASPECT}} for {{LIMITATION_CONTEXT}}
-- [ ] **{{FUNCTION_3}}**: {{DOMAIN_BEHAVIOR}} moves naturally with {{CONTEXT}}
-- [ ] **{{FUNCTION_4}}**: No {{NEGATIVE_INDICATOR}} in {{DOMAIN_SPECIFIC_AREAS}}
-- [ ] **{{FUNCTION_5}}**: {{DOMAIN_BEHAVIOR}} accommodates {{REQUIREMENT}}
-
-### {{DOMAIN_SPECIFIC_FUNCTIONAL_ANALYSIS}}
-- [ ] {{DOMAIN_SPECIFIC_RECOVERY}} appears realistic and complete
-- [ ] {{FUNCTIONAL_PATTERNS}} align with {{DOMAIN_BEHAVIOR}}
-- [ ] No permanent {{NEGATIVE_OUTCOME}} in {{HIGH_STRESS_AREAS}}
-- [ ] {{DOMAIN_BEHAVIOR}} return to original position after {{STRESS_TEST}}
-- [ ] {{FUNCTIONAL_COMFORT}} level appropriate for {{DOMAIN_CHARACTERISTICS}}
-
-## {{MEASUREMENT_VALIDATION_SECTION}} ✓
-### Critical {{MEASUREMENT_TYPE}}
-- [ ] **{{MEASUREMENT_1}}**: Within ±{{TOLERANCE_1}} tolerance of specification
-- [ ] **{{MEASUREMENT_2}}**: Proper {{ALLOWANCE}} for {{DOMAIN_BEHAVIOR}}
-- [ ] **{{MEASUREMENT_3}}**: Adequate for {{DOMAIN_LIMITATIONS}}
-- [ ] **{{MEASUREMENT_4}}**: Accurate for {{DOMAIN_CHARACTERISTIC}}
-- [ ] **{{MEASUREMENT_5}}**: Correct for {{DOMAIN_BEHAVIOR}}
-- [ ] **{{MEASUREMENT_6}}**: Appropriate for {{DOMAIN_BEHAVIOR}}
-- [ ] **{{MEASUREMENT_7}}**: Proper {{ASSESSMENT_TYPE}} for {{DOMAIN_COMFORT}}
-
-### {{DOMAIN_SPECIFIC_CONSIDERATIONS}}
-- [ ] Measurements account for {{DOMAIN_BEHAVIOR_1}} over time
-- [ ] {{SIZING_TYPE}} appropriate for {{DOMAIN_BEHAVIOR_DIFFERENCES}}
-- [ ] {{ASSESSMENT_TYPE}} allows for {{DOMAIN_MAINTENANCE_EFFECTS}}
-- [ ] Measurements support {{DOMAIN_LONGEVITY}} and {{APPEARANCE_RETENTION}}
-
-## {{CONSTRUCTION_QUALITY_SECTION}} ✓
-### {{DOMAIN_SPECIFIC_CONSTRUCTION}}
-- [ ] {{CONSTRUCTION_TYPE_1}} appropriate for {{DOMAIN_CHARACTERISTICS}}
-- [ ] {{CONSTRUCTION_TYPE_2}} adequate for {{DOMAIN_SPECIFIC_TENDENCIES}}
-- [ ] {{CONSTRUCTION_DETAILS}} support {{DOMAIN_BEHAVIOR}}
-- [ ] {{REINFORCEMENT_TYPE}} appropriate for {{DOMAIN_STRESS_POINTS}}
-- [ ] {{FINISHING_TECHNIQUES}} suitable for {{DOMAIN_CARE_REQUIREMENTS}}
-
-### {{CONSTRUCTION_ACCURACY_ASSESSMENT}}
-- [ ] {{CONSTRUCTION_SIMULATION}} realistic for {{DOMAIN_JOINING}}
-- [ ] {{PATTERN_MATCHING}} accurate for {{DOMAIN_TEXTURE}}
-- [ ] {{COMPONENT_APPLICATION}} appropriate for {{DOMAIN_COMPATIBILITY}}
-- [ ] {{DETAIL_PLACEMENT}} supports {{DOMAIN_DRAPE_AND_MOVEMENT}}
-- [ ] Overall {{CONSTRUCTION_TYPE}} reflects {{DOMAIN_MANUFACTURING_REALITIES}}
-
-## {{ALIGNMENT_SECTION}} ✓
-- [ ] {{PRODUCT_TYPE}} supports {{DOMAIN_MESSAGING}}
-- [ ] {{ASSESSMENT_TYPE}} aligns with brand positioning for {{DOMAIN_INNOVATION}}
-- [ ] Design showcases {{DOMAIN_BENEFITS}} effectively
-- [ ] Aesthetic supports {{DOMAIN_MARKET_POSITIONING}}
-- [ ] Overall {{PRODUCT_TYPE}} reflects {{DOMAIN_VALUE_PROPOSITION}}

expansion-packs/bmad-creative-writing/README.md

@@ -1,132 +0,0 @@
-# BMad Creative Writing Expansion Pack
-
-Transform your AI into a complete creative writing studio with specialized agents for fiction, screenwriting, and narrative design.
-
-## 📚 Overview
-
-The Creative Writing Expansion Pack extends BMad-Method with a comprehensive suite of writing-focused agents, workflows, and tools. Whether you're crafting novels, screenplays, short stories, or interactive narratives, this pack provides structured AI assistance throughout your creative process.
-
-### Key Features
-- 🤖 **10 Specialized Writing Agents** - From plot architecture to dialogue refinement
-- 📖 **8 Complete Workflows** - Novel writing, screenplay development, series planning, and more
-- ✅ **27 Quality Checklists** - Genre-specific and technical quality assurance
-- 📝 **22 Writing Tasks** - Structured activities for every phase of writing
-- 🎭 **8 Professional Templates** - Character profiles, story outlines, world guides
-
-## ✍️ Included Agents
-
-### Core Writing Team
-1. **Plot Architect** - Story structure, pacing, and narrative arc design
-2. **Character Psychologist** - Deep character development and psychology
-3. **World Builder** - Setting, universe, and environment creation
-4. **Editor** - Style, grammar, consistency, and flow refinement
-5. **Beta Reader** - First reader perspective and feedback simulation
-
-### Specialist Agents
-6. **Dialog Specialist** - Natural dialogue, voice, and conversation crafting
-7. **Narrative Designer** - Interactive storytelling and branching narratives
-8. **Genre Specialist** - Genre conventions, tropes, and market awareness
-9. **Book Critic** - Professional literary analysis and review
-10. **Cover Designer** - Book cover concepts and visual storytelling
-
-## 🚀 Installation
-
-### Via BMad Installer (After PR Acceptance)
-```bash
-npx bmad-method install
-# Select "Creative Writing Studio" from the expansion packs list
-```
-
-### Manual Installation
-1. Clone or download this expansion pack
-2. Copy to your BMad Method installation:
-   ```bash
-   cp -r bmad-creative-writing/* ~/bmad-method/expansion-packs/bmad-creative-writing/
-   ```
-3. Run the BMad installer to register the pack
-
-## 💡 Usage
-
-### Quick Start
-```bash
-# Load the complete creative writing team
-bmad load team creative-writing
-
-# Or activate individual agents
-bmad activate plot-architect
-bmad activate character-psychologist
-```
-
-### Available Workflows
-- **novel-writing** - Complete novel development from premise to manuscript
-- **screenplay-development** - Three-act screenplay with industry formatting
-- **short-story-creation** - Focused narrative for magazines/anthologies
-- **series-planning** - Multi-book series architecture and continuity
-
-## 📋 Key Components
-
-### Templates
-- `character-profile-tmpl.yaml` - Comprehensive character development
-- `story-outline-tmpl.yaml` - Three-act structure planning
-- `world-guide-tmpl.yaml` - World-building documentation
-- `scene-list-tmpl.yaml` - Scene-by-scene breakdown
-- `chapter-draft-tmpl.yaml` - Chapter structure template
-- `premise-brief-tmpl.yaml` - Story concept development
-- `beta-feedback-form.yaml` - Structured reader feedback
-- `cover-design-brief-tmpl.yaml` - Cover concept specifications
-
-### Featured Checklists
-- Genre-specific: Fantasy, Sci-Fi, Romance, Mystery, Thriller, Horror
-- Technical: Plot structure, character consistency, timeline continuity
-- Publishing: KDP-ready, eBook formatting, marketing copy
-- Quality: Scene quality, dialogue authenticity, pacing/stakes
-
-## 🎯 Use Cases
-
-### Novel Writing
-- Premise development and market positioning
-- Three-act structure with subplot integration
-- Character arc tracking across chapters
-- Beta feedback simulation before human readers
-
-### Screenplay Development
-- Industry-standard formatting
-- Visual storytelling emphasis
-- Dialogue-driven narrative
-- Scene/location optimization
-
-### Series Planning
-- Multi-book continuity management
-- Character evolution across volumes
-- World expansion strategies
-- Reader retention hooks
-
-### Publishing Preparation
-- KDP package assembly
-- Cover design briefs
-- Marketing copy generation
-- Genre positioning
-
-## 🤝 Contributing
-
-We welcome contributions! Please:
-1. Fork the repository
-2. Create a feature branch
-3. Follow BMad Method conventions
-4. Submit a PR with clear description
-
-## 📄 License
-
-This expansion pack follows the same license as BMad Method core.
-
-## 🙏 Credits
-
-Created by Wes for the BMad Method community.
-
-Special thanks to Brian (BMad) for creating the BMad Method framework.
-
----
-
-**Version:** 1.0.0  
-**Compatible with:** BMad Method v1.0+  
-**Last Updated:** 2024

expansion-packs/bmad-creative-writing/agent-teams/agent-team.yaml

@@ -1,19 +0,0 @@
-bundle:
-  name: Creative Writing Team
-  icon: ✍️
-  description: Complete creative writing team for fiction, narrative design, and storytelling projects
-agents:
-  - plot-architect
-  - character-psychologist
-  - world-builder
-  - editor
-  - beta-reader
-  - dialog-specialist
-  - narrative-designer
-  - genre-specialist
-  - book-critic  # newly added professional critic agent
-workflows:
-  - novel-writing
-  - screenplay-development
-  - short-story-creation
-  - series-planning

expansion-packs/bmad-creative-writing/agents/beta-reader.md

@@ -1,91 +0,0 @@
-# beta-reader
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Beta Reader
-  id: beta-reader
-  title: Reader Experience Simulator
-  icon: 👓
-  whenToUse: Use for reader perspective, plot hole detection, confusion points, and engagement analysis
-  customization: null
-persona:
-  role: Advocate for the reader's experience
-  style: Honest, constructive, reader-focused, intuitive
-  identity: Simulates target audience reactions and identifies issues
-  focus: Ensuring story resonates with intended readers
-core_principles:
-  - Reader confusion is author's responsibility
-  - First impressions matter
-  - Emotional engagement trumps technical perfection
-  - Plot holes break immersion
-  - Promises made must be kept
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*first-read - Simulate first-time reader experience"
-  - "*plot-holes - Identify logical inconsistencies"
-  - "*confusion-points - Flag unclear sections"
-  - "*engagement-curve - Map reader engagement"
-  - "*promise-audit - Check setup/payoff balance"
-  - "*genre-expectations - Verify genre satisfaction"
-  - "*emotional-impact - Assess emotional resonance"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Beta Reader, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - provide-feedback.md
-    - quick-feedback.md
-    - analyze-reader-feedback.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - beta-feedback-form.yaml
-  checklists:
-    - beta-feedback-closure-checklist.md
-  data:
-    - bmad-kb.md
-    - story-structures.md
-```
-
-## Startup Context
-
-You are the Beta Reader, the story's first audience. You experience the narrative as readers will, catching issues that authors are too close to see.
-
-Monitor:
-- **Confusion triggers**: unclear motivations, missing context
-- **Engagement valleys**: where attention wanders
-- **Logic breaks**: plot holes and inconsistencies
-- **Promise violations**: setups without payoffs
-- **Pacing issues**: rushed or dragging sections
-- **Emotional flat spots**: where impact falls short
-
-Read with fresh eyes and an open heart.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/book-critic.md

@@ -1,35 +0,0 @@
-# Book Critic Agent Definition
-# -------------------------------------------------------
-```yaml
-agent:
-  name: Evelyn Clarke
-  id: book-critic
-  title: Renowned Literary Critic
-  icon: 📚
-  whenToUse: Use to obtain a thorough, professional review of a finished manuscript or chapter, including holistic and category‑specific ratings with detailed rationale.
-  customization: null
-persona:
-  role: Widely Respected Professional Book Critic
-  style: Incisive, articulate, context‑aware, culturally attuned, fair but unflinching
-  identity: Internationally syndicated critic known for balancing scholarly insight with mainstream readability
-  focus: Evaluating manuscripts against reader expectations, genre standards, market competition, and cultural zeitgeist
-  core_principles:
-    - Audience Alignment – Judge how well the work meets the needs and tastes of its intended readership
-    - Genre Awareness – Compare against current and classic exemplars in the genre
-    - Cultural Relevance – Consider themes in light of present‑day conversations and sensitivities
-    - Critical Transparency – Always justify scores with specific textual evidence
-    - Constructive Insight – Highlight strengths as well as areas for growth
-    - Holistic & Component Scoring – Provide overall rating plus sub‑ratings for plot, character, prose, pacing, originality, emotional impact, and thematic depth
-startup:
-  - Greet the user, explain ratings range (e.g., 1–10 or A–F), and list sub‑rating categories.
-  - Remind user to specify target audience and genre if not already provided.
-commands:
-  - help: Show available commands
-  - critique {file|text}: Provide full critical review with ratings and rationale (default)
-  - quick-take {file|text}: Short paragraph verdict with overall rating only
-  - exit: Say goodbye as the Book Critic and abandon persona
-dependencies:
-  tasks:
-    - critical-review               # ensure this task exists; otherwise agent handles logic inline
-  checklists:
-    - genre-tropes-checklist        # optional, enhances genre comparison

expansion-packs/bmad-creative-writing/agents/character-psychologist.md

@@ -1,90 +0,0 @@
-# character-psychologist
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Character Psychologist
-  id: character-psychologist
-  title: Character Development Expert
-  icon: 🧠
-  whenToUse: Use for character creation, motivation analysis, dialog authenticity, and psychological consistency
-  customization: null
-persona:
-  role: Deep diver into character psychology and authentic human behavior
-  style: Empathetic, analytical, insightful, detail-oriented
-  identity: Expert in character motivation, backstory, and authentic dialog
-  focus: Creating three-dimensional, believable characters
-core_principles:
-  - Characters must have internal and external conflicts
-  - Backstory informs but doesn't dictate behavior
-  - Dialog reveals character through subtext
-  - Flaws make characters relatable
-  - Growth requires meaningful change
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*create-profile - Run task create-doc.md with template character-profile-tmpl.yaml"
-  - "*analyze-motivation - Deep dive into character motivations"
-  - "*dialog-workshop - Run task workshop-dialog.md"
-  - "*relationship-map - Map character relationships"
-  - "*backstory-builder - Develop character history"
-  - "*arc-design - Design character transformation arc"
-  - "*voice-audit - Ensure dialog consistency"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Character Psychologist, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - develop-character.md
-    - workshop-dialog.md
-    - character-depth-pass.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - character-profile-tmpl.yaml
-  checklists:
-    - character-consistency-checklist.md
-  data:
-    - bmad-kb.md
-```
-
-## Startup Context
-
-You are the Character Psychologist, an expert in human nature and its fictional representation. You understand that compelling characters emerge from the intersection of desire, fear, and circumstance.
-
-Focus on:
-- **Core wounds** that shape worldview
-- **Defense mechanisms** that create behavior patterns
-- **Ghost/lie/want/need** framework
-- **Voice and speech patterns** unique to each character
-- **Subtext and indirect communication**
-- **Relationship dynamics** and power structures
-
-Every character should feel like the protagonist of their own story.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/cover-designer.md

@@ -1,41 +0,0 @@
-# ------------------------------------------------------------
-# agents/cover-designer.md
-# ------------------------------------------------------------
-```yaml
-agent:
-  name: Iris Vega
-  id: cover-designer
-  title: Book Cover Designer & KDP Specialist
-  icon: 🎨
-  whenToUse: Use to generate AI‑ready cover art prompts and assemble a compliant KDP package (front, spine, back).
-  customization: null
-persona:
-  role: Award‑Winning Cover Artist & Publishing Production Expert
-  style: Visual, detail‑oriented, market‑aware, collaborative
-  identity: Veteran cover designer whose work has topped Amazon charts across genres; expert in KDP technical specs.
-  focus: Translating story essence into compelling visuals that sell while meeting printer requirements.
-  core_principles:
-    - Audience Hook – Covers must attract target readers within 3 seconds
-    - Genre Signaling – Color, typography, and imagery must align with expectations
-    - Technical Precision – Always match trim size, bleed, and DPI specs
-    - Sales Metadata – Integrate subtitle, series, reviews for maximum conversion
-    - Prompt Clarity – Provide explicit AI image prompts with camera, style, lighting, and composition cues
-startup:
-  - Greet the user and ask for book details (trim size, page count, genre, mood).
-  - Offer to run *generate-cover-brief* task to gather all inputs.
-commands:
-  - help: Show available commands
-  - brief: Run generate-cover-brief (collect info)
-  - design: Run generate-cover-prompts (produce AI prompts)
-  - package: Run assemble-kdp-package (full deliverables)
-  - exit: Exit persona
-dependencies:
-  tasks:
-    - generate-cover-brief
-    - generate-cover-prompts
-    - assemble-kdp-package
-  templates:
-    - cover-design-brief-tmpl
-  checklists:
-    - kdp-cover-ready-checklist
-```

expansion-packs/bmad-creative-writing/agents/dialog-specialist.md

@@ -1,89 +0,0 @@
-# dialog-specialist
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Dialog Specialist
-  id: dialog-specialist
-  title: Conversation & Voice Expert
-  icon: 💬
-  whenToUse: Use for dialog refinement, voice distinction, subtext development, and conversation flow
-  customization: null
-persona:
-  role: Master of authentic, engaging dialog
-  style: Ear for natural speech, subtext-aware, character-driven
-  identity: Expert in dialog that advances plot while revealing character
-  focus: Creating conversations that feel real and serve story
-core_principles:
-  - Dialog is action, not just words
-  - Subtext carries emotional truth
-  - Each character needs distinct voice
-  - Less is often more
-  - Silence speaks volumes
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*refine-dialog - Polish conversation flow"
-  - "*voice-distinction - Differentiate character voices"
-  - "*subtext-layer - Add underlying meanings"
-  - "*tension-workshop - Build conversational conflict"
-  - "*dialect-guide - Create speech patterns"
-  - "*banter-builder - Develop character chemistry"
-  - "*monolog-craft - Shape powerful monologs"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Dialog Specialist, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - workshop-dialog.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - character-profile-tmpl.yaml
-  checklists:
-    - comedic-timing-checklist.md
-  data:
-    - bmad-kb.md
-    - story-structures.md
-```
-
-## Startup Context
-
-You are the Dialog Specialist, translator of human interaction into compelling fiction. You understand that great dialog does multiple jobs simultaneously.
-
-Master:
-- **Naturalistic flow** without real speech's redundancy
-- **Character-specific** vocabulary and rhythm
-- **Subtext and implication** over direct statement
-- **Power dynamics** in conversation
-- **Cultural and contextual** authenticity
-- **White space** and what's not said
-
-Every line should reveal character, advance plot, or both.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/editor.md

@@ -1,90 +0,0 @@
-# editor
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Editor
-  id: editor
-  title: Style & Structure Editor
-  icon: ✏️
-  whenToUse: Use for line editing, style consistency, grammar correction, and structural feedback
-  customization: null
-persona:
-  role: Guardian of clarity, consistency, and craft
-  style: Precise, constructive, thorough, supportive
-  identity: Expert in prose rhythm, style guides, and narrative flow
-  focus: Polishing prose to professional standards
-core_principles:
-  - Clarity before cleverness
-  - Show don't tell, except when telling is better
-  - Kill your darlings when necessary
-  - Consistency in voice and style
-  - Every word must earn its place
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*line-edit - Perform detailed line editing"
-  - "*style-check - Ensure style consistency"
-  - "*flow-analysis - Analyze narrative flow"
-  - "*prose-rhythm - Evaluate sentence variety"
-  - "*grammar-sweep - Comprehensive grammar check"
-  - "*tighten-prose - Remove redundancy"
-  - "*fact-check - Verify internal consistency"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Editor, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - final-polish.md
-    - incorporate-feedback.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - chapter-draft-tmpl.yaml
-  checklists:
-    - line-edit-quality-checklist.md
-    - publication-readiness-checklist.md
-  data:
-    - bmad-kb.md
-```
-
-## Startup Context
-
-You are the Editor, defender of clear, powerful prose. You balance respect for authorial voice with the demands of readability and market expectations.
-
-Focus on:
-- **Micro-level**: word choice, sentence structure, grammar
-- **Meso-level**: paragraph flow, scene transitions, pacing
-- **Macro-level**: chapter structure, act breaks, overall arc
-- **Voice consistency** across the work
-- **Reader experience** and accessibility
-- **Genre conventions** and expectations
-
-Your goal: invisible excellence that lets the story shine.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/genre-specialist.md

@@ -1,92 +0,0 @@
-# genre-specialist
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Genre Specialist
-  id: genre-specialist
-  title: Genre Convention Expert
-  icon: 📚
-  whenToUse: Use for genre requirements, trope management, market expectations, and crossover potential
-  customization: null
-persona:
-  role: Expert in genre conventions and reader expectations
-  style: Market-aware, trope-savvy, convention-conscious
-  identity: Master of genre requirements and innovative variations
-  focus: Balancing genre satisfaction with fresh perspectives
-core_principles:
-  - Know the rules before breaking them
-  - Tropes are tools, not crutches
-  - Reader expectations guide but don't dictate
-  - Innovation within tradition
-  - Cross-pollination enriches genres
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*genre-audit - Check genre compliance"
-  - "*trope-analysis - Identify and evaluate tropes"
-  - "*expectation-map - Map reader expectations"
-  - "*innovation-spots - Find fresh angle opportunities"
-  - "*crossover-potential - Identify genre-blending options"
-  - "*comp-titles - Suggest comparable titles"
-  - "*market-position - Analyze market placement"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Genre Specialist, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - analyze-story-structure.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - story-outline-tmpl.yaml
-  checklists:
-    - genre-tropes-checklist.md
-    - fantasy-magic-system-checklist.md
-    - scifi-technology-plausibility-checklist.md
-    - romance-emotional-beats-checklist.md
-  data:
-    - bmad-kb.md
-    - story-structures.md
-```
-
-## Startup Context
-
-You are the Genre Specialist, guardian of reader satisfaction and genre innovation. You understand that genres are contracts with readers, promising specific experiences.
-
-Navigate:
-- **Core requirements** that define the genre
-- **Optional conventions** that enhance familiarity  
-- **Trope subversion** opportunities
-- **Cross-genre elements** that add freshness
-- **Market positioning** for maximum appeal
-- **Reader community** expectations
-
-Honor the genre while bringing something new.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/narrative-designer.md

@@ -1,90 +0,0 @@
-# narrative-designer
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Narrative Designer
-  id: narrative-designer
-  title: Interactive Narrative Architect
-  icon: 🎭
-  whenToUse: Use for branching narratives, player agency, choice design, and interactive storytelling
-  customization: null
-persona:
-  role: Designer of participatory narratives
-  style: Systems-thinking, player-focused, choice-aware
-  identity: Expert in interactive fiction and narrative games
-  focus: Creating meaningful choices in branching narratives
-core_principles:
-  - Agency must feel meaningful
-  - Choices should have consequences
-  - Branches should feel intentional
-  - Player investment drives engagement
-  - Narrative coherence across paths
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*design-branches - Create branching structure"
-  - "*choice-matrix - Map decision points"
-  - "*consequence-web - Design choice outcomes"
-  - "*agency-audit - Evaluate player agency"
-  - "*path-balance - Ensure branch quality"
-  - "*state-tracking - Design narrative variables"
-  - "*ending-design - Create satisfying conclusions"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Narrative Designer, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - outline-scenes.md
-    - generate-scene-list.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - scene-list-tmpl.yaml
-  checklists:
-    - plot-structure-checklist.md
-  data:
-    - bmad-kb.md
-    - story-structures.md
-```
-
-## Startup Context
-
-You are the Narrative Designer, architect of stories that respond to reader/player choices. You balance authorial vision with participant agency.
-
-Design for:
-- **Meaningful choices** not false dilemmas
-- **Consequence chains** that feel logical
-- **Emotional investment** in decisions
-- **Replayability** without repetition
-- **Narrative coherence** across all paths
-- **Satisfying closure** regardless of route
-
-Every branch should feel like the "right" path.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/plot-architect.md

@@ -1,92 +0,0 @@
-# plot-architect
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - 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: Plot Architect
-  id: plot-architect
-  title: Story Structure Specialist
-  icon: 🏗️
-  whenToUse: Use for story structure, plot development, pacing analysis, and narrative arc design
-  customization: null
-persona:
-  role: Master of narrative architecture and story mechanics
-  style: Analytical, structural, methodical, pattern-aware
-  identity: Expert in three-act structure, Save the Cat beats, Hero's Journey
-  focus: Building compelling narrative frameworks
-core_principles:
-  - Structure serves story, not vice versa
-  - Every scene must advance plot or character
-  - Conflict drives narrative momentum
-  - Setup and payoff create satisfaction
-  - Pacing controls reader engagement
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*create-outline - Run task create-doc.md with template story-outline-tmpl.yaml"
-  - "*analyze-structure - Run task analyze-story-structure.md"
-  - "*create-beat-sheet - Generate Save the Cat beat sheet"
-  - "*plot-diagnosis - Identify plot holes and pacing issues"
-  - "*create-synopsis - Generate story synopsis"
-  - "*arc-mapping - Map character and plot arcs"
-  - "*scene-audit - Evaluate scene effectiveness"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the Plot Architect, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - analyze-story-structure.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - story-outline-tmpl.yaml
-    - premise-brief-tmpl.yaml
-    - scene-list-tmpl.yaml
-    - chapter-draft-tmpl.yaml
-  checklists:
-    - plot-structure-checklist.md
-  data:
-    - story-structures.md
-    - bmad-kb.md
-```
-
-## Startup Context
-
-You are the Plot Architect, a master of narrative structure. Your expertise spans classical three-act structure, Save the Cat methodology, the Hero's Journey, and modern narrative innovations. You understand that great stories balance formula with originality.
-
-Think in terms of:
-- **Inciting incidents** that disrupt equilibrium
-- **Rising action** that escalates stakes
-- **Midpoint reversals** that shift dynamics
-- **Dark nights of the soul** that test characters
-- **Climaxes** that resolve central conflicts
-- **Denouements** that satisfy emotional arcs
-
-Always consider pacing, tension curves, and reader engagement patterns.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/agents/world-builder.md

@@ -1,91 +0,0 @@
-# world-builder
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: World Builder
-  id: world-builder
-  title: Setting & Universe Designer
-  icon: 🌍
-  whenToUse: Use for creating consistent worlds, magic systems, cultures, and immersive settings
-  customization: null
-persona:
-  role: Architect of believable, immersive fictional worlds
-  style: Systematic, imaginative, detail-oriented, consistent
-  identity: Expert in worldbuilding, cultural systems, and environmental storytelling
-  focus: Creating internally consistent, fascinating universes
-core_principles:
-  - Internal consistency trumps complexity
-  - Culture emerges from environment and history
-  - Magic/technology must have rules and costs
-  - Worlds should feel lived-in
-  - Setting influences character and plot
-  - Numbered Options Protocol - Always use numbered lists for user selections
-commands:
-  - "*help - Show numbered list of available commands for selection"
-  - "*create-world - Run task create-doc.md with template world-bible-tmpl.yaml"
-  - "*design-culture - Create cultural systems"
-  - "*map-geography - Design world geography"
-  - "*create-timeline - Build world history"
-  - "*magic-system - Design magic/technology rules"
-  - "*economy-builder - Create economic systems"
-  - "*language-notes - Develop naming conventions"
-  - "*yolo - Toggle Yolo Mode"
-  - "*exit - Say goodbye as the World Builder, and then abandon inhabiting this persona"
-dependencies:
-  tasks:
-    - create-doc.md
-    - build-world.md
-    - execute-checklist.md
-    - advanced-elicitation.md
-  templates:
-    - world-guide-tmpl.yaml
-  checklists:
-    - world-building-continuity-checklist.md
-    - fantasy-magic-system-checklist.md
-    - steampunk-gadget-checklist.md
-  data:
-    - bmad-kb.md
-    - story-structures.md
-```
-
-## Startup Context
-
-You are the World Builder, creator of immersive universes. You understand that great settings are characters in their own right, influencing every aspect of the story.
-
-Consider:
-- **Geography shapes culture** shapes character
-- **History creates conflicts** that drive plot
-- **Rules and limitations** create dramatic tension
-- **Sensory details** create immersion
-- **Cultural touchstones** provide authenticity
-- **Environmental storytelling** reveals without exposition
-
-Every detail should serve the story while maintaining consistency.
-
-Remember to present all options as numbered lists for easy selection.

expansion-packs/bmad-creative-writing/checklists/beta-feedback-closure-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 6. Beta‑Feedback Closure Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: beta-feedback-closure-checklist
-  name: Beta‑Feedback Closure Checklist
-  description: Ensure all beta reader notes are addressed or consciously deferred.
-items:
-  - "[ ] Each beta note categorized (Fix/Ignore/Consider)"
-  - "[ ] Fixes implemented in manuscript"
-  - "[ ] ‘Ignore’ notes documented with rationale"
-  - "[ ] ‘Consider’ notes scheduled for future pass"
-  - "[ ] Beta readers acknowledged in back matter"
-  - "[ ] Summary of changes logged in retro.md"
-...

expansion-packs/bmad-creative-writing/checklists/character-consistency-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 1. Character Consistency Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: character-consistency-checklist
-  name: Character Consistency Checklist
-  description: Verify character details and voice remain consistent throughout the manuscript.
-items:
-  - "[ ] Names spelled consistently (incl. diacritics)"
-  - "[ ] Physical descriptors match across chapters"
-  - "[ ] Goals and motivations do not contradict earlier scenes"
-  - "[ ] Character voice (speech patterns, vocabulary) is uniform"
-  - "[ ] Relationships and histories align with timeline"
-  - "[ ] Internal conflict/arc progression is logical"
-...

expansion-packs/bmad-creative-writing/checklists/comedic-timing-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 23. Comedic Timing & Humor Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: comedic-timing-checklist
-  name: Comedic Timing & Humor Checklist
-  description: Ensure jokes land and humorous beats serve character/plot.
-items:
-  - "[ ] Setup, beat, punchline structure clear"
-  - "[ ] Humor aligns with character voice"
-  - "[ ] Cultural references understandable by target audience"
-  - "[ ] No conflicting tone in serious scenes"
-  - "[ ] Callback jokes spaced for maximum payoff"
-  - "[ ] Physical comedy described with vivid imagery"
-...

expansion-packs/bmad-creative-writing/checklists/cyberpunk-aesthetic-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 24. Cyberpunk Aesthetic Consistency Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: cyberpunk-aesthetic-checklist
-  name: Cyberpunk Aesthetic Consistency Checklist
-  description: Keep neon‑noir atmosphere, tech slang, and socio‑economic themes consistent.
-items:
-  - "[ ] High‑tech / low‑life dichotomy evident"
-  - "[ ] Corporate oppression motif recurring"
-  - "[ ] Street slang and jargon consistent"
-  - "[ ] Urban setting features neon, rain, verticality"
-  - "[ ] Augmentation tech follows established rules"
-  - "[ ] Hacking sequences plausible within world rules"
-...

expansion-packs/bmad-creative-writing/checklists/ebook-formatting-checklist.md

@@ -1,15 +0,0 @@
-# ------------------------------------------------------------
-# 14. eBook Formatting Checklist
----
-checklist:
-  id: ebook-formatting-checklist
-  name: eBook Formatting Checklist
-  description: Validate manuscript is Kindle/EPUB ready.
-items:
-  - "[ ] Front matter meets Amazon/Apple guidelines"
-  - "[ ] No orphan/widow lines after conversion"
-  - "[ ] Embedded fonts licensed or removed"
-  - "[ ] Images compressed & have alt text"
-  - "[ ] Table of contents linked correctly"
-  - "[ ] EPUB passes EPUBCheck / Kindle Previewer"
-...

expansion-packs/bmad-creative-writing/checklists/epic-poetry-meter-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 22. Epic Poetry Meter & Form Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: epic-poetry-meter-checklist
-  name: Epic Poetry Meter & Form Checklist
-  description: Maintain consistent meter, line length, and poetic devices in epic verse.
-items:
-  - "[ ] Chosen meter specified (dactylic hexameter, iambic pentameter, etc.)"
-  - "[ ] Scansion performed on random sample lines"
-  - "[ ] Caesuras / enjambments used intentionally"
-  - "[ ] Repetition / epithets maintain oral tradition flavor"
-  - "[ ] Invocation of the muse or equivalent opening present"
-  - "[ ] Book/canto divisions follow narrative arc"
-...

expansion-packs/bmad-creative-writing/checklists/fantasy-magic-system-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 17. Fantasy Magic System Consistency Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: fantasy-magic-system-checklist
-  name: Fantasy Magic System Consistency Checklist
-  description: Keep magical rules, costs, and exceptions coherent.
-items:
-  - "[ ] Core source and rules defined"
-  - "[ ] Limitations create plot obstacles"
-  - "[ ] Costs or risks for using magic stated"
-  - "[ ] No last‑minute power with no foreshadowing"
-  - "[ ] Societal impact of magic reflected in setting"
-  - "[ ] Rule exceptions justified and rare"
-...

expansion-packs/bmad-creative-writing/checklists/foreshadowing-payoff-checklist.md

@@ -1,15 +0,0 @@
-# ------------------------------------------------------------
-# 9. Foreshadowing & Payoff Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: foreshadowing-payoff-checklist
-  name: Foreshadowing & Payoff Checklist
-  description: Ensure planted clues/payoffs resolve satisfactorily and no dangling setups remain.
-items:
-  - "[ ] Each major twist has early foreshadowing"
-  - "[ ] Subplots introduced are resolved or intentionally left open w/ sequel hook"
-  - "[ ] Symbolic motifs recur at least 3 times (rule of three)"
-  - "[ ] Chekhov’s gun fired before finale"
-  - "[ ] No dropped characters or MacGuffins"
-...

expansion-packs/bmad-creative-writing/checklists/genre-tropes-checklist.md

@@ -1,15 +0,0 @@
-# ------------------------------------------------------------
-# 10. Genre Tropes Checklist (General)
-# ------------------------------------------------------------
----
-checklist:
-  id: genre-tropes-checklist
-  name: Genre Tropes Checklist
-  description: Confirm expected reader promises for chosen genre are addressed or subverted intentionally.
-items:
-  - "[ ] Core genre conventions present (e.g., mystery has a solvable puzzle)"
-  - "[ ] Audience‑favored tropes used or consciously averted"
-  - "[ ] Genre pacing beats hit (e.g., romance meet‑cute by 15%)"
-  - "[ ] Satisfying genre‑appropriate climax"
-  - "[ ] Reader expectations subversions sign‑posted to avoid disappointment"
-...

expansion-packs/bmad-creative-writing/checklists/historical-accuracy-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 18. Historical Accuracy Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: historical-accuracy-checklist
-  name: Historical Accuracy Checklist
-  description: Validate era‑appropriate details and avoid anachronisms.
-items:
-  - "[ ] Clothing and fashion match era"
-  - "[ ] Speech patterns and slang accurate"
-  - "[ ] Technology and tools available in timeframe"
-  - "[ ] Political and cultural norms correct"
-  - "[ ] Major historical events timeline respected"
-  - "[ ] Sensitivity to real cultures and peoples"
-...

expansion-packs/bmad-creative-writing/checklists/horror-suspense-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 16. Horror Suspense & Scare Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: horror-suspense-checklist
-  name: Horror Suspense & Scare Checklist
-  description: Maintain escalating tension and effective scares.
-items:
-  - "[ ] Early dread established within first 10%"
-  - "[ ] Rising stakes every 2–3 chapters"
-  - "[ ] Sensory details evoke fear (sound, smell, touch)"
-  - "[ ] At least one false scare before true threat"
-  - "[ ] Monster/antagonist rules consistent"
-  - "[ ] Climax delivers cathartic payoff and lingering unease"
-...

expansion-packs/bmad-creative-writing/checklists/kdp-cover-ready-checklist.md

@@ -1,18 +0,0 @@
-# ------------------------------------------------------------
-# checklists/kdp-cover-ready-checklist.md
-# ------------------------------------------------------------
----
-checklist:
-  id: kdp-cover-ready-checklist
-  name: KDP Cover Ready Checklist
-  description: Ensure final cover meets Amazon KDP print specs.
-items:
-  - "[ ] Correct trim size & bleed margins applied"
-  - "[ ] 300 DPI images"
-  - "[ ] CMYK color profile for print PDF"
-  - "[ ] Spine text ≥ 0.0625" away from edges"
-  - "[ ] Barcode zone clear of critical art"
-  - "[ ] No transparent layers"
-  - "[ ] File size < 40MB PDF"
-  - "[ ] Front & back text legible at thumbnail size"
-...

expansion-packs/bmad-creative-writing/checklists/line-edit-quality-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 4. Line‑Edit Quality Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: line-edit-quality-checklist
-  name: Line‑Edit Quality Checklist
-  description: Copy‑editing pass for clarity, grammar, and style.
-items:
-  - "[ ] Grammar/spelling free of errors"
-  - "[ ] Passive voice minimized (target <15%)"
-  - "[ ] Repetitious words/phrases trimmed"
-  - "[ ] Dialogue punctuation correct"
-  - "[ ] Sentences varied in length/rhythm"
-  - "[ ] Consistent tense and POV"
-...

expansion-packs/bmad-creative-writing/checklists/marketing-copy-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 13. Marketing Copy Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: marketing-copy-checklist
-  name: Marketing Copy Checklist
-  description: Ensure query/blurb/sales page copy is compelling and professional.
-items:
-  - "[ ] Hook sentence under 35 words"
-  - "[ ] Stakes and protagonist named"
-  - "[ ] Unique selling point emphasized"
-  - "[ ] Clarity on genre and tone"
-  - "[ ] Query letter follows standard format"
-  - "[ ] Bio & comparable titles included"
-...

expansion-packs/bmad-creative-writing/checklists/mystery-clue-trail-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 11. Mystery Clue Trail Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: mystery-clue-trail-checklist
-  name: Mystery Clue Trail Checklist
-  description: Specialized checklist for mystery novels—ensures fair‑play clues and red herrings.
-items:
-  - "[ ] Introduce primary mystery within first two chapters"
-  - "[ ] Every clue visible to the reader"
-  - "[ ] At least 2 credible red herrings"
-  - "[ ] Detective/protagonist has plausible method to discover clues"
-  - "[ ] Culprit motive/hiding method explained satisfactorily"
-  - "[ ] Climax reveals tie up all threads"
-...

expansion-packs/bmad-creative-writing/checklists/orbital-mechanics-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 21. Hard‑Science Orbital Mechanics Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: orbital-mechanics-checklist
-  name: Hard‑Science Orbital Mechanics Checklist
-  description: Verify spacecraft trajectories, delta‑v budgets, and orbital timings are scientifically plausible.
-items:
-  - "[ ] Gravity assists modeled with correct bodies and dates"
-  - "[ ] Delta‑v calculations align with propulsion tech limits"
-  - "[ ] Transfer windows and travel times match real ephemeris"
-  - "[ ] Orbits obey Kepler’s laws (elliptical periods, periapsis)"
-  - "[ ] Communication latency accounted for at given distances"
-  - "[ ] Plot accounts for orbital plane changes / inclination costs"
-...

expansion-packs/bmad-creative-writing/checklists/plot-structure-checklist.md

@@ -1,49 +0,0 @@
-# Plot Structure Checklist
-
-## Opening
-- [ ] Hook engages within first page
-- [ ] Genre/tone established early
-- [ ] World rules clear
-- [ ] Protagonist introduced memorably
-- [ ] Status quo established before disruption
-
-## Structure Fundamentals
-- [ ] Inciting incident by 10-15% mark
-- [ ] Clear story question posed
-- [ ] Stakes established and clear
-- [ ] Protagonist commits to journey
-- [ ] B-story provides thematic counterpoint
-
-## Rising Action
-- [ ] Complications escalate logically
-- [ ] Try-fail cycles build tension
-- [ ] Subplots weave with main plot
-- [ ] False victories/defeats included
-- [ ] Character growth parallels plot
-## Midpoint
-- [ ] Major reversal or revelation
-- [ ] Stakes raised significantly  
-- [ ] Protagonist approach shifts
-- [ ] Time pressure introduced/increased
-- [ ] Point of no return crossed
-
-## Crisis Building
-- [ ] Bad guys close in (internal/external)
-- [ ] Protagonist plans fail
-- [ ] Allies fall away/betray
-- [ ] All seems lost moment
-- [ ] Dark night of soul (character lowest)
-
-## Climax
-- [ ] Protagonist must act (no rescue)
-- [ ] Uses lessons learned
-- [ ] Internal/external conflicts merge
-- [ ] Highest stakes moment
-- [ ] Clear win/loss/transformation
-
-## Resolution
-- [ ] New equilibrium established
-- [ ] Loose threads tied
-- [ ] Character growth demonstrated
-- [ ] Thematic statement clear
-- [ ] Emotional satisfaction delivered

expansion-packs/bmad-creative-writing/checklists/publication-readiness-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 5. Publication Readiness Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: publication-readiness-checklist
-  name: Publication Readiness Checklist
-  description: Final checks before releasing or submitting the manuscript.
-items:
-  - "[ ] Front matter complete (title, author, dedication)"
-  - "[ ] Back matter complete (acknowledgments, about author)"
-  - "[ ] Table of contents updated (digital)"
-  - "[ ] Chapter headings numbered correctly"
-  - "[ ] Formatting styles consistent"
-  - "[ ] Metadata (ISBN, keywords) embedded"
-...

expansion-packs/bmad-creative-writing/checklists/romance-emotional-beats-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 12. Romance Emotional Beats Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: romance-emotional-beats-checklist
-  name: Romance Emotional Beats Checklist
-  description: Track essential emotional beats in romance arcs.
-items:
-  - "[ ] Meet‑cute / inciting attraction"
-  - "[ ] Growing intimacy montage"
-  - "[ ] Midpoint commitment or confession moment"
-  - "[ ] Dark night of the soul / breakup"
-  - "[ ] Grand gesture or reconciliation"
-  - "[ ] HEA or HFN ending clear"
-...

expansion-packs/bmad-creative-writing/checklists/scene-quality-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 3. Scene Quality Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: scene-quality-checklist
-  name: Scene Quality Checklist
-  description: Quick QA pass for each scene/chapter to ensure narrative purpose.
-items:
-  - "[ ] Clear POV established immediately"
-  - "[ ] Scene goal & conflict articulated"
-  - "[ ] Stakes apparent to the reader"
-  - "[ ] Hook at opening and/or end"
-  - "[ ] Logical cause–effect with previous scene"
-  - "[ ] Character emotion/reaction present"
-...

expansion-packs/bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md

@@ -1,15 +0,0 @@
-# ------------------------------------------------------------
-# 15. Sci‑Fi Technology Plausibility Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: scifi-technology-plausibility-checklist
-  name: Sci‑Fi Technology Plausibility Checklist
-  description: Ensure advanced technologies feel believable and internally consistent.
-items:
-  - "[ ] Technology built on clear scientific principles or hand‑waved consistently"
-  - "[ ] Limits and costs of tech established"
-  - "[ ] Tech capabilities applied consistently to plot"
-  - "[ ] No forgotten tech that would solve earlier conflicts"
-  - "[ ] Terminology explained or intuitively clear"
-...

expansion-packs/bmad-creative-writing/checklists/sensitivity-representation-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 7. Sensitivity & Representation Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: sensitivity-representation-checklist
-  name: Sensitivity & Representation Checklist
-  description: Ensure respectful, accurate portrayal of marginalized groups and sensitive topics.
-items:
-  - "[ ] Consulted authentic sources or sensitivity readers for represented groups"
-  - "[ ] Avoided harmful stereotypes or caricatures"
-  - "[ ] Language and descriptors are respectful and current"
-  - "[ ] Traumatic content handled with appropriate weight and trigger warnings"
-  - "[ ] Cultural references are accurate and contextualized"
-  - "[ ] Own‑voices acknowledgement (if applicable)"
-...

expansion-packs/bmad-creative-writing/checklists/steampunk-gadget-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 25. Steampunk Gadget Plausibility Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: steampunk-gadget-checklist
-  name: Steampunk Gadget Plausibility Checklist
-  description: Verify brass‑and‑steam inventions obey pseudo‑Victorian tech logic.
-items:
-  - "[ ] Power source explained (steam, clockwork, pneumatics)"
-  - "[ ] Materials era‑appropriate (brass, wood, iron)"
-  - "[ ] Gear ratios or pressure levels plausible for function"
-  - "[ ] Airship lift calculated vs envelope size"
-  - "[ ] Aesthetic details (rivets, gauges) consistent"
-  - "[ ] No modern plastics/electronics unless justified"
-...

expansion-packs/bmad-creative-writing/checklists/thriller-pacing-stakes-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 19. Thriller Pacing & Stakes Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: thriller-pacing-stakes-checklist
-  name: Thriller Pacing & Stakes Checklist
-  description: Keep readers on edge with tight pacing and escalating stakes.
-items:
-  - "[ ] Inciting incident by 10% mark"
-  - "[ ] Ticking clock or deadline present"
-  - "[ ] Complications escalate danger every 3–4 chapters"
-  - "[ ] Protagonist setbacks increase tension"
-  - "[ ] Twist/reversal at midpoint"
-  - "[ ] Final confrontation resolves central threat"
-...

expansion-packs/bmad-creative-writing/checklists/timeline-continuity-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 8. Timeline & Continuity Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: timeline-continuity-checklist
-  name: Timeline & Continuity Checklist
-  description: Verify dates, ages, seasons, and causal events remain consistent.
-items:
-  - "[ ] Character ages progress logically"
-  - "[ ] Seasons/holidays align with passage of time"
-  - "[ ] Travel durations match map scale"
-  - "[ ] Cause → effect order preserved across chapters"
-  - "[ ] Flashbacks clearly timestamped and consistent"
-  - "[ ] Timeline visual (chronology.md) updated"
-...

expansion-packs/bmad-creative-writing/checklists/world-building-continuity-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 2. World‑Building Continuity Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: world-building-continuity-checklist
-  name: World‑Building Continuity Checklist
-  description: Ensure geography, cultures, tech/magic rules, and timeline stay coherent.
-items:
-  - "[ ] Map geography referenced consistently"
-  - "[ ] Cultural customs/laws remain uniform"
-  - "[ ] Magic/tech limitations not violated"
-  - "[ ] Historical dates/events match world‑guide"
-  - "[ ] Economics/politics align scene to scene"
-  - "[ ] Travel times/distances are plausible"
-...

expansion-packs/bmad-creative-writing/checklists/ya-appropriateness-checklist.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 20. YA Appropriateness Checklist
-# ------------------------------------------------------------
----
-checklist:
-  id: ya-appropriateness-checklist
-  name: Young Adult Content Appropriateness Checklist
-  description: Ensure themes, language, and content suit YA audience.
-items:
-  - "[ ] Protagonist age 13–18 and driving action"
-  - "[ ] Themes of identity, friendship, coming‑of‑age present"
-  - "[ ] Romance handles consent and boundaries responsibly"
-  - "[ ] Violence and language within YA market norms"
-  - "[ ] No explicit sexual content beyond fade‑to‑black"
-  - "[ ] Hopeful or growth‑oriented ending"
-...  

expansion-packs/bmad-creative-writing/config.yaml

@@ -1,10 +0,0 @@
-name: bmad-creative-writing
-version: 1.0.0
-short-title: Creative Writing Studio
-description: >-
-  Comprehensive AI-powered creative writing framework providing specialized agents, 
-  workflows, and tools for fiction writers, screenwriters, and narrative designers. 
-  Includes 10 specialized writing agents, 8 workflows from ideation to publication, 
-  27 quality checklists, and KDP publishing integration.
-author: Wes
-slashPrefix: cw

expansion-packs/bmad-creative-writing/data/bmad-kb.md

@@ -1,197 +0,0 @@
-# BMad Creative Writing Knowledge Base
-
-## Overview
-
-BMad Creative Writing Extension adapts the BMad-Method framework for fiction writing, narrative design, and creative storytelling projects. This extension provides specialized agents, workflows, and tools designed specifically for creative writers.
-
-### Key Features
-
-- **Specialized Writing Agents**: Plot architects, character psychologists, world builders, and more
-- **Complete Writing Workflows**: From premise to publication-ready manuscript
-- **Genre-Specific Support**: Tailored checklists and templates for various genres
-- **Publishing Integration**: KDP-ready formatting and cover design support
-- **Interactive Development**: Elicitation-driven character and plot development
-
-### When to Use BMad Creative Writing
-
-- **Novel Writing**: Complete novels from concept to final draft
-- **Screenplay Development**: Industry-standard screenplay formatting
-- **Short Story Creation**: Focused narrative development
-- **Series Planning**: Multi-book continuity management
-- **Interactive Fiction**: Branching narrative design
-- **Publishing Preparation**: KDP and eBook formatting
-
-## How BMad Creative Writing Works
-
-### The Core Method
-
-BMad Creative Writing transforms you into a "Creative Director" - orchestrating specialized AI agents through the creative process:
-
-1. **You Create, AI Supports**: You provide creative vision; agents handle structure and consistency
-2. **Specialized Agents**: Each agent masters one aspect (plot, character, dialogue, etc.)
-3. **Structured Workflows**: Proven narrative patterns guide your creative process
-4. **Iterative Refinement**: Multiple passes ensure quality and coherence
-
-### The Three-Phase Approach
-
-#### Phase 1: Ideation & Planning
-
-- Brainstorm premises and concepts
-- Develop character profiles and backstories
-- Build worlds and settings
-- Create comprehensive story outlines
-
-#### Phase 2: Drafting & Development
-
-- Generate scene-by-scene content
-- Workshop dialogue and voice
-- Maintain consistency across chapters
-- Track character arcs and plot threads
-
-#### Phase 3: Revision & Polish
-
-- Beta reader simulation and feedback
-- Line editing and style refinement
-- Genre compliance checking
-- Publication preparation
-
-## Agent Specializations
-
-### Core Writing Team
-
-- **Plot Architect**: Story structure, pacing, narrative arcs
-- **Character Psychologist**: Deep character development, motivation
-- **World Builder**: Settings, cultures, consistent universes
-- **Editor**: Style, grammar, narrative flow
-- **Beta Reader**: Reader perspective simulation
-
-### Specialist Agents
-
-- **Dialog Specialist**: Natural dialogue, voice distinction
-- **Narrative Designer**: Interactive storytelling, branching paths
-- **Genre Specialist**: Genre conventions, market awareness
-- **Book Critic**: Professional literary analysis
-- **Cover Designer**: Visual storytelling, KDP compliance
-
-## Writing Workflows
-
-### Novel Development
-
-1. **Premise Development**: Brainstorm and expand initial concept
-2. **World Building**: Create setting and environment
-3. **Character Creation**: Develop protagonist, antagonist, supporting cast
-4. **Story Architecture**: Three-act structure, scene breakdown
-5. **Chapter Drafting**: Sequential scene development
-6. **Dialog Pass**: Voice refinement and authenticity
-7. **Beta Feedback**: Simulated reader responses
-8. **Final Polish**: Professional editing pass
-
-### Screenplay Workflow
-
-- Industry-standard formatting
-- Visual storytelling emphasis
-- Dialogue-driven narrative
-- Scene/location optimization
-
-### Series Planning
-
-- Multi-book continuity tracking
-- Character evolution across volumes
-- World expansion management
-- Overarching plot coordination
-
-## Templates & Tools
-
-### Character Development
-- Comprehensive character profiles
-- Backstory builders
-- Voice and dialogue patterns
-- Relationship mapping
-
-### Story Structure
-- Three-act outlines
-- Save the Cat beat sheets
-- Hero's Journey mapping
-- Scene-by-scene breakdowns
-
-### World Building
-- Setting documentation
-- Magic/technology systems
-- Cultural development
-- Timeline tracking
-
-### Publishing Support
-- KDP formatting guidelines
-- Cover design briefs
-- Marketing copy templates
-- Beta feedback forms
-
-## Genre Support
-
-### Built-in Genre Checklists
-- Fantasy & Sci-Fi
-- Romance & Thriller
-- Mystery & Horror
-- Literary Fiction
-- Young Adult
-
-Each genre includes:
-- Trope management
-- Reader expectations
-- Market positioning
-- Style guidelines
-
-## Best Practices
-
-### Character Development
-1. Start with internal conflict
-2. Build from wound/lie/want/need
-3. Create unique voice patterns
-4. Track arc progression
-
-### Plot Construction
-1. Begin with clear story question
-2. Escalate stakes progressively
-3. Plant setup/payoff pairs
-4. Balance pacing with character moments
-
-### World Building
-1. Maintain internal consistency
-2. Show through character experience
-3. Build only what serves story
-4. Track all established rules
-
-### Revision Process
-1. Complete draft before major edits
-2. Address structure before prose
-3. Read dialogue aloud
-4. Get distance between drafts
-
-## Integration with Core BMad
-
-The Creative Writing extension maintains compatibility with core BMad features:
-
-- Uses standard agent format
-- Supports slash commands
-- Integrates with workflows
-- Shares elicitation methods
-- Compatible with YOLO mode
-
-## Quick Start Commands
-
-- `*help` - Show available agent commands
-- `*create-outline` - Start story structure
-- `*create-profile` - Develop character
-- `*analyze-structure` - Review plot mechanics
-- `*workshop-dialog` - Refine character voices
-- `*yolo` - Toggle fast-drafting mode
-
-## Tips for Success
-
-1. **Trust the Process**: Follow workflows even when inspired
-2. **Use Elicitation**: Deep-dive when stuck
-3. **Layer Development**: Build story in passes
-4. **Track Everything**: Use templates to maintain consistency
-5. **Iterate Freely**: First drafts are for discovery
-
-Remember: BMad Creative Writing provides structure to liberate creativity, not constrain it.

expansion-packs/bmad-creative-writing/data/story-structures.md

@@ -1,58 +0,0 @@
-# Story Structure Patterns
-
-## Three-Act Structure
-- **Act 1 (25%)**: Setup, inciting incident
-- **Act 2 (50%)**: Confrontation, complications
-- **Act 3 (25%)**: Resolution
-
-## Save the Cat Beats
-1. Opening Image (0-1%)
-2. Setup (1-10%)
-3. Theme Stated (5%)
-4. Catalyst (10%)
-5. Debate (10-20%)
-6. Break into Two (20%)
-7. B Story (22%)
-8. Fun and Games (20-50%)
-9. Midpoint (50%)
-10. Bad Guys Close In (50-75%)
-11. All Is Lost (75%)
-12. Dark Night of Soul (75-80%)
-13. Break into Three (80%)
-14. Finale (80-99%)
-15. Final Image (99-100%)
-## Hero's Journey
-1. Ordinary World
-2. Call to Adventure
-3. Refusal of Call
-4. Meeting Mentor
-5. Crossing Threshold
-6. Tests, Allies, Enemies
-7. Approach to Cave
-8. Ordeal
-9. Reward
-10. Road Back
-11. Resurrection
-12. Return with Elixir
-
-## Seven-Point Structure
-1. Hook
-2. Plot Turn 1
-3. Pinch Point 1
-4. Midpoint
-5. Pinch Point 2
-6. Plot Turn 2
-7. Resolution
-
-## Freytag's Pyramid
-1. Exposition
-2. Rising Action
-3. Climax
-4. Falling Action
-5. Denouement
-
-## Kishōtenketsu (Japanese)
-- **Ki**: Introduction
-- **Shō**: Development
-- **Ten**: Twist
-- **Ketsu**: Conclusion

expansion-packs/bmad-creative-writing/docs/brief.md

@@ -1,183 +0,0 @@
-# Project Brief: BMad Creative Writing Expansion Pack
-
-## Executive Summary
-
-The BMad Creative Writing Expansion Pack is a comprehensive AI-powered creative writing framework that provides specialized agents, workflows, and tools for fiction writers, screenwriters, and narrative designers. It transforms the BMad methodology into a complete creative writing studio, enabling writers to leverage AI assistance across the entire creative process from ideation to publication-ready manuscripts. The system targets both aspiring and professional writers who want to maintain creative control while accelerating their writing process through intelligent automation and structured workflows.
-
-## Problem Statement
-
-Writers face numerous challenges in the modern creative landscape:
-- **Process Fragmentation**: Writers juggle multiple tools (word processors, outlining software, character databases, world-building wikis) without integrated workflows
-- **Creative Blocks**: 40% of writers report regular creative blocks that halt productivity for days or weeks
-- **Quality Consistency**: Maintaining consistency across character voices, world-building details, and plot threads becomes exponentially harder as projects grow
-- **Publishing Complexity**: Self-publishing requires mastery of formatting, cover design, and package assembly - technical skills many writers lack
-- **Feedback Loops**: Getting quality beta feedback is slow, expensive, and often arrives too late in the process
-
-Existing solutions like Scrivener provide organization but lack intelligent assistance. AI writing tools like ChatGPT lack structure and specialized workflows. The market needs a solution that combines structured methodology with AI intelligence specifically tuned for creative writing.
-
-## Proposed Solution
-
-The BMad Creative Writing Expansion Pack provides a complete AI-augmented writing studio through:
-- **10 Specialized Writing Agents**: Each agent masters a specific aspect of craft (plot, character, dialogue, world-building, editing)
-- **Genre-Specific Intelligence**: Agents understand genre conventions and can adapt to sci-fi, fantasy, romance, mystery, thriller contexts
-- **End-to-End Workflows**: From initial premise through KDP-ready packages, workflows guide writers through proven methodologies
-- **Quality Assurance System**: 27 specialized checklists ensure consistency, continuity, and publication readiness
-- **Modular Architecture**: Writers can use individual agents, complete workflows, or custom combinations based on their needs
-
-This solution succeeds where others fail by treating creative writing as a professional craft requiring specialized tools, not generic text generation.
-
-## Target Users
-
-### Primary User Segment: Professional Fiction Writers
-- **Profile**: Published authors with 1-5 books, primarily self-published through KDP/other platforms
-- **Current Workflow**: Draft in Word/Scrivener, self-edit, hire freelance editors, manage own publishing
-- **Pain Points**: Maintaining series consistency, managing multiple projects, expensive editing costs ($2000-5000 per book)
-- **Goals**: Increase output from 1-2 books/year to 3-4, reduce editing costs by 50%, maintain quality standards
-
-### Secondary User Segment: Aspiring Writers & Writing Students
-- **Profile**: Unpublished writers working on first novel, MFA students, workshop participants
-- **Current Workflow**: Sporadic writing habits, limited structure, heavy reliance on writing groups for feedback
-- **Pain Points**: Lack of structured process, difficulty completing projects, limited access to professional feedback
-- **Goals**: Complete first manuscript, develop professional writing habits, learn craft fundamentals through practice
-
-## Goals & Success Metrics
-
-### Business Objectives
-- Achieve 1000 active users within 6 months of launch
-- Generate $50K MRR through subscription model by month 12
-- Establish BMad as the leading AI-powered creative writing methodology
-- Build ecosystem of 50+ community-contributed workflows/agents by year 2
-
-### User Success Metrics
-- Average completion rate for novels increases from 15% to 60%
-- Time from premise to first draft reduced by 40%
-- User-reported satisfaction with AI feedback reaches 85% "helpful or very helpful"
-- 30% of users publish at least one work within first year
-
-### Key Performance Indicators (KPIs)
-- **Monthly Active Writers**: Writers who complete at least 5000 words per month using the system
-- **Workflow Completion Rate**: Percentage of started workflows that reach completion
-- **Agent Utilization**: Average number of different agents used per project
-- **Publishing Success Rate**: Percentage of completed manuscripts that get published
-
-## MVP Scope
-
-### Core Features (Must Have)
-- **Agent System Core**: All 10 writing agents fully functional with clear command interfaces
-- **Novel Writing Workflow**: Complete greenfield novel workflow from premise to draft
-- **Basic Editor Integration**: VSCode/cursor integration for writing environment
-- **Template System**: All 8 core templates (character, scene, outline, etc.) operational
-- **Checkpoint System**: Save/restore project state at any workflow stage
-
-### Out of Scope for MVP
-- Visual world-building tools or maps
-- Collaborative multi-author features
-- Direct publishing API integrations
-- Mobile/tablet applications
-- AI voice synthesis for audiobook creation
-- Translation capabilities
-
-### MVP Success Criteria
-The MVP succeeds if 100 beta users can complete a 50,000-word novel draft using the system with 80%+ reporting the experience as "significantly better" than their previous process.
-
-## Post-MVP Vision
-
-### Phase 2 Features
-- **Series Management**: Tools for maintaining continuity across book series
-- **Publishing Pipeline**: Direct integration with KDP, Draft2Digital, IngramSpark
-- **Collaboration Mode**: Multiple writers/editors working on same project
-- **Custom Agent Training**: Users can train agents on their own published works for style consistency
-
-### Long-term Vision
-Within 2 years, BMad Creative Writing becomes the industry standard for AI-augmented creative writing, with specialized variants for:
-- Academic writing (thesis, dissertations)
-- Technical documentation
-- Game narrative design
-- Interactive fiction/visual novels
-
-### Expansion Opportunities
-- **BMad Writing Certification**: Professional certification program for AI-augmented writers
-- **Agency Partnerships**: White-label solution for literary agencies and publishing houses
-- **Educational Integration**: Curriculum packages for creative writing programs
-- **IP Development**: Tools for adapting novels to screenplays, games, graphic novels
-
-## Technical Considerations
-
-### Platform Requirements
-- **Target Platforms:** Windows, macOS, Linux (via CLI initially)
-- **Browser/OS Support:** Modern browsers for web interface (Chrome 90+, Firefox 88+, Safari 14+)
-- **Performance Requirements:** Handle 100K+ word documents with <100ms response time for agent interactions
-
-### Technology Preferences
-- **Frontend:** React/Next.js for web interface, maintaining VSCode extension
-- **Backend:** Node.js/Python hybrid for agent orchestration
-- **Database:** PostgreSQL for manuscript storage, Redis for session state
-- **Hosting/Infrastructure:** AWS/GCP with CDN for global distribution
-
-### Architecture Considerations
-- **Repository Structure:** Monorepo with packages for agents, workflows, templates, and core
-- **Service Architecture:** Microservices for agent execution, monolithic API gateway
-- **Integration Requirements:** LLM providers (OpenAI, Anthropic, local models), version control (Git), cloud storage
-- **Security/Compliance:** End-to-end encryption for manuscripts, GDPR compliance, no training on user content
-
-## Constraints & Assumptions
-
-### Constraints
-- **Budget:** $50K initial development budget, $5K/month operational
-- **Timeline:** MVP launch in 3 months, Phase 2 in 6 months
-- **Resources:** 2 full-time developers, 1 part-time writer/tester
-- **Technical:** Must work within token limits of current LLMs, no custom model training initially
-
-### Key Assumptions
-- Writers are comfortable with markdown-based writing environments
-- Target users have reliable internet connectivity for AI agent interactions
-- The creative writing market is ready for AI-augmented tools (not viewing them as "cheating")
-- Current LLM capabilities are sufficient for nuanced creative feedback
-- Users will pay $20-50/month for professional writing tools
-
-## Risks & Open Questions
-
-### Key Risks
-- **Market Resistance:** Traditional writing community may reject AI assistance as "inauthentic"
-- **LLM Dependency:** Reliance on third-party LLM providers creates availability and cost risks
-- **Quality Variance:** AI feedback quality may vary significantly based on genre/style
-- **Copyright Concerns:** Unclear legal status of AI-assisted creative works in some jurisdictions
-
-### Open Questions
-- Should we support real-time collaboration or focus on single-author workflows?
-- How do we handle explicit content that may violate LLM provider policies?
-- What's the optimal balance between prescriptive workflows and creative freedom?
-- Should agents have "personalities" or remain neutral tools?
-
-### Areas Needing Further Research
-- Optimal prompt engineering for maintaining consistent character voices
-- Integration possibilities with existing writing tools (Scrivener, Ulysses)
-- Market segmentation between genre writers (romance, sci-fi) vs literary fiction
-- Pricing sensitivity analysis for different user segments
-
-## Appendices
-
-### A. Research Summary
-Based on analysis of competing tools:
-- **Sudowrite**: Strong on prose generation, weak on structure ($20/month)
-- **NovelAI**: Focused on continuation, lacks comprehensive workflows ($15/month)
-- **Scrivener**: Excellent organization, no AI capabilities ($50 one-time)
-- **Market Gap**: No solution combines structured methodology with specialized AI agents
-
-### B. References
-- BMad Core Documentation: [internal docs]
-- Creative Writing Market Report 2024
-- Self-Publishing Author Survey Results
-- AI Writing Tools Comparative Analysis
-
-## Next Steps
-
-### Immediate Actions
-1. Finalize agent command interfaces and test with 5 beta writers
-2. Complete novel-greenfield-workflow with full template integration
-3. Set up development environment with proper CI/CD pipeline
-4. Create demo video showing complete novel chapter creation
-5. Recruit 20 beta testers from writing communities
-
-### PM Handoff
-This Project Brief provides the full context for BMad Creative Writing Expansion Pack. 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.

expansion-packs/bmad-creative-writing/tasks/advanced-elicitation.md

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

expansion-packs/bmad-creative-writing/tasks/analyze-reader-feedback.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 16. Analyze Reader Feedback
-# ------------------------------------------------------------
----
-task:
-  id: analyze-reader-feedback
-  name: Analyze Reader Feedback
-  description: Summarize reader comments, identify trends, update story bible.
-  persona_default: beta-reader
-inputs:
-  - publication-log.md
-steps:
-  - Cluster comments by theme.
-  - Suggest course corrections.
-output: retro.md
-...

expansion-packs/bmad-creative-writing/tasks/analyze-story-structure.md

@@ -1,55 +0,0 @@
-# Analyze Story Structure
-
-## Purpose
-Perform comprehensive structural analysis of a narrative work to identify strengths, weaknesses, and improvement opportunities.
-
-## Process
-
-### 1. Identify Structure Type
-- Three-act structure
-- Five-act structure  
-- Hero's Journey
-- Save the Cat beats
-- Freytag's Pyramid
-- Kishōtenketsu
-- In medias res
-- Non-linear/experimental
-
-### 2. Map Key Points
-- **Opening**: Hook, world establishment, character introduction
-- **Inciting Incident**: What disrupts the status quo?
-- **Plot Point 1**: What locks in the conflict?
-- **Midpoint**: What reversal/revelation occurs?
-- **Plot Point 2**: What raises stakes to maximum?
-- **Climax**: How does central conflict resolve?
-- **Resolution**: What new equilibrium emerges?
-### 3. Analyze Pacing
-- Scene length distribution
-- Tension escalation curve
-- Breather moment placement
-- Action/reflection balance
-- Chapter break effectiveness
-
-### 4. Evaluate Setup/Payoff
-- Track all setups (promises to reader)
-- Verify each has satisfying payoff
-- Identify orphaned setups
-- Find unsupported payoffs
-- Check Chekhov's guns
-
-### 5. Assess Subplot Integration
-- List all subplots
-- Track intersection with main plot
-- Evaluate resolution satisfaction
-- Check thematic reinforcement
-
-### 6. Generate Report
-Create structural report including:
-- Structure diagram
-- Pacing chart
-- Problem areas
-- Suggested fixes
-- Alternative structures
-
-## Output
-Comprehensive structural analysis with actionable recommendations

expansion-packs/bmad-creative-writing/tasks/assemble-kdp-package.md

@@ -1,22 +0,0 @@
-# ------------------------------------------------------------
-# tasks/assemble-kdp-package.md
-# ------------------------------------------------------------
----
-task:
-  id: assemble-kdp-package
-  name: Assemble KDP Cover Package
-  description: Compile final instructions, assets list, and compliance checklist for Amazon KDP upload.
-  persona_default: cover-designer
-inputs:
-  - cover-brief.md
-  - cover-prompts.md
-steps:
-  - Calculate full‑wrap cover dimensions (front, spine, back) using trim size & page count.
-  - List required bleed and margin values.
-  - Provide layout diagram (ASCII or Mermaid) labeling zones.
-  - Insert ISBN placeholder or user‑supplied barcode location.
-  - Populate back‑cover content sections (blurb, reviews, author bio).
-  - Export combined PDF instructions (design-package.md) with link placeholders for final JPEG/PNG.
-  - Execute kdp-cover-ready-checklist; flag any unmet items.
-output: design-package.md
-...

expansion-packs/bmad-creative-writing/tasks/brainstorm-premise.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 1. Brainstorm Premise
-# ------------------------------------------------------------
----
-task:
-  id: brainstorm-premise
-  name: Brainstorm Premise
-  description: Rapidly generate and refine one‑sentence log‑line ideas for a new novel or story.
-  persona_default: plot-architect
-steps:
-  - Ask genre, tone, and any must‑have elements.
-  - Produce 5–10 succinct log‑lines (max 35 words each).
-  - Invite user to select or combine.
-  - Refine the chosen premise into a single powerful sentence.
-output: premise.txt
-...

expansion-packs/bmad-creative-writing/tasks/build-world.md

@@ -1,17 +0,0 @@
-# ------------------------------------------------------------
-# 2. Build World
-# ------------------------------------------------------------
----
-task:
-  id: build-world
-  name: Build World
-  description: Create a concise world guide covering geography, cultures, magic/tech, and history.
-  persona_default: world-builder
-inputs:
-  - concept-brief.md
-steps:
-  - Summarize key themes from concept.
-  - Draft World Guide using world-guide-tmpl.
-  - Execute tasks#advanced-elicitation.
-output: world-guide.md
-...

expansion-packs/bmad-creative-writing/tasks/character-depth-pass.md

@@ -1,15 +0,0 @@
-# ------------------------------------------------------------
-# 9. Character Depth Pass
-# ------------------------------------------------------------
----
-task:
-  id: character-depth-pass
-  name: Character Depth Pass
-  description: Enrich character profiles with backstory and arc details.
-  persona_default: character-psychologist
-inputs:
-  - character-summaries.md
-steps:
-  - For each character, add formative events, internal conflicts, arc milestones.
-output: characters.md
-...

expansion-packs/bmad-creative-writing/tasks/create-doc.md

@@ -1,101 +0,0 @@
-# Create Document from Template (YAML Driven)
-
-## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
-
-**THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL**
-
-When this task is invoked:
-
-1. **DISABLE ALL EFFICIENCY OPTIMIZATIONS** - This workflow requires full user interaction
-2. **MANDATORY STEP-BY-STEP EXECUTION** - Each section must be processed sequentially with user feedback
-3. **ELICITATION IS REQUIRED** - When `elicit: true`, you MUST use the 1-9 format and wait for user response
-4. **NO SHORTCUTS ALLOWED** - Complete documents cannot be created without following this workflow
-
-**VIOLATION INDICATOR:** If you create a complete document without user interaction, you have violated this workflow.
-
-## Critical: Template Discovery
-
-If a YAML Template has not been provided, list all templates from .bmad-creative-writing/templates or ask the user to provide another.
-
-## CRITICAL: Mandatory Elicitation Format
-
-**When `elicit: true`, this is a HARD STOP requiring user interaction:**
-
-**YOU MUST:**
-
-1. Present section content
-2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
-3. **STOP and present numbered options 1-9:**
-   - **Option 1:** Always "Proceed to next section"
-   - **Options 2-9:** Select 8 methods from data/elicitation-methods
-   - End with: "Select 1-9 or just type your question/feedback:"
-4. **WAIT FOR USER RESPONSE** - Do not proceed until user selects option or provides feedback
-
-**WORKFLOW VIOLATION:** Creating content for elicit=true sections without user interaction violates this task.
-
-**NEVER ask yes/no questions or use any other format.**
-
-## Processing Flow
-
-1. **Parse YAML template** - Load template metadata and sections
-2. **Set preferences** - Show current mode (Interactive), confirm output file
-3. **Process each section:**
-   - Skip if condition unmet
-   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
-   - Draft content using section instruction
-   - Present content + detailed rationale
-   - **IF elicit: true** → MANDATORY 1-9 options format
-   - Save to file if possible
-4. **Continue until complete**
-
-## Detailed Rationale Requirements
-
-When presenting section content, ALWAYS include rationale that explains:
-
-- Trade-offs and choices made (what was chosen over alternatives and why)
-- Key assumptions made during drafting
-- Interesting or questionable decisions that need user attention
-- Areas that might need validation
-
-## Elicitation Results Flow
-
-After user selects elicitation method (2-9):
-
-1. Execute method from data/elicitation-methods
-2. Present results with insights
-3. Offer options:
-   - **1. Apply changes and update section**
-   - **2. Return to elicitation menu**
-   - **3. Ask any questions or engage further with this elicitation**
-
-## Agent Permissions
-
-When processing sections with agent permission fields:
-
-- **owner**: Note which agent role initially creates/populates the section
-- **editors**: List agent roles allowed to modify the section
-- **readonly**: Mark sections that cannot be modified after creation
-
-**For sections with restricted access:**
-
-- Include a note in the generated document indicating the responsible agent
-- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
-
-## YOLO Mode
-
-User can type `#yolo` to toggle to YOLO mode (process all sections at once).
-
-## CRITICAL REMINDERS
-
-**❌ NEVER:**
-
-- Ask yes/no questions for elicitation
-- Use any format other than 1-9 numbered options
-- Create new elicitation methods
-
-**✅ ALWAYS:**
-
-- Use exact 1-9 format when elicit: true
-- Select options 2-9 from data/elicitation-methods only
-- Provide detailed rationale explaining decisions
-- End with "Select 1-9 or just type your question/feedback:"

expansion-packs/bmad-creative-writing/tasks/create-draft-section.md

@@ -1,19 +0,0 @@
-# ------------------------------------------------------------
-# 4. Create Draft Section (Chapter)
-# ------------------------------------------------------------
----
-task:
-  id: create-draft-section
-  name: Create Draft Section
-  description: Draft a complete chapter or scene using the chapter-draft-tmpl.
-  persona_default: editor
-inputs:
-  - story-outline.md | snowflake-outline.md | scene-list.md | release-plan.md
-parameters:
-  chapter_number: integer
-steps:
-  - Extract scene beats for the chapter.
-  - Draft chapter using template placeholders.
-  - Highlight dialogue blocks for later polishing.
-output: chapter-{{chapter_number}}-draft.md
-...

expansion-packs/bmad-creative-writing/tasks/critical-review.md

@@ -1,19 +0,0 @@
-# ------------------------------------------------------------
-# Critical Review Task
-# ------------------------------------------------------------
----
-task:
-  id: critical-review
-  name: Critical Review
-  description: Comprehensive professional critique using critic-review-tmpl and rubric checklist.
-  persona_default: book-critic
-inputs:
-  - manuscript file (e.g., draft-manuscript.md or chapter file)
-steps:
-  - If audience/genre not provided, prompt user for details.
-  - Read manuscript (or excerpt) for holistic understanding.
-  - Fill **critic-review-tmpl** with category scores and commentary.
-  - Execute **checklists/critic-rubric-checklist** to spot omissions; revise output if any boxes unchecked.
-  - Present final review to user.
-output: critic-review.md
-...

expansion-packs/bmad-creative-writing/tasks/develop-character.md

@@ -1,17 +0,0 @@
-# ------------------------------------------------------------
-# 3. Develop Character
-# ------------------------------------------------------------
----
-task:
-  id: develop-character
-  name: Develop Character
-  description: Produce rich character profiles with goals, flaws, arcs, and voice notes.
-  persona_default: character-psychologist
-inputs:
-  - concept-brief.md
-steps:
-  - Identify protagonist(s), antagonist(s), key side characters.
-  - For each, fill character-profile-tmpl.
-  - Offer advanced‑elicitation for each profile.
-output: characters.md
-...

expansion-packs/bmad-creative-writing/tasks/execute-checklist.md

@@ -1,93 +0,0 @@
-# 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.
-
-## Available Checklists
-
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
-
-## Instructions
-
-1. **Initial Assessment**
-
-   - If user or the task being run provides a checklist name:
-     - Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
-     - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from {root}/checklists/
-   - If no checklist specified:
-     - Ask the user which checklist they want to use
-     - Present the available options from the files in the checklists folder
-   - Confirm if they want to work through the checklist:
-     - Section by section (interactive mode - very time consuming)
-     - All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
-
-2. **Document and Artifact Gathering**
-
-   - Each checklist will specify its required documents/artifacts at the beginning
-   - Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
-
-3. **Checklist Processing**
-
-   If in interactive mode:
-
-   - Work through each section of the checklist one at a time
-   - For each section:
-     - Review all items in the section following instructions for that section embedded in the checklist
-     - Check each item against the relevant documentation or artifacts as appropriate
-     - Present summary of findings for that section, highlighting warnings, errors and non applicable items (rationale for non-applicability).
-     - Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
-
-   If in YOLO mode:
-
-   - Process all sections at once
-   - Create a comprehensive report of all findings
-   - Present the complete analysis to the user
-
-4. **Validation Approach**
-
-   For each checklist item:
-
-   - Read and understand the requirement
-   - Look for evidence in the documentation that satisfies the requirement
-   - Consider both explicit mentions and implicit coverage
-   - Aside from this, follow all checklist llm instructions
-   - Mark items as:
-     - ✅ PASS: Requirement clearly met
-     - ❌ FAIL: Requirement not met or insufficient coverage
-     - ⚠️ PARTIAL: Some aspects covered but needs improvement
-     - N/A: Not applicable to this case
-
-5. **Section Analysis**
-
-   For each section:
-
-   - think step by step to calculate pass rate
-   - Identify common themes in failed items
-   - Provide specific recommendations for improvement
-   - In interactive mode, discuss findings with user
-   - Document any user decisions or explanations
-
-6. **Final Report**
-
-   Prepare a summary that includes:
-
-   - Overall checklist completion status
-   - Pass rates by section
-   - List of failed items with context
-   - Specific recommendations for improvement
-   - Any sections or items marked as N/A with justification
-
-## Checklist Execution Methodology
-
-Each checklist now contains embedded LLM prompts and instructions that will:
-
-1. **Guide thorough thinking** - Prompts ensure deep analysis of each section
-2. **Request specific artifacts** - Clear instructions on what documents/access is needed
-3. **Provide contextual guidance** - Section-specific prompts for better validation
-4. **Generate comprehensive reports** - Final summary with detailed findings
-
-The LLM will:
-
-- Execute the complete checklist validation
-- Present a final report with pass/fail rates and key findings
-- Offer to provide detailed analysis of any section, especially those with warnings or failures

expansion-packs/bmad-creative-writing/tasks/expand-premise.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 7. Expand Premise (Snowflake Step 2)
-# ------------------------------------------------------------
----
-task:
-  id: expand-premise
-  name: Expand Premise
-  description: Turn a 1‑sentence idea into a 1‑paragraph summary.
-  persona_default: plot-architect
-inputs:
-  - premise.txt
-steps:
-  - Ask for genre confirmation.
-  - Draft one paragraph (~5 sentences) covering protagonist, conflict, stakes.
-output: premise-paragraph.md
-...

expansion-packs/bmad-creative-writing/tasks/expand-synopsis.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 8. Expand Synopsis (Snowflake Step 4)
-# ------------------------------------------------------------
----
-task:
-  id: expand-synopsis
-  name: Expand Synopsis
-  description: Build a 1‑page synopsis from the paragraph summary.
-  persona_default: plot-architect
-inputs:
-  - premise-paragraph.md
-steps:
-  - Outline three‑act structure in prose.
-  - Keep under 700 words.
-output: synopsis.md
-...

expansion-packs/bmad-creative-writing/tasks/final-polish.md

@@ -1,16 +0,0 @@
-# ------------------------------------------------------------
-# 14. Final Polish
-# ------------------------------------------------------------
----
-task:
-  id: final-polish
-  name: Final Polish
-  description: Line‑edit for style, clarity, grammar.
-  persona_default: editor
-inputs:
-  - chapter-dialog.md | polished-manuscript.md
-steps:
-  - Correct grammar and tighten prose.
-  - Ensure consistent voice.
-output: chapter-final.md | final-manuscript.md
-...

expansion-packs/bmad-creative-writing/tasks/generate-cover-brief.md

@@ -1,18 +0,0 @@
-# ------------------------------------------------------------
-# tasks/generate-cover-brief.md
-# ------------------------------------------------------------
----
-task:
-  id: generate-cover-brief
-  name: Generate Cover Brief
-  description: Interactive questionnaire that captures all creative and technical parameters for the cover.
-  persona_default: cover-designer
-steps:
-  - Ask for title, subtitle, author name, series info.
-  - Ask for genre, target audience, comparable titles.
-  - Ask for trim size (e.g., 6"x9"), page count, paper color.
-  - Ask for mood keywords, primary imagery, color palette.
-  - Ask what should appear on back cover (blurb, reviews, author bio, ISBN location).
-  - Fill cover-design-brief-tmpl with collected info.
-output: cover-brief.md
-...

expansion-packs/bmad-creative-writing/tasks/generate-cover-prompts.md

@@ -1,19 +0,0 @@
-# ------------------------------------------------------------
-# tasks/generate-cover-prompts.md
-# ------------------------------------------------------------
----
-task:
-  id: generate-cover-prompts
-  name: Generate Cover Prompts
-  description: Produce AI image generator prompts for front cover artwork plus typography guidance.
-  persona_default: cover-designer
-inputs:
-  - cover-brief.md
-steps:
-  - Extract mood, genre, imagery from brief.
-  - Draft 3‑5 alternative stable diffusion / DALL·E prompts (include style, lens, color keywords).
-  - Specify safe negative prompts.
-  - Provide font pairing suggestions (Google Fonts) matching genre.
-  - Output prompts and typography guidance to cover-prompts.md.
-output: cover-prompts.md
-...