ma-agents 3.12.2 → 3.13.0

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

@@ -96,6 +96,8 @@ network-first,Network-First Safeguards,Intercept-before-navigate workflow,"netwo
 fixture-architecture,Fixture Architecture,Composable fixture patterns,"fixtures,architecture",knowledge/fixture-architecture.md
 ```
 
+The agent-level `resources/` directory is the reference catalog for Murat. Workflow skills also carry their own `resources/tea-index.csv` and `resources/knowledge/` directories. That duplication is intentional: workflow step frontmatter resolves `knowledgeIndex: './resources/tea-index.csv'` from `{skill-root}`, keeping each workflow skill modular and self-contained.
+
 **2. Workflow Loads Relevant Fragments**
 
 When user runs `atdd`:

package/lib/bmad-cache/tea/docs/explanation/risk-based-testing.md

@@ -611,7 +611,7 @@ flowchart TD
 
 - [How to Run Test Design](/docs/how-to/workflows/run-test-design.md) - Apply risk scoring
 - [How to Run Trace](/docs/how-to/workflows/run-trace.md) - Gate decisions based on risk
-- [How to Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md) - NFR risk assessment
+- [How to Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md) - NFR evidence status for gate decisions
 
 **Use-Case Guides:**
 

package/lib/bmad-cache/tea/docs/explanation/tea-overview.md

@@ -51,28 +51,44 @@ BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pic
    - 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.
+   - Gate: optional `nfr-assess` for NFR Evidence Audit, then `trace` Phase 2.
+   - For brownfield BMad Method, run `nfr-assess` only when NFR evidence exists and matters to release.
 
 5. **Integrated: Greenfield - Enterprise Method (Enterprise/Compliance Work)**
-   - Phase 2: `nfr-assess`.
-   - Phase 3: system-level `test-design`, then `framework` and `ci`.
+   - Phase 2: PM defines NFRs in PRD.
+   - Phase 3: system-level `test-design` plans NFR thresholds/evidence, then `framework` and `ci`.
    - Phase 4: per-epic `test-design`, plus `atdd`/`automate`/`test-review`.
-   - Gate (Phase 2): `trace`; archive artifacts as needed.
+   - Gate: `nfr-assess` audits evidence, `trace` Phase 2 makes the gate decision; archive artifacts as needed.
 
 If you are unsure, default to the integrated path for your track and adjust later.
 
+### Exact Phase 3 Commands
+
+When this page says `test-design`, `framework`, or `ci`, those are TEA workflow names. If the TEA agent menu is already active, you can use the menu codes `TD`, `TF`, and `CI`. Otherwise, use the full command form for your tool:
+
+| Phase 3 Step             | Claude Code / Cursor / Windsurf | Codex                            |
+| ------------------------ | ------------------------------- | -------------------------------- |
+| System-level test design | `/bmad:tea:test-design`         | `$bmad-tea-testarch-test-design` |
+| Test framework setup     | `/bmad:tea:framework`           | `$bmad-tea-testarch-framework`   |
+| CI/CD quality pipeline   | `/bmad:tea:ci`                  | `$bmad-tea-testarch-ci`          |
+
+Example Phase 3 sequence:
+
+1. Run `/bmad:tea:test-design` and ask for **system-level** mode against the PRD, architecture, and ADRs.
+2. Run `/bmad:tea:framework` after the architecture and test design establish the test stack and quality requirements.
+3. Run `/bmad:tea:ci` after the framework exists so TEA can wire the pipeline to real test commands.
+
 ## TEA Command Catalog
 
 | Command       | Primary Outputs                                                                               | Notes                                                | With Browser Automation (CLI/MCP)                                                                                                    |
 | ------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `test-design` | Combined risk assessment, NFR planning, mitigation plan, and coverage strategy                | Risk scoring + NFR thresholds/evidence plan          | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)                                   |
 | `framework`   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                                                    |
 | `ci`          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                                                    |
-| `test-design` | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)                                   |
 | `atdd`        | Red-phase acceptance test scaffolds + implementation checklist                                | TDD red phase + optional recording mode              | **+ Recording**: UI selectors verified with live browser; API tests benefit from trace analysis                                      |
 | `automate`    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Visual debugging + trace analysis for test fixes; **+ Recording**: Verified selectors (UI) + network inspection (API) |
 | `test-review` | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                                                    |
-| `nfr-assess`  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                                                    |
+| `nfr-assess`  | NFR Evidence Audit report with actions                                                        | Audits implemented evidence against thresholds       | -                                                                                                                                    |
 | `trace`       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                                                    |
 
 ## TEA Workflow Lifecycle
@@ -93,7 +109,7 @@ graph TB
     subgraph Phase2["<b>Phase 2: PLANNING</b>"]
         PM["<b>PM: prd (creates PRD with FRs/NFRs)</b>"]
         PlanNote["<b>Business requirements phase</b>"]
-        NFR2["<b>TEA: nfr-assess (optional, enterprise)</b>"]
+        NFR2["<b>NFRs captured in PRD</b>"]
         PM -.-> NFR2
         NFR2 -.-> PlanNote
         PM -.-> PlanNote
@@ -102,7 +118,7 @@ graph TB
     subgraph Phase3["<b>Phase 3: SOLUTIONING</b>"]
         Architecture["<b>Architect: architecture</b>"]
         EpicsStories["<b>PM/Architect: create-epics-and-stories</b>"]
-        TestDesignSys["<b>TEA: test-design (system-level)</b>"]
+        TestDesignSys["<b>TEA: test-design (system-level + NFR planning)</b>"]
         Framework["<b>TEA: framework (optional if needed)</b>"]
         CI["<b>TEA: ci (optional if needed)</b>"]
         GateCheck["<b>Architect: implementation-readiness</b>"]
@@ -139,7 +155,7 @@ graph TB
     end
 
     subgraph Gate["<b>EPIC/RELEASE GATE</b>"]
-        NFR["<b>TEA: nfr-assess (if not done earlier)</b>"]
+        NFR["<b>TEA: nfr-assess (NFR Evidence Audit)</b>"]
         TestReview2["<b>TEA: test-review (final audit, optional)</b>"]
         TraceGate["<b>TEA: trace - Phase 2: Gate</b>"]
         GateDecision{"<b>Gate Decision</b>"}
@@ -167,10 +183,28 @@ graph TB
     style Waived fill:#9c27b0,stroke:#4a148c,stroke-width:3px,color:#000
 ```
 
