diff --git a/docs/modules/bmm-bmad-method/index.md b/docs/modules/bmm-bmad-method/index.md index 6541317d..c01f8978 100644 --- a/docs/modules/bmm-bmad-method/index.md +++ b/docs/modules/bmm-bmad-method/index.md @@ -40,6 +40,8 @@ First know there is the full BMad Method Process and then there is a Quick Flow - 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)** +- **TEA engagement (optional)** - Choose TEA engagement: none, TEA-only (standalone), or integrated by track. See **[Test Architect Guide](./test-architecture.md)**. + ## 🤖 Agents and Collaboration Complete guide to BMM's AI agent team: diff --git a/docs/modules/bmm-bmad-method/quick-start.md b/docs/modules/bmm-bmad-method/quick-start.md index f5f73785..9358ba15 100644 --- a/docs/modules/bmm-bmad-method/quick-start.md +++ b/docs/modules/bmm-bmad-method/quick-start.md @@ -179,6 +179,16 @@ Once epics and stories are created: **Why run this?** It ensures all your planning assets align properly before you start building. +#### Optional: TEA Engagement + +Testing is not mandated by BMad. Decide how you want to engage TEA: + +- **No TEA** - Use your existing team testing approach +- **TEA-only (Standalone)** - Use TEA workflows with your own requirements and environment +- **TEA-integrated** - Use TEA as part of the BMad Method or Enterprise flow + +See the [Test Architect Guide](./test-architecture.md) for the five TEA engagement models and recommended sequences. + #### Context Management Tips - **Use 200k+ context models** for best results (Claude Sonnet 4.5, GPT-4, etc.) @@ -211,7 +221,14 @@ Once planning and architecture are complete, you'll move to Phase 4. **Important 3. Tell the agent: "Run dev-story" 4. The DEV agent will implement the story and update the sprint status -#### 3.4 Review the Code (Optional but Recommended) +#### 3.4 Generate Guardrail Tests (Optional) + +1. **Start a new chat** with the **TEA agent** +2. Wait for the menu +3. Tell the agent: "Run automate" +4. The TEA agent generates or expands tests to act as guardrails + +#### 3.5 Review the Code (Optional but Recommended) 1. **Start a new chat** with the **DEV agent** 2. Wait for the menu @@ -224,7 +241,8 @@ For each subsequent story, repeat the cycle using **fresh chats** for each workf 1. **New chat** → SM agent → "Run create-story" 2. **New chat** → DEV agent → "Run dev-story" -3. **New chat** → DEV agent → "Run code-review" (optional but recommended) +3. **New chat** → TEA agent → "Run automate" (optional) +4. **New chat** → DEV agent → "Run code-review" (optional but recommended) After completing all stories in an epic: diff --git a/docs/modules/bmm-bmad-method/test-architecture.md b/docs/modules/bmm-bmad-method/test-architecture.md index e64282d3..9d417a7a 100644 --- a/docs/modules/bmm-bmad-method/test-architecture.md +++ b/docs/modules/bmm-bmad-method/test-architecture.md @@ -6,6 +6,38 @@ - **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project complexity and compliance demands. - **Use When:** BMad Method or Enterprise track projects, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required. (Quick Flow projects typically don't require TEA) +## Choose Your TEA Engagement Model + +BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pick one intentionally. + +1. **No TEA** + - Skip all TEA workflows. Use your existing team testing approach. + +2. **TEA-only (Standalone)** + - Use TEA on a non-BMad project. Bring your own requirements, acceptance criteria, and environments. + - Typical sequence: `*test-design` (system or epic) -> `*atdd` and/or `*automate` -> optional `*test-review` -> `*trace` for coverage and gate decisions. + - Run `*framework` or `*ci` only if you want TEA to scaffold the harness or pipeline. + +3. **Integrated: Greenfield - BMad Method (Simple/Standard Work)** + - Phase 3: system-level `*test-design`, then `*framework` and `*ci`. + - Phase 4: per-epic `*test-design`, optional `*atdd`, then `*automate` and optional `*test-review`. + - Gate (Phase 2): `*trace`. + +4. **Integrated: Brownfield - BMad Method or Enterprise (Simple or Complex)** + - Phase 2: baseline `*trace`. + - Phase 3: system-level `*test-design`, then `*framework` and `*ci`. + - Phase 4: per-epic `*test-design` focused on regression and integration risks. + - Gate (Phase 2): `*trace`; `*nfr-assess` (if not done earlier). + - For brownfield BMad Method, follow the same flow with `*nfr-assess` optional. + +5. **Integrated: Greenfield - Enterprise Method (Enterprise/Compliance Work)** + - Phase 2: `*nfr-assess`. + - Phase 3: system-level `*test-design`, then `*framework` and `*ci`. + - Phase 4: per-epic `*test-design`, plus `*atdd`/`*automate`/`*test-review`. + - Gate (Phase 2): `*trace`; archive artifacts as needed. + +If you are unsure, default to the integrated path for your track and adjust later. + ## TEA Workflow Lifecycle TEA integrates into the BMad development lifecycle during Solutioning (Phase 3) and Implementation (Phase 4): @@ -16,6 +48,9 @@ graph TB subgraph Phase2["Phase 2: PLANNING"] PM["PM: *prd (creates PRD with FRs/NFRs)"] PlanNote["Business requirements phase"] + NFR2["TEA: *nfr-assess (optional, enterprise)"] + PM -.-> NFR2 + NFR2 -.-> PlanNote PM -.-> PlanNote end @@ -23,8 +58,8 @@ graph TB Architecture["Architect: *architecture"] EpicsStories["PM/Architect: *create-epics-and-stories"] TestDesignSys["TEA: *test-design (system-level)"] - Framework["TEA: *framework"] - CI["TEA: *ci"] + Framework["TEA: *framework (optional if needed)"] + CI["TEA: *ci (optional if needed)"] GateCheck["Architect: *implementation-readiness"] Architecture --> EpicsStories Architecture --> TestDesignSys @@ -174,7 +209,7 @@ npm install -D @seontechnologies/playwright-utils **Enable during BMAD installation** by answering "Yes" when prompted. -**Supported utilities (11 total):** +**Supported utilities (10 total):** - api-request, network-recorder, auth-session, intercept-network-call, recurse - log, file-utils, burn-in, network-error-monitor @@ -429,7 +464,7 @@ Provides fixture-based utilities that integrate into TEA's test generation and r Benefit: Faster CI feedback, HTTP error detection -**Utilities available** (11 total): api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor, fixtures-composition +**Utilities available** (10 total): api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor, fixtures-composition **Enable during BMAD installation** by answering "Yes" when prompted, or manually set `tea_use_playwright_utils: true` in `_bmad/bmm/config.yaml`. diff --git a/docs/modules/bmm-bmad-method/workflows-implementation.md b/docs/modules/bmm-bmad-method/workflows-implementation.md index 73dfa432..02d9c471 100644 --- a/docs/modules/bmm-bmad-method/workflows-implementation.md +++ b/docs/modules/bmm-bmad-method/workflows-implementation.md @@ -98,8 +98,9 @@ Stories move through these states in the sprint status file: 1. SM runs `create-story` 2. DEV runs `dev-story` -3. DEV runs `code-review` -4. If code review fails: DEV fixes issues in `dev-story`, then re-runs `code-review` +3. (Optional) TEA runs `*automate` to generate or expand guardrail tests +4. DEV runs `code-review` +5. If code review fails: DEV fixes issues in `dev-story`, then re-runs `code-review` **After Epic Complete:** diff --git a/docs/modules/bmm-bmad-method/workflows-solutioning.md b/docs/modules/bmm-bmad-method/workflows-solutioning.md index 3b6590e2..8cd61852 100644 --- a/docs/modules/bmm-bmad-method/workflows-solutioning.md +++ b/docs/modules/bmm-bmad-method/workflows-solutioning.md @@ -434,7 +434,7 @@ Architecture documents are living. Update them as you learn during implementatio **Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE create-epics-and-stories. Everything else is identical to BMad Method. -**Note:** TEA (Test Architect) operates across all phases and validates architecture testability but is not a Phase 3-specific workflow. See [Test Architecture Guide](../../../../docs/modules/bmm-bmad-method/test-architecture.md) for TEA's full lifecycle integration. +**Note:** TEA (Test Architect) operates across all phases and validates architecture testability but is not a Phase 3-specific workflow. See [Test Architecture Guide](./test-architecture.md) for TEA's full lifecycle integration. --- diff --git a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml index 52405e71..701b438e 100644 --- a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml +++ b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml @@ -336,9 +336,10 @@ 1. Review the comprehensive story in {{story_file}} 2. Run dev agents `dev-story` for optimized implementation 3. Run `code-review` when complete (auto-marks done) + 4. Optional: Run TEA `*automate` after `dev-story` to generate guardrail tests **The developer now has everything needed for flawless implementation!** - \ No newline at end of file + diff --git a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml index 40c56244..4fb70efe 100644 --- a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml +++ b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml @@ -397,6 +397,7 @@ - Verify all acceptance criteria are met - Ensure deployment readiness if applicable - Run `code-review` workflow for peer review + - Optional: Run TEA `*automate` to expand guardrail tests 💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story. @@ -406,4 +407,4 @@ Remain flexible - allow user to choose their own path or ask for other assistance - \ No newline at end of file +