ma-agents 3.12.2 → 3.13.0

package/lib/bmad-cache/tea/docs/how-to/workflows/run-test-design.md

@@ -3,7 +3,7 @@ title: 'How to Run Test Design with TEA'
 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.
+Use TEA's `test-design` workflow to create comprehensive test plans with risk assessment, NFR planning, and coverage strategies.
 
 ## When to Use This
 
@@ -12,12 +12,14 @@ Use TEA's `test-design` workflow to create comprehensive test plans with risk as
 - After architecture is complete
 - Before implementation-readiness gate
 - To validate architecture testability
+- To define NFR thresholds, unknowns, and planned evidence before implementation
 
 **Epic-level (Phase 4):**
 
 - At the start of each epic
 - Before implementing stories in the epic
 - To identify epic-specific testing needs
+- To refine NFR validation when the epic has security, performance, reliability, scalability, compliance, or maintainability requirements
 
 :::note[Prerequisites]
 
@@ -43,8 +45,8 @@ test-design
 
 TEA will ask if you want:
 
-- **System-level** — For architecture testability review (Phase 3)
-- **Epic-level** — For epic-specific test planning (Phase 4)
+- **System-level** — For architecture testability review and NFR planning (Phase 3)
+- **Epic-level** — For epic-specific test and NFR planning (Phase 4)
 
 ### 4. Provide Context
 
@@ -52,11 +54,13 @@ For system-level:
 
 - Point to your architecture document
 - Reference any ADRs (Architecture Decision Records)
+- Include PRD NFRs, SLO/SLA targets, compliance requirements, and known monitoring needs
 
 For epic-level:
 
 - Specify which epic you're planning
 - Reference the epic file with stories
+- Mention any NFR-heavy scenarios or inherited system-level NFR plans
 
 ### 5. Review the Output
 
@@ -72,20 +76,18 @@ TEA produces two focused documents for system-level mode:
    - Purpose: Architectural concerns, testability gaps, NFR requirements
    - Quick Guide with 🚨 BLOCKERS / ⚠️ HIGH PRIORITY / 📋 INFO ONLY
    - Risk assessment (high/medium/low-priority with scoring)
+   - NFR testability requirements: thresholds, unknowns, architecture gaps, planned evidence
    - Testability concerns and architectural gaps
    - Risk mitigation plans for high-priority risks (≥6)
    - Assumptions and dependencies
 
 2. **`test-design-qa.md`** (for QA team)
    - Purpose: Test execution recipe, coverage plan, Sprint 0 setup
-   - Quick Reference for QA (Before You Start, Execution Order, Need Help)
-   - System architecture summary
-   - Test environment requirements (moved up - early in doc)
-   - Testability assessment (prerequisites checklist)
-   - Test levels strategy (unit/integration/E2E split)
    - Test coverage plan (P0/P1/P2/P3 with detailed scenarios + checkboxes)
+   - NFR test coverage plan with planned validation tools and evidence artifacts
    - Sprint 0 setup requirements (blockers, infrastructure, environments)
-   - NFR readiness summary
+
+`test-design` does **not** make final NFR PASS/CONCERNS/FAIL decisions. It defines the thresholds and evidence that `nfr-assess` audits later.
 
 **Why Two Documents?**
 
@@ -101,17 +103,18 @@ TEA produces two focused documents for system-level mode:
 - Risk assessment for the epic
 - Test priorities (P0-P3)
 - Coverage plan
+- NFR planning when NFRs are in scope
 - Regression hotspots (for brownfield)
 - Integration risks
 - Mitigation strategies
 
 ## Test Design for Different Tracks
 
-| Track          | Phase 3 Focus                         | Phase 4 Focus                          |
-| -------------- | ------------------------------------- | -------------------------------------- |
-| **Greenfield** | System-level testability review       | Per-epic risk assessment and test plan |
-| **Brownfield** | System-level + existing test baseline | Regression hotspots, integration risks |
-| **Enterprise** | Compliance-aware testability          | Security/performance/compliance focus  |
+| Track          | Phase 3 Focus                                    | Phase 4 Focus                              |
+| -------------- | ------------------------------------------------ | ------------------------------------------ |
+| **Greenfield** | System-level testability + NFR planning          | Per-epic risk assessment and test plan     |
+| **Brownfield** | System-level + existing test baseline            | Regression hotspots, integration/NFR risks |
+| **Enterprise** | Compliance-aware testability + NFR evidence plan | Security/performance/compliance focus      |
 
 ## Examples
 
@@ -129,9 +132,11 @@ TEA produces two focused documents for system-level mode:
 ## Tips
 
 - **Run system-level right after architecture** — Early testability review
