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

package/docs/explanation/faq/tools-faq.md

@@ -0,0 +1,253 @@
+---
+title: "Tools and Advanced FAQ"
+description: Common questions about tools, IDEs, and advanced topics in the BMad Method
+---
+
+Quick answers to common questions about tools, IDEs, and advanced topics in the BMad Method.
+
+## Questions
+
+**Tools and Technical**
+
+- [Why are my Mermaid diagrams not rendering?](#why-are-my-mermaid-diagrams-not-rendering)
+- [Can I use BMM with GitHub Copilot / Cursor / other AI tools?](#can-i-use-bmm-with-github-copilot--cursor--other-ai-tools)
+- [What IDEs/tools support BMM?](#what-idestools-support-bmm)
+- [Can I customize agents?](#can-i-customize-agents)
+- [What happens to my planning docs after implementation?](#what-happens-to-my-planning-docs-after-implementation)
+- [Can I use BMM for non-software projects?](#can-i-use-bmm-for-non-software-projects)
+
+**Advanced**
+
+- [What if my project grows from Level 1 to Level 3?](#what-if-my-project-grows-from-level-1-to-level-3)
+- [Can I mix greenfield and brownfield approaches?](#can-i-mix-greenfield-and-brownfield-approaches)
+- [How do I handle urgent hotfixes during a sprint?](#how-do-i-handle-urgent-hotfixes-during-a-sprint)
+- [What if I disagree with the workflow's recommendations?](#what-if-i-disagree-with-the-workflows-recommendations)
+- [Can multiple developers work on the same BMM project?](#can-multiple-developers-work-on-the-same-bmm-project)
+- [What is party mode and when should I use it?](#what-is-party-mode-and-when-should-i-use-it)
+
+**Getting Help**
+
+- [Where do I get help if my question isn't answered here?](#where-do-i-get-help-if-my-question-isnt-answered-here)
+- [How do I report a bug or request a feature?](#how-do-i-report-a-bug-or-request-a-feature)
+
+## Tools and Technical
+
+### Why are my Mermaid diagrams not rendering?
+
+Common issues:
+
+1. Missing language tag: Use ` ```mermaid` not just ` ``` `
+2. Syntax errors in diagram (validate at mermaid.live)
+3. Tool doesn't support Mermaid (check your Markdown renderer)
+
+All BMM docs use valid Mermaid syntax that should render in GitHub, VS Code, and most IDEs.
+
+### Can I use BMM with GitHub Copilot / Cursor / other AI tools?
+
+Yes! BMM is complementary. BMM handles:
+
+- Project planning and structure
+- Workflow orchestration
+- Agent Personas and expertise
+- Documentation generation
+- Quality gates
+
+Your AI coding assistant handles:
+
+- Line-by-line code completion
+- Quick refactoring
+- Test generation
+
+Use them together for best results.
+
+### What IDEs/tools support BMM?
+
+BMM requires tools with **agent mode** and access to **high-quality LLM models** that can load and follow complex workflows, then properly implement code changes.
+
+**Recommended Tools:**
+
+- **Claude Code** — Best choice
+  - Sonnet 4.5 (excellent workflow following, coding, reasoning)
+  - Opus (maximum context, complex planning)
+  - Native agent mode designed for BMM workflows
+
+- **Cursor**
+  - Supports Anthropic (Claude) and OpenAI models
+  - Agent mode with composer
+  - Good for developers who prefer Cursor's UX
+
+- **Windsurf**
+  - Multi-model support
+  - Agent capabilities
+  - Suitable for BMM workflows
+
+**What Matters:**
+
+1. **Agent mode** — Can load long workflow instructions and maintain context
+2. **High-quality LLM** — Models ranked high on SWE-bench (coding benchmarks)
+3. **Model selection** — Access to Claude Sonnet 4.5, Opus, or GPT-4o class models
+4. **Context capacity** — Can handle large planning documents and codebases
+
+**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.
+
+### Can I customize agents?
+
+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.
+
+**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags — a format any LLM can read and follow.
+
+### What happens to my planning docs after implementation?
+
+Keep them! They serve as:
+
+- Historical record of decisions
+- Onboarding material for new team members
+- Reference for future enhancements
+- Audit trail for compliance
+
+For enterprise projects (Level 4), consider archiving completed planning artifacts to keep workspace clean.
+
+### Can I use BMM for non-software projects?
+
+BMM is optimized for software development, but the methodology principles (scale-adaptive planning, just-in-time design, context injection) can apply to other complex project types. You'd need to adapt workflows and agents for your domain.
+
+## Advanced
+
+### What if my project grows from Level 1 to Level 3?
+
+Totally fine! When you realize scope has grown:
+
+1. Run create-prd to add product-level planning
+2. Run create-architecture for system design
+3. Use existing tech-spec as input for PRD
+4. Continue with updated level
+
+The system is flexible — growth is expected.
+
+### Can I mix greenfield and brownfield approaches?
+
+Yes! Common scenario: adding new greenfield feature to brownfield codebase. Approach:
+
+1. Run document-project for brownfield context
+2. Use greenfield workflows for new feature planning
+3. Explicitly document integration points between new and existing
+4. Test integration thoroughly
+
+### How do I handle urgent hotfixes during a sprint?
+
+Use correct-course workflow or just:
+
+1. Save your current work state
+2. Load PM agent → quick tech-spec for hotfix
+3. Implement hotfix (Level 0 flow)
+4. Deploy hotfix
+5. Return to original sprint work
+
+Level 0 Quick Spec Flow is perfect for urgent fixes.
+
+### What if I disagree with the workflow's recommendations?
+
+Workflows are guidance, not enforcement. If a workflow recommends something that doesn't make sense for your context:
+
+- Explain your reasoning to the agent
+- Ask for alternative approaches
+- Skip the recommendation if you're confident
+- Document why you deviated (for future reference)
+
+Trust your expertise — BMM supports your decisions.
+
+### Can multiple developers work on the same BMM project?
+
+Yes! But the paradigm is fundamentally different from traditional agile teams.
+
+**Key Difference:**
+
+- **Traditional** — Multiple devs work on stories within one epic (months)
+- **Agentic** — Each dev owns complete epics (days)
+
+**In traditional agile:** A team of 5 devs might spend 2-3 months on a single epic, with each dev owning different stories.
+
+**With BMM + AI agents:** A single dev can complete an entire epic in 1-3 days. What used to take months now takes days.
+
+**Team Work Distribution:**
+
+- **Recommended:** Split work by **epic** (not story)
+- Each developer owns complete epics end-to-end
+- Parallel work happens at epic level
+- Minimal coordination needed
+
+**For full-stack apps:**
+
+- Frontend and backend can be separate epics (unusual in traditional agile)
+- Frontend dev owns all frontend epics
+- Backend dev owns all backend epics
+- Works because delivery is so fast
+
+**Enterprise Considerations:**
+
+- Use **git submodules** for BMM installation (not .gitignore)
+- Allows personal configurations without polluting main repo
+- Teams may use different AI tools (Claude Code, Cursor, etc.)
+- Developers may follow different methods or create custom agents/workflows
+
+**Quick Tips:**
+
+- Share `sprint-status.yaml` (single source of truth)
+- Assign entire epics to developers (not individual stories)
+- Coordinate at epic boundaries, not story level
+- Use git submodules for BMM in enterprise settings
+
+### What is party mode and when should I use it?
+
+Party mode is a unique multi-agent collaboration feature where ALL your installed agents (19+ from BMM, CIS, BMB, custom modules) discuss your challenges together in real-time.
+
+**How it works:**
+
+1. Run `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent)
+2. Introduce your topic
+3. BMad Master selects 2-3 most relevant agents per message
+4. Agents cross-talk, debate, and build on each other's ideas
+
+**Best for:**
+
+- Strategic decisions with trade-offs (architecture choices, tech stack, scope)
+- Creative brainstorming (game design, product innovation, UX ideation)
+- Cross-functional alignment (epic kickoffs, retrospectives, phase transitions)
+- Complex problem-solving (multi-faceted challenges, risk assessment)
+
+**Example parties:**
+
+- **Product Strategy** — PM + Innovation Strategist (CIS) + Analyst
+- **Technical Design** — Architect + Creative Problem Solver (CIS) + Game Architect
+- **User Experience** — UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
+
+**Why it's powerful:**
+
+- Diverse perspectives (technical, creative, strategic)
+- Healthy debate reveals blind spots
+- Emergent insights from agent interaction
+- Natural collaboration across modules
+
+**For complete documentation:** See the [Party Mode Guide](/docs/explanation/features/party-mode.md)
+
+## Getting Help
+
+### Where do I get help if my question isn't answered here?
+
+1. Search [Complete Documentation](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) for related topics
+2. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#bmad-method-help)
+3. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+4. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
+
+### How do I report a bug or request a feature?
+
+Open a GitHub issue at: <https://github.com/bmad-code-org/BMAD-METHOD/issues>
+
+Please include:
+
+- BMM version (check your installed version)
+- Steps to reproduce (for bugs)
+- Expected vs actual behavior
+- Relevant workflow or agent involved
+
+**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

package/docs/explanation/faq/workflows-faq.md

@@ -0,0 +1,61 @@
+---
+title: "Workflows FAQ"
+description: Common questions about BMad Method workflows and phases
+---
+
+Quick answers to common questions about BMad Method workflows and phases.
+
+## Questions
+
+- [What's the difference between workflow-status and workflow-init?](#whats-the-difference-between-workflow-status-and-workflow-init)
+- [Can I skip Phase 1 (Analysis)?](#can-i-skip-phase-1-analysis)
+- [When is Phase 3 (Architecture) required?](#when-is-phase-3-architecture-required)
+- [What happens if I skip a recommended workflow?](#what-happens-if-i-skip-a-recommended-workflow)
+- [How do I know when Phase 3 is complete?](#how-do-i-know-when-phase-3-is-complete)
+- [Can I run workflows in parallel?](#can-i-run-workflows-in-parallel)
+
+### What's the difference between workflow-status and workflow-init?
+
+- **workflow-status** — Checks existing status and tells you what's next (use when continuing work)
+- **workflow-init** — Creates new status file and sets up project (use when starting new project)
+
+If status file exists, use workflow-status. If not, use workflow-init.
+
+### Can I skip Phase 1 (Analysis)?
+
+Yes! Phase 1 is optional for all levels, though recommended for complex projects. Skip if:
+
+- Requirements are clear
+- No research needed
+- Time-sensitive work
+- Small changes (Level 0-1)
+
+### When is Phase 3 (Architecture) required?
+
+- **Level 0-1** — Never (skip entirely)
+- **Level 2** — Optional (only if system design needed)
+- **Level 3-4** — Required (comprehensive architecture mandatory)
+
+### What happens if I skip a recommended workflow?
+
+Nothing breaks! Workflows are guidance, not enforcement. However, skipping recommended workflows (like architecture for Level 3) may cause:
+
+- Integration issues during implementation
+- Rework due to poor planning
+- Conflicting design decisions
+- Longer development time overall
+
+### How do I know when Phase 3 is complete?
+
+For Level 3-4, run the implementation-readiness workflow. It validates PRD + Architecture + Epics + UX (optional) are aligned before implementation. Pass the gate check = ready for Phase 4.
+
+### Can I run workflows in parallel?
+
+Most workflows must be sequential within a phase:
+
+- **Phase 1** — brainstorm → research → product-brief (optional order)
+- **Phase 2** — PRD must complete before moving forward
+- **Phase 3** — architecture → epics+stories → implementation-readiness (sequential)
+- **Phase 4** — Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
+
+**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

package/docs/explanation/features/advanced-elicitation.md

@@ -0,0 +1,108 @@
+---
+title: "Advanced Elicitation"
+---
+
+
+**Push the LLM to rethink its work through 50+ reasoning methods—essentially, LLM brainstorming.**
+
+Advanced Elicitation is the inverse of Brainstorming. Instead of pulling ideas out of you, the LLM applies sophisticated reasoning techniques to re-examine and enhance content it has just generated. It's the LLM brainstorming with itself to find better approaches, uncover hidden issues, and discover improvements it missed on the first pass.
+
+---
+
+## When to Use It
+
+- After a workflow generates a section of content and you want to explore alternatives
+- When the LLM's initial output seems adequate but you suspect there's more depth available
+- For high-stakes content where multiple perspectives would strengthen the result
+- To stress-test assumptions, explore edge cases, or find weaknesses in generated plans
+- When you want the LLM to "think again" but with structured reasoning methods
+
+---
+
+## How It Works
+
+### 1. Context Analysis
+The LLM analyzes the current content, understanding its type, complexity, stakeholder needs, risk level, and creative potential.
+
+### 2. Smart Method Selection
+Based on context, 5 methods are intelligently selected from a library of 50+ techniques and presented to you:
+
+| Option            | Description                              |
+| ----------------- | ---------------------------------------- |
+| **1-5**           | Apply the selected method to the content |
+| **[r] Reshuffle** | Get 5 new methods selected randomly      |
+| **[a] List All**  | Browse the complete method library       |
+| **[x] Proceed**   | Continue with enhanced content           |
+
+### 3. Method Execution & Iteration
+- The selected method is applied to the current content
+- Improvements are shown for your review
+- You choose whether to apply changes or discard them
+- The menu re-appears for additional elicitations
+- Each method builds on previous enhancements
+
+### 4. Party Mode Integration (Optional)
+If Party Mode is active, BMad agents participate randomly in the elicitation process, adding their unique perspectives to the methods.
+
+---
+
+## Method Categories
+
+| Category          | Focus                               | Example Methods                                                |
+| ----------------- | ----------------------------------- | -------------------------------------------------------------- |
+| **Core**          | Foundational reasoning techniques   | First Principles Analysis, 5 Whys, Socratic Questioning        |
+| **Collaboration** | Multiple perspectives and synthesis | Stakeholder Round Table, Expert Panel Review, Debate Club      |
+| **Advanced**      | Complex reasoning frameworks        | Tree of Thoughts, Graph of Thoughts, Self-Consistency          |
+| **Competitive**   | Adversarial stress-testing          | Red Team vs Blue Team, Shark Tank Pitch, Code Review Gauntlet  |
+| **Technical**     | Architecture and code quality       | Decision Records, Rubber Duck Debugging, Algorithm Olympics    |
+| **Creative**      | Innovation and lateral thinking     | SCAMPER, Reverse Engineering, Random Input Stimulus            |
+| **Research**      | Evidence-based analysis             | Literature Review Personas, Thesis Defense, Comparative Matrix |
+| **Risk**          | Risk identification and mitigation  | Pre-mortem Analysis, Failure Mode Analysis, Chaos Monkey       |
+| **Learning**      | Understanding verification          | Feynman Technique, Active Recall Testing                       |
+| **Philosophical** | Conceptual clarity                  | Occam's Razor, Ethical Dilemmas                                |
+| **Retrospective** | Reflection and lessons              | Hindsight Reflection, Lessons Learned Extraction               |
+
+---
+
+## Key Features
+
+- **50+ reasoning methods** — Spanning core logic to advanced multi-step reasoning frameworks
+- **Smart context selection** — Methods chosen based on content type, complexity, and stakeholder needs
+- **Iterative enhancement** — Each method builds on previous improvements
+- **User control** — Accept or discard each enhancement before proceeding
+- **Party Mode integration** — Agents can participate when Party Mode is active
+
+---
+
+## Workflow Integration
+
+Advanced Elicitation is a core workflow designed to be invoked by other workflows during content generation:
+
+| Parameter              | Description                                               |
+| ---------------------- | --------------------------------------------------------- |
+| **Content to enhance** | The current section content that was just generated       |
+| **Context type**       | The kind of content being created (spec, code, doc, etc.) |
+| **Enhancement goals**  | What the calling workflow wants to improve                |
+
+### Integration Flow
+
+When called from a workflow:
+1. Receives the current section content that was just generated
+2. Applies elicitation methods iteratively to enhance that content
+3. Returns the enhanced version when user selects 'x' to proceed
+4. The enhanced content replaces the original section in the output document
+
+### Example
+
+A specification generation workflow could invoke Advanced Elicitation after producing each major section (requirements, architecture, implementation plan). The workflow would pass the generated section, and Advanced Elicitation would offer methods like "Stakeholder Round Table" to gather diverse perspectives on requirements, or "Red Team vs Blue Team" to stress-test the architecture for vulnerabilities.
+
+---
+
+## Advanced Elicitation vs. Brainstorming
+
+|              | **Advanced Elicitation**                          | **Brainstorming**                             |
+| ------------ | ------------------------------------------------- | --------------------------------------------- |
+| **Source**   | LLM generates ideas through structured reasoning  | User provides ideas, AI coaches them out      |
+| **Purpose**  | Rethink and improve LLM's own output              | Unlock user's creativity                      |
+| **Methods**  | 50+ reasoning and analysis techniques             | 60+ ideation and creativity techniques        |
+| **Best for** | Enhancing generated content, finding alternatives | Breaking through blocks, generating new ideas |

package/docs/explanation/features/brainstorming-techniques.md

@@ -0,0 +1,103 @@
+---
+title: "Brainstorming"
+---
+
+
+**Facilitate structured creative sessions using 60+ proven ideation techniques.**
+
+The Brainstorming workflow is an interactive facilitation system that helps you unlock your own creativity. The AI acts as coach, guide, and creative partner—using proven techniques to draw out ideas and insights that are already within you.
+
+**Important:** Every idea comes from you. The workflow creates the conditions for your best thinking to emerge through guided exploration, but you are the source.
+
+---
+
+## When to Use It
+
+- Breaking through creative blocks on a specific challenge
+- Generating innovative ideas for products, features, or solutions
+- Exploring a problem from completely new angles
+- Systematically developing ideas from raw concepts to actionable plans
+- Team ideation (with collaborative techniques) or personal creative exploration
+
+---
+
+## How It Works
+
+### 1. Session Setup
+Define your topic, goals, and any constraints.
+
+### 2. Choose Your Approach
+
+| Approach | Description |
+|----------|-------------|
+| **User-Selected** | Browse the full technique library and pick what appeals to you |
+| **AI-Recommended** | Get customized technique suggestions based on your goals |
+| **Random Selection** | Discover unexpected methods through serendipitous technique combinations |
+| **Progressive Flow** | Journey systematically from expansive exploration to focused action planning |
+
+### 3. Interactive Facilitation
+Work through techniques with true collaborative coaching. The AI asks probing questions, builds on your ideas, and helps you think deeper—but your ideas are the source.
+
+### 4. Idea Organization
+All your generated ideas are organized into themes and prioritized.
+
+### 5. Action Planning
+Top ideas get concrete next steps, resource requirements, and success metrics.
+
+---
+
+## What You Get
+
+A comprehensive session document that captures the entire journey:
+
+- Topic, goals, and session parameters
+- Each technique used and how it was applied
+- Your contributions and the ideas you generated
+- Thematic organization connecting related insights
+- Prioritized ideas with action plans
+- Session highlights and key breakthroughs
+
+This document becomes a permanent record of your creative process—valuable for future reference, sharing with stakeholders, or continuing the session later.
+
+---
+
+## Technique Categories
+
+| Category | Focus |
+|----------|-------|
+| **Collaborative** | Team dynamics and inclusive participation |
+| **Creative** | Breakthrough thinking and paradigm shifts |
+| **Deep** | Root cause analysis and strategic insight |
+| **Structured** | Organized frameworks and systematic exploration |
+| **Theatrical** | Playful, radical perspectives |
+| **Wild** | Boundary-pushing, extreme thinking |
+| **Biomimetic** | Nature-inspired solutions |
+| **Quantum** | Quantum principles for innovation |
+| **Cultural** | Traditional knowledge and cross-cultural approaches |
+| **Introspective Delight** | Inner wisdom and authentic exploration |
+
+---
+
+## Key Features
+
+- **Interactive coaching** — Pulls ideas *out* of you, doesn't generate them for you
+- **On-demand loading** — Techniques loaded from a comprehensive library as needed
+- **Session preservation** — Every step, insight, and action plan is documented
+- **Continuation support** — Pause sessions and return later, or extend with additional techniques
+
+---
+
+## Workflow Integration
+
+Brainstorming is a core workflow designed to be invoked and configured by other modules. When called from another workflow, it accepts contextual parameters:
+
+| Parameter | Description |
+|-----------|-------------|
+| **Topic focus** | What the brainstorming should help discover or solve |
+| **Guardrails** | Constraints, boundaries, or must-avoid areas |
+| **Output goals** | What the final output needs to accomplish for the calling workflow |
+| **Context files** | Project-specific guidance to inform technique selection |
+
+### Example
+
+When creating a new module in the BMad Builder workflow, Brainstorming can be invoked with guardrails around the module's purpose and a goal to discover key features, user needs, or architectural considerations. The session becomes focused on producing exactly what the module creation workflow needs.