nonfunctional-spec

Generates a non-functional requirements register with quantified acceptance criteria across eight quality attribute categories.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill nonfunctional-spec-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nonfunctional-spec
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/requirements/nonfunctional-spec
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill nonfunctional-spec-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Functional requirements alone leave quality expectations ambiguous, causing AI development agents to invent performance, security, and availability targets. This Skill produces a signed, measurable NFR specification that downstream architecture, testing, security, and infrastructure phases can build against. ## Core Features & Use Cases - NFR Register Generation: Documents requirements across 8 categories (performance, security, availability, usability, reliability, maintainability, compatibility, compliance) with targets, thresholds, and verification methods. - Governed Sign-Off Workflow: Enforces prerequisite signature checks, validation rules, and a Solution Architect approval gate before the document is baselined. - Traceability & Sources Tracking: Maps each NFR to functional requirements and architecture components, and logs questions, gaps, and generation history in a sources file. - Use Case: After experience design is signed, run this Skill to produce documentation/04-requirements/nonfunctional-spec.md defining SLA targets, encryption standards, and WCAG compliance criteria that the test plan and security assessment will consume. ## Quick Start Ask the agent to generate the non-functional requirements specification for the current project once strategic intake, functional spec, and experience design are signed.

Frequently Asked Questions about nonfunctional-spec

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

FAQPage Schema
How do I write non-functional requirements with measurable acceptance criteria?▼

Define each NFR with a target, threshold, and measurement method, such as page load under 2 seconds at the 95th percentile. This Skill generates a register template covering 8 categories with acceptance criteria tables and verification methods for each requirement.

What categories should a non-functional requirements document cover?▼

Cover performance, security, availability, usability, reliability, maintainability, compatibility, and compliance. The Skill's quality criteria flag coverage below 4 categories as a red flag and target at least 6.

What prerequisites are required before generating the NFR specification?▼

Three documents must be signed first: strategic-intake, functional-spec, and experience-design. The Skill blocks generation with a validation error if any prerequisite signature is missing.

Who approves a non-functional requirements specification?▼

The Solution Architect holds final approval authority for the NFR baseline. Security, QA, operations, and technical leads provide required reviews, while the CISO and QA Lead reviews do not gate the signature.

How do NFRs connect to test plans and security assessments?▼

Each NFR includes verification methods and traceability links to functional requirements and architecture components. Downstream skills like test-plan, security-assessment, and infra-spec consume the signed NFR document directly.