-**TEA workflows:** `framework` and `ci` run once in Phase 3 after architecture. `test-design` is **dual-mode**:
+**TEA workflows:** `test-design` runs before `framework` and `ci` so NFR evidence needs can influence infrastructure. `framework` and `ci` run once in Phase 3 after architecture. `test-design` is **dual-mode**:
+
+- **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce TWO documents: `test-design-architecture.md` (for Architecture/Dev teams: testability gaps, ASRs, NFR requirements, planned evidence) + `test-design-qa.md` (for QA team: test execution recipe, coverage plan, Sprint 0 setup, NFR coverage plan). Feeds the implementation-readiness gate.
+- **Epic-level (Phase 4):** Run per-epic to produce `test-design-epic-N.md` (risk, priorities, coverage plan, and epic-specific NFR planning when relevant).
+
+Use the same `test-design` workflow command for both modes; make the scope explicit in your prompt:
+
+**Phase 3 system-level example**
+
+```text
+/bmad:tea:test-design
+Run system-level test-design for Phase 3 using docs/prd.md, docs/architecture.md, and docs/adr/*.md. Focus on architecture testability, ASRs, NFR thresholds, planned NFR evidence, integration risks, and Sprint 0 setup. Produce test-design-architecture.md and test-design-qa.md before implementation-readiness.
+```
+
+**Phase 4 per-epic example**
+
+```text
+/bmad:tea:test-design
+Run epic-level test-design for Phase 4 on Epic 3 using docs/epics/epic-3.md and its stories. Use prior system-level test-design outputs if present. Produce test-design-epic-3.md with risk scores, P0-P3 scenarios, regression/integration/NFR coverage, and follow-on guidance for atdd and automate.
+```
 
-- **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce TWO documents: `test-design-architecture.md` (for Architecture/Dev teams: testability gaps, ASRs, NFR requirements) + `test-design-qa.md` (for QA team: test execution recipe, coverage plan, Sprint 0 setup). Feeds the implementation-readiness gate.
-- **Epic-level (Phase 4):** Run per-epic to produce `test-design-epic-N.md` (risk, priorities, coverage plan).
+Codex users run `$bmad-tea-testarch-test-design` instead of `/bmad:tea:test-design` and use the same scope-setting prompt.
 
 The Quick Flow track skips Phases 1 and 3.
 BMad Method and Enterprise use all phases based on project needs.
@@ -180,14 +214,15 @@ When an ADR or architecture draft is produced, run `test-design` in **system-lev
 
 TEA spans multiple phases (Phase 3, Phase 4, and the release gate). Most BMM agents operate in a single phase. That multi-phase role is paired with a dedicated testing knowledge base so standards stay consistent across projects.
 
-### TEA's 8 Workflows Across Phases
+### TEA's 9 Workflows Across Phases
 
