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

package/docs/how-to/workflows/run-implementation-readiness.md

@@ -0,0 +1,162 @@
+---
+title: "How to Run Implementation Readiness"
+description: How to validate planning and solutioning before implementation
+---
+
+
+Use the `implementation-readiness` workflow to validate that planning and solutioning are complete and aligned before Phase 4 implementation.
+
+---
+
+## When to Use This
+
+- **Always** before Phase 4 for BMad Method and Enterprise projects
+- After create-epics-and-stories workflow completes
+- Before sprint-planning workflow
+- When stakeholders request readiness check
+
+---
+
+## When to Skip This
+
+- Quick Flow (no solutioning phase)
+- BMad Method Simple (no gate check required)
+
+---
+
+## Prerequisites
+
+- BMad Method installed
+- Architect agent available
+- PRD, Architecture, and Epics completed
+
+---
+
+## Steps
+
+### 1. Load the Architect Agent
+
+Start a fresh chat and load the Architect agent.
+
+### 2. Run the Workflow
+
+```
+*implementation-readiness
+```
+
+### 3. Let the Agent Validate
+
+The workflow systematically checks:
+- PRD completeness
+- Architecture completeness
+- Epic/Story completeness
+- Alignment between all documents
+
+### 4. Review the Gate Decision
+
+The agent produces a gate decision with rationale.
+
+---
+
+## Gate Decision Outcomes
+
+### ✅ PASS
+
+- All critical criteria met
+- Minor gaps acceptable with documented plan
+- **Action:** Proceed to Phase 4
+
+### ⚠️ CONCERNS
+
+- Some criteria not met but not blockers
+- Gaps identified with clear resolution path
+- **Action:** Proceed with caution, address gaps in parallel
+
+### ❌ FAIL
+
+- Critical gaps or contradictions
+- Architecture missing key decisions
+- Epics conflict with PRD/architecture
+- **Action:** BLOCK Phase 4, resolve issues first
+
+---
+
+## What Gets Checked
+
+### PRD/GDD Completeness
+- Problem statement clear and evidence-based
+- Success metrics defined
+- User personas identified
+- Functional requirements (FRs) complete
+- Non-functional requirements (NFRs) specified
+- Risks and assumptions documented
+
+### Architecture Completeness
+- System architecture defined
+- Data architecture specified
+- API architecture decided
+- Key ADRs documented
+- Security architecture addressed
+- FR/NFR-specific guidance provided
+- Standards and conventions defined
+
+### Epic/Story Completeness
+- All PRD features mapped to stories
+- Stories have acceptance criteria
+- Stories prioritized (P0/P1/P2/P3)
+- Dependencies identified
+- Story sequencing logical
+
+### Alignment Checks
+- Architecture addresses all PRD FRs/NFRs
+- Epics align with architecture decisions
+- No contradictions between epics
+- NFRs have technical approach
+- Integration points clear
+
+---
+
+## What You Get
+
+An `implementation-readiness.md` document containing:
+
+1. **Executive Summary** (PASS/CONCERNS/FAIL)
+2. **Completeness Assessment** (scores for PRD, Architecture, Epics)
+3. **Alignment Assessment** (PRD↔Architecture, Architecture↔Epics)
+4. **Quality Assessment** (story quality, dependencies, risks)
+5. **Gaps and Recommendations** (critical/minor gaps, remediation)
+6. **Gate Decision** with rationale
+7. **Next Steps**
+
+---
+
+## Example
+
+E-commerce platform → CONCERNS ⚠️
+
+**Gaps identified:**
+- Missing security architecture section
+- Undefined payment gateway
+
+**Recommendation:**
+- Complete security section
+- Add payment gateway ADR
+
+**Action:** Proceed with caution, address before payment epic.
+
+---
+
+## Tips
+
+- Run this before every Phase 4 start
+- Take FAIL decisions seriously - fix issues first
+- Use CONCERNS as a checklist for parallel work
+- Document why you proceed despite concerns
+
+---
+
+## Related
+
+- [Create Architecture](/docs/how-to/workflows/create-architecture.md) - Architecture workflow
+- [Create Epics and Stories](/docs/how-to/workflows/create-epics-and-stories.md) - Work breakdown
+- [Run Sprint Planning](/docs/how-to/workflows/run-sprint-planning.md) - Start implementation

