npm - bmad-method-test-architecture-enterprise - Versions diffs - 1.18.0 → 1.19.0 - Mend

bmad-method-test-architecture-enterprise 1.18.0 → 1.19.0

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

Files changed (61) hide show

package/.claude-plugin/marketplace.json CHANGED Viewed

@@ -12,7 +12,7 @@
       "name": "bmad-method-test-architecture-enterprise",
       "source": "./",
       "description": "Master Test Architect module for quality strategy, test automation, CI/CD quality gates, and structured testing education. Part of the BMad Method ecosystem.",
-      "version": "1.18.0",
+      "version": "1.19.0",
       "author": {
         "name": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison"
       },

package/CHANGELOG.md CHANGED Viewed

@@ -9,6 +9,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
+- NFR workflow boundary clarified: `test-design` now owns NFR planning (thresholds, planned evidence, NFR-derived risks) and `nfr-assess` is reframed as NFR Evidence Audit — evaluating implementation evidence against planned thresholds after code exists.
+- `nfr-assess` step-02 now checks for an existing `test-design` NFR plan first and uses it as the primary threshold source, falling back to raw documents only for missing or UNKNOWN thresholds.
+- TEA agent menu gains a `GATE` routing intent that guides users through the release gate sequence (optional test-review → optional nfr-assess → trace Phase 2 gate) without merging those workflows.
+- NFR domains in `nfr-assess` corrected from "maintainability" to "scalability" to match the four parallel subagent domains (security, performance, reliability, scalability).
+- TEA phase table updated: `nfr-assess` marked optional at the Release phase.
+- NFR planning items in `test-design` step-05 output checklist conditioned on NFR scope.
+- Engagement models table: TEA Solo row for NFR Evidence Audit updated from No to Optional.
 - GitHub Actions workflow dependencies upgraded to Node 24-compatible major versions:
   - `actions/checkout@v5`
   - `actions/setup-node@v6`

package/README.md CHANGED Viewed

