bmad-tea-nfr — Claude Code skill for NFR audits
bmad-tea-nfr — a Claude Code skill that checks implementation evidence for performance, security, reliability, and maintainability. Start it by asking for an NFR review when implementation evidence is available.
MIT 860 installs ★ 118 updated 2026-11-13
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a claude-codeWhat bmad-tea-nfr does
The skill reviews non-functional requirement evidence before release and saves the audit as nfr-assessment-{run_key}.md. It supports new audits, resume, validation, and editing. Each run gets a separate output for the system, an epic, or a story.
It loads project settings, applies overrides, and reads persistent facts before the audit begins. The project needs uv, a configured TEA module in _bmad/config.toml, and the bmod-tea skill installed beside this one, with its knowledge and contracts folders. If legacy NFR settings remain in _bmad/custom/, the workflow stops and asks for migration with npx --package=bmad-method-test-architecture-enterprise@4 tea-migrate-customizations --project-root {project-root}.
What it helps with
- check performance evidence before release
- review security requirements against implementation evidence
- assess system reliability and maintainability
- resume or validate a saved NFR audit
Example prompts for the agent
- Audit the implementation evidence for non-functional requirements.
- Review security and performance evidence before release.
- Resume the interrupted NFR audit for this story.
How to install bmad-tea-nfr
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a claude-code2Manually: put the files in place
~/.claude/skills/bmad-tea-nfr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bmad-tea-nfr/
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a codex2Manually: put the files in place
.agents/skills/bmad-tea-nfr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a cursor2Manually: put the files in place
.cursor/skills/bmad-tea-nfr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bmad-code-org/bmad-method-test-architecture-enterprise skills/bmad-tea-nfr2Manually: put the files in place
.github/skills/bmad-tea-nfr/SKILL.md1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a gemini-cli2Platform CLI
gemini skills install https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --path skills/bmad-tea-nfrManually: put the files in place
.devin/skills/bmad-tea-nfr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bmad-tea-nfr
How do I install bmad-tea-nfr in Claude Code?
Run npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-nfr -a claude-code. The skill file is installed at ~/.claude/skills/bmad-tea-nfr/SKILL.md.
What does bmad-tea-nfr do?
It reviews implementation evidence for performance, security, reliability, and maintainability. The audit is saved to a separate Markdown file for a system, epic, or story.
What does bmad-tea-nfr need to run?
The project needs uv, a configured TEA module in _bmad/config.toml, and bmod-tea installed beside this skill in the same scope. If TEA is not configured, run bmad setup tea first.
Source text
SKILL.md · MIT
---
name: bmad-tea-nfr
description: 'Audit NFR evidence for performance, security, reliability, and maintainability. Use when implementation evidence exists and the user says "audit NFR evidence", "audit NFRs", or "evaluate non-functional requirements"'
---
# NFR Evidence Audit
**Goal:** Audit implemented non-functional requirement evidence (performance, security, reliability, maintainability) before release with evidence-based validation.
**Role:** You are the Master Test Architect.
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
## Conventions
- Bare paths (e.g. `instructions.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}` is the nearest folder containing `_bmad/`, starting at the project working directory and moving up through its parents.
- `{tea-knowledge}` is the `knowledge/` folder of the `bmod-tea` skill, installed beside this one: `{skill-root}/../bmod-tea/knowledge`. `tea-index.csv` there lists every fragment by a path relative to that folder.
- `{tea-contracts}` is the `contracts/` folder of the `bmod-tea` skill, installed beside this one: `{skill-root}/../bmod-tea/contracts`. `story-identity.md` there says how a story is resolved, read and named.
- `{skill-name}` resolves to the skill directory's basename.
- Resolve sibling workflow files such as `instructions.md`, `checklist.md`, `steps-c/...`, `steps-e/...`, `steps-v/...`, and templates from `{skill-root}`.
## On Activation
Before resolving customizations or running hooks, inspect `{project-root}/_bmad/custom/` for `bmad-testarch-nfr.toml` and `bmad-testarch-nfr.user.toml`. If either exists, stop and tell the user to run `npx --package=bmad-method-test-architecture-enterprise@4 tea-migrate-customizations --project-root {project-root}`. Resolve any reported manual merge, then start a fresh chat. Do not continue with default settings while legacy overrides remain.
### Step 1: Resolve the Workflow Block
Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`
**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
1. `{skill-root}/customize.toml` — defaults
2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
### Step 2: Execute Prepend Steps
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
### Step 3: Load Persistent Facts
Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs resolved from `{project-root}` — expand them and load every matching file in lexical path order as facts. All other entries are facts verbatim.
### Step 4: Load Config
Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core --key modules.tea`. If the script fails, merge `{project-root}/_bmad/config.toml`, `{project-root}/_bmad/custom/config.toml` and `{project-root}/_bmad/custom/config.user.toml` yourself, in that order, with the merge rules above. If `_bmad/config.toml` is missing or has no `modules.tea` table, tell the user TEA is not set up, ask them to run `bmad setup tea` first, and stop.
Each `core` and `modules.tea` key is available as `{<key>}`, and as `config.<key>` in later steps. Replace `{project-root}` inside a value with the project root. Setup answers are strings: read `"true"` and `"false"` as booleans.
If `{tea-knowledge}/tea-index.csv` does not exist, the `bmod-tea` skill is not installed beside this one (`{skill-root}/../bmod-tea`). Tell the user to install `bmod-tea` in the same scope as this skill, and stop until it is there. For a skill in the project's skills folder run `npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmod-tea`; for a skill in the global skills folder add `-g`. Run the command on a yes. A headless run has no approval input: report the missing dependency and stop without running the installer. A `bmod-tea` installed in the other scope does not satisfy this skill.
### Step 5: Greet the User
Greet `{user_name}`, speaking in `{communication_language}`.
### Step 6: Execute Append Steps
Execute each entry in `{workflow.activation_steps_append}` in order.
Activation is complete. Begin the workflow below.
## Workflow Architecture
This workflow uses **tri-modal step-file architecture**:
- **Create mode (steps-c/)**: primary execution flow for new runs and resume continuation
- **Validate mode (steps-v/)**: validation against checklist
- **Edit mode (steps-e/)**: revise existing outputs
## Initialization Sequence
### 1. Mode Determination
"Welcome to the workflow. What would you like to do?"
- **[C] Create** — Run the workflow from the beginning
- **[R] Resume** — Resume an interrupted Create workflow
- **[V] Validate** — Validate existing outputs
- **[E] Edit** — Edit existing outputs
### 2. Route to First Step
- **If C:** Load `{skill-root}/steps-c/step-01-load-context.md`
- **If R:** Load `{skill-root}/steps-c/step-01b-resume.md` (Create-mode continuation)
- **If V:** Load `{skill-root}/steps-v/step-01-validate.md`
- **If E:** Load `{skill-root}/steps-e/step-01-assess.md`
Each run writes its audit to `{test_artifacts}/nfr/nfr-assessment-{run_key}.md`, where `run_key` is `system`, `epic-{epic_num}`, or `story-{story_key}`. Step 1 resolves it before the first save, so an audit for one scope never overwrites or merges into another scope's audit. Browser evidence screenshots also live under `{test_artifacts}/nfr/`.
Resume mode selects the output document matching the run being resumed, asks when several exist and no scope was named, and refuses to continue a document whose `runKey` belongs to a different run.
© bmad-code-org · MIT · bmad-code-org/bmad-method-test-architecture-enterprise