-| Phase       | TEA Workflows                                             | Frequency        | Purpose                                                 |
-| ----------- | --------------------------------------------------------- | ---------------- | ------------------------------------------------------- |
-| **Phase 2** | (none)                                                    | -                | Planning phase - PM defines requirements                |
-| **Phase 3** | `test-design` (system-level), `framework`, `ci`           | Once per project | System testability review and test infrastructure setup |
-| **Phase 4** | `test-design`, `atdd`, `automate`, `test-review`, `trace` | Per epic/story   | Test planning per epic, then per-story testing          |
-| **Release** | `nfr-assess`, `trace` (Phase 2: gate)                     | Per epic/release | Go/no-go decision                                       |
+| Phase        | TEA Workflows                                             | Frequency        | Purpose                                                         |
+| ------------ | --------------------------------------------------------- | ---------------- | --------------------------------------------------------------- |
+| **Learning** | `teach-me-testing`                                        | Per learner      | Progressive testing education                                   |
+| **Phase 2**  | (none)                                                    | -                | Planning phase - PM defines FRs/NFRs                            |
+| **Phase 3**  | `test-design` (system-level), `framework`, `ci`           | Once per project | System testability, NFR planning, and test infrastructure setup |
+| **Phase 4**  | `test-design`, `atdd`, `automate`, `test-review`, `trace` | Per epic/story   | Test planning per epic, then per-story testing                  |
+| **Release**  | `nfr-assess` (optional), `trace` (Phase 2: gate)          | Per epic/release | Optional NFR evidence audit; go/no-go gate decision             |
 
 **Note**: `trace` is a two-phase workflow: Phase 1 (traceability) + Phase 2 (gate decision). This reduces cognitive load while maintaining natural workflow.
 
@@ -245,25 +280,25 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
 - ➕ Documentation (Prerequisite) - Document existing codebase if undocumented
 - ➕ Phase 2: `trace` - Baseline existing test coverage before planning
 - 🔄 Phase 4: `test-design` - Focus on regression hotspots and brownfield risks