@@ -3,7 +3,7 @@
 [![Python Version](https://img.shields.io/badge/python-%3E%3D3.10-blue?logo=python&logoColor=white)](https://www.python.org)
 [![uv](https://img.shields.io/badge/uv-package%20manager-blueviolet?logo=uv)](https://docs.astral.sh/uv/)
-TEA (Test Engineering Architect) is a standalone BMAD module that delivers risk-based test strategy, test automation guidance, and release gate decisions. It provides a single expert agent (Murat, Master Test Architect and Quality Advisor) and nine workflows spanning Teach Me Testing (TEA Academy), framework setup, test design, ATDD, automation, traceability, NFR assessment, CI guidance, and test review.
+TEA (Test Engineering Architect) is a standalone BMAD module that delivers risk-based test strategy, test automation guidance, and release gate decisions. It provides a single expert agent (Murat, Master Test Architect and Quality Advisor) and nine workflows spanning Teach Me Testing (TEA Academy), test design, framework setup, CI guidance, ATDD, automation, test review, NFR Evidence Audit, and traceability.
 Docs: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
@@ -123,7 +123,7 @@ npx bmad-method install
 1. Install TEA (above)
 2. Load the TEA menu with `$bmad-tea` if you want a conversational entrypoint.
 3. Run one of the core workflows:
-   - `TD` / `/bmad:tea:test-design` / `$bmad-tea-testarch-test-design` — test design and risk assessment
+   - `TD` / `/bmad:tea:test-design` / `$bmad-tea-testarch-test-design` — test design, risk assessment, and NFR planning
    - `AT` / `/bmad:tea:atdd` / `$bmad-tea-testarch-atdd` — failing acceptance tests first (TDD red phase)
    - `TA` / `/bmad:tea:automate` / `$bmad-tea-testarch-automate` — expand automation coverage
 4. Or use in party mode: `/party` to include TEA with other agents
@@ -140,14 +140,14 @@ npx bmad-method install
 | Trigger | Slash Command                | Codex Skill                      | Purpose                                                   |
 | ------- | ---------------------------- | -------------------------------- | --------------------------------------------------------- |
 | TMT     | `/bmad:tea:teach-me-testing` | `$bmad-tea-teach-me-testing`     | Teach Me Testing (TEA Academy)                            |
+| TD      | `/bmad:tea:test-design`      | `$bmad-tea-testarch-test-design` | System-level or epic-level test design and NFR planning   |
 | TF      | `/bmad:tea:framework`        | `$bmad-tea-testarch-framework`   | Scaffold test framework (frontend, backend, or fullstack) |
 | CI      | `/bmad:tea:ci`               | `$bmad-tea-testarch-ci`          | Set up CI/CD quality pipeline (multi-platform)            |
-| TD      | `/bmad:tea:test-design`      | `$bmad-tea-testarch-test-design` | System-level or epic-level test design                    |
 | AT      | `/bmad:tea:atdd`             | `$bmad-tea-testarch-atdd`        | Generate failing acceptance tests + checklist             |
 | TA      | `/bmad:tea:automate`         | `$bmad-tea-testarch-automate`    | Expand test automation coverage                           |
 | RV      | `/bmad:tea:test-review`      | `$bmad-tea-testarch-test-review` | Review test quality and score                             |
+| NR      | `/bmad:tea:nfr-assess`       | `$bmad-tea-testarch-nfr`         | Audit implemented NFR evidence                            |
 | TR      | `/bmad:tea:trace`            | `$bmad-tea-testarch-trace`       | Trace requirements to tests + gate decision               |
-| NR      | `/bmad:tea:nfr-assess`       | `$bmad-tea-testarch-nfr`         | Assess non-functional requirements                        |
 ## Configuration

package/docs/explanation/engagement-models.md CHANGED Viewed

@@ -205,12 +205,11 @@ Steps:
 **Phase 2: Planning**
 - PM creates PRD with NFRs
-- (Optional) TEA runs `nfr-assess` (Enterprise only)
 **Phase 3: Solutioning**
 - Architect creates architecture
-- TEA runs `test-design` (system-level) → testability review
+- TEA runs `test-design` (system-level) → testability review and NFR evidence plan
 - TEA runs `framework` → test infrastructure
 - TEA runs `ci` → CI/CD pipeline
 - Architect runs `implementation-readiness` (fed by test design)
@@ -229,7 +228,7 @@ Steps:
 **Release Gate:**
 - (Optional) TEA runs `test-review` → final audit
-- (Optional) TEA runs `nfr-assess` → validate NFRs
+- (Optional) TEA runs `nfr-assess` → audit NFR evidence
 - TEA runs `trace` Phase 2 → gate decision (PASS/CONCERNS/FAIL/WAIVED)
 **What You Get:**
@@ -396,7 +395,7 @@ flowchart TD
 | -------------------------- | --------------------------- | ----------------------------- |
 | **None**                   | Any model                   | Choose based on project needs |
 | **Light** (internal audit) | TEA Solo or Integrated      | Gate decisions helpful        |
-| **Heavy** (SOC 2, HIPAA)   | TEA Integrated (Enterprise) | NFR assessment mandatory      |
+| **Heavy** (SOC 2, HIPAA)   | TEA Integrated (Enterprise) | NFR evidence audit mandatory  |
 ## Switching Between Models
@@ -444,17 +443,17 @@ Result: TEA where it adds value, skip where it doesn't
 ## Comparison Table
-| Aspect                | No TEA  | TEA Lite  | TEA Solo   | Integrated (Green) | Integrated (Brown) |
-| --------------------- | ------- | --------- | ---------- | ------------------ | ------------------ |
-| **BMad Required**     | No      | No        | No         | Yes                | Yes                |
-| **Learning Curve**    | None    | Low       | Medium     | High               | High               |
-| **Setup Time**        | 0       | 30 min    | 2 hours    | 1 day              | 2 days             |
-| **Workflows Used**    | 0       | 2-3       | 4-6        | 8                  | 8                  |
-| **Test Planning**     | Manual  | Optional  | Yes        | Systematic         | + Regression focus |
-| **Quality Gates**     | No      | No        | Optional   | Yes                | Yes + baseline     |
-| **NFR Assessment**    | No      | No        | No         | Optional           | Recommended        |
-| **Coverage Tracking** | Manual  | No        | Optional   | Yes                | Yes + trending     |
-| **Best For**          | Experts | Beginners | Standalone | New projects       | Legacy code        |
+| Aspect                 | No TEA  | TEA Lite  | TEA Solo   | Integrated (Green) | Integrated (Brown) |
+| ---------------------- | ------- | --------- | ---------- | ------------------ | ------------------ |
+| **BMad Required**      | No      | No        | No         | Yes                | Yes                |
+| **Learning Curve**     | None    | Low       | Medium     | High               | High               |
+| **Setup Time**         | 0       | 30 min    | 2 hours    | 1 day              | 2 days             |
+| **Workflows Used**     | 0       | 2-3       | 4-6        | 8                  | 8                  |
+| **Test Planning**      | Manual  | Optional  | Yes        | Systematic         | + Regression focus |
+| **Quality Gates**      | No      | No        | Optional   | Yes                | Yes + baseline     |
+| **NFR Evidence Audit** | No      | No        | Optional   | Optional           | Recommended        |
+| **Coverage Tracking**  | Manual  | No        | Optional   | Yes                | Yes + trending     |
+| **Best For**           | Experts | Beginners | Standalone | New projects       | Legacy code        |
 ## Real-World Examples
@@ -496,7 +495,7 @@ Decision: Full BMad Method + TEA Integrated
 Result:
 - Full lifecycle integration
 - Quality gates before releases
-- NFR assessment for enterprise customers
+- NFR evidence audit for enterprise customers
 ```
 ### Example 2: Enterprise (TEA Integrated - Brownfield)

package/docs/explanation/risk-based-testing.md CHANGED Viewed

@@ -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/docs/explanation/tea-overview.md CHANGED Viewed

@@ -51,14 +51,14 @@ 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.
@@ -82,13 +82,13 @@ Example Phase 3 sequence:
 | 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
@@ -109,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
@@ -118,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>"]
@@ -155,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>"}
@@ -183,10 +183,10 @@ 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) + `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).
+- **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:
@@ -194,14 +194,14 @@ Use the same `test-design` workflow command for both modes; make the scope expli
 ```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, NFRs, integration risks, and Sprint 0 setup. Produce test-design-architecture.md and test-design-qa.md before implementation-readiness.
+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 coverage, and follow-on guidance for atdd and automate.
+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.
 ```
 Codex users run `$bmad-tea-testarch-test-design` instead of `/bmad:tea:test-design` and use the same scope-setting prompt.
@@ -214,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.
@@ -279,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)
@@ -307,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:**
@@ -335,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
@@ -457,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
@@ -479,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/docs/explanation/testing-as-engineering.md CHANGED Viewed

@@ -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/docs/glossary/index.md CHANGED Viewed

@@ -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/docs/how-to/brownfield/use-tea-for-enterprise.md CHANGED Viewed

@@ -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/docs/how-to/brownfield/use-tea-with-existing-tests.md CHANGED Viewed

@@ -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
 ```