ma-agents 3.12.2 → 3.13.0

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

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

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

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

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

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

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

@@ -1,11 +1,11 @@
 ---
 name: bmad-testarch-nfr
-description: 'Assess NFRs like performance security and reliability. Use when the user says "lets assess NFRs" or "I want to evaluate non-functional requirements"'
+description: 'Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says "audit NFR evidence", "audit NFRs", or "evaluate non-functional requirements"'
 ---
 
-# Non-Functional Requirements Assessment
+# NFR Evidence Audit
 
-**Goal:** Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation.
+**Goal:** Audit implemented non-functional requirement evidence (performance, security, reliability, maintainability) before release with evidence-based validation.
 
 **Role:** You are the Master Test Architect.
 

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

@@ -1,11 +1,11 @@
-# Non-Functional Requirements Assessment - Validation Checklist
+# NFR Evidence Audit - Validation Checklist
 
 **Workflow:** `testarch-nfr`
-**Purpose:** Ensure comprehensive and evidence-based NFR assessment with actionable recommendations
+**Purpose:** Ensure comprehensive evidence-based NFR audit with actionable recommendations
 
 ---
 
-Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI workflows.
+Note: `nfr-assess` is the NFR Evidence Audit. It evaluates existing implementation evidence; it does not run tests or CI workflows. Use `test-design` to plan NFR thresholds and evidence before implementation.
 
 ## Prerequisites Validation
 
@@ -110,7 +110,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 
 ---
 
-## NFR Assessment with Deterministic Rules
+## NFR Evidence Audit with Deterministic Rules
 
 ### Performance Assessment
 
@@ -152,7 +152,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 - [ ] Status classified (PASS/CONCERNS/FAIL) with justification
 - [ ] Evidence source documented (file path, coverage report)
 
-### Custom NFR Assessment (if applicable)
+### Custom NFR Evidence Audit (if applicable)
 
 - [ ] Custom NFR 1 assessed against threshold with justification
 - [ ] Custom NFR 2 assessed against threshold with justification
@@ -225,7 +225,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 
 ## Deliverables Generated
 
-### NFR Assessment Report
+### NFR Evidence Audit Report
 
 - [ ] File created at `{test_artifacts}/nfr-assessment.md`
 - [ ] Template from `nfr-report-template.md` used
@@ -257,8 +257,8 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 
 ### Updated Story File (if enabled and requested)
 
-- [ ] "NFR Assessment" section added to story markdown
-- [ ] Link to NFR assessment report included
+- [ ] "NFR Evidence Audit" section added to story markdown
+- [ ] Link to NFR evidence audit report included
 - [ ] Overall status and critical issues included
 - [ ] Gate status included
 
@@ -358,7 +358,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 
 ## Documentation and Communication
 
-- [ ] NFR assessment report is readable and well-formatted
+- [ ] NFR evidence audit report is readable and well-formatted
 - [ ] Tables render correctly in markdown
 - [ ] Code blocks have proper syntax highlighting
 - [ ] Links are valid and accessible
@@ -377,7 +377,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 - [ ] Quick wins identified for all CONCERNS/FAIL
 - [ ] Recommended actions are specific and actionable
 - [ ] Evidence gaps documented with owners and deadlines
-- [ ] NFR assessment report generated and saved
+- [ ] NFR evidence audit report generated and saved
 - [ ] Gate YAML snippet generated (if enabled)
 - [ ] Evidence checklist generated (if enabled)
 - [ ] Workflow completed successfully
@@ -386,7 +386,7 @@ Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI work
 
 ## Sign-Off
 
-**NFR Assessment Status:**
+**NFR Evidence Audit Status:**
 
 - [ ] ✅ PASS - All NFRs meet requirements, ready for release
 - [ ] ⚠️ CONCERNS - Some NFRs have concerns, address before next release

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

@@ -1,4 +1,4 @@
-# Non-Functional Requirements Assessment
+# NFR Evidence Audit
 
 **Workflow:** `bmad-testarch-nfr`
 **Version:** 5.0 (Step-File Architecture)
@@ -7,7 +7,9 @@
 
 ## Overview
 
