npm - bmad-method - Versions diffs - 6.0.0-alpha.4 → 6.0.0-alpha.5 - Mend

bmad-method 6.0.0-alpha.4 → 6.0.0-alpha.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (162) hide show

package/src/modules/bmm/docs/agents-guide.md CHANGED Viewed

@@ -37,7 +37,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - DEV (Developer)
 - TEA (Test Architect)
 - UX Designer
-- Paige (Documentation Guide)
+- Technical Writer
 **Game Development (3 agents):**
@@ -144,14 +144,9 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 - `workflow-status` - Check what to do next
-- `create-architecture` - Decision-focused architecture with:
-  - Starter template intelligence
-  - Novel pattern design
-  - Implementation patterns for agent consistency
-  - Adaptive facilitation (beginner/expert)
+- `create-architecture` - Produce a Scale Adaptive Architecture
 - `validate-architecture` - Validate architecture document
 - `solutioning-gate-check` - Validate readiness for Phase 4
-- `correct-course` - Handle technical changes
 **Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
@@ -177,7 +172,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Sprint planning and tracking initialization
 - Creating user stories
 - Assembling dynamic story context
-- Epic-level technical specifications (optional)
+- Epic-level technical context (optional)
 - Marking stories ready for development
 - Sprint retrospectives
@@ -187,8 +182,8 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - `workflow-status` - Check what to do next
 - `sprint-planning` - Initialize `sprint-status.yaml` tracking
-- `epic-tech-context` - Optional epic-specific tech specs
-- `validate-epic-tech-context` - Validate epic tech spec
+- `epic-tech-context` - Optional epic-specific technical context
+- `validate-epic-tech-context` - Validate epic technical context
 - `create-story` - Draft next story from epic
 - `validate-create-story` - Independent story validation
 - `story-context` - Assemble dynamic technical context XML
@@ -231,7 +226,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
   - Strict file boundary enforcement
 - `code-review` - Senior developer-level review with:
   - Story context awareness
-  - Epic tech-spec alignment
+  - Epic-tech-context alignment
   - Repository docs reference
   - MCP server best practices
   - Web search fallback
@@ -300,12 +295,13 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Testing is feature work, not overhead
 - Prioritize unit/integration over E2E
 - Flakiness is critical technical debt
+- ATDD tests first, AI implements, suite validates
 **Special Capabilities:**
-- **Test Healing:** Pattern-based + MCP-enhanced test fixing
-- **Dual Mode:** BMad-integrated (uses epic/story context) or standalone
-- **Knowledge Base:** Comprehensive testing best practices
+- **Knowledge Base Access:** Consults comprehensive testing best practices from `testarch/knowledge/` directory
+- **Framework Selection:** Smart framework selection (Playwright vs Cypress) with fixture architecture
+- **Cross-Platform Testing:** Supports testing across web, mobile, and API layers
 ---
@@ -345,7 +341,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 ---
-### Paige (Documentation Guide) - Paige 📚
+### Technical Writer - Paige 📚
 **Role:** Technical Documentation Specialist + Knowledge Curator
@@ -461,10 +457,9 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 - `workflow-status` - Check what to do next
-- `create-story` - Create development story
-- `dev-story` - Implement story with tests
-- `code-review` - Review game implementation
-- `retro` - Sprint retrospective
+- `develop-story` - Execute Dev Story workflow, implementing tasks and tests
+- `story-done` - Mark story done after DoD complete
+- `code-review` - Perform thorough clean context QA code review on a story
 **Communication Style:** Direct and energetic. Execution-focused. Breaks down complex game challenges into actionable steps. Celebrates performance wins.