package/docs/how-to/workflows/run-sprint-planning.md

@@ -0,0 +1,111 @@
+---
+title: "How to Run Sprint Planning"
+description: How to initialize sprint tracking for implementation
+---
+
+
+Use the `sprint-planning` workflow to initialize the sprint tracking file and organize work for implementation.
+
+---
+
+## When to Use This
+
+- Once at the start of Phase 4 (Implementation)
+- After implementation-readiness gate passes
+- When starting a new sprint cycle
+
+---
+
+## Prerequisites
+
+- BMad Method installed
+- SM (Scrum Master) agent available
+- Epic files created from `create-epics-and-stories`
+- Implementation-readiness passed (for BMad Method/Enterprise)
+
+---
+
+## Steps
+
+### 1. Load the SM Agent
+
+Start a fresh chat and load the SM (Scrum Master) agent.
+
+### 2. Run the Workflow
+
+```
+*sprint-planning
+```
+
+### 3. Provide Context
+
+Point the agent to your epic files created during Phase 3.
+
+### 4. Review Sprint Organization
+
+The agent organizes stories into the sprint tracking file.
+
+---
+
+## What You Get
+
+A `sprint-status.yaml` file containing:
+
+- All epics with their stories
+- Story status tracking (TODO, IN PROGRESS, READY FOR REVIEW, DONE)
+- Dependencies between stories
+- Priority ordering
+
+---
+
+## Story Lifecycle States
+
+Stories move through these states in the sprint status file:
+
+| State | Description |
+|-------|-------------|
+| **TODO** | Story identified but not started |
+| **IN PROGRESS** | Story being implemented |
+| **READY FOR REVIEW** | Implementation complete, awaiting code review |
+| **DONE** | Accepted and complete |
+
+---
+
+## Typical Sprint Flow
+
+### Sprint 0 (Planning Phase)
+- Complete Phases 1-3
+- PRD/GDD + Architecture complete
+- Epics+Stories created via create-epics-and-stories
+
+### Sprint 1+ (Implementation Phase)
+
+**Start of Phase 4:**
+1. SM runs `sprint-planning` (once)
+
+**Per Story (repeat until epic complete):**
+1. SM runs `create-story`
+2. DEV runs `dev-story`
+3. DEV runs `code-review`
+4. Update sprint-status.yaml
+
+**After Epic Complete:**
+- SM runs `retrospective`
+- Move to next epic
+
+---
+
+## Tips
+
+- Run sprint-planning only once at Phase 4 start
+- Use `sprint-status` during Phase 4 to check current state
+- Keep the sprint-status.yaml file as single source of truth
+- Update story status after each stage
+
+---
+
+## Related
+
+- [Create Story](/docs/how-to/workflows/create-story.md) - Prepare stories for implementation
+- [Implement Story](/docs/how-to/workflows/implement-story.md) - Dev workflow
+- [Run Code Review](/docs/how-to/workflows/run-code-review.md) - Quality assurance

package/docs/how-to/workflows/run-test-design.md