-Assess non-functional requirements (performance, security, reliability, maintainability) with evidence-based validation and deterministic PASS/CONCERNS/FAIL outcomes.
+Audit non-functional requirement evidence (performance, security, reliability, maintainability) with deterministic PASS/CONCERNS/FAIL outcomes.
+
+Use this workflow after implementation evidence exists: tests, scans, metrics, logs, monitoring data, CI results, or other release evidence. Use `test-design` earlier to define NFR thresholds, planned evidence, and NFR-derived risks.
 
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/nfr-report-template.md

@@ -6,7 +6,7 @@ workflowType: 'testarch-nfr-assess'
 inputDocuments: []
 ---
 
-# NFR Assessment - {FEATURE_NAME}
+# NFR Evidence Audit - {FEATURE_NAME}
 
 **Date:** {DATE}
 **Story:** {STORY_ID} (if applicable)
@@ -14,7 +14,7 @@ inputDocuments: []
 
 ---
 
-Note: This assessment summarizes existing evidence; it does not run tests or CI workflows.
+Note: This audit summarizes existing implementation evidence; it does not run tests or CI workflows. NFR thresholds and planned evidence should come from PRD, architecture, and `test-design` outputs where available.
 
 ## Executive Summary
 
@@ -217,7 +217,7 @@ Note: This assessment summarizes existing evidence; it does not run tests or CI
 
 ---
 
-## Custom NFR Assessments (if applicable)
+## Custom NFR Evidence Audits (if applicable)
 
 ### {CUSTOM_NFR_NAME_1}
 
@@ -446,7 +446,7 @@ nfr_assessment:
 
 ## Sign-Off
 
-**NFR Assessment:**
+**NFR Evidence Audit:**
 
 - Overall Status: {OVERALL_STATUS} {OVERALL_ICON}
 - Critical Issues: {CRITICAL_COUNT}
@@ -463,7 +463,7 @@ nfr_assessment:
 - If FAIL ❌: Resolve FAIL status NFRs, re-run `*nfr-assess`
 
 **Generated:** {DATE}
-**Workflow:** testarch-nfr v4.0
+**Workflow:** testarch-nfr v5.0
 
 ---
 

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

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

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-01-load-context.md

@@ -10,7 +10,7 @@ outputFile: '{test_artifacts}/nfr-assessment.md'
 
 ## STEP GOAL
 
-Gather NFR requirements, evidence sources, and knowledge fragments needed for assessment.
+Gather NFR requirements, evidence sources, and knowledge fragments needed for the evidence audit.
 
 ## MANDATORY EXECUTION RULES
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-01b-resume.md