+- **Shift NFRs left** — Define thresholds and planned evidence before implementation
 - **Run epic-level at the start of each epic** — Targeted test planning
 - **Update if ADRs change** — Keep test design aligned
 - **Use output to guide other workflows** — Feeds into `atdd` and `automate`
+- **Use `nfr-assess` later** — Audit evidence after tests, scans, metrics, or logs exist
 - **Architecture teams review Architecture doc** — Focus on blockers and mitigation plans
 - **QA teams use QA doc as implementation guide** — Follow test scenarios and Sprint 0 checklist
 
@@ -142,3 +147,4 @@ After test design:
 1. **Setup Test Framework** — If not already configured
 2. **Implementation Readiness** — System-level feeds into gate check
 3. **Story Implementation** — Epic-level guides testing during dev
+4. **NFR Evidence Audit** — Run `nfr-assess` after implementation evidence exists

package/lib/bmad-cache/tea/docs/how-to/workflows/run-trace.md

@@ -444,7 +444,7 @@ test-review.md (from test-review)
 
 ```
 
-**NFR Assessment (Optional):**
+**NFR Evidence Audit (Optional):**
 ```
 
 nfr-assessment.md (from nfr-assess)
@@ -476,7 +476,7 @@ TEA makes evidence-based gate decision and writes to separate file.
 - P1 coverage: 100% (6/6 requirements)
 - P2 coverage: 33% (1/3 requirements) - acceptable
 - Test quality score: 84/100
-- NFR assessment: PASS
+- NFR evidence audit: PASS
 
 ## Coverage Analysis
 
@@ -949,7 +949,7 @@ Result: PARTIAL coverage (3/4 criteria)
 
 - [How to Run Test Design](/docs/how-to/workflows/run-test-design.md) - Provides requirements for traceability
 - [How to Run Test Review](/docs/how-to/workflows/run-test-review.md) - Quality scores feed gate
-- [How to Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md) - NFR status feeds gate
+- [How to Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md) - NFR status feeds gate
 
 ## Understanding the Concepts
 

package/lib/bmad-cache/tea/docs/index.md

@@ -40,17 +40,19 @@ Pick a path:
 
 ## Core Workflows
 
-| Workflow                                                  | Trigger | Purpose                                |
-| --------------------------------------------------------- | ------- | -------------------------------------- |
-| [Teach Me Testing](/how-to/workflows/teach-me-testing)    | TMT     | Learn testing (7 sessions, 1-2 weeks)  |
-| [Framework Setup](/how-to/workflows/setup-test-framework) | TF      | Scaffold test framework                |
-| [CI/CD Integration](/how-to/workflows/setup-ci)           | CI      | Set up quality pipeline                |
-| [Test Design](/how-to/workflows/run-test-design)          | TD      | Risk-based test planning               |
-| [ATDD](/how-to/workflows/run-atdd)                        | AT      | Failing acceptance tests (TDD)         |
-| [Test Automation](/how-to/workflows/run-automate)         | TA      | Expand automation coverage             |
-| [Test Review](/how-to/workflows/run-test-review)          | RV      | Quality audit with scoring             |
-| [Requirements Tracing](/how-to/workflows/run-trace)       | TR      | Coverage mapping + gate decision       |
-| [NFR Assessment](/how-to/workflows/run-nfr-assess)        | NR      | Non-functional requirements evaluation |
+| Workflow                                                  | Trigger | Purpose                               |
+| --------------------------------------------------------- | ------- | ------------------------------------- |
+| [Teach Me Testing](/how-to/workflows/teach-me-testing)    | TMT     | Learn testing (7 sessions, 1-2 weeks) |
+| [Test Design](/how-to/workflows/run-test-design)          | TD      | Risk-based planning + NFR planning    |
+| [Framework Setup](/how-to/workflows/setup-test-framework) | TF      | Scaffold test framework               |
+| [CI/CD Integration](/how-to/workflows/setup-ci)           | CI      | Set up quality pipeline               |
+| [ATDD](/how-to/workflows/run-atdd)                        | AT      | Failing acceptance tests (TDD)        |
+| [Test Automation](/how-to/workflows/run-automate)         | TA      | Expand automation coverage            |
+| [Test Review](/how-to/workflows/run-test-review)          | RV      | Quality audit with scoring            |
+| [NFR Evidence Audit](/how-to/workflows/run-nfr-assess)    | NR      | Non-functional evidence evaluation    |
+| [Requirements Tracing](/how-to/workflows/run-trace)       | TR      | Coverage mapping + gate decision      |
+
+> **Agent menu shortcut:** The TEA agent menu also provides a `GATE` intent (trigger: `GATE` in chat after loading `bmad-tea`). It is a routing helper — not a standalone workflow — that guides you through the release gate sequence: optional test-review → optional nfr-assess → trace Phase 2 gate decision. It produces no artifact of its own.
 
 ## Documentation Structure
 

