bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.22

package/docs/modules/bmb-bmad-builder/agent-creation-guide.md

@@ -0,0 +1,166 @@
+# Agent Creation Guide
+
+Create your own custom agents using the BMAD Builder workflow.
+
+## Overview
+
+The BMAD Builder (BMB) module provides an interactive workflow that guides you through creating a custom agent from concept to completion. You define the agent's purpose, personality, capabilities, and menu - then the workflow generates a complete, ready-to-use agent file.
+
+## Before You Start
+
+**Prerequisites:**
+- BMAD installed with the BMB module
+- An idea for what you want your agent to do
+- About 15-30 minutes for your first agent
+
+**Know Before You Go:**
+- What problem should your agent solve?
+- Who will use this agent?
+- What should the agent be able to do?
+
+## Quick Start
+
+### 1. Start the Workflow
+
+In your IDE (Claude Code, Cursor, etc.), invoke the create-agent workflow:
+
+```
+"Run the BMAD Builder create-agent workflow"
+```
+
+Or trigger it via the BMAD Master menu.
+
+### 2. Follow the Steps
+
+The workflow guides you through:
+
+| Step | What You'll Do |
+|------|----------------|
+| **Brainstorm** (optional) | Explore ideas with creative techniques |
+| **Discovery** | Define the agent's purpose and goals |
+| **Type & Metadata** | Choose Simple or Expert, name your agent |
+| **Persona** | Craft the agent's personality and principles |
+| **Commands** | Define what the agent can do |
+| **Activation** | Set up autonomous behaviors (optional) |
+| **Build** | Generate the agent file |
+| **Validation** | Review and verify everything works |
+
+### 3. Install Your Agent
+
+Once created, package your agent for installation:
+
+```
+my-custom-stuff/
+├── module.yaml          # Contains: unitary: true
+├── agents/
+│   └── {agent-name}/
+│       ├── {agent-name}.agent.yaml
+│       └── _memory/              # Expert agents only
+│           └── {sidecar-folder}/
+└── workflows/           # Optional: custom workflows
+```
+
+See [Custom Content Installation](./custom-content-installation.md) for details.
+
+## Choosing Your Agent Type
+
+The workflow will help you decide, but here's the quick reference:
+
+### Choose Simple Agent When:
+
+- Task is well-defined and focused
+- Don't need persistent memory
+- Want fast setup and deployment
+- Single-purpose assistant (e.g., commit messages, code review)
+
+**Example:** A "Code Commenter" that reads files and adds helpful comments.
+
+### Choose Expert Agent When:
+
+- Domain requires specialized knowledge
+- Need persistent memory across sessions
+- Agent coordinates complex workflows
+- Building ongoing project infrastructure
+
+**Example:** A "Security Architect" that remembers your design decisions and maintains security standards across the project.
+
+### Choose Module Agent When:
+
+- Agent builds other agents or workflows
+- Need integration with module system
+- Creating professional tooling
+
+**Example:** A "Team Builder" that helps set up agents for new team members.
+
+## The Persona System
+
+Your agent's personality is defined by four fields:
+
+| Field | Purpose | Example |
+|-------|---------|---------|
+| **Role** | What they do | "Senior code reviewer who catches bugs and suggests improvements" |
+| **Identity** | Who they are | "Friendly but exacting, believes clean code is a craft" |
+| **Communication Style** | How they speak | "Direct, constructive, explains the 'why' behind suggestions" |
+| **Principles** | Why they act | "Security first, clarity over cleverness, test what you fix" |
+
+**Key:** Keep each field focused on its purpose. The role isn't personality; the identity isn't job description.
+
+## Tips for Success
+
+### Start Small
+
+Your first agent should solve **one problem well**. You can always add more capabilities later.
+
+### Learn by Example
+
+Study the reference agents in `src/modules/bmb/reference/agents/`:
+- **Simple:** [commit-poet](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml)
+- **Expert:** [journal-keeper](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper)
+
+### Write Great Principles
+
+The first principle should "activate" the agent's expertise:
+
+❌ **Weak:** "Be helpful and accurate"
+✅ **Strong:** "Channel decades of security expertise: threat modeling begins with trust boundaries, never trust client input, defense in depth is non-negotiable"
+
+### Use the Menu System
+
+The workflow provides options at each step:
+- **[A] Advanced** - Get deeper insights and reasoning
+- **[P] Party** - Get multiple agent perspectives
+- **[C] Continue** - Move to the next step
+
+Use these when you need extra input or creative options.
+
+## After Creation
+
+### Test Your Agent
+
+1. Install your custom module using the BMAD installer
+2. Invoke your new agent in your IDE
+3. Try each menu command
+4. Verify the personality feels right
+
+### Iterate
+
+If something isn't right:
+1. Edit the agent YAML directly, or
+2. Edit the customization file in `_bmad/_config/agents/`
+3. Rebuild using `npx bmad-method build <agent-name>`
+
+### Share
+
+Package your agent as a standalone module (see [Installation Guide](../../bmad-core-concepts/installing/)) and share it with your team or the community.
+
+## Further Reading
+
+- **[Agent Architecture](./index.md)** - Deep technical details on agent types
+- **[Agent Customization](../../bmad-core-concepts/agent-customization/)** - Modify agents without editing core files
+- **[Custom Content Installation](./custom-content-installation.md)** - Package and distribute your agents
+
+---
+
+**Ready?** Start the workflow and create your first agent!
+
+[← Back to BMB Documentation](./index.md)

