bmad-method 6.0.0-alpha.6 → 6.0.0-alpha.7

package/.claude/commands/bmad/cis/agents/storyteller.md

@@ -1,59 +0,0 @@
----
-name: 'storyteller'
-description: 'Master Storyteller'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="bmad/cis/agents/storyteller.md" name="Sophia" title="Master Storyteller" icon="📖">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/cis/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-
-  <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="exec">
-        When menu item has: exec="path/to/file.md"
-        Actually LOAD and EXECUTE the file at that path - do not improvise
-        Read the complete file and follow all instructions within it
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Expert Storytelling Guide + Narrative Strategist</role>
-    <identity>Master storyteller with 50+ years crafting compelling narratives across multiple mediums. Expert in narrative frameworks, emotional psychology, and audience engagement. Background in journalism, screenwriting, and brand storytelling with deep understanding of universal human themes.</identity>
-    <communication_style>Speaks in a flowery whimsical manner, every communication is like being enraptured by the master story teller. Insightful and engaging with natural storytelling ability. Articulate and empathetic approach that connects emotionally with audiences. Strategic in narrative construction while maintaining creative flexibility and authenticity.</communication_style>
-    <principles>I believe that powerful narratives connect with audiences on deep emotional levels by leveraging timeless human truths that transcend context while being carefully tailored to platform and audience needs. My approach centers on finding and amplifying the authentic story within any subject, applying proven frameworks flexibly to showcase change and growth through vivid details that make the abstract concrete. I craft stories designed to stick in hearts and minds, building and resolving tension in ways that create lasting engagement and meaningful impact.</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*story" exec="{project-root}/bmad/cis/workflows/storytelling/workflow.yaml">Craft compelling narrative using proven frameworks</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

package/.claude/commands/bmad/cis/workflows/README.md

@@ -1,37 +0,0 @@
-# CIS Workflows
-
-## Available Workflows in cis
-
-**design-thinking**
-
-- Path: `bmad/cis/workflows/design-thinking/workflow.yaml`
-- Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.
-
-**innovation-strategy**
-
-- Path: `bmad/cis/workflows/innovation-strategy/workflow.yaml`
-- Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.
-
-**problem-solving**
-
-- Path: `bmad/cis/workflows/problem-solving/workflow.yaml`
-- Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.
-
-**storytelling**
-
-- Path: `bmad/cis/workflows/storytelling/workflow.yaml`
-- Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.
-
-## Execution
-
-When running any workflow:
-
-1. LOAD {project-root}/bmad/core/tasks/workflow.xml
-2. Pass the workflow path as 'workflow-config' parameter
-3. Follow workflow.xml instructions EXACTLY
-4. Save outputs after EACH section
-
-## Modes
-
-- Normal: Full interaction
-- #yolo: Skip optional steps

package/.claude/commands/bmad/cis/workflows/design-thinking.md

@@ -1,15 +0,0 @@
----
-description: 'Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.'
----
-
-# design-thinking
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/cis/workflows/design-thinking/workflow.yaml
-3. Pass the yaml path bmad/cis/workflows/design-thinking/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/cis/workflows/innovation-strategy.md

@@ -1,15 +0,0 @@
----
-description: 'Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.'
----
-
-# innovation-strategy
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/cis/workflows/innovation-strategy/workflow.yaml
-3. Pass the yaml path bmad/cis/workflows/innovation-strategy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/cis/workflows/problem-solving.md

@@ -1,15 +0,0 @@
----
-description: 'Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.'
----
-
-# problem-solving
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/cis/workflows/problem-solving/workflow.yaml
-3. Pass the yaml path bmad/cis/workflows/problem-solving/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/cis/workflows/storytelling.md

@@ -1,15 +0,0 @@
----
-description: 'Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.'
----
-
-# storytelling
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/cis/workflows/storytelling/workflow.yaml
-3. Pass the yaml path bmad/cis/workflows/storytelling/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

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

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

package/bmad/_cfg/agents/bmm-analyst.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-architect.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-dev.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-pm.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-sm.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-tea.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-tech-writer.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/_cfg/agents/bmm-ux-designer.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/bmad/bmm/README.md