package/lib/bmad-cache/tea/docs/reference/commands.md

@@ -18,14 +18,15 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 ## Quick Index
 
 - [`teach-me-testing`](#teach-me-testing) - Learn testing (TEA Academy)
+- [`test-design`](#test-design) - Risk-based test planning
 - [`framework`](#framework) - Scaffold test framework
 - [`ci`](#ci) - Setup CI/CD pipeline
-- [`test-design`](#test-design) - Risk-based test planning
 - [`atdd`](#atdd) - Acceptance TDD
 - [`automate`](#automate) - Test automation
 - [`test-review`](#test-review) - Quality audit
-- [`nfr-assess`](#nfr-assess) - NFR assessment
+- [`nfr-assess`](#nfr-assess) - NFR Evidence Audit
 - [`trace`](#trace) - Coverage traceability
+- [`GATE`](#gate-agent-menu-shortcut) - Release gate routing helper (agent menu only)
 
 ---
 
@@ -123,7 +124,7 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 
 ## test-design
 
-**Purpose:** Risk-based test planning with coverage strategy
+**Purpose:** Risk-based test planning with coverage strategy and NFR planning
 
 **Phase:** Phase 3 (system-level), Phase 4 (epic-level)
 
@@ -131,8 +132,8 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 
 **Modes:**
 
-- **System-level:** Architecture testability review (TWO documents)
-- **Epic-level:** Per-epic risk assessment (ONE document)
+- **System-level:** Architecture testability review and NFR planning (TWO documents)
+- **Epic-level:** Per-epic risk and NFR planning (ONE document)
 
 **Key Inputs:**
 
@@ -147,12 +148,13 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
   - Quick Guide (🚨 BLOCKERS / ⚠️ HIGH PRIORITY / 📋 INFO ONLY)
   - Risk assessment with scoring
   - Testability concerns and gaps
+  - NFR thresholds, unknowns, and planned evidence
   - Mitigation plans
 - `test-design-qa.md` - For QA team
   - Test execution recipe
   - Coverage plan (P0/P1/P2/P3 with checkboxes)
   - Sprint 0 setup requirements
-  - NFR readiness summary
+  - NFR test coverage and evidence plan
 
 **Epic-Level (ONE Document):**
 
@@ -160,6 +162,7 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
   - Risk assessment (probability × impact scores)
   - Test priorities (P0-P3)
   - Coverage strategy
+  - NFR planning when NFRs are in scope
   - Mitigation plans
 
 **Why Two Documents for System-Level?**
@@ -256,16 +259,17 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 
 ## nfr-assess
 
-**Purpose:** Validate non-functional requirements with evidence
+**Purpose:** Audit implemented NFR evidence against defined thresholds
 
-**Phase:** Phase 2 (enterprise), Release Gate
+**Phase:** Release Gate; optional earlier evidence audit when implementation evidence exists
 
 **Frequency:** Per release (enterprise projects)
 
 **Key Inputs:**
 
 - NFR categories (Security, Performance, Reliability, Maintainability)
-- Thresholds, evidence location
+- Thresholds from PRD, architecture, or `test-design`
+- Evidence locations (test reports, scans, metrics, logs, monitoring, CI results)
 
 **Key Outputs:**
 
@@ -274,7 +278,9 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 - Mitigation plans
 - Gate decision inputs
 
-**How-To Guide:** [Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md)
+**Boundary:** Use `test-design` to plan NFR thresholds and evidence before implementation. Use `nfr-assess` after evidence exists to audit the evidence.
+
+**How-To Guide:** [Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md)
 
 ---
 
@@ -311,18 +317,36 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 
 ---
 
+## GATE (Agent Menu Shortcut)
+
+**Purpose:** Release gate routing helper — not a standalone workflow; produces no artifact of its own.
+
+**Trigger:** Type `GATE` in chat after loading the TEA agent (`bmad-tea`).
+
+**What it does:** Determines which release gate evidence exists and guides you through the correct sequence:
+
+1. (Optional) `test-review` — final test quality audit
+2. (Optional) `nfr-assess` — NFR Evidence Audit
+3. `trace` Phase 2 — PASS/CONCERNS/FAIL/WAIVED gate decision
+
+The agent asks which evidence is available and routes to the right workflow. It does not merge these workflows; each workflow is invoked separately in sequence.
+
+**When to use:** When you are approaching a release and want a single starting point that covers all release gate checks without needing to know which workflow to invoke first.
+
+---
+
 ## Summary Table
 
 | Command            | Phase      | Frequency                 | Primary Output             |
 | ------------------ | ---------- | ------------------------- | -------------------------- |
 | `teach-me-testing` | Learning   | Once per learner          | Progress + notes + cert    |
+| `test-design`      | 3, 4       | System + per epic         | Test design + NFR plan     |
 | `framework`        | 3          | Once                      | Test infrastructure        |
 | `ci`               | 3          | Once                      | CI/CD pipeline             |
-| `test-design`      | 3, 4       | System + per epic         | Test design doc            |
 | `atdd`             | 4          | Per story (optional)      | Failing tests              |
 | `automate`         | 4          | Per story                 | Passing tests              |
 | `test-review`      | 4, Gate    | Per epic/release          | Quality report             |
-| `nfr-assess`       | 2, Gate    | Per release               | NFR assessment             |
+| `nfr-assess`       | Gate       | Per release               | NFR evidence audit         |
 | `trace`            | 2, 4, Gate | Baseline + refresh + gate | Coverage matrix + decision |
 
 ---
@@ -338,7 +362,7 @@ All workflows listed here are current and supported in TEA, including `nfr-asses
 - [Run ATDD](/docs/how-to/workflows/run-atdd.md)
 - [Run Automate](/docs/how-to/workflows/run-automate.md)
 - [Run Test Review](/docs/how-to/workflows/run-test-review.md)
-- [Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md)
+- [Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md)
 - [Run Trace](/docs/how-to/workflows/run-trace.md)
 
 **Explanation:**

package/lib/bmad-cache/tea/docs/reference/knowledge-base.md

@@ -377,7 +377,7 @@ Each TEA workflow loads specific fragments:
 - risk-governance.md
 - probability-impact.md
 
-**Purpose:** NFR assessment frameworks and decision rules
+**Purpose:** NFR Evidence Audit frameworks and decision rules
 
 ---
 
@@ -391,7 +391,7 @@ Each TEA workflow loads specific fragments:
 
 **Purpose:** Traceability and gate decision standards
 
-**Note:** Loads nfr-criteria.md if NFR assessment is part of gate decision.
+**Note:** Loads nfr-criteria.md if NFR evidence audit status is part of the gate decision.
 
 ---
 

package/lib/bmad-cache/tea/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.15.1",
+  "version": "1.19.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method-test-architecture-enterprise",
-      "version": "1.15.1",
+      "version": "1.19.0",
       "license": "MIT",
       "dependencies": {
         "@clack/prompts": "^0.11.0",

package/lib/bmad-cache/tea/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.15.1",
+  "version": "1.19.0",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",

package/lib/bmad-cache/tea/src/agents/bmad-tea/customize.toml

@@ -63,11 +63,21 @@ code = "TMT"
 description = "Teach Me Testing — interactive learning companion with 7 progressive sessions from fundamentals to advanced practices"
 skill = "bmad-teach-me-testing"
 
+[[agent.menu]]
+code = "TD"
+description = "Test Design — risk assessment, NFR planning, and coverage strategy for system or epic scope"
+skill = "bmad-testarch-test-design"
+
 [[agent.menu]]
 code = "TF"
 description = "Test Framework — initialize production-ready test framework architecture"
 skill = "bmad-testarch-framework"
 
+[[agent.menu]]
+code = "CI"
+description = "Continuous Integration — recommend and scaffold CI/CD quality pipeline"
+skill = "bmad-testarch-ci"
+
 [[agent.menu]]
 code = "AT"
 description = "ATDD — generate failing acceptance tests plus an implementation checklist before development"
@@ -79,26 +89,21 @@ description = "Test Automation — generate prioritized API/E2E tests, fixtures,
 skill = "bmad-testarch-automate"
 
 [[agent.menu]]
-code = "TD"
-description = "Test Design — risk assessment plus coverage strategy for system or epic scope"
-skill = "bmad-testarch-test-design"
+code = "GATE"
+description = "Release Gate — route final audit, NFR evidence audit, and trace gate decision"
+prompt = "Help the user run the release gate path. First determine which evidence exists, then recommend the correct sequence: optional test-review for final test quality audit, optional nfr-assess for NFR Evidence Audit, then trace Phase 2 for PASS/CONCERNS/FAIL/WAIVED gate decision. Do not merge these workflows; route to the right one based on available evidence."
 
 [[agent.menu]]
-code = "TR"
-description = "Trace Coverage — map requirements, specs, or inferred journeys to tests (Phase 1) and make quality gate decision (Phase 2)"
-skill = "bmad-testarch-trace"
+code = "RV"
+description = "Review Tests — perform a quality check against written tests using comprehensive knowledge base and best practices"
+skill = "bmad-testarch-test-review"
 
 [[agent.menu]]
 code = "NR"
-description = "Non-Functional Requirements — assess NFRs and recommend actions"
+description = "NFR Evidence Audit — assess implemented NFR evidence and recommend actions"
 skill = "bmad-testarch-nfr"
 
 [[agent.menu]]
-code = "CI"
-description = "Continuous Integration — recommend and scaffold CI/CD quality pipeline"
-skill = "bmad-testarch-ci"
-
-[[agent.menu]]
-code = "RV"
-description = "Review Tests — perform a quality check against written tests using comprehensive knowledge base and best practices"
-skill = "bmad-testarch-test-review"
+code = "TR"
+description = "Trace Coverage — map requirements to tests (Phase 1) and make quality gate decision (Phase 2)"
+skill = "bmad-testarch-trace"

package/lib/bmad-cache/tea/src/agents/bmad-tea/resources/knowledge/confidence-gate.md

@@ -0,0 +1,73 @@
+# Confidence Gate
+
+## Principle
+
+When generating tests, scaffolding fixtures, classifying risk, or proposing any non-trivial test artifact, emit a confidence assessment before writing code. If confidence is below the threshold, stop and ask the user instead of generating plausible-looking output built on guesses.
+
+## Rationale
+
+The failure mode of LLM-generated tests is rarely "refused to try" — it is "generated something plausible that passes locally and breaks silently in CI." Hallucinated selectors, invented endpoint paths, fabricated risk scores, and reverse-engineered schemas all produce code that looks correct and tests nothing real. A confidence gate makes that failure mode loud by forcing the agent to declare its evidence and its unknowns before any artifact is committed.
+
+## Required output shape
+
+Every non-trivial test artifact proposal must include:
+
+```
+Confidence: <1-10>
+Rationale: <one or two sentences citing concrete evidence from the repo or contract>
+Unknowns: <bulleted list of things the agent does not know>
+```
+
+The Rationale must cite a file path, a contract document, an existing pattern, or a captured observation. Vague rationale ("based on standard patterns", "looks similar to other tests") is not evidence and forces the score down.
+
+## Threshold rule
+
+- **Confidence ≥ 7** — proceed with generation.
+- **Confidence 5–6** — proceed but surface the assumptions to the user in the output so they can correct mid-flight.
+- **Confidence < 5** — STOP. Do not generate. Ask the user to resolve the most-blocking Unknown first.
+
+## When to apply
+
+Apply the gate when generating or proposing:
+
+- **Selectors and page objects.** Must have explored the live application via `playwright-cli` or read existing page object patterns. Confidence < 5 if neither.
+- **Endpoint paths and request shapes.** Must have read the OpenAPI / Swagger contract or existing endpoint enums. Confidence < 5 if the endpoint is being invented.
+- **Risk classification (test-design, NFR).** Must cite probability and impact evidence. Confidence < 5 if scoring is vibes-based.
+- **Fixture composition.** Must understand existing `mergeTests` patterns and fixture boundaries in the repo. Confidence < 5 if composing blindly.
+- **Schema authoring (Zod, Ajv, JSON Schema).** Must have a documented contract source (OpenAPI, JSON schema, existing schema file). Confidence < 5 if reverse-engineering from a single sample response.
+- **Data factories.** Must understand the production data shape and constraints. Confidence < 5 if guessing field validity rules.
+
+## When NOT to apply
+
+- Mechanical refactors with clear scope (rename a variable, add a tag, update an import).
+- Reading or summarizing existing artifacts.
+- Producing reports from already-gathered data.
+- Trivial test additions that copy an existing pattern exactly.
+
+The gate exists to prevent fabrication, not to bureaucratize obvious work.
+
+## Anti-patterns
+
+❌ **Vanity scores.** `Confidence: 9` with no Rationale, or Rationale that does not cite evidence. Score the evidence, not the optimism.
+
+❌ **Listing then ignoring Unknowns.** Listing unknowns and then proceeding anyway when Confidence is below threshold. If the gate is below threshold, the only valid next action is to ask the user.
+
+❌ **Asking generically.** Asking "should I proceed?" instead of resolving the most-blocking Unknown with a concrete one-sentence question.
+
+❌ **Inflating to clear the bar.** Adjusting Confidence upward to avoid the stop rule. If the evidence is weak, the score is weak; resolve the evidence, not the number.
+
+## Patterns that work
+
+✅ **Cite the source.** "Confidence: 8 — Rationale: read `src/openapi/users.yaml` line 142-167 and existing schema at `tests/api/users.schema.ts`."
+
+✅ **One concrete Unknown.** When below threshold, ask one specific question: "Is `POST /users/{id}/role` documented anywhere? I can't find it in the OpenAPI spec and there are no existing tests for it."
+
+✅ **Promote evidence.** When the user answers the Unknown, the Rationale gets stronger and Confidence rises legitimately. The gate is a feedback loop, not a checkpoint.
+
+## Related fragments
+
+- `test-quality.md` — Definition of Done for tests; the gate protects DoD compliance.
+- `risk-governance.md` — risk scoring discipline that informs Rationale for risk-related gates.
+- `probability-impact.md` — scoring scales used in risk-related Rationale.
+- `selector-resilience.md` — selector confidence specifically.
+- `playwright-cli.md` — the sanctioned exploration tool that promotes selector Confidence.

package/lib/bmad-cache/tea/src/agents/bmad-tea/resources/knowledge/test-quality.md

@@ -647,6 +647,7 @@ test('admin action', async ({ page }) => {
   - `data-factories.md` - Isolated, parallel-safe data patterns
   - `fixture-architecture.md` - Setup extraction and cleanup
   - `test-levels-framework.md` - Choosing appropriate test granularity for speed
+  - `confidence-gate.md` - Agent reliability gate that protects DoD compliance during LLM-assisted test generation
 
 ## Core Quality Checklist
 

package/lib/bmad-cache/tea/src/agents/bmad-tea/resources/tea-index.csv

@@ -40,7 +40,7 @@ pactjs-utils-request-filter,Pact.js Utils Request Filter,"createRequestFilter, n
 pact-mcp,Pact MCP Server,"SmartBear MCP for PactFlow: generate tests, review, can-i-deploy, provider states","pact,mcp,pactflow,contract-testing,broker",specialized,knowledge/pact-mcp.md
 pact-consumer-framework-setup,Pact Consumer CDC Framework Setup,"Directory structure, vitest config with fileParallelism:false + pool:forks + singleFork:true (FFI safety), one-file-per-consumer+provider-pair rule (FFI handle collision prevention), jq-normalized publishing, 1:1 local/CI parity, PactV4 patterns","pactjs-utils,consumer,contract-testing,pact,ci,framework,setup,vitest,shell-scripts,jq,pactv4,ffi,file-organization,one-file-per-pair",specialized,knowledge/pact-consumer-framework-setup.md
 pact-broker-webhooks,Pact Broker Webhooks,"PactFlow → GitHub repository_dispatch auth via dedicated machine user + classic PAT (repo scope, no expiration) + PactFlow secret; staleness monitoring and PAT rotation runbook","pact,pactflow,broker,webhooks,github,auth,pat,ci,operations,security",specialized,knowledge/pact-broker-webhooks.md
-adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR assessment","nfr,testability,adr,quality,assessment,checklist",extended,knowledge/adr-quality-readiness-checklist.md
+adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR evidence audit","nfr,testability,adr,quality,assessment,checklist",extended,knowledge/adr-quality-readiness-checklist.md
 playwright-cli,Playwright CLI,"Token-efficient CLI for AI coding agents: element refs, sessions, snapshots, trace analysis, debug=cli autonomous investigation","cli,browser,agent,automation,snapshot,trace,debug",core,knowledge/playwright-cli.md
 pact-consumer-di,Pact Consumer DI Pattern,"Dependency injection pattern for Pact consumer tests — call actual source code instead of raw fetch by injecting mock server URL via optional baseUrl in context type","contract-testing,pact,consumer,dependency-injection,api,backend,architecture",extended,knowledge/pact-consumer-di.md
 webhook-fundamentals,Webhook Testing Fundamentals,"Why webhook delivery is hard: async, parallel pollution, opaque timeouts, cleanup drift. playwright-utils approach with polling, typed matchers, rich errors, startedAt isolation","webhook,async,playwright-utils,event-driven,eventually-consistent",core,knowledge/webhook-testing-fundamentals.md
@@ -50,3 +50,4 @@ webhook-waiting,Webhook Waiting and Querying,"waitFor, waitForCount, getReceived
 webhook-timeout-error,WebhookTimeoutError Debugging,"templateName, timeoutMs, totalReceived, receivedWebhooks, matcherDetails, toJSON — inspect what arrived vs what was expected","webhook,debugging,errors,playwright-utils",extended,knowledge/webhook-timeout-error.md
 webhook-providers,Webhook Provider Patterns,"WireMock (deleteById supported), MockServer (deleteById no-op), Mockoon (deleteById no-op, 100-entry limit), custom WebhookProvider interface","webhook,providers,playwright-utils,wiremock,mockserver,mockoon",extended,knowledge/webhook-providers.md
 webhook-risk,Webhook Testing Risk Guidance,"When webhook tests are required, P2×I3 default risk score, complete test checklist, failure patterns and mitigations, TA assessment checklist","webhook,risk,assessment,event-driven,async,playwright-utils,governance",core,knowledge/webhook-risk-guidance.md
+confidence-gate,Confidence Gate,"1-10 confidence scoring with stop-and-ask rule below threshold for selectors, endpoints, risk classification, fixtures, schemas, and data factories — prevents agent fabrication","reliability,agent-safety,generation,quality,governance",core,knowledge/confidence-gate.md

package/lib/bmad-cache/tea/src/module-help.csv

@@ -1,4 +1,4 @@
-module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
 Test Architecture Enterprise,_meta,,,,,,,,,false,https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/llms.txt,
 Test Architecture Enterprise,bmad-teach-me-testing,Teach Me Testing,TMT,Teach testing fundamentals through 7 sessions (TEA Academy).,,,0-learning,,,false,test_artifacts,progress file|session notes|certificate
 Test Architecture Enterprise,bmad-testarch-test-design,Test Design,TD,Risk-based test planning.,,,3-solutioning,,bmad-testarch-framework,false,test_artifacts,test design document
@@ -7,5 +7,5 @@ Test Architecture Enterprise,bmad-testarch-ci,CI Setup,CI,Configure CI/CD qualit
 Test Architecture Enterprise,bmad-testarch-atdd,ATDD,AT,Generate red-phase acceptance test scaffolds before implementation.,,,4-implementation,bmad-create-story:create,bmad-dev-story,false,test_artifacts,atdd-checklist|red-phase acceptance tests
 Test Architecture Enterprise,bmad-testarch-automate,Test Automation,TA,Expand test coverage.,,,4-implementation,bmad-testarch-atdd,,false,test_artifacts,test suite
 Test Architecture Enterprise,bmad-testarch-test-review,Test Review,RV,Quality audit (0-100 scoring).,,,4-implementation,bmad-testarch-automate,,false,test_artifacts,review report
-Test Architecture Enterprise,bmad-testarch-nfr,NFR Assessment,NR,Non-functional requirements assessment.,,,4-implementation,bmad-testarch-automate,,false,test_artifacts,nfr report
+Test Architecture Enterprise,bmad-testarch-nfr,NFR Evidence Audit,NR,Audit non-functional requirement evidence.,,,4-implementation,bmad-testarch-automate,,false,test_artifacts,nfr report
 Test Architecture Enterprise,bmad-testarch-trace,Traceability,TR,Coverage traceability and gate.,,,4-implementation,bmad-testarch-test-review,,false,test_artifacts,traceability matrix|gate decision

package/lib/bmad-cache/tea/src/workflows/testarch/README.md

@@ -59,14 +59,15 @@ This folder contains the Test Architect (TEA) workflows converted to skill-drive
 
 ## TEA Workflows
 
+- teach-me-testing
 - test-design
-- automate
-- atdd
-- test-review
-- trace
 - framework
 - ci
+- atdd
+- automate
+- test-review
 - nfr-assess
+- trace
 
 ## Notes
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-teach-me-testing/data/role-paths.yaml

@@ -107,7 +107,7 @@ roles:
       session-04-test-design: "Test design makes risk visible to stakeholders"
       session-05-atdd-automate: "ATDD reduces defect rates early"
       session-06-quality-trace: "Quality metrics: P0/P1 coverage, not vanity metrics"
-      session-07-advanced: "Governance patterns, CI orchestration, NFR assessment"
+      session-07-advanced: "Governance patterns, CI orchestration, NFR evidence audit"
 
 # Role-Based Example Types
 example_types:

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-teach-me-testing/data/tea-resources-index.yaml

@@ -51,7 +51,7 @@ documentation:
         online: "/how-to/workflows/run-trace/"
         workflow: trace
 
-      - name: "NFR Assessment"
+      - name: "NFR Evidence Audit"
         local: "/docs/how-to/workflows/run-nfr-assess.md"
         online: "/how-to/workflows/run-nfr-assess/"
         workflow: nfr-assess

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-teach-me-testing/steps-c/step-04-session-01.md

@@ -95,7 +95,7 @@ Present this content (mostly autonomous, clear and educational):
 
 TEA is a comprehensive test architecture framework that provides:
 
-- **9 Workflows:** Teach Me Testing, Framework, Test Design, ATDD, Automate, Test Review, Trace, NFR Assessment, CI
+- **9 Workflows:** Teach Me Testing, Test Design, Framework, CI, ATDD, Automate, Test Review, NFR Evidence Audit, Trace
 - **35 Knowledge Fragments:** Distilled expertise on patterns, best practices, Playwright Utils
 - **Quality Standards:** Definition of Done with execution limits (no flaky tests, no hard waits, etc.)
 - **Risk-Based Testing:** P0-P3 matrix for prioritizing test coverage
@@ -113,7 +113,7 @@ Testing knowledge doesn't scale through manual teaching. TEA makes testing exper
 1. **TEA Lite (30 min):** Quick start - run Automate workflow, generate tests
 2. **TEA Solo:** Use workflows individually as needed
 3. **TEA Integrated:** Full lifecycle - Framework → Test Design → ATDD/Automate → Review → Trace
-4. **TEA Enterprise:** Add NFR Assessment + CI integration for compliance
+4. **TEA Enterprise:** Add NFR Evidence Audit + CI integration for compliance
 5. **TEA Brownfield:** Adapt TEA for existing test suites
 
 **Today we're experiencing TEA Lite!**"

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-teach-me-testing/steps-c/step-04-session-07.md

@@ -118,7 +118,7 @@ Set session-07-advanced `status: 'in-progress'` (only first time).
 - test-levels-framework.md - Unit/Integration/E2E
 - test-priorities-matrix.md - P0-P3 coverage targets
 - probability-impact.md - Probability × impact scoring
-- nfr-criteria.md - NFR assessment definitions
+- nfr-criteria.md - NFR evidence audit definitions
 
 **5. Authentication & Security (3 fragments)**
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-teach-me-testing/templates/certificate-template.md

@@ -53,7 +53,7 @@ average_score: { { average_score } }
 - ✅ **Architecture Patterns:** Fixtures, network-first patterns, data factories
 - ✅ **Test Design:** Risk assessment, coverage planning, P0-P3 prioritization
 - ✅ **Test Development:** ATDD red-green approach, test automation
-- ✅ **Quality Assurance:** Test review, traceability, NFR assessment
+- ✅ **Quality Assurance:** Test review, traceability, NFR evidence audit
 - ✅ **Advanced Techniques:** 42 knowledge fragments explored
 
 ---

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/resources/tea-index.csv

@@ -40,7 +40,7 @@ pactjs-utils-request-filter,Pact.js Utils Request Filter,"createRequestFilter, n
 pact-mcp,Pact MCP Server,"SmartBear MCP for PactFlow: generate tests, review, can-i-deploy, provider states","pact,mcp,pactflow,contract-testing,broker",specialized,knowledge/pact-mcp.md
 pact-consumer-framework-setup,Pact Consumer CDC Framework Setup,"Directory structure, vitest config with fileParallelism:false + pool:forks + singleFork:true (FFI safety), determinism gate (check-pact-determinism.sh), jq-normalized publishing, 1:1 local/CI parity, PactV4 patterns","pactjs-utils,consumer,contract-testing,pact,ci,framework,setup,vitest,shell-scripts,determinism,jq,pactv4,ffi",specialized,knowledge/pact-consumer-framework-setup.md
 pact-broker-webhooks,Pact Broker Webhooks,"PactFlow → GitHub repository_dispatch auth via dedicated machine user + classic PAT (repo scope, no expiration) + PactFlow secret; staleness monitoring and PAT rotation runbook","pact,pactflow,broker,webhooks,github,auth,pat,ci,operations,security",specialized,knowledge/pact-broker-webhooks.md
-adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR assessment","nfr,testability,adr,quality,assessment,checklist",extended,knowledge/adr-quality-readiness-checklist.md
+adr-quality-readiness-checklist,ADR Quality Readiness Checklist,"8-category 29-criteria framework for ADR testability and NFR evidence audit","nfr,testability,adr,quality,assessment,checklist",extended,knowledge/adr-quality-readiness-checklist.md
 playwright-cli,Playwright CLI,"Token-efficient CLI for AI coding agents: element refs, sessions, snapshots, trace analysis, debug=cli autonomous investigation","cli,browser,agent,automation,snapshot,trace,debug",core,knowledge/playwright-cli.md
 pact-consumer-di,Pact Consumer DI Pattern,"Dependency injection pattern for Pact consumer tests — call actual source code instead of raw fetch by injecting mock server URL via optional baseUrl in context type","contract-testing,pact,consumer,dependency-injection,api,backend,architecture",extended,knowledge/pact-consumer-di.md
 webhook-fundamentals,Webhook Testing Fundamentals,"Why webhook delivery is hard: async, parallel pollution, opaque timeouts, cleanup drift. playwright-utils approach with polling, typed matchers, rich errors, startedAt isolation","webhook,async,playwright-utils,event-driven,eventually-consistent",core,knowledge/webhook-testing-fundamentals.md