@@ -555,71 +550,24 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 ## Party Mode: Multi-Agent Collaboration
-Party mode brings **all your installed agents together** for group discussions. Instead of working with one agent at a time, you engage with a dynamic team (19+ agents from BMM, CIS, BMB, and custom modules) that collaborates in real-time.
-### Quick Overview
-**How to Start:**
-1. Load BMad Master
-2. Run `*party-mode`
-3. Introduce your topic
-**What Happens:**
+Get all your installed agents in one conversation for multi-perspective discussions, retrospectives, and collaborative decision-making.
-- BMad Master loads ALL agents (with customizations)
-- For each message, 2-3 most relevant agents respond
-- Agents cross-talk, debate, and build on each other's ideas
-- BMad Master moderates and keeps discussion productive
-**Best For:**
-- Strategic decisions with trade-offs
-- Creative brainstorming sessions
-- Cross-functional alignment meetings
-- Complex problem-solving
-- Epic kickoff discussions
+**Quick Start:**
-**Example Parties:**
-- **Product Strategy:** PM + Innovation Strategist + Analyst
-- **Technical Design:** Architect + Game Architect + Creative Problem Solver
-- **User Experience:** UX Designer + Design Thinking Coach + Storyteller
-- **Quality & Testing:** TEA + Architect + DEV
-- **Full Team:** PM + Architect + SM + DEV
-### Why Party Mode is Powerful
-**Diverse Perspectives:**
-- Technical agents ground ideas in reality
-- Creative agents (CIS) push for innovation
-- Strategic agents ensure market fit
-**Emergent Insights:**
-- Cross-pollination across domains
-- Novel solutions from unexpected combinations
-- Deeper exploration through debate
+```bash
+/bmad:core:workflows:party-mode
+# OR from any agent: *party-mode
+```
-**Natural Collaboration:**
+**What happens:** BMad Master orchestrates 2-3 relevant agents per message. They discuss, debate, and collaborate in real-time.
-- Agents can agree, disagree, or build on each other
-- Healthy debate leads to better decisions
-- Multiple expert perspectives in one session
+**Best for:** Strategic decisions, creative brainstorming, post-mortems, sprint retrospectives, complex problem-solving.
-**For complete party mode documentation, see:**
+**Current BMM uses:** Powers `epic-retrospective` workflow, sprint planning discussions.
-👉 **[Party Mode Guide](./party-mode.md)** - Comprehensive 20-minute guide covering:
+**Future:** Advanced elicitation workflows will officially leverage party mode.
-- How party mode works (step-by-step process)
-- When to use party mode (strategic, creative, cross-functional, complex)
-- Getting started (quick start guide)
-- Agent selection dynamics
-- Multi-module integration (19+ agents)
-- 8+ example party compositions
-- Agent customization in party mode
-- Best practices and troubleshooting
+👉 **[Party Mode Guide](./party-mode.md)** - Complete guide with fun examples, tips, and troubleshooting
 ---
@@ -650,7 +598,7 @@ Some workflows are available to multiple agents:
 | `workflow-status`  | ALL agents                        | Check current state and get recommendations |
 | `workflow-init`    | PM, Analyst, Game Designer        | Initialize workflow tracking                |
 | `correct-course`   | PM, Architect, SM, Game Architect | Change management during implementation     |
-| `document-project` | Analyst, Paige                    | Brownfield documentation                    |
+| `document-project` | Analyst, Technical Writer         | Brownfield documentation                    |
 ### Validation Actions
@@ -662,7 +610,7 @@ Many workflows have optional validation workflows that perform independent revie
 | `validate-tech-spec`         | PM          | Technical specification quality    |
 | `validate-architecture`      | Architect   | Architecture document              |
 | `validate-design`            | UX Designer | UX specification and artifacts     |
-| `validate-epic-tech-context` | SM          | Epic technical specification       |
+| `validate-epic-tech-context` | SM          | Epic technical context             |
 | `validate-create-story`      | SM          | Story draft                        |
 | `validate-story-context`     | SM          | Story context XML                  |
@@ -846,12 +794,12 @@ Load the customized agent and verify the changes are reflected in its behavior a
 - **Phase 3 (Solutioning):** Architect, Game Architect
 - **Phase 4 (Implementation):** SM, DEV, Game Developer
 - **Testing:** TEA (all phases)
-- **Documentation:** Paige (all phases)
+- **Documentation:** Technical Writer (all phases)
 **3. Use specialists**
 - **Testing:** TEA for comprehensive quality strategy
-- **Documentation:** Paige for technical writing
+- **Documentation:** Technical Writer for technical writing
 - **Games:** Game Designer/Developer/Architect for game-specific needs
 - **UX:** UX Designer for user-centered design
