# NFR Assessment v3.0 ```xml Preflight requirements: - Implementation is deployed locally or accessible for evaluation. - Non-functional goals/SLAs are defined or discoverable. Confirm prerequisites; halt if targets are unknown and cannot be clarified. Identify which NFRs to assess (default: Security, Performance, Reliability, Maintainability). Gather thresholds from story/architecture/technical preferences; mark unknown targets. Inspect evidence (tests, telemetry, logs) for each NFR and classify status using deterministic PASS/CONCERNS/FAIL rules. List quick wins and recommended actions for any concerns/failures. Produce NFR assessment markdown summarizing evidence, status, and actions; update gate YAML block with NFR findings; compile checklist of evidence gaps and owners. If NFR targets are undefined and cannot be obtained, halt and request definition. Load the `nfr-criteria`, `ci-burn-in`, and relevant fragments via `{project-root}/bmad/bmm/testarch/tea-index.csv` to ground the assessment. Unknown thresholds default to CONCERNS—never guess. Ensure every NFR has evidence or call it out explicitly. Suggest monitoring hooks and fail-fast mechanisms when gaps exist.

NFR assessment report with actionable follow-ups and gate snippet.

```