bmad-testarch-nfr

Execute a tri-mode NFR audit workflow and generate a gate-ready YAML report.

88|24|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-nfr-bmad-code-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-nfr
Source: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/workflows/testarch/bmad-testarch-nfr
Command: npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-nfr-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This NFR audit workflow standardizes the assessment of non-functional requirements, ensuring evidence is collected, analyzed, and gated for release decisions.

Core Features & Use Cases

  • Load and standardize evidence from tech-specs, PRDs, and test design to support NFR decision making.
  • Gather, score, and aggregate domain results (performance, security, reliability, maintainability) and generate an executive summary.
  • Produce a gate-ready artifact (YAML gate snippet) and a comprehensive narrative report for stakeholders.

Quick Start

Run the bmad-testarch-nfr workflow to generate an NFR assessment report from your project documents.

Frequently Asked Questions about bmad-testarch-nfr

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

FAQPage Schema
How do I generate an NFR audit report for release decisions?

To generate an NFR audit report, execute the deterministic tri-mode workflow to define categories, collect evidence from tech-specs and PRDs, evaluate domain results, and output a structured audit artifact with a gate YAML snippet.

What is a non-functional requirement audit and when do I need one?

A non-functional requirement audit standardizes the assessment of domains like performance, security, and reliability. You need this audit to ensure evidence is collected and gated properly before making safe software release decisions.

How do I collect and standardize evidence for non-functional requirements?

You collect and standardize NFR evidence by loading project documents such as tech-specs, PRDs, and test designs. The workflow extracts and aggregates this data to support scoring and domain-level decision making.

Can I use this workflow to evaluate security and performance risks before deployment?

Yes, this workflow evaluates security and performance risks by gathering, scoring, and aggregating domain results. It produces a gate-ready artifact highlighting per-category gaps and actions to ensure safe releases.

What format does the NFR audit output for release gating?

The NFR audit outputs a structured audit artifact containing a gate-ready YAML snippet and a comprehensive narrative report. This provides stakeholders with per-category results, identified gaps, and necessary actions for release decisions.

Are there limitations to using a deterministic workflow for NFR compliance?

The deterministic workflow relies on identifying NFR sources and loading required evidence from existing project documents. If your tech-specs, PRDs, or test designs lack sufficient detail, the generated audit report may show evidence gaps requiring manual action.