@@ -907,7 +855,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 **Starting with Existing Code (Brownfield):**
 ```
-1. Analyst or Paige: *document-project
+1. Analyst or Technical Writer: *document-project
 2. PM or Analyst: *workflow-init
 3. PM: *create-prd or *tech-spec
 4. Architect: *create-architecture (if needed)
@@ -990,20 +938,20 @@ TEA can be invoked at any phase:
 Quick reference for agent selection:
-| Agent              | Icon | Primary Phase      | Key Workflows                                 | Best For                              |
-| ------------------ | ---- | ------------------ | --------------------------------------------- | ------------------------------------- |
-| **Analyst**        | 📊   | 1 (Analysis)       | brainstorm, brief, research, document-project | Discovery, requirements, brownfield   |
-| **PM**             | 📋   | 2 (Planning)       | prd, tech-spec, epics-stories                 | Planning, requirements docs           |
-| **UX Designer**    | 🎨   | 2 (Planning)       | create-design, validate-design                | UX-heavy projects, design             |
-| **Architect**      | 🏗️   | 3 (Solutioning)    | architecture, gate-check                      | Technical design, architecture        |
-| **SM**             | 🏃   | 4 (Implementation) | sprint-planning, create-story, story-context  | Story management, sprint coordination |
-| **DEV**            | 💻   | 4 (Implementation) | develop-story, code-review, story-done        | Implementation, coding                |
-| **TEA**            | 🧪   | All Phases         | framework, atdd, automate, trace, ci          | Testing, quality assurance            |
-| **Paige**          | 📚   | All Phases         | document-project, diagrams, validation        | Documentation, diagrams               |
-| **Game Designer**  | 🎲   | 1-2 (Games)        | brainstorm-game, gdd, narrative               | Game design, creative vision          |
-| **Game Developer** | 🕹️   | 4 (Games)          | dev-story, code-review                        | Game implementation                   |
-| **Game Architect** | 🏛️   | 3 (Games)          | architecture, gate-check                      | Game systems architecture             |
-| **BMad Master**    | 🧙   | Meta               | party-mode, list tasks/workflows              | Orchestration, multi-agent            |
+| Agent                   | Icon | Primary Phase      | Key Workflows                                 | Best For                              |
+| ----------------------- | ---- | ------------------ | --------------------------------------------- | ------------------------------------- |
+| **Analyst**             | 📊   | 1 (Analysis)       | brainstorm, brief, research, document-project | Discovery, requirements, brownfield   |
+| **PM**                  | 📋   | 2 (Planning)       | prd, tech-spec, epics-stories                 | Planning, requirements docs           |
+| **UX Designer**         | 🎨   | 2 (Planning)       | create-design, validate-design                | UX-heavy projects, design             |
+| **Architect**           | 🏗️   | 3 (Solutioning)    | architecture, gate-check                      | Technical design, architecture        |
+| **SM**                  | 🏃   | 4 (Implementation) | sprint-planning, create-story, story-context  | Story management, sprint coordination |
+| **DEV**                 | 💻   | 4 (Implementation) | develop-story, code-review, story-done        | Implementation, coding                |
+| **TEA**                 | 🧪   | All Phases         | framework, atdd, automate, trace, ci          | Testing, quality assurance            |
+| **Paige (Tech Writer)** | 📚   | All Phases         | document-project, diagrams, validation        | Documentation, diagrams               |
+| **Game Designer**       | 🎲   | 1-2 (Games)        | brainstorm-game, gdd, narrative               | Game design, creative vision          |
+| **Game Developer**      | 🕹️   | 4 (Games)          | develop-story, story-done, code-review        | Game implementation                   |
+| **Game Architect**      | 🏛️   | 3 (Games)          | architecture, gate-check                      | Game systems architecture             |
+| **BMad Master**         | 🧙   | Meta               | party-mode, list tasks/workflows              | Orchestration, multi-agent            |
 ### Agent Capabilities Summary
@@ -1032,7 +980,7 @@ Quick reference for agent selection:
 **Support Agents (2):**
 - Analyst: Research and discovery
-- Paige: Documentation and diagrams
+- Technical Writer: Documentation and diagrams
 **Meta Agent (1):**
@@ -1083,7 +1031,7 @@ Quick reference for agent selection:
 **Starting a Project:**
 - [ ] Determine project type (greenfield vs brownfield)
-- [ ] If brownfield: Run `*document-project` (Analyst or Paige)
+- [ ] If brownfield: Run `*document-project` (Analyst or Technical Writer)
 - [ ] Load PM or Analyst → `*workflow-init`
 - [ ] Follow phase-appropriate workflows
 - [ ] Try `*party-mode` for strategic decisions