bmad-nfr-assess

Assess non-functional requirements across codebases and generate an auditable markdown tracker with gate decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-nfr-assess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-nfr-assess
Source: https://github.com/florian-trehaut/bmad-global/tree/main/src/bmm-skills/3-solutioning/bmad-nfr-assess
Command: npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-nfr-assess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Non-Functional Requirements assessment framework helps teams quantify and govern security, performance, reliability, maintainability, observability, and testability across projects, enabling auditable gate decisions.

Core Features & Use Cases

  • Comprehensive, evidence-based scanning of NFR areas with structured findings.
  • Epic-level or system-level scope to support project-specific or full-codebase evaluations, with a tracker document generated for traceability.
  • Automated gate decision synthesis and remediation planning feeding into the tracker.

Quick Start

Run the NFR assessment workflow to generate a tracker-ready evaluation.

Frequently Asked Questions about bmad-nfr-assess

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

FAQPage Schema
How do I assess non-functional requirements across a codebase for release risk?

To assess non-functional requirements for release risk, scan the codebase across security, performance, reliability, maintainability, observability, and testability domains, validating findings with concrete file paths to produce an auditable tracker document.

What is an evidence-driven NFR assessment and how does it work?

Evidence-driven NFR assessment evaluates non-functional requirements by combining security, performance, and reliability scans with concrete file path validation, generating structured findings and deterministic gate outcomes stored in a tracker markdown document.

How do I generate an auditable gate decision tracker for software quality?

Generate an auditable gate decision tracker by running NFR assessments at epic-level or system-level scope, synthesizing automated gate decisions and remediation planning into a structured markdown document for traceability.

Can I run a non-functional requirements assessment on a specific epic instead of the full codebase?

Yes, you can run non-functional requirements assessments at epic-level scope for project-specific evaluations or system-level scope for full-codebase evaluations, both generating a tracker markdown document with traceable findings.

Does non-functional requirement assessment validate findings with concrete code evidence?

Yes, non-functional requirement assessment validates all findings with concrete file paths and evidence, ensuring structured findings support deterministic gate outcomes for safe releases.

What is the best way to track non-functional requirements across multiple software quality dimensions?

The best way to track non-functional requirements across multiple dimensions is to evaluate security, performance, reliability, maintainability, observability, and testability together, storing synthesized gate decisions in an auditable tracker document.