@@ -0,0 +1,128 @@
+---
+title: "How to Run Test Design"
+description: How to create comprehensive test plans using TEA's test-design workflow
+---
+
+
+Use TEA's `*test-design` workflow to create comprehensive test plans with risk assessment and coverage strategies.
+
+---
+
+## When to Use This
+
+**System-level (Phase 3):**
+- After architecture is complete
+- Before implementation-readiness gate
+- To validate architecture testability
+
+**Epic-level (Phase 4):**
+- At the start of each epic
+- Before implementing stories in the epic
+- To identify epic-specific testing needs
+
+---
+
+## Prerequisites
+
+- BMad Method installed
+- TEA agent available
+- For system-level: Architecture document complete
+- For epic-level: Epic defined with stories
+
+---
+
+## Steps
+
+### 1. Load the TEA Agent
+
+Start a fresh chat and load the TEA (Test Architect) agent.
+
+### 2. Run the Test Design Workflow
+
+```
+*test-design
+```
+
+### 3. Specify the Mode
+
+TEA will ask if you want:
+
+- **System-level** - For architecture testability review (Phase 3)
+- **Epic-level** - For epic-specific test planning (Phase 4)
+
+### 4. Provide Context
+
+For system-level:
+- Point to your architecture document
+- Reference any ADRs (Architecture Decision Records)
+
+For epic-level:
+- Specify which epic you're planning
+- Reference the epic file with stories
+
+### 5. Review the Output
+
+TEA generates a comprehensive test design document.
+
+---
+
+## What You Get
+
+### System-Level Output (`test-design-system.md`)
+
+- Testability review of architecture
+- ADR → test mapping
+- Architecturally Significant Requirements (ASRs)
+- Environment needs
+- Test infrastructure recommendations
+
+### Epic-Level Output (`test-design-epic-N.md`)
+
+- Risk assessment for the epic
+- Test priorities
+- Coverage plan
+- Regression hotspots (for brownfield)
+- Integration risks
+- Mitigation strategies
+
+---
+
+## Test Design for Different Tracks
+
+### Greenfield - BMad Method
+
+| Stage | Test Design Focus |
+|-------|-------------------|
+| Phase 3 | System-level testability review |
+| Phase 4 | Per-epic risk assessment and test plan |
+
+### Brownfield - BMad Method/Enterprise
+
+| Stage | Test Design Focus |
+|-------|-------------------|
+| Phase 3 | System-level + existing test baseline |
+| Phase 4 | Regression hotspots, integration risks |
+
+### Enterprise
+
+| Stage | Test Design Focus |
+|-------|-------------------|
+| Phase 3 | Compliance-aware testability |
+| Phase 4 | Security/performance/compliance focus |
+
+---
+
+## Tips
+
+- Run system-level test-design right after architecture
+- Run epic-level test-design at the start of each epic
+- Update test design if ADRs change
+- Use the output to guide `*atdd` and `*automate` workflows
+
+---
+
+## Related
+
+- [TEA Overview](/docs/explanation/features/tea-overview.md) - Understanding the Test Architect
+- [Setup Test Framework](/docs/how-to/workflows/setup-test-framework.md) - Setting up testing infrastructure
+- [Create Architecture](/docs/how-to/workflows/create-architecture.md) - Architecture workflow

package/docs/how-to/workflows/setup-party-mode.md

@@ -0,0 +1,117 @@
+---
+title: "How to Set Up Party Mode"
+description: How to set up and use Party Mode for multi-agent collaboration
+---
+
+
+Use Party Mode to orchestrate dynamic multi-agent conversations with your entire BMad team.
+
+---
+
+## When to Use This
+
+- Exploring complex topics that benefit from diverse expert perspectives
+- Brainstorming with agents who can build on each other's ideas
+- Getting comprehensive views across multiple domains
+- Strategic decisions with trade-offs
+
+---
+
+## Prerequisites
+
+- BMad Method installed with multiple agents
+- Any agent loaded that supports party mode
+
+---
+
+## Steps
+
+### 1. Load Any Agent
+
+Start with any agent that supports party mode (most do).
+
+### 2. Start Party Mode
+
+```
+*party-mode
+```
+
+Or use the full path:
+```
+/bmad:core:workflows:party-mode
+```
+
+### 3. Introduce Your Topic
+
+Present a topic or question for the group to discuss:
+
+```
+I'm trying to decide between a monolithic architecture
+and microservices for our new platform.
+```
+
+### 4. Engage with the Discussion
+
+The facilitator will:
+- Select 2-3 most relevant agents based on expertise
+- Let agents respond in character
+- Enable natural cross-talk and debate
+- Continue until you choose to exit
+
+### 5. Exit When Ready
+
+Type "exit" or "done" to conclude the session. Participating agents will say personalized farewells.
+
+---
+
+## What Happens
+
+1. **Agent Roster** - Party Mode loads your complete agent roster
+2. **Introduction** - Available team members are introduced
+3. **Topic Analysis** - The facilitator analyzes your topic
+4. **Agent Selection** - 2-3 most relevant agents are selected
+5. **Discussion** - Agents respond, reference each other, engage in cross-talk
+6. **Exit** - Session concludes with farewells
+
+---
+
+## Example Party Compositions
+
+### 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)
+
+### Quality Assessment
+- TEA + DEV + Architect
+
+---
+
+## Key Features
+
+- **Intelligent agent selection** - Selects based on expertise needed
+- **Authentic personalities** - Each agent maintains their unique voice
+- **Natural cross-talk** - Agents reference and build on each other
+- **Optional TTS** - Voice configurations for each agent
+- **Graceful exit** - Personalized farewells
+
+---
+
+## Tips
+
+- Be specific about your topic for better agent selection
+- Let the conversation flow naturally
+- Ask follow-up questions to go deeper
+- Take notes on key insights
+- Use for strategic decisions, not routine tasks
+
+---
+
+## Related
+
+- [Party Mode](/docs/explanation/features/party-mode.md) - Understanding Party Mode
+- [Agent Roles](/docs/explanation/core-concepts/agent-roles.md) - Available agents