@@ -54,7 +54,7 @@ Read `{outputFile}` and parse YAML frontmatter for:
 Display progress with checkmark/empty indicators:
 
 ```
-NFR Assessment - Resume Progress:
+NFR Evidence Audit - Resume Progress:
 
 1. Load Context (step-01-load-context)                    [completed/pending]
 2. Define Thresholds (step-02-define-thresholds)           [completed/pending]

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-02-define-thresholds.md

@@ -36,6 +36,17 @@ Establish the NFR categories to assess and the thresholds used for validation.
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
 
+## 0. Check for Existing Test-Design NFR Plan
+
+Before deriving thresholds from raw documents, check if a `test-design` output exists with NFR planning:
+
+- Look for `test-design-architecture.md`, `test-design-qa.md`, or any test-design output in `{test_artifacts}/` that contains an NFR section.
+- If found, **load it as the primary source of NFR categories and thresholds**. Use those values directly; do not re-derive them from scratch.
+- Only fall back to raw documents (tech-spec, PRD, story) for categories or thresholds that are still missing or marked **UNKNOWN** in the test-design output.
+- If no test-design NFR plan exists, proceed with step 1 using raw documents.
+
+---
+
 ## 1. Select Categories
 
 Use the ADR Quality Readiness Checklist (8 categories):
@@ -55,13 +66,13 @@ Add any `custom_nfr_categories` if provided.
 
 ## 2. Define Thresholds
 
-For each category, extract thresholds from:
+For each category, use thresholds from the test-design NFR plan (step 0) where available. For any remaining UNKNOWN or missing thresholds, extract from:
 
 - tech-spec (primary)
 - PRD (secondary)
-- story or test-design (feature-specific)
+- story (feature-specific)
 
-If a threshold is unknown, mark it **UNKNOWN** and plan to report **CONCERNS**.
+If a threshold is still unknown after checking all sources, mark it **UNKNOWN** and plan to report **CONCERNS**.
 
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04-evaluate-and-score.md

@@ -1,14 +1,14 @@
 ---
 name: 'step-04-evaluate-and-score'
-description: 'Orchestrate adaptive NFR domain assessments (agent-team, subagent, or sequential)'
+description: 'Orchestrate adaptive NFR evidence domain audits (agent-team, subagent, or sequential)'
 nextStepFile: '{skill-root}/steps-c/step-04e-aggregate-nfr.md'
 ---
 
-# Step 4: Orchestrate Adaptive NFR Assessment
+# Step 4: Orchestrate Adaptive NFR Evidence Audit
 
 ## STEP GOAL
 
-Select execution mode deterministically, then assess NFR domains using agent-team, subagent, or sequential execution while preserving output contracts.
+Select execution mode deterministically, then audit NFR evidence domains using agent-team, subagent, or sequential execution while preserving output contracts.
 
 ## MANDATORY EXECUTION RULES
 
@@ -141,7 +141,7 @@ If probing is disabled, honor the requested mode strictly. If that mode cannot b
 
 ### 3. Dispatch 4 NFR Workers
 
-**Subagent A: Security Assessment**
+**Subagent A: Security Evidence Audit**
 
 - File: `./step-04a-subagent-security.md`
 - Output: `/tmp/tea-nfr-security-${timestamp}.json`
@@ -150,19 +150,19 @@ If probing is disabled, honor the requested mode strictly. If that mode cannot b
   - `sequential`: run blocking and wait
 - Status: Running... ⟳
 
-**Subagent B: Performance Assessment**
+**Subagent B: Performance Evidence Audit**
 
 - File: `./step-04b-subagent-performance.md`
 - Output: `/tmp/tea-nfr-performance-${timestamp}.json`
 - Status: Running... ⟳
 
-**Subagent C: Reliability Assessment**
+**Subagent C: Reliability Evidence Audit**
 
 - File: `./step-04c-subagent-reliability.md`
 - Output: `/tmp/tea-nfr-reliability-${timestamp}.json`
 - Status: Running... ⟳
 
-**Subagent D: Scalability Assessment**
+**Subagent D: Scalability Evidence Audit**
 
 - File: `./step-04d-subagent-scalability.md`
 - Output: `/tmp/tea-nfr-scalability-${timestamp}.json`

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04a-subagent-security.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04a-subagent-security'
-description: 'Subagent: Security NFR assessment'
+description: 'Subagent: Security NFR evidence audit'
 subagent: true
 outputFile: '/tmp/tea-nfr-security-{{timestamp}}.json'
 ---
 
-# Subagent 4A: Security NFR Assessment
+# Subagent 4A: Security NFR Evidence Audit
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with other NFR domain assessments.
+This is an **isolated subagent** running in parallel with other NFR domain evidence audits.
 
 **Your task:** Assess SECURITY NFR domain only.
 
@@ -25,7 +25,7 @@ This is an **isolated subagent** running in parallel with other NFR domain asses
 
 ## SUBAGENT TASK
 
-### 1. Security Assessment Categories
+### 1. Security Evidence Audit Categories
 
 **Assess the following security dimensions:**
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04b-subagent-performance.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04b-subagent-performance'
-description: 'Subagent: Performance NFR assessment'
+description: 'Subagent: Performance NFR evidence audit'
 subagent: true
 outputFile: '/tmp/tea-nfr-performance-{{timestamp}}.json'
 ---
 
-# Subagent 4B: Performance NFR Assessment
+# Subagent 4B: Performance NFR Evidence Audit
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with other NFR domain assessments.
+This is an **isolated subagent** running in parallel with other NFR domain evidence audits.
 
 **Your task:** Assess PERFORMANCE NFR domain only.
 
@@ -17,7 +17,7 @@ This is an **isolated subagent** running in parallel with other NFR domain asses
 
 ## SUBAGENT TASK
 
-### 1. Performance Assessment Categories
+### 1. Performance Evidence Audit Categories
 
 **A) Response Times:**
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04c-subagent-reliability.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04c-subagent-reliability'
-description: 'Subagent: Reliability NFR assessment'
+description: 'Subagent: Reliability NFR evidence audit'
 subagent: true
 outputFile: '/tmp/tea-nfr-reliability-{{timestamp}}.json'
 ---
 
-# Subagent 4C: Reliability NFR Assessment
+# Subagent 4C: Reliability NFR Evidence Audit
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with other NFR domain assessments.
+This is an **isolated subagent** running in parallel with other NFR domain evidence audits.
 
 **Your task:** Assess RELIABILITY NFR domain only.
 
@@ -17,7 +17,7 @@ This is an **isolated subagent** running in parallel with other NFR domain asses
 
 ## SUBAGENT TASK
 
-### 1. Reliability Assessment Categories
+### 1. Reliability Evidence Audit Categories
 
 **A) Error Handling:**
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04d-subagent-scalability.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04d-subagent-scalability'
-description: 'Subagent: Scalability NFR assessment'
+description: 'Subagent: Scalability NFR evidence audit'
 subagent: true
 outputFile: '/tmp/tea-nfr-scalability-{{timestamp}}.json'
 ---
 
-# Subagent 4D: Scalability NFR Assessment
+# Subagent 4D: Scalability NFR Evidence Audit
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with other NFR domain assessments.
+This is an **isolated subagent** running in parallel with other NFR domain evidence audits.
 
 **Your task:** Assess SCALABILITY NFR domain only.
 
@@ -17,7 +17,7 @@ This is an **isolated subagent** running in parallel with other NFR domain asses
 
 ## SUBAGENT TASK
 
-### 1. Scalability Assessment Categories
+### 1. Scalability Evidence Audit Categories
 
 **A) Horizontal Scaling:**
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-04e-aggregate-nfr.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04e-aggregate-nfr'
-description: 'Aggregate NFR domain assessments into executive summary'
+description: 'Aggregate NFR domain evidence audits into executive summary'
 nextStepFile: '{skill-root}/steps-c/step-05-generate-report.md'
 outputFile: '{test_artifacts}/nfr-assessment.md'
 ---
 
-# Step 4E: Aggregate NFR Assessment Results
+# Step 4E: Aggregate NFR Evidence Audit Results
 
 ## STEP GOAL
 
-Read outputs from 4 parallel NFR subagents, calculate overall risk level, aggregate compliance status, and identify cross-domain risks.
+Read outputs from 4 parallel NFR evidence audit subagents, calculate overall risk level, aggregate compliance status, and identify cross-domain risks.
 
 ---
 
@@ -186,7 +186,7 @@ fs.writeFileSync('/tmp/tea-nfr-summary-{{timestamp}}.json', JSON.stringify(execu
 ### 7. Display Summary to User
 
 ```