-- 🔄 Phase 4: Story Review - May include `nfr-assess` if not done earlier
-
-| Workflow Stage                     | Test Architect                                                            | Dev / Team                                                                       | Outputs                                                                |
-| ---------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| **Documentation**: Prerequisite ➕ | -                                                                         | Analyst `document-project` (if undocumented)                                     | Comprehensive project documentation                                    |
-| **Phase 1**: Discovery             | -                                                                         | Analyst/PM/Architect rerun planning workflows                                    | Updated planning artifacts in `{output_folder}`                        |
-| **Phase 2**: Planning              | Run ➕ `trace` (baseline coverage)                                        | PM `prd` (creates PRD with FRs/NFRs)                                             | PRD with FRs/NFRs, ➕ coverage baseline                                |
-| **Phase 3**: Solutioning           | Run `framework`, `ci` AFTER architecture and epic creation                | Architect `architecture`, `create-epics-and-stories`, `implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline               |
-| **Phase 4**: Sprint Start          | -                                                                         | SM `sprint-planning`                                                             | Sprint status file with all epics and stories                          |
-| **Phase 4**: Epic Planning         | Run `test-design` for THIS epic 🔄 (regression hotspots)                  | Review epic scope and brownfield risks                                           | `test-design-epic-N.md` with brownfield risk assessment and mitigation |
-| **Phase 4**: Story Dev             | (Optional) `atdd` before dev, then `automate` after                       | SM `create-story`, DEV implements                                                | Tests, story implementation                                            |
-| **Phase 4**: Story Review          | Apply `test-review` (optional), re-run `trace`, ➕ `nfr-assess` if needed | Resolve gaps, update docs/tests                                                  | Quality report, refreshed coverage matrix, NFR report                  |
-| **Phase 4**: Release Gate          | (Optional) `test-review` for final audit, Run `trace` (Phase 2)           | Capture sign-offs, share release notes                                           | Quality audit, Gate YAML + release summary                             |
+- 🔄 Release Gate - May include `nfr-assess` when NFR evidence exists
+
+| Workflow Stage                     | Test Architect                                                      | Dev / Team                                                                       | Outputs                                                                     |
+| ---------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| **Documentation**: Prerequisite ➕ | -                                                                   | Analyst `document-project` (if undocumented)                                     | Comprehensive project documentation                                         |
+| **Phase 1**: Discovery             | -                                                                   | Analyst/PM/Architect rerun planning workflows                                    | Updated planning artifacts in `{output_folder}`                             |
+| **Phase 2**: Planning              | Run ➕ `trace` (baseline coverage)                                  | PM `prd` (creates PRD with FRs/NFRs)                                             | PRD with FRs/NFRs, ➕ coverage baseline                                     |
+| **Phase 3**: Solutioning           | Run `test-design`, then `framework` and `ci`                        | Architect `architecture`, `create-epics-and-stories`, `implementation-readiness` | Architecture, epics/stories, NFR evidence plan, test framework, CI pipeline |
+| **Phase 4**: Sprint Start          | -                                                                   | SM `sprint-planning`                                                             | Sprint status file with all epics and stories                               |
+| **Phase 4**: Epic Planning         | Run `test-design` for THIS epic 🔄 (regression hotspots)            | Review epic scope and brownfield risks                                           | `test-design-epic-N.md` with brownfield risk assessment and mitigation      |
+| **Phase 4**: Story Dev             | (Optional) `atdd` before dev, then `automate` after                 | SM `create-story`, DEV implements                                                | Tests, story implementation                                                 |
+| **Phase 4**: Story Review          | Apply `test-review` (optional), re-run `trace`                      | Resolve gaps, update docs/tests                                                  | Quality report, refreshed coverage matrix                                   |
+| **Phase 4**: Release Gate          | Optional `test-review`, optional `nfr-assess`, then `trace` Phase 2 | Capture sign-offs, share release notes                                           | Quality audit, NFR evidence audit, Gate YAML + release summary              |
 
 **Key notes:**
 
 - Start with `trace` in Phase 2 to baseline coverage.
 - Focus `test-design` on regression hotspots and integration risk.
-- Run `nfr-assess` before the gate if it wasn't done earlier.
+- Run `nfr-assess` before the gate when NFR evidence exists and matters to release.
 
 ### Greenfield - Enterprise Method (Enterprise/Compliance Work)
 
@@ -273,24 +308,25 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
 **🏢 Enterprise Deltas from BMad Method:**
 
 - ➕ Phase 1: `research` - Domain and compliance research (recommended)
-- ➕ Phase 2: `nfr-assess` - Capture NFR requirements early (security/performance/reliability)
+- 🔄 Phase 3: `test-design` - Capture NFR thresholds and planned evidence early (security/performance/reliability)
 - 🔄 Phase 4: `test-design` - Enterprise focus (compliance, security architecture alignment)
+- ➕ Release Gate: `nfr-assess` - Audit NFR evidence before final gate
 - 📦 Release Gate - Archive artifacts and compliance evidence for audits
 
-| Workflow Stage             | Test Architect                                                         | Dev / Team                                                                       | Outputs                                                            |
-| -------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
-| **Phase 1**: Discovery     | -                                                                      | Analyst ➕ `research`, `product-brief`                                           | Domain research, compliance analysis, product brief                |
-| **Phase 2**: Planning      | Run ➕ `nfr-assess`                                                    | PM `prd` (creates PRD with FRs/NFRs), UX `create-ux-design`                      | Enterprise PRD with FRs/NFRs, UX design, ➕ NFR documentation      |
-| **Phase 3**: Solutioning   | Run `framework`, `ci` AFTER architecture and epic creation             | Architect `architecture`, `create-epics-and-stories`, `implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline           |
-| **Phase 4**: Sprint Start  | -                                                                      | SM `sprint-planning`                                                             | Sprint plan with all epics                                         |
-| **Phase 4**: Epic Planning | Run `test-design` for THIS epic 🔄 (compliance focus)                  | Review epic scope and compliance requirements                                    | `test-design-epic-N.md` with security/performance/compliance focus |
-| **Phase 4**: Story Dev     | (Optional) `atdd`, `automate`, `test-review`, `trace` per story        | SM `create-story`, DEV implements                                                | Tests, fixtures, quality reports, coverage matrices                |
-| **Phase 4**: Release Gate  | Final `test-review` audit, Run `trace` (Phase 2), 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence                                        | Quality audit, updated assessments, gate YAML, 📦 audit trail      |
+| Workflow Stage             | Test Architect                                                           | Dev / Team                                                                       | Outputs                                                                     |
+| -------------------------- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
+| **Phase 1**: Discovery     | -                                                                        | Analyst ➕ `research`, `product-brief`                                           | Domain research, compliance analysis, product brief                         |
+| **Phase 2**: Planning      | -                                                                        | PM `prd` (creates PRD with FRs/NFRs), UX `create-ux-design`                      | Enterprise PRD with FRs/NFRs, UX design                                     |
+| **Phase 3**: Solutioning   | Run `test-design`, then `framework` and `ci`                             | Architect `architecture`, `create-epics-and-stories`, `implementation-readiness` | Architecture, epics/stories, NFR evidence plan, test framework, CI pipeline |
+| **Phase 4**: Sprint Start  | -                                                                        | SM `sprint-planning`                                                             | Sprint plan with all epics                                                  |
+| **Phase 4**: Epic Planning | Run `test-design` for THIS epic 🔄 (compliance focus)                    | Review epic scope and compliance requirements                                    | `test-design-epic-N.md` with security/performance/compliance focus          |
+| **Phase 4**: Story Dev     | (Optional) `atdd`, `automate`, `test-review`, `trace` per story          | SM `create-story`, DEV implements                                                | Tests, fixtures, quality reports, coverage matrices                         |
+| **Phase 4**: Release Gate  | Final `test-review`, `nfr-assess`, `trace` Phase 2, 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence                                        | Quality audit, NFR evidence audit, gate YAML, 📦 audit trail                |
 
 **Key notes:**
 
