bmad-method 5.1.3 → 6.0.0-alpha.0

package/tools/validate-bundles.js

@@ -0,0 +1,87 @@
+const fs = require('fs-extra');
+const path = require('node:path');
+const xml2js = require('xml2js');
+const chalk = require('chalk');
+const glob = require('glob');
+
+async function validateXmlFile(filePath) {
+  try {
+    const content = await fs.readFile(filePath, 'utf8');
+    await xml2js.parseStringPromise(content, {
+      strict: true,
+      explicitArray: false,
+    });
+    return { valid: true };
+  } catch (error) {
+    return { valid: false, error: error.message };
+  }
+}
+
+async function validateAllBundles() {
+  console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════'));
+  console.log(chalk.cyan.bold('        VALIDATING WEB BUNDLE XML FILES'));
+  console.log(chalk.cyan.bold('═══════════════════════════════════════════════\n'));
+
+  const bundlesDir = path.join(__dirname, '..', 'web-bundles');
+
+  // Find all XML files in web-bundles
+  const pattern = path.join(bundlesDir, '**/*.xml');
+  const files = glob.sync(pattern);
+
+  if (files.length === 0) {
+    console.log(chalk.yellow('No XML files found in web-bundles directory'));
+    return;
+  }
+
+  console.log(`Found ${chalk.bold(files.length)} XML files to validate\n`);
+
+  let validCount = 0;
+  let invalidCount = 0;
+  const invalidFiles = [];
+
+  for (const file of files) {
+    const relativePath = path.relative(bundlesDir, file);
+    const result = await validateXmlFile(file);
+
+    if (result.valid) {
+      console.log(`${chalk.green('✓')} ${relativePath}`);
+      validCount++;
+    } else {
+      console.log(`${chalk.red('✗')} ${relativePath}`);
+      console.log(`  ${chalk.red('→')} ${result.error}`);
+      invalidCount++;
+      invalidFiles.push({ path: relativePath, error: result.error });
+    }
+  }
+
+  // Summary
+  console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════'));
+  console.log(chalk.cyan.bold('                 SUMMARY'));
+  console.log(chalk.cyan.bold('═══════════════════════════════════════════════\n'));
+
+  console.log(`  Total files checked: ${chalk.bold(files.length)}`);
+  console.log(`  Valid XML files:     ${chalk.green(validCount)}`);
+  console.log(`  Invalid XML files:   ${invalidCount > 0 ? chalk.red(invalidCount) : chalk.green(invalidCount)}`);
+
+  if (invalidFiles.length > 0) {
+    console.log(chalk.red.bold('\n  Invalid Files:'));
+    for (const { path, error } of invalidFiles) {
+      console.log(`    ${chalk.red('•')} ${path}`);
+      if (error.length > 100) {
+        console.log(`      ${error.slice(0, 100)}...`);
+      } else {
+        console.log(`      ${error}`);
+      }
+    }
+  }
+
+  console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════\n'));
+
+  process.exit(invalidCount > 0 ? 1 : 0);
+}
+
+// Run validation
+validateAllBundles().catch((error) => {
+  console.error(chalk.red('Error running validation:'), error);
+  process.exit(1);
+});

package/.github/ISSUE_TEMPLATE/feature_request.md

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

package/README.md