-✅ NFR Assessment Complete ({subagentExecutionLabel})
+✅ NFR Evidence Audit Complete ({subagentExecutionLabel})
 
 🎯 Overall Risk Level: {overallRisk}
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/steps-c/step-05-generate-report.md

@@ -8,7 +8,7 @@ outputFile: '{test_artifacts}/nfr-assessment.md'
 
 ## STEP GOAL
 
-Produce the NFR assessment report and validate completeness.
+Produce the NFR evidence audit report and validate completeness.
 
 ## MANDATORY EXECUTION RULES
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/workflow-plan.md

@@ -1,4 +1,4 @@
-    # Workflow Plan: testarch-nfr
+    # Workflow Plan: testarch-nfr Evidence Audit
 
     ## Create Mode (steps-c)
     - step-01-load-context.md

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-nfr/workflow.yaml

@@ -1,7 +1,7 @@
 # Test Architect workflow: bmad-testarch-nfr
 name: bmad-testarch-nfr
 # prettier-ignore
-description: 'Assess NFRs like performance security and reliability. Use when the user says "lets assess NFRs" or "I want to evaluate non-functional requirements"'
+description: 'Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says "lets assess NFRs", "audit NFR evidence", or "evaluate non-functional requirements"'
 
 # Critical variables from config
 config_source: "{project-root}/_bmad/tea/config.yaml"