package/docs/how-to/workflows/setup-test-framework.md

@@ -0,0 +1,113 @@
+---
+title: "How to Set Up a Test Framework"
+description: How to set up a production-ready test framework using TEA
+---
+
+
+Use TEA's `*framework` workflow to scaffold a production-ready test framework for your project.
+
+---
+
+## When to Use This
+
+- No existing test framework in your project
+- Current test setup isn't production-ready
+- Starting a new project that needs testing infrastructure
+- Phase 3 (Solutioning) after architecture is complete
+
+---
+
+## Prerequisites
+
+- BMad Method installed
+- Architecture completed (or at least tech stack decided)
+- TEA agent available
+
+---
+
+## Steps
+
+### 1. Load the TEA Agent
+
+Start a fresh chat and load the TEA (Test Architect) agent.
+
+### 2. Run the Framework Workflow
+
+```
+*framework
+```
+
+### 3. Answer TEA's Questions
+
+TEA will ask about:
+
+- Your tech stack (React, Node, etc.)
+- Preferred test framework (Playwright, Cypress, Jest)
+- Testing scope (E2E, integration, unit)
+- CI/CD platform (GitHub Actions, etc.)
+
+### 4. Review Generated Output
+
+TEA generates:
+
+- **Test scaffold** - Directory structure and config files
+- **Sample specs** - Example tests following best practices
+- **`.env.example`** - Environment variable template
+- **`.nvmrc`** - Node version specification
+- **README updates** - Testing documentation
+
+---
+
+## What You Get
+
+```
+tests/
+├── e2e/
+│   ├── example.spec.ts
+│   └── fixtures/
+├── integration/
+├── unit/
+├── playwright.config.ts  # or cypress.config.ts
+└── README.md
+```
+
+---
+
+## Optional: Playwright Utils Integration
+
+TEA can integrate with `@seontechnologies/playwright-utils` for advanced fixtures:
+
+```bash
+npm install -D @seontechnologies/playwright-utils
+```
+
+Enable during BMad installation or set `tea_use_playwright_utils: true` in config.
+
+**Utilities available:** api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor
+
+---
+
+## Optional: MCP Enhancements
+
+TEA can use Playwright MCP servers for enhanced capabilities:
+
+- `playwright` - Browser automation
+- `playwright-test` - Test runner with failure analysis
+
+Configure in your IDE's MCP settings.
+
+---
+
+## Tips
+
+- Run `*framework` only once per repository
+- Run after architecture is complete so framework aligns with tech stack
+- Follow up with `*ci` to set up CI/CD pipeline
+
+---
+
+## Related
+
+- [TEA Overview](/docs/explanation/features/tea-overview.md) - Understanding the Test Architect
+- [Run Test Design](/docs/how-to/workflows/run-test-design.md) - Creating test plans
+- [Create Architecture](/docs/how-to/workflows/create-architecture.md) - Architecture workflow