bmad-testarch-nfr

Audit non-functional requirement evidence for performance, security, reliability, and maintainability.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-nfr-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-nfr
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-testarch-nfr
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-nfr-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams approaching release often lack a structured way to verify that performance, security, reliability, and maintainability requirements are actually met by existing implementation evidence, leading to unverified thresholds and risky release decisions. ## Core Features & Use Cases - Evidence-Based NFR Audit: Evaluates existing test results, metrics, logs, scans, and CI data against defined thresholds with deterministic PASS/CONCERNS/FAIL classifications. - Four-Domain Parallel Assessment: Dispatches Security, Performance, Reliability, and Maintainability audit workers via subagent, agent-team, or sequential execution modes. - Release Gate Reporting: Generates an nfr-assessment.md report with quick wins, prioritized remediation actions, evidence gaps, and a gate YAML snippet for release decisions. - Use Case: Before shipping a bulk export feature, run the audit to confirm load-test results meet the p95 latency threshold, Snyk scans show no critical vulnerabilities, and CI burn-in demonstrates stability, then receive a gate decision with blockers flagged. ## Quick Start Ask the assistant to audit NFR evidence for the current feature using the available test results, metrics, and logs.

Frequently Asked Questions about bmad-testarch-nfr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit non-functional requirements before a release?

Run the NFR evidence audit after implementation evidence exists. It loads thresholds from your tech spec, PRD, or test-design output, gathers test results, metrics, logs, and scan reports, then classifies each NFR as PASS, CONCERNS, or FAIL with a release gate recommendation.

What evidence sources does an NFR assessment use?

It consumes load test results (k6, JMeter), security scans (Snyk, npm audit, SAST/DAST), uptime and error-rate monitoring data, CI burn-in logs, coverage reports, and code duplication reports. Missing evidence is flagged as a gap with an owner and deadline.

What happens when an NFR threshold is not defined?

Undefined thresholds are marked UNKNOWN and the corresponding finding is classified as CONCERNS, never PASS. The workflow never guesses thresholds, so an absent target cannot produce a passing result.

Does the NFR audit run tests or CI pipelines itself?

No. The audit only evaluates existing implementation evidence such as prior test results, metrics, and logs. Use a test-design workflow earlier to plan NFR thresholds and the evidence that must be collected.

How are the four NFR domains evaluated in parallel?

Step 4 dispatches Security, Performance, Reliability, and Maintainability workers using agent-team, subagent, or sequential execution based on config and runtime capability probing. Results are aggregated into an overall status with cross-domain risk analysis.