@@ -1,128 +0,0 @@
-# BMM - BMad Method Module
-
-Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
-
----
-
-## 📚 Complete Documentation
-
-👉 **[BMM Documentation Hub](./docs/README.md)** - Start here for complete guides, tutorials, and references
-
-**Quick Links:**
-
-- **[Quick Start Guide](./docs/quick-start.md)** - New to BMM? Start here (15 min)
-- **[Agents Guide](./docs/agents-guide.md)** - Meet your 12 specialized AI agents (45 min)
-- **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - How BMM adapts to project size (42 min)
-- **[FAQ](./docs/faq.md)** - Quick answers to common questions
-- **[Glossary](./docs/glossary.md)** - Key terminology reference
-
----
-
-## 🏗️ Module Structure
-
-This module contains:
-
-```
-bmm/
-├── agents/          # 12 specialized AI agents (PM, Architect, SM, DEV, TEA, etc.)
-├── workflows/       # 34 workflows across 4 phases + testing
-├── teams/           # Pre-configured agent groups
-├── tasks/           # Atomic work units
-├── testarch/        # Comprehensive testing infrastructure
-└── docs/            # Complete user documentation
-```
-
-### Agent Roster
-
-**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer
-**Game Development:** Game Designer, Game Developer, Game Architect
-**Orchestration:** BMad Master (from Core)
-
-👉 **[Full Agents Guide](./docs/agents-guide.md)** - Roles, workflows, and when to use each agent
-
-### Workflow Phases
-
-**Phase 0:** Documentation (brownfield only)
-**Phase 1:** Analysis (optional) - 5 workflows
-**Phase 2:** Planning (required) - 6 workflows
-**Phase 3:** Solutioning (Level 3-4) - 2 workflows
-**Phase 4:** Implementation (iterative) - 10 workflows
-**Testing:** Quality assurance (parallel) - 9 workflows
-
-👉 **[Workflow Guides](./docs/README.md#-workflow-guides)** - Detailed documentation for each phase
-
----
-
-## 🚀 Getting Started
-
-**New Project:**
-
-```bash
-# Install BMM
-npx bmad-method@alpha install
-
-# Load Analyst agent in your IDE, then:
-*workflow-init
-```
-
-**Existing Project (Brownfield):**
-
-```bash
-# Document your codebase first
-*document-project
-
-# Then initialize
-*workflow-init
-```
-
-👉 **[Quick Start Guide](./docs/quick-start.md)** - Complete setup and first project walkthrough
-
----
-
-## 🎯 Key Concepts
-
-### Scale-Adaptive Design
-
-BMM automatically adjusts to project complexity (Levels 0-4):
-
-- **Level 0-1:** Quick Spec Flow for bug fixes and small features
-- **Level 2:** PRD with optional architecture
-- **Level 3-4:** Full PRD + comprehensive architecture
-
-👉 **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - Complete level breakdown
-
-### Story-Centric Implementation
-
-Stories move through a defined lifecycle: `backlog → drafted → ready → in-progress → review → done`
-
-Just-in-time epic context and story context provide exact expertise when needed.
-
-👉 **[Implementation Workflows](./docs/workflows-implementation.md)** - Complete story lifecycle guide
-
-### Multi-Agent Collaboration
-
-Use party mode to engage all 19+ agents (from BMM, CIS, BMB, custom modules) in group discussions for strategic decisions, creative brainstorming, and complex problem-solving.
-
-👉 **[Party Mode Guide](./docs/party-mode.md)** - How to orchestrate multi-agent collaboration
-
----
-
-## 📖 Additional Resources
-
-- **[Brownfield Guide](./docs/brownfield-guide.md)** - Working with existing codebases
-- **[Quick Spec Flow](./docs/quick-spec-flow.md)** - Fast-track for Level 0-1 projects
-- **[Enterprise Agentic Development](./docs/enterprise-agentic-development.md)** - Team collaboration patterns
-- **[Troubleshooting](./docs/troubleshooting.md)** - Common issues and solutions
-- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure Claude Code, Cursor, Windsurf, etc.
-
----
-
-## 🤝 Community
-
-- **[Discord](https://discord.gg/gk8jAdXWmj)** - Get help, share feedback (#general-dev, #bugs-issues)
-- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
-- **[YouTube](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
-
----
-
-**Ready to build?** → [Start with the Quick Start Guide](./docs/quick-start.md)