@@ -1,221 +0,0 @@
-# BMad-Method: Universal AI Agent Framework
-
-[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
-[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
-
-Foundations in Agentic Agile Driven Development, known as the Breakthrough Method of Agile AI-Driven Development, yet so much more. Transform any domain with specialized AI expertise: software development, entertainment, creative writing, business strategy to personal wellness just to name a few.
-
-**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)**
-
-**[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you! **Some mobile and VPN may have issue joining the discord, this is a discord issue - if the invite does not work, try from your own internet or another network, or non-VPN.**
-
-⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-Method and you will be notified of updates!
-
-## Overview
-
-**BMad Method's Two Key Innovations:**
-
-**1. Agentic Planning:** Dedicated agents (Analyst, PM, Architect) collaborate with you to create detailed, consistent PRDs and Architecture documents. Through advanced prompt engineering and human-in-the-loop refinement, these planning agents produce comprehensive specifications that go far beyond generic AI task generation.
-
-**2. Context-Engineered Development:** The Scrum Master agent then transforms these detailed plans into hyper-detailed development stories that contain everything the Dev agent needs - full context, implementation details, and architectural guidance embedded directly in story files.
-
-This two-phase approach eliminates both **planning inconsistency** and **context loss** - the biggest problems in AI-assisted development. Your Dev agent opens a story file with complete understanding of what to build, how to build it, and why.
-
-**📖 [See the complete workflow in the User Guide](docs/user-guide.md)** - Planning phase, development cycle, and all agent roles
-
-## Quick Navigation
-
-### Understanding the BMad Workflow
-
-**Before diving in, review these critical workflow diagrams that explain how BMad works:**
-
-1. **[Planning Workflow (Web UI)](docs/user-guide.md#the-planning-workflow-web-ui)** - How to create PRD and Architecture documents
-2. **[Core Development Cycle (IDE)](docs/user-guide.md#the-core-development-cycle-ide)** - How SM, Dev, and QA agents collaborate through story files
-
-> ⚠️ **These diagrams explain 90% of BMad Method Agentic Agile flow confusion** - Understanding the PRD+Architecture creation and the SM/Dev/QA workflow and how agents pass notes through story files is essential - and also explains why this is NOT taskmaster or just a simple task runner!
-
-### What would you like to do?
-
-- **[Install and Build software with Full Stack Agile AI Team](#quick-start)** → Quick Start Instruction
-- **[Learn how to use BMad](docs/user-guide.md)** → Complete user guide and walkthrough
-- **[See available AI agents](/bmad-core/agents))** → Specialized roles for your team
-- **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** → Creative writing, business, wellness, education
-- **[Create my own AI agents](docs/expansion-packs.md)** → Build agents for your domain
-- **[Browse ready-made expansion packs](expansion-packs/)** → Game dev, DevOps, infrastructure and get inspired with ideas and examples
-- **[Understand the architecture](docs/core-architecture.md)** → Technical deep dive
-- **[Join the community](https://discord.gg/gk8jAdXWmj)** → Get help and share ideas
-
-## Important: Keep Your BMad Installation Updated
-
-**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
-
-```bash
-npx bmad-method install
-# OR
-git pull
-npm run install:bmad
-```
-
-This will:
-
-- ✅ Automatically detect your existing v4 installation
-- ✅ Update only the files that have changed and add new files
-- ✅ Create `.bak` backup files for any custom modifications you've made
-- ✅ Preserve your project-specific configurations
-
-This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations!
-
-## Quick Start
-
-### One Command for Everything (IDE Installation)
-
-**Just run one of these commands:**
-
-```bash
-npx bmad-method install
-# OR explicitly use stable tag:
-npx bmad-method@stable install
-# OR if you already have BMad installed:
-git pull
-npm run install:bmad
-```
-
-This single command handles:
-
-- **New installations** - Sets up BMad in your project
-- **Upgrades** - Updates existing installations automatically
-- **Expansion packs** - Installs any expansion packs you've added to package.json
-
-> **That's it!** Whether you're installing for the first time, upgrading, or adding expansion packs - these commands do everything.
-
-**Prerequisites**: [Node.js](https://nodejs.org) v20+ required
-
-### Fastest Start: Web UI Full Stack Team at your disposal (2 minutes)
-
-1. **Get the bundle**: Save or clone the [full stack team file](dist/teams/team-fullstack.txt) or choose another team
-2. **Create AI agent**: Create a new Gemini Gem or CustomGPT
-3. **Upload & configure**: Upload the file and set instructions: "Your critical operating instructions are attached, do not break character as directed"
-4. **Start Ideating and Planning**: Start chatting! Type `*help` to see available commands or pick an agent like `*analyst` to start right in on creating a brief.
-5. **CRITICAL**: Talk to BMad Orchestrator in the web at ANY TIME (#bmad-orchestrator command) and ask it questions about how this all works!
-6. **When to move to the IDE**: Once you have your PRD, Architecture, optional UX and Briefs - its time to switch over to the IDE to shard your docs, and start implementing the actual code! See the [User guide](docs/user-guide.md) for more details
-
-### Alternative: Clone and Build
-
-```bash
-git clone https://github.com/bmadcode/bmad-method.git
-npm run install:bmad # build and install all to a destination folder
-```
-
-## 🌟 Beyond Software Development - Expansion Packs
-
-BMad's natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMad-Method with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
-
-## Codebase Flattener Tool
-
-The BMad-Method includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
-
-### Features
-
-- **AI-Optimized Output**: Generates clean XML format specifically designed for AI model consumption
-- **Smart Filtering**: Automatically respects `.gitignore` patterns to exclude unnecessary files
-- **Binary File Detection**: Intelligently identifies and excludes binary files, focusing on source code
-- **Progress Tracking**: Real-time progress indicators and comprehensive completion statistics
-- **Flexible Output**: Customizable output file location and naming
-
-### Usage
-
-```bash
-# Basic usage - creates flattened-codebase.xml in current directory
-npx bmad-method flatten
-
-# Specify custom input directory
-npx bmad-method flatten --input /path/to/source/directory
-npx bmad-method flatten -i /path/to/source/directory
-
-# Specify custom output file
-npx bmad-method flatten --output my-project.xml
-npx bmad-method flatten -o /path/to/output/codebase.xml
-
-# Combine input and output options
-npx bmad-method flatten --input /path/to/source --output /path/to/output/codebase.xml
-```
-
-### Example Output
-
-The tool will display progress and provide a comprehensive summary:
-
-```text
-📊 Completion Summary:
-✅ Successfully processed 156 files into flattened-codebase.xml
-📁 Output file: /path/to/your/project/flattened-codebase.xml
-📏 Total source size: 2.3 MB
-📄 Generated XML size: 2.1 MB
-📝 Total lines of code: 15,847
-🔢 Estimated tokens: 542,891
-📊 File breakdown: 142 text, 14 binary, 0 errors
-```
-
-The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMad-Method projects.
-
-#### Advanced Usage & Options
-
-- CLI options
-  - `-i, --input <path>`: Directory to flatten. Default: current working directory or auto-detected project root when run interactively.
-  - `-o, --output <path>`: Output file path. Default: `flattened-codebase.xml` in the chosen directory.
-- Interactive mode
-  - If you do not pass `--input` and `--output` and the terminal is interactive (TTY), the tool will attempt to detect your project root (by looking for markers like `.git`, `package.json`, etc.) and prompt you to confirm or override the paths.
-  - In non-interactive contexts (e.g., CI), it will prefer the detected root silently; otherwise it falls back to the current directory and default filename.
-- File discovery and ignoring
-  - Uses `git ls-files` when inside a git repository for speed and correctness; otherwise falls back to a glob-based scan.
-  - Applies your `.gitignore` plus a curated set of default ignore patterns (e.g., `node_modules`, build outputs, caches, logs, IDE folders, lockfiles, large media/binaries, `.env*`, and previously generated XML outputs).
-- Binary handling
-  - Binary files are detected and excluded from the XML content. They are counted in the final summary but not embedded in the output.
-- XML format and safety
-  - UTF-8 encoded file with root element `<files>`.
-  - Each text file is emitted as a `<file path="relative/path">` element whose content is wrapped in `<![CDATA[ ... ]]>`.
-  - The tool safely handles occurrences of `]]>` inside content by splitting the CDATA to preserve correctness.
-  - File contents are preserved as-is and indented for readability inside the XML.
-- Performance
-  - Concurrency is selected automatically based on your CPU and workload size. No configuration required.
-  - Running inside a git repo improves discovery performance.
-
-#### Minimal XML example
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<files>
-  <file path="src/index.js"><![CDATA[
-    // your source content
-  ]]></file>
-</files>
-```
-
-## Documentation & Resources
-
-### Essential Guides
-
-- 📖 **[User Guide](docs/user-guide.md)** - Complete walkthrough from project inception to completion
-- 🏗️ **[Core Architecture](docs/core-architecture.md)** - Technical deep dive and system design
-- 🚀 **[Expansion Packs Guide](docs/expansion-packs.md)** - Extend BMad to any domain beyond software development
-
-## Support
-
-- 💬 [Discord Community](https://discord.gg/gk8jAdXWmj)
-- 🐛 [Issue Tracker](https://github.com/bmadcode/bmad-method/issues)
-- 💬 [Discussions](https://github.com/bmadcode/bmad-method/discussions)
-
-## Contributing
-
-**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
-
-📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete guide to contributing, including guidelines, process, and requirements
-
-## License
-
-MIT License - see [LICENSE](LICENSE) for details.
-
-[![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
-
-<sub>Built with ❤️ for the AI-assisted development community</sub>

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

@@ -1,14 +0,0 @@
-bundle:
-  name: Team All
-  icon: 👥
-  description: Includes every core system agent.
-agents:
-  - bmad-orchestrator
-  - "*"
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml

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

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

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

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

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

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

package/bmad-core/agents/analyst.md

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

package/bmad-core/agents/architect.md

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

package/bmad-core/agents/bmad-master.md

@@ -1,107 +0,0 @@
-# BMad Master
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded
-  - CRITICAL: Do NOT run discovery tasks automatically
-  - CRITICAL: NEVER LOAD {root}/data/bmad-kb.md UNLESS USER TYPES *kb
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: BMad Master
-  id: bmad-master
-  title: BMad Master Task Executor
-  icon: 🧙
-  whenToUse: Use when you need comprehensive expertise across all domains, running 1 off tasks that do not require a persona, or just wanting to use the same agent for many things.
-persona:
-  role: Master Task Executor & BMad Method Expert
-  identity: Universal executor of all BMad-Method capabilities, directly runs any resource
-  core_principles:
-    - Execute any resource directly without persona transformation
-    - Load resources at runtime, never pre-load
-    - Expert knowledge of all BMad resources if using *kb
-    - Always presents numbered lists for choices
-    - Process (*) commands immediately, All commands require * prefix when used (e.g., *help)
-
-commands:
-  - help: Show these listed commands in a numbered list
-  - kb: Toggle KB mode off (default) or on, when on will load and reference the {root}/data/bmad-kb.md and converse with the user answering his questions with this informational resource
-  - task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
-  - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
-  - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
-  - yolo: Toggle Yolo Mode
-  - exit: Exit (confirm)
-
-dependencies:
-  tasks:
-    - advanced-elicitation.md
-    - facilitate-brainstorming-session.md
-    - brownfield-create-epic.md
-    - brownfield-create-story.md
-    - correct-course.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - document-project.md
-    - create-next-story.md
-    - execute-checklist.md
-    - generate-ai-frontend-prompt.md
-    - index-docs.md
-    - shard-doc.md
-  templates:
-    - architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-    - brownfield-prd-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - front-end-architecture-tmpl.yaml
-    - front-end-spec-tmpl.yaml
-    - fullstack-architecture-tmpl.yaml
-    - market-research-tmpl.yaml
-    - prd-tmpl.yaml
-    - project-brief-tmpl.yaml
-    - story-tmpl.yaml
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-    - elicitation-methods.md
-    - technical-preferences.md
-  workflows:
-    - brownfield-fullstack.md
-    - brownfield-service.md
-    - brownfield-ui.md
-    - greenfield-fullstack.md
-    - greenfield-service.md
-    - greenfield-ui.md
-  checklists:
-    - architect-checklist.md
-    - change-checklist.md
-    - pm-checklist.md
-    - po-master-checklist.md
-    - story-dod-checklist.md
-    - story-draft-checklist.md
-```