package/docs/{custom-content-installation.md → modules/bmb-bmad-builder/custom-content-installation.md}

@@ -2,7 +2,7 @@
 
 This guide explains how to create and install custom BMAD content including agents, workflows, and modules. Custom content extends BMAD's functionality with specialized tools and workflows that can be shared across projects or teams.
 
-For detailed information about the different types of custom content available, see [Custom Content](./custom-content.md).
+For detailed information about the different types of custom content available, see [Custom Content](modules/bmb-bmad-builder/custom-content.md).
 
 You can find example custom modules in the `samples/sample-custom-modules/` folder of the repository. Download either of the sample folders to try them out.
 
@@ -26,10 +26,8 @@ To create an installable custom module:
    - Create a folder with a short, abbreviated name (e.g., `cis` for Creative Intelligence Suite)
    - The folder name serves as the module code
 
-2. **Required Files**
-   - Include a `module.yaml` file in the root folder
-   - This file drives the installation process when used by the BMAD installer
-   - Reference existing modules or the BMad Builder for configuration examples
+2. **Required File**
+   - Include a `module.yaml` file in the root folder (this drives questions for the final generated config.yaml at install target)
 
 3. **Folder Organization**
    Follow these conventions for optimal compatibility:
@@ -56,8 +54,10 @@ For standalone content that isn't part of a cohesive module collection, follow t
 
 1. **Module Configuration**
    - Create a folder with a `module.yaml` file (similar to custom modules)
-   - Add the property `unitary: true` to the module.yaml
-   - The `unitary: true` property indicates this is a collection of potentially unrelated items that don't depend on each other
+   - Add the property `unitary: true` in the module.yaml
+     - The `unitary: true` property indicates this is a collection of potentially unrelated items that don't depend on each other
+   - Any content you add to this folder should still be nested under workflows and agents - but the key with stand alone content is they do not rely on each other.
+     - Agents do not reference other workflows even if stored in a unitary:true module. But unitary Agents can have their own workflows in their sidecar, or reference workflows as requirements from other modules - with a process known as workflow vendoring. Keep in mind, this will require that the workflow referenced from the other module would need to be available for the end user to install, so its recommended to only vendor workflows from the core module, or official bmm modules (See [Workflow Vendoring, Customization, and Inheritance](workflow-vendoring-customization-inheritance.md)).
 
 2. **Folder Structure**
    Organize content in specific named folders:

package/docs/{custom-content.md → modules/bmb-bmad-builder/custom-content.md}

@@ -1,6 +1,6 @@
 # Custom Content
 
-BMAD supports several categories of officially supported custom content that extend the platform's capabilities. Custom content can be created manually or with the recommended assistance of the BMad Builder (BoMB) Module. The BoMB Agent provides workflows and expertise to plan and build any custom content you can imagine.
+BMAD supports several categories of officially supported custom content that extend the platform's capabilities. Custom content can be created manually or with the recommended assistance of the BMad Builder (BoMB) Module. The BoMB Agents provides workflows and expertise to plan and build any custom content you can imagine.
 
 This flexibility transforms the platform beyond its current capabilities, enabling:
 
@@ -21,7 +21,7 @@ This flexibility transforms the platform beyond its current capabilities, enabli
   - [Custom Global Modules](#custom-global-modules)
   - [Custom Agents](#custom-agents)
     - [BMad Tiny Agents](#bmad-tiny-agents)
-    - [Simple vs Expert Agents](#simple-vs-expert-agents)
+    - [Simple and Expert Agents](#simple-and-expert-agents)
   - [Custom Workflows](#custom-workflows)
 
 ## Custom Stand Alone Modules
@@ -57,7 +57,7 @@ Similar to Custom Stand Alone Modules, but designed to add functionality that ap
 
 Examples include:
 
-- The current TTS (Text-to-Speech) functionality for Claude, which will be rebuilt as a global module
+- The current TTS (Text-to-Speech) functionality for Claude, which will soon be converted to a global module
 - The core module, which is always installed and provides all agents with party mode and advanced elicitation capabilities
 - Installation and update tools that work with any BMAD method configuration
 
@@ -81,7 +81,7 @@ Personal agents designed for highly specific needs that may not be suitable for
 
 These are simple, standalone files that can be scoped to focus on specific data or paths when integrated into an information vault or repository.
 
-### Simple vs Expert Agents
+### Simple and Expert Agents
 
 The distinction between simple and expert agents lies in their structure:
 
@@ -89,7 +89,6 @@ The distinction between simple and expert agents lies in their structure:
 
 - Single file containing all prompts and configuration
 - Self-contained and straightforward
-- has metadata type: simple
 
 **Expert Agent:**
 

package/{src/modules/bmb/docs/agents → docs/modules/bmb-bmad-builder}/index.md

@@ -1,6 +1,11 @@
 # BMB Module Documentation
 
-Reference documentation for building BMAD agents and workflows.
+Create custom agents, workflows, and modules for BMAD.
+
+## Quick Start
+
+- **[Agent Creation Guide](./agent-creation-guide.md)** - Step-by-step guide to building your first agent
+- **[Understanding Agent Types](./understanding-agent-types.md)** - Learn the differences between Simple and Expert agents
 
 ## Agent Architecture
 
@@ -37,7 +42,7 @@ Production-ready examples in [bmb/reference/agents/](https://github.com/bmad-cod
 
 For installing standalone simple and expert agents, see:
 
-- [Custom Agent Installation](/docs/custom-content-installation.md)
+- [Custom Agent Installation](/docs/modules/bmb-bmad-builder/custom-content-installation.md)
 
 ## Key Concepts
 

package/docs/modules/bmb-bmad-builder/workflow-vendoring-customization-inheritance.md

@@ -0,0 +1,42 @@
+# Workflow Vendoring, Customization, and Inheritance (Official Support Consing Soon)
+
+Vendoring and Inheritance of workflows are 2 ways of sharing or reutilizing workflows - but with some key distinctions and use cases.
+
+## Workflow Vendoring
+
+Workflow Vendoring allows an agent to have access to a workflow from another module, without having to install said module. At install time, the module workflow being vendored will be cloned and installed into the module that is receiving the vendored workflow the agent needs.
+
+### How to Vendor
+
+Lets assume you are building a module, and you do not want to recreate a workflow from the BMad Method, such as workflows/4-implementation/dev-story/workflow.md. Instead of copying all the context to your module, and having to maintain it over time as updates are made, you can instead use the exec-vendor menu item in your agent.
+
+From your modules agent definition, you would implement the menu item as follows in the agent:
+
+```yaml
+    - trigger: develop-story
+      exec-vendor: "{project-root}/_bmad/<source-module>/workflows/4-production/dev-story/workflow.md"
+      exec: "{project-root}/_bmad/<my-module>/workflows/dev-story/workflow.md"
+      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
+```
+
+At install time, it will clone the workflow and all of its required assets, and the agent that gets built will have an exec to a path installed in its own module. The content gets added to the folder you specify in exec. While it does not have to exactly match the source path, you will want to ensure you are specifying the workflow.md to be in a new location (in other words in this example, dev-story would not already be the path of another custom module workflow that already exists.)
+
+## Workflow Inheritance (Official Support Coming Post Beta)
+
+Workflow Inheritance is a different concept, that allows you to modify or extend existing workflow.
+
+Party Mode from the core is an example of a workflow that is designed with inheritance in mind - customization for specific party needs. While party mode itself is generic - there might be specific agent collaborations you want to create. Without having to reinvent the whole party mode concept, or copy and paste all of its content - you could inherit from party mode to extend it to be specific.
+
+Some possible examples could be:
+
+- Retrospective
+- Sprint Planning
+- Collaborative Brainstorming Sessions
+
+## Workflow Customization (Official Support Coming Post Beta)
+
+Similar to Workflow Inheritance, Workflow Customization will soon be allowed for certain workflows that are meant to be user customized - similar in process to how agents are customized now.
+
+This will take the shape of workflows with optional hooks, configurable inputs, and the ability to replace whole at install time.
+
+For example, assume you are using the Create PRD workflow, which is comprised of 11 steps, and you want to always include specifics about your companies domain, technical landscape or something else. While project-context can be helpful with that, you can also through hooks and step overrides, have full replace steps, the key requirement being to ensure your step replace file is an exact file name match of an existing step, follows all conventions, and ends in a similar fashion to either hook back in to call the next existing step, or more custom steps that eventually hook back into the flow.

package/{src/modules/bmgd/docs → docs/modules/bmgd-bmad-game-dev}/glossary.md

@@ -291,4 +291,3 @@ Phase 4 workflows inherit from BMM base and add BMGD-specific overrides.
 
 - **[Quick Start Guide](./quick-start.md)** - Get started with BMGD
 - **[Game Types Guide](./game-types-guide.md)** - Game genre reference
-- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions

package/{src/modules/bmgd/docs → docs/modules/bmgd-bmad-game-dev}/index.md

@@ -50,7 +50,6 @@ Understanding how BMGD works:
 Essential reference materials:
 
 - **[Glossary](./glossary.md)** - Key game development terminology
-- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions
 
 ---
 
@@ -148,7 +147,6 @@ BMGD Documentation
 ├── quick-flow-guide.md     # Rapid prototyping and development
 ├── game-types-guide.md     # Game type templates
 ├── glossary.md             # Terminology
-└── troubleshooting.md      # Common issues
 ```
 
 ---
@@ -164,9 +162,6 @@ BMGD Documentation
 ### Related Documentation
 
 - **[BMM Documentation](../../bmm/docs/index.md)** - Core BMad Method documentation
-- **[IDE Guides](../../ide-info/)** - Configure your development environment
-
----
 
 ## Tips for Using This Documentation
 

package/{src/modules/bmgd/docs → docs/modules/bmgd-bmad-game-dev}/workflows-guide.md

@@ -8,7 +8,7 @@ Complete reference for all BMGD workflows organized by development phase.
 
 BMGD workflows are organized into four phases:
 
-![BMGD Workflow Overview](./workflow-overview.jpg)
+![BMGD Workflow Overview](../../../../docs/modules/bmgd-bmad-game-dev/workflow-overview.jpg)
 
 ---
 
@@ -259,7 +259,7 @@ Checks current project status across all phases. Shows completed documents, curr
 
 ## Quick-Flow Workflows
 
-Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](./quick-flow-guide.md)** for detailed usage.
+Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-flow-guide.md)** for detailed usage.
 
 ### Quick-Prototype
 
@@ -457,7 +457,7 @@ This means:
 
 ## Next Steps
 
-- **[Quick Start Guide](./quick-start.md)** - Get started with BMGD
-- **[Quick-Flow Guide](./quick-flow-guide.md)** - Rapid prototyping and development
-- **[Agents Guide](./agents-guide.md)** - Agent reference
-- **[Game Types Guide](./game-types-guide.md)** - Game type templates
+- **[Quick Start Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-start.md)** - Get started with BMGD
+- **[Quick-Flow Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-flow-guide.md)** - Rapid prototyping and development
+- **[Agents Guide](../../../../docs/modules/bmgd-bmad-game-dev/agents-guide.md)** - Agent reference
+- **[Game Types Guide](../../../../docs/modules/bmgd-bmad-game-dev/game-types-guide.md)** - Game type templates

package/{src/modules/bmm/docs → docs/modules/bmm-bmad-method}/brownfield-guide.md

@@ -725,7 +725,6 @@ flowchart TD
 - **[Quick Start Guide](./quick-start.md)** - Getting started with BMM
 - **[Glossary](./glossary.md)** - Key terminology
 - **[FAQ](./faq.md)** - Common questions
-- **[Troubleshooting](./troubleshooting.md)** - Problem resolution
 - **[Workflow Documentation](./index.md#-workflow-guides)** - Complete workflow reference
 
 ---

package/{src/modules/bmm/docs → docs/modules/bmm-bmad-method}/faq.md

@@ -354,8 +354,6 @@ Use them together for best results.
 
 **Why model quality matters:** BMM workflows require LLMs that can follow multi-step processes, maintain context across phases, and implement code that adheres to specifications. Tools with weaker models will struggle with workflow adherence and code quality.
 
-See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for configuration specifics.
-
 ### Q: Can I customize agents?
 
 **A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `_bmad/_config/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.

package/{src/modules/bmm/docs → docs/modules/bmm-bmad-method}/index.md

@@ -22,26 +22,23 @@ Complete guides for the BMad Method Module (BMM) - AI-powered agile development
 
 ## 📖 Core Concepts
 
-Understanding how BMM adapts to your needs:
+The BMad Method is meant to be adapted and customized to your specific needs. In this realm there is no one size fits all - your needs are unique, and BMad Method is meant to support this (and if it does not, can be further customized or extended with new modules).
 
-- **[Scale Adaptive System](./scale-adaptive-system.md)** - How BMM adapts to project size and complexity
-  - Three planning tracks (Quick Flow, BMad Method, Enterprise Method)
-  - Automatic track recommendation
-  - Documentation requirements per track
-  - Planning workflow routing
+First know there is the full BMad Method Process and then there is a Quick Flow for those quicker smaller efforts.
+
+- **[Full Adaptive BMad Method](#-workflow-guides)** - Full planning and scope support through extensive development and testing.
+  - Broken down into 4 phases, all of which are comprised of both required and optional phases
+    - Phases 1-3 are all about progressive idea development through planning and preparations to build your project.
+    - Phase 4 is the implementation cycle where you will Just In Time (JIT) produce the contextual stories needed for the dev agent based on the extensive planing completed
+    - All 4 phases have optional steps in them, depending on how rigorous you want to go with planning, research ideation, validation, testing and traceability.
+  - While there is a lot here, know that even this can be distilled down to a simple PRD, Epic and Story list and then jump into the dev cycle. But if that is all you want, you might be better off with the BMad Quick Flow described next
 
 - **[BMAD Quick Flow](./bmad-quick-flow.md)** - Fast-track development workflow
   - 3-step process: spec → dev → optional review
   - Perfect for bug fixes and small features
   - Rapid prototyping with production quality
-  - Hours to implementation, not days
-  - Barry (Quick Flow Solo Dev) agent owned
-
-- **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)** - Elite solo developer for rapid development
-  - Barry is an elite developer who thrives on autonomous execution
-  - Lives and breathes the BMAD Quick Flow workflow
-  - Takes projects from concept to deployment with ruthless efficiency
-  - No handoffs, no delays - just pure focused development
+  - Implementation in minutes, not days
+  - Has a specialized single agent that does all of this: **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)**
 
 ## 🤖 Agents and Collaboration
 
@@ -78,7 +75,6 @@ Essential reference materials:
 
 - **[Glossary](./glossary.md)** - Key terminology and concepts
 - **[FAQ](./faq.md)** - Frequently asked questions across all topics
-- **[Enterprise Agentic Development](./enterprise-agentic-development.md)** - Team collaboration strategies
 
 ## 🎯 Choose Your Path
 
@@ -86,19 +82,14 @@ Essential reference materials:
 
 **Build something new (greenfield)**
 → Start with [Quick Start Guide](./quick-start.md)
-→ Then review [Scale Adaptive System](./scale-adaptive-system.md) to understand tracks
 
 **Fix a bug or add small feature**
-→ Go to [BMAD Quick Flow](./bmad-quick-flow.md) for rapid development
-→ Or use [Quick Flow Solo Dev](./quick-flow-solo-dev.md) directly
+→ User the [Quick Flow Solo Dev](./quick-flow-solo-dev.md) directly with its dedicated stand alone [Quick Bmad Spec Flow](./quick-spec-flow.md) process
 
 **Work with existing codebase (brownfield)**
 → Read [Brownfield Development Guide](./brownfield-guide.md)
 → Pay special attention to documentation requirements for brownfield projects
 
-**Understand planning tracks and methodology**
-→ See [Scale Adaptive System](./scale-adaptive-system.md)
-
 ## 📋 Workflow Guides
 
 Comprehensive documentation for all BMM workflows organized by phase:
@@ -127,35 +118,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
 - **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
   - Test strategy, automation, quality gates
   - TEA agent and test healing
-  - BMad-integrated vs standalone modes
-
-**Total: 34 workflows documented across all phases**
-
-### Advanced Workflow References
-
-For detailed technical documentation on specific complex workflows:
-
-- **[Document Project Workflow Reference](./workflow-document-project-reference.md)** - Technical deep-dive (445 lines)
-  - v1.2.0 context-safe architecture
-  - Scan levels, resumability, write-as-you-go
-  - Multi-part project detection
-  - Deep-dive mode for targeted analysis
-
-- **[Architecture Workflow Reference](./workflow-architecture-reference.md)** - Decision architecture guide (320 lines)
-  - Starter template intelligence
-  - Novel pattern design
-  - Implementation patterns for agent consistency
-  - Adaptive facilitation approach
-
-## 🏗️ Module Structure
-
-Understanding BMM components:
-
-- **[BMM Module README](../README.md)** - Overview of module structure
-  - Agent roster and roles
-  - Workflow organization
-  - Teams and collaboration
-  - Best practices
 
 ## 🌐 External Resources
 

package/{src/modules/bmm/docs → docs/modules/bmm-bmad-method}/party-mode.md

@@ -2,13 +2,11 @@
 
 **Get all your AI agents in one conversation**
 
----
-
 ## What is Party Mode?
 
 Ever wanted to gather your entire AI team in one room and see what happens? That's party mode.
 
-Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and suddenly you've got **all your AI agents** in one conversation. PM, Architect, DEV, UX Designer, the CIS creative agents - everyone shows up.
+Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent or at key workflow junctions when asked), and suddenly you've got **all your AI agents** in one conversation. PM, Architect, DEV, UX Designer and more that you can choose from.
 
 **Why it's useful:**
 
@@ -19,8 +17,6 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su
 - **Sprint retrospectives** - Party mode powers the retrospective workflow
 - **Sprint planning** - Multi-agent collaboration for planning sessions
 
-**Future use:** Advanced elicitation workflows will leverage party mode for sophisticated requirement gathering.
-
 ---
 
 ## How It Works
@@ -46,6 +42,10 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su
 # OR from any agent context
 *party-mode
 
+# Super Hack
+
+/bmad:core:workflows:party-mode and include also in the party Santa Clause and Einstein 
+
 # During party
 Ask questions, respond to agents, direct the conversation
 
@@ -103,116 +103,6 @@ _(Ideas cross-pollinate and evolve)_
 
 _(Multiple perspectives reveal the right answer)_
 
----
-
-## When NOT to Use Party Mode
-
-**Skip party mode for:**
-
-- Simple implementation questions → Use DEV agent
-- Document review → Use Technical Writer
-- Workflow status checks → Use any agent + `*workflow-status`
-- Single-domain questions → Use specialist agent
-
-**Use party mode for:**
-
-- Multi-perspective decisions
-- Creative collaboration
-- Post-mortems and retrospectives
-- Sprint planning sessions
-- Complex problem-solving
-
----
-
-## Agent Customization
-
-Party mode uses agents from `_bmad/[module]/agents/*.md` - these already include any customizations you applied during install.
-
-**To customize agents for party mode:**
-
-1. Create customization file: `_bmad/_config/agents/bmm-pm.customize.yaml`
-2. Run `npx bmad-method install` to rebuild agents
-3. Customizations now active in party mode
-
-Example customization:
-
-```yaml
-agent:
-  persona:
-    principles:
-      - 'HIPAA compliance is non-negotiable'
-      - 'Patient safety over feature velocity'
-```
-
-See [Agents Guide](./agents-guide.md#agent-customization) for details.
-
----
-
-## BMM Workflows That Use Party Mode
-
-**Current:**
-
-- `epic-retrospective` - Post-epic team retrospective powered by party mode
-- Sprint planning discussions (informal party mode usage)
-
-**Future:**
-
-- Advanced elicitation workflows will officially integrate party mode
-- Multi-agent requirement validation
-- Collaborative technical reviews
-
----
-
-## Available Agents
-
-Party mode can include **19+ agents** from all installed modules:
-
-**BMM (12 agents):** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer, Game Designer, Game Developer, Game Architect
-
-**CIS (5 agents):** Brainstorming Coach, Creative Problem Solver, Design Thinking Coach, Innovation Strategist, Storyteller
-
-**BMB (1 agent):** BMad Builder
-
-**Core (1 agent):** BMad Master (orchestrator)
-
-**Custom:** Any agents you've created
-
----
-
-## Tips
-
-**Get better results:**
-
-- Be specific with your topic/question
-- Provide context (project type, constraints, goals)
-- Direct specific agents when you want their expertise
-- Make decisions - party mode informs, you decide
-- Time box discussions (15-30 minutes is usually plenty)
-
-**Examples of good opening questions:**
-
-- "We need to decide between REST and GraphQL for our mobile API. Project is a B2B SaaS with 50 enterprise clients."
-- "Our last sprint failed spectacularly. Let's discuss what went wrong with authentication implementation."
-- "Brainstorm: how can we make our game's tutorial feel rewarding instead of tedious?"
-
----
-
-## Troubleshooting
-
-**Same agents responding every time?**
-Vary your questions or explicitly request other perspectives: "Game Designer, your thoughts?"
-
-**Discussion going in circles?**
-BMad Master will summarize and redirect, or you can make a decision and move on.
-
-**Too many agents talking?**
-Make your topic more specific - BMad Master picks 2-3 agents based on relevance.
-
-**Agents not using customizations?**
-Make sure you ran `npx bmad-method install` after creating customization files.
-
----
-
 ## Related Documentation
 
 - [Agents Guide](./agents-guide.md) - Complete agent reference