@@ -21,7 +21,7 @@ template: "./nfr-report-template.md"
 # Variables and inputs
 variables:
   # NFR category assessment (defaults to all categories)
-  custom_nfr_categories: "" # Optional additional categories beyond standard (security, performance, reliability, maintainability)
+  custom_nfr_categories: "" # Optional additional categories beyond standard (security, performance, reliability, scalability)
 
 # Output configuration
 default_output_file: "{test_artifacts}/nfr-assessment.md"
@@ -29,7 +29,7 @@ default_output_file: "{test_artifacts}/nfr-assessment.md"
 # Required tools
 required_tools:
   - read_file # Read story, test results, metrics, logs, BMad artifacts
-  - write_file # Create NFR assessment, gate YAML, evidence checklist
+  - write_file # Create NFR evidence audit, gate YAML, evidence checklist
   - list_files # Discover test results, metrics, logs
   - search_repo # Find NFR-related tests and evidence
   - glob # Find result files matching patterns

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-test-design/checklist.md

@@ -26,6 +26,7 @@
 - [ ] Architecture documents reviewed (if available)
 - [ ] Existing test coverage analyzed
 - [ ] Knowledge base fragments loaded (risk-governance, probability-impact, test-levels, test-priorities)
+- [ ] `nfr-criteria.md` loaded for system-level mode, and for epic-level mode when NFRs are in scope
 
 ### Step 2: Risk Assessment
 
@@ -40,6 +41,15 @@
 - [ ] Timelines set for mitigations
 - [ ] Residual risk documented
 
+### Step 2A: NFR Planning
+
+- [ ] NFR categories in scope identified (security, performance, reliability, scalability, maintainability, compliance, custom)
+- [ ] NFR thresholds extracted from PRD, architecture, ADRs, epics, or stories
+- [ ] Unknown thresholds marked as UNKNOWN; no values guessed
+- [ ] Missing thresholds converted into risks, assumptions, blockers, or clarification items
+- [ ] Planned evidence sources identified for later `nfr-assess`
+- [ ] NFR-derived risks mapped into the normal risk register using SEC/PERF/OPS/TECH/DATA categories
+
 ### Step 3: Coverage Design
 
 - [ ] Acceptance criteria broken into atomic scenarios
@@ -47,6 +57,8 @@
 - [ ] No duplicate coverage across levels
 - [ ] Priority levels assigned (P0/P1/P2/P3)
 - [ ] P0 scenarios meet strict criteria (blocks core + high risk + no workaround)
+- [ ] NFR-derived risks mapped to planned validation scenarios
+- [ ] Planned NFR evidence artifacts documented without final PASS/CONCERNS/FAIL decisions
 - [ ] Data prerequisites identified
 - [ ] Tooling/access requirements documented when applicable
 - [ ] Execution order defined (smoke → P0 → P1 → P2/P3)
@@ -58,6 +70,7 @@
 - [ ] Execution order documented
 - [ ] Resource estimates calculated
 - [ ] Quality gate criteria defined
+- [ ] NFR planning summary included when NFRs are in scope
 - [ ] Output file written to correct location
 - [ ] Output file uses template structure
 
@@ -112,6 +125,8 @@
 - [ ] P1 pass rate threshold defined (typically ≥95%)
 - [ ] High-risk mitigation completion required
 - [ ] Coverage targets specified (≥80% recommended)
+- [ ] NFR evidence expectation defined for each in-scope NFR category
+- [ ] Full NFR evidence decision deferred to `nfr-assess`
 
 ## Quality Checks
 
@@ -161,6 +176,7 @@
 - [ ] probability-impact.md applied
 - [ ] test-levels-framework.md referenced
 - [ ] test-priorities-matrix.md used
+- [ ] nfr-criteria.md consulted for NFR planning when applicable
 - [ ] Additional fragments loaded as needed
 
 ### Status File Integration
@@ -254,13 +270,13 @@
   - [ ] QA execution assumptions belong in QA doc instead
 - [ ] **NO test implementation code** (long examples belong in QA doc)
 - [ ] **NO test scripts** (no Playwright test(...) blocks, no assertions, no test setup code)
-- [ ] **NO NFR test examples** (NFR sections describe WHAT to test, not HOW to test)
+- [ ] **NFR Testability Requirements are concise** (WHAT architecture must provide, thresholds, planned evidence; no full audit tables)
 - [ ] **NO test scenario checklists** (belong in QA doc)
 - [ ] **NO bloat or repetition** (consolidate repeated notes, avoid over-explanation)
 - [ ] **Cross-references to QA doc** where appropriate (instead of duplication)
 - [ ] **RECIPE SECTIONS NOT IN ARCHITECTURE DOC:**
   - [ ] NO "Test Levels Strategy" section (unit/integration/E2E split belongs in QA doc only)
-  - [ ] NO "NFR Testing Approach" section with detailed test procedures (belongs in QA doc only)
+  - [ ] NO "NFR Testing Approach" section with detailed test procedures (use concise NFR Testability Requirements only)
   - [ ] NO "Test Environment Requirements" section (belongs in QA doc only)
   - [ ] NO "Recommendations for pre-implementation" section with test framework setup (belongs in QA doc only)
   - [ ] NO "Quality Gate Criteria" section (pass rates, coverage targets belong in QA doc only)
@@ -287,6 +303,10 @@
   - [ ] Priority sections have ONLY "Criteria" (no execution context)
   - [ ] Note at top: "P0/P1/P2/P3 = priority, NOT execution timing"
   - [ ] Test tables with columns: Test ID | Requirement | Test Level | Risk Link | Notes
+- [ ] **NFR Test Coverage Plan** section
+  - [ ] Maps NFR category to requirement/threshold, planned validation, tool/level, evidence artifact, and priority
+  - [ ] Lists missing thresholds or missing evidence sources
+  - [ ] Does not assign final PASS/CONCERNS/FAIL status
 - [ ] **Execution Strategy** section (organized by TOOL TYPE)
   - [ ] Every PR: Playwright tests (~10-15 min)
   - [ ] Nightly: k6 performance tests (~30-60 min)
@@ -310,7 +330,7 @@
 - [ ] ❌ NO Test Environment Requirements as separate section (integrate into Dependencies)
 - [ ] ❌ NO Testability Assessment section (covered in Dependencies)
 - [ ] ❌ NO Test Levels Strategy section (obvious from test scenarios)
-- [ ] ❌ NO NFR Readiness Summary
+- [ ] ❌ NO full NFR Evidence Audit or final PASS/CONCERNS/FAIL decisions
 - [ ] ❌ NO Quality Gate Criteria section (teams decide for themselves)
 - [ ] ❌ NO Follow-on Workflows section (BMAD commands self-explanatory)
 - [ ] ❌ NO Approval section

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

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

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-test-design/steps-c/step-02-load-context.md

@@ -75,6 +75,7 @@ Extract:
 - Tech stack & dependencies
 - Integration points
 - NFRs (performance, security, reliability, compliance)
+- NFR thresholds and missing threshold questions
 
 ### Epic-Level Mode (Phase 4)
 
@@ -165,6 +166,7 @@ Use `{knowledgeIndex}` to select and load only relevant fragments.
 ### System-Level Mode (Required)
 
 - `adr-quality-readiness-checklist.md`
+- `nfr-criteria.md`
 - `test-levels-framework.md`
 - `risk-governance.md`
 - `test-quality.md`
@@ -176,6 +178,11 @@ Use `{knowledgeIndex}` to select and load only relevant fragments.
 - `test-levels-framework.md`
 - `test-priorities-matrix.md`
 
+**Epic-Level NFR Loading:**
+
+- Load `nfr-criteria.md` when the epic/story includes security, performance, reliability, scalability, compliance, maintainability, or operational requirements.
+- Use prior system-level NFR planning from `test-design-architecture.md` or `test-design-qa.md` if present.
+
 **Playwright CLI (if `tea_browser_automation` is "cli" or "auto"):**
 
 - `playwright-cli.md`