-- Run `nfr-assess` early in Phase 2.
-- `test-design` emphasizes compliance, security, and performance alignment.
+- Run `test-design` early enough to define NFR thresholds and planned evidence before implementation.
+- Run `nfr-assess` at the release gate after evidence exists.
 - Archive artifacts at the release gate for audits.
 
 **Related how-to guides:**
@@ -301,7 +337,7 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
 - [How to Run Automate](/docs/how-to/workflows/run-automate.md)
 - [How to Run Test Review](/docs/how-to/workflows/run-test-review.md)
 - [How to Set Up CI Pipeline](/docs/how-to/workflows/setup-ci.md)
-- [How to Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md)
+- [How to Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md)
 - [How to Run Trace](/docs/how-to/workflows/run-trace.md)
 
 ## Deep Dive Concepts
@@ -423,13 +459,13 @@ Optional MCP integration for design-time broker interaction in contract testing
 **All 9 TEA workflows with step-by-step instructions:**
 
 1. [How to Learn Testing with TEA Academy](/docs/how-to/workflows/teach-me-testing.md) - Teach Me Testing (TEA Academy)
-2. [How to Set Up a Test Framework with TEA](/docs/how-to/workflows/setup-test-framework.md) - Scaffold Playwright or Cypress
-3. [How to Set Up CI Pipeline with TEA](/docs/how-to/workflows/setup-ci.md) - Configure CI/CD with selective testing
-4. [How to Run Test Design with TEA](/docs/how-to/workflows/run-test-design.md) - Risk-based test planning (system or epic)
+2. [How to Run Test Design with TEA](/docs/how-to/workflows/run-test-design.md) - Risk-based test and NFR planning (system or epic)
+3. [How to Set Up a Test Framework with TEA](/docs/how-to/workflows/setup-test-framework.md) - Scaffold Playwright or Cypress
+4. [How to Set Up CI Pipeline with TEA](/docs/how-to/workflows/setup-ci.md) - Configure CI/CD with selective testing
 5. [How to Run ATDD with TEA](/docs/how-to/workflows/run-atdd.md) - Generate red-phase test scaffolds before implementation
 6. [How to Run Automate with TEA](/docs/how-to/workflows/run-automate.md) - Expand test coverage after implementation
 7. [How to Run Test Review with TEA](/docs/how-to/workflows/run-test-review.md) - Audit test quality (0-100 scoring)
-8. [How to Run NFR Assessment with TEA](/docs/how-to/workflows/run-nfr-assess.md) - Validate non-functional requirements
+8. [How to Run NFR Evidence Audit with TEA](/docs/how-to/workflows/run-nfr-assess.md) - Audit non-functional requirement evidence
 9. [How to Run Trace with TEA](/docs/how-to/workflows/run-trace.md) - Coverage traceability + gate decisions
 
 ### Customization & Integration
@@ -445,7 +481,7 @@ Optional MCP integration for design-time broker interaction in contract testing
 **Specialized guidance for specific contexts:**
 
 - [Using TEA with Existing Tests (Brownfield)](/docs/how-to/brownfield/use-tea-with-existing-tests.md) - Incremental improvement, regression hotspots, baseline coverage
-- [Running TEA for Enterprise](/docs/how-to/brownfield/use-tea-for-enterprise.md) - Compliance, NFR assessment, audit trails, SOC 2/HIPAA
+- [Running TEA for Enterprise](/docs/how-to/brownfield/use-tea-for-enterprise.md) - Compliance, NFR evidence audit, audit trails, SOC 2/HIPAA
 
 ### Concept Deep Dives (Understanding-Oriented)
 

package/lib/bmad-cache/tea/docs/explanation/testing-as-engineering.md

@@ -47,18 +47,19 @@ Together, these utility libraries eliminate the need to reinvent core testing pr
 
 ### 2. Process: TEA (Test Architect Agent)
 
-A quality operating model packaged as eight executable workflows spanning test design, CI/CD gates, and release readiness. TEA encodes test architecture expertise into repeatable processes.
-
-| Workflow      | Purpose                                       |
-| ------------- | --------------------------------------------- |
-| `test-design` | Risk-based test planning per epic             |
-| `framework`   | Scaffold production-ready test infrastructure |
-| `ci`          | CI pipeline with selective testing            |
-| `atdd`        | Acceptance test-driven development            |
-| `automate`    | Prioritized test automation                   |
-| `test-review` | Test quality audits (0-100 score)             |
-| `nfr-assess`  | Non-functional requirements assessment        |
-| `trace`       | Coverage traceability and gate decisions      |
+A quality operating model packaged as nine workflows spanning learning, test design, CI/CD gates, and release readiness. TEA encodes test architecture expertise into repeatable processes.
+
+| Workflow           | Purpose                                       |
+| ------------------ | --------------------------------------------- |
+| `teach-me-testing` | Guided testing education                      |
+| `test-design`      | Risk-based planning plus NFR planning         |
+| `framework`        | Scaffold production-ready test infrastructure |
+| `ci`               | CI pipeline with selective testing            |
+| `atdd`             | Acceptance test-driven development            |
+| `automate`         | Prioritized test automation                   |
+| `test-review`      | Test quality audits (0-100 score)             |
+| `nfr-assess`       | NFR Evidence Audit                            |
+| `trace`            | Coverage traceability and gate decisions      |
 
 :::tip[Key Insight]
 TEA doesn't just generate tests—it provides a complete quality operating model with workflows for planning, execution, and release gates.

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

@@ -63,7 +63,7 @@ Terminology reference for Test Architect (TEA).
 | **Party Mode**       | Multi-agent collaboration feature where agents discuss challenges together. BMad Master orchestrates, selecting 2-3 relevant agents per message. |
 | **PM**               | Product Manager agent creating PRDs and tech-specs. Primary agent for Phase 2 planning.                                                          |
 | **SM**               | Scrum Master agent managing sprints, creating stories, and coordinating implementation. Primary orchestrator for Phase 4.                        |
-| **TEA**              | Test Architect agent responsible for test strategy, quality gates, and NFR assessment. Integrates throughout all phases.                         |
+| **TEA**              | Test Architect agent responsible for test strategy, quality gates, NFR planning, and NFR evidence audit. Integrates throughout all phases.       |
 | **Technical Writer** | Agent specialized in creating technical documentation, diagrams, and maintaining documentation standards.                                        |
 | **UX Designer**      | Agent creating UX design documents, interaction patterns, and visual specifications for UI-heavy projects.                                       |
 
@@ -136,7 +136,7 @@ Terminology reference for Test Architect (TEA).
 | **Knowledge Fragment**       | Individual markdown file in TEA's knowledge base covering a specific testing pattern or practice (42 fragments total).                                                                                                       |
 | **Browser Automation**       | Playwright CLI and/or MCP servers enabling live browser interaction during test generation. CLI provides token-efficient stateless commands; MCP provides rich stateful automation. Configured via `tea_browser_automation`. |
 | **Network-First Pattern**    | Testing pattern that waits for actual network responses instead of fixed timeouts to avoid race conditions and flakiness.                                                                                                    |
-| **NFR Assessment**           | Validation of non-functional requirements (security, performance, reliability, maintainability) with evidence-based decisions.                                                                                               |
+| **NFR Evidence Audit**       | Validation of non-functional requirement evidence (security, performance, reliability, maintainability) against defined thresholds.                                                                                          |
 | **Playwright Utils**         | Optional package (`@seontechnologies/playwright-utils`) providing production-ready fixtures and utilities for Playwright tests.                                                                                              |
 | **Risk-Based Testing**       | Testing approach where depth scales with business impact using probability × impact scoring (1-9 scale).                                                                                                                     |
 | **System-Level Test Design** | Test planning at architecture level (Phase 3) focusing on testability review, ADR mapping, and test infrastructure needs.                                                                                                    |

package/lib/bmad-cache/tea/docs/how-to/brownfield/use-tea-for-enterprise.md

@@ -5,7 +5,7 @@ description: Use TEA with compliance, security, and regulatory requirements in e
 
 # Running TEA for Enterprise Projects
 
-Use TEA on enterprise projects with compliance, security, audit, and regulatory requirements. This guide covers NFR assessment, audit trails, and evidence collection.
+Use TEA on enterprise projects with compliance, security, audit, and regulatory requirements. This guide covers NFR planning, NFR Evidence Audit, audit trails, and evidence collection.
 
 ## When to Use This
 
@@ -24,11 +24,11 @@ Use TEA on enterprise projects with compliance, security, audit, and regulatory
 
 ## Enterprise-Specific TEA Workflows
 
-### NFR Assessment (`nfr-assess`)
+### NFR Evidence Audit (`nfr-assess`)
 
-**Purpose:** Validate non-functional requirements with evidence.
+**Purpose:** Audit implemented non-functional requirement evidence against defined thresholds.
 
-**When:** Phase 2 (early) and Release Gate
+**When:** Release Gate, or earlier only when implementation evidence already exists. Use `test-design` in Phase 3 to plan NFR thresholds and evidence.
 
 **Why Enterprise Needs This:**
 
@@ -56,7 +56,7 @@ Evidence:
 - Compliance audit: reports/soc2-evidence.zip
 ```
 
-**Output:** NFR assessment with PASS/CONCERNS/FAIL for each category.
+**Output:** NFR evidence audit with PASS/CONCERNS/FAIL for each category.
 
 ### Trace with Audit Evidence (`trace`)
 
@@ -156,17 +156,18 @@ Include in PRD:
 - Compliance mandates (data retention, audit logs)
 ```
 
-**2. Assess NFRs:**
+**2. Plan NFR evidence with test-design:**
 
 ```
-TEA: nfr-assess
+TEA: test-design
 
-Categories: All (Security, Performance, Reliability, Maintainability)
+Scope: system-level
+Focus: NFR thresholds, planned validation, required evidence
 
-Output: nfr-assessment.md
-- NFR requirements documented
-- Acceptance criteria defined
-- Test strategy planned
+Output: test-design-architecture.md + test-design-qa.md
+- NFR thresholds and unknowns documented
+- Planned evidence sources defined
+- Test strategy and NFR coverage planned
 ```
 
 **3. Baseline (brownfield only):**
@@ -240,12 +241,12 @@ Requirements:
 
 ### Release Gate (Required)
 
-**1. Final NFR assessment:**
+**1. Final NFR Evidence Audit:**
 
 ```
 TEA: nfr-assess
 
-All categories (if not done earlier)
+All categories with available evidence
 Latest evidence (performance tests, security scans)
 ```
 
@@ -266,7 +267,7 @@ TEA: trace Phase 2
 Evidence required:
 - traceability-matrix.md (from Phase 1)
 - test-review.md (from quality audit)
-- nfr-assessment.md (from NFR assessment)
+- nfr-assessment.md (from NFR Evidence Audit)
 - Test execution results (must have test results available)
 
 Decision: PASS/CONCERNS/FAIL/WAIVED
@@ -282,7 +283,7 @@ Archive all artifacts for compliance audit
 Archive:
 - All test results
 - Coverage reports
-- NFR assessments
+- NFR evidence audits
 - Gate decisions
 - Approver signatures
 
@@ -297,7 +298,7 @@ Retention: Per compliance requirements (7 years for HIPAA)
 
 - Requirements traceability matrix
 - Test execution results (with timestamps)
-- NFR assessment reports
+- NFR evidence audit reports
 - Security scan results
 - Performance test results
 - Gate decision records
@@ -539,7 +540,7 @@ testWithAuth('admin can access admin endpoint', async ({ apiRequest, authToken,
 
 **Workflow Guides:**
 
-- [How to Run NFR Assessment](/docs/how-to/workflows/run-nfr-assess.md) - Deep dive on NFRs
+- [How to Run NFR Evidence Audit](/docs/how-to/workflows/run-nfr-assess.md) - Deep dive on evidence auditing
 - [How to Run Trace](/docs/how-to/workflows/run-trace.md) - Gate decisions with evidence
 - [How to Run Test Review](/docs/how-to/workflows/run-test-review.md) - Quality audits
 - [How to Run Test Design](/docs/how-to/workflows/run-test-design.md) - Compliance-focused planning

package/lib/bmad-cache/tea/docs/how-to/brownfield/use-tea-with-existing-tests.md

@@ -595,7 +595,7 @@ trace Phase 1 - Refresh coverage
 **6. Release Gate:**
 
 ```
-nfr-assess - Validate NFRs (if enterprise)
+nfr-assess - Audit NFR evidence (if enterprise and evidence exists)
 trace Phase 2 - Gate decision
 ```
 

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

@@ -1,17 +1,20 @@
 ---
-title: 'How to Run NFR Assessment with TEA'
-description: Validate non-functional requirements for security, performance, reliability, and maintainability using TEA
+title: 'How to Run NFR Evidence Audit with TEA'
+description: Audit non-functional requirement evidence for security, performance, reliability, and maintainability using TEA
 ---
 
-# How to Run NFR Assessment with TEA
+# How to Run NFR Evidence Audit with TEA
 
-Use TEA's `nfr-assess` workflow to validate non-functional requirements (NFRs) with evidence-based assessment across security, performance, reliability, and maintainability.
+Use TEA's `nfr-assess` workflow to audit non-functional requirement (NFR) evidence across security, performance, reliability, and maintainability. The command remains `nfr-assess` for compatibility; the workflow role is an evidence audit.
+
+Use `test-design` before implementation to define NFR thresholds, planned validation, and expected evidence. Use `nfr-assess` after evidence exists to decide PASS/CONCERNS/FAIL.
 
 ## When to Use This
 
 - Enterprise projects with compliance requirements
 - Projects with strict NFR thresholds
 - Before production release
+- After tests, scans, metrics, logs, monitoring data, or CI reports exist
 - When NFRs are critical to project success
 - Security or performance is mission-critical
 
@@ -26,14 +29,14 @@ Use TEA's `nfr-assess` workflow to validate non-functional requirements (NFRs) w
 
 - BMad Method installed
 - TEA agent available
-- NFRs defined in PRD or requirements doc
-- Evidence preferred but not required (test results, security scans, performance metrics)
+- NFRs defined in PRD, requirements doc, architecture, or `test-design`
+- Evidence sources available or explicitly missing (test results, security scans, performance metrics, logs, dashboards, CI reports)
 
-**Note:** You can run NFR assessment without complete evidence. TEA will mark categories as CONCERNS where evidence is missing and document what's needed.
+**Note:** You can run the audit without complete evidence. TEA will mark categories as CONCERNS where evidence is missing and document what's needed.
 
 ## Steps
 
-### 1. Run the NFR Assessment Workflow
+### 1. Run the NFR Evidence Audit Workflow
 
 Start a fresh chat and run:
 
@@ -41,11 +44,11 @@ Start a fresh chat and run:
 nfr-assess
 ```
 
-This loads TEA and starts the NFR assessment workflow.
+This loads TEA and starts the NFR Evidence Audit workflow.
 
 ### 2. Specify NFR Categories
 
-TEA will ask which NFR categories to assess.
+TEA will ask which NFR categories to audit.
 
 **Available Categories:**
 
@@ -69,11 +72,11 @@ Skip maintainability for now
 
 ### 3. Provide NFR Thresholds
 
-TEA will ask for specific thresholds for each category.
+TEA will use specific thresholds for each category, preferably from PRD, architecture, or `test-design`.
 
 **Critical Principle: Never guess thresholds.**
 
-If you don't know the exact requirement, tell TEA to mark as CONCERNS and request clarification from stakeholders.
+If you don't know the exact requirement, tell TEA to mark it as UNKNOWN/CONCERNS and request clarification from stakeholders.
 
 #### Security Thresholds
 
@@ -159,14 +162,14 @@ Don't have:
 - Mark as CONCERNS and request monitoring setup
 ```
 
-### 5. Review NFR Assessment Report
+### 5. Review NFR Evidence Audit Report
 
-TEA generates a comprehensive assessment report.
+TEA generates a comprehensive evidence audit report.
 
-#### Assessment Report (`nfr-assessment.md`):
+#### Evidence Audit Report (`nfr-assessment.md`):
 
 ````markdown
-# Non-Functional Requirements Assessment
+# NFR Evidence Audit
 
 **Date:** 2026-01-13
 **Epic:** User Profile Management
@@ -411,8 +414,8 @@ Lines        : 85.2% ( 1205/1414 )
    - Validate P99 < 200ms
    - Validate throughput > 1000 rps
 
-3. **Update this assessment** (TEA, 1 hour)
-   - Re-run `*nfr-assess` with new results
+3. **Update this audit** (TEA, 1 hour)
+   - Re-run `*nfr-assess` with new evidence
    - Confirm PASS status
 
 ### Waiver Option (If Business Approves)
@@ -461,13 +464,13 @@ If business decides to deploy with current performance:
 
 - Daily: Check performance dashboards
 - Weekly: Review alert trends
-- Monthly: Re-assess NFRs
+- Monthly: Re-audit NFR evidence
 
 ```
 
 ## What You Get
 
-### NFR Assessment Report
+### NFR Evidence Audit Report
 - Category-by-category analysis (Security, Performance, Reliability, Maintainability)
 - Requirements status (target vs actual)
 - Evidence for each requirement
@@ -482,7 +485,7 @@ If business decides to deploy with current performance:
 ### Mitigation Plans
 - Specific actions to address concerns
 - Owners and deadlines
-- Re-assessment criteria
+- Re-audit criteria
 
 ### Monitoring Plan
 - Post-release monitoring strategy
@@ -491,17 +494,20 @@ If business decides to deploy with current performance:
 
 ## Tips
 
-### Run NFR Assessment Early
+### Plan NFRs Early, Audit Evidence Later
 
 **Phase 2 (Enterprise):**
-Run `nfr-assess` during planning to:
+Define NFR requirements in the PRD so `test-design` can:
 - Identify NFR requirements early
 - Plan for performance testing
 - Budget for security audits
 - Set up monitoring infrastructure
 
+**Phase 3:**
+Run `test-design` to turn NFRs into thresholds, planned validation, and expected evidence.
+
 **Phase 4 or Gate:**
-Re-run before release to validate all requirements met.
+Run `nfr-assess` before release to audit the evidence.
 
 ### Never Guess Thresholds
 
@@ -649,7 +655,7 @@ Don't deploy with CONCERNS without mitigation or waiver.
 ```
 Mark as CONCERNS for categories without evidence
 Document what evidence is needed
-Set up tests/scans before re-assessment
+Set up tests/scans before re-audit
 ```
 
 **Don't block on missing evidence** - document what's needed and proceed.
@@ -675,7 +681,7 @@ Negotiate thresholds with stakeholders:
 
 Use data to negotiate realistic requirements.
 
-### Assessment Takes Too Long
+### Audit Takes Too Long
 
 **Problem:** Gathering evidence for all categories is time-consuming.