dotnet-mcaf-nfr

Define measurable non-functional requirements for architecture changes using MCAF quality-attribute guidance.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-mcaf-nfr-zhenpenglai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-mcaf-nfr
Source: https://github.com/zhenpengLai/myuseskill/tree/main/dotnet-mcaf-nfr
Command: npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-mcaf-nfr-zhenpenglai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often describe quality goals with vague words like "fast", "reliable", or "secure" that cannot be tested or verified. This Skill turns those vague goals into explicit, measurable non-functional requirements and links them to feature docs, ADRs, tests, and operational expectations. ## Core Features & Use Cases - NFR Definition Workflow: Guides you through selecting the quality attributes that materially affect a change and converting them into falsifiable requirements. - Targeted Reference Library: Loads only the specific reference file for the active attribute, covering accessibility, availability, capacity, compliance, data integrity, disaster recovery, internationalization, interoperability, maintainability, performance, portability, reliability, scalability, and usability. - Ralph Loop Iteration: Enforces a brainstorm-plan-execute-review cycle with a structured result format including status, actions taken, and verification evidence. - Use Case: When designing a new service, use this Skill to document explicit performance, reliability, and compliance expectations in an ADR so architecture, testing, and operations stay aligned. ## Quick Start Ask the assistant to make the non-functional requirements explicit for your current feature or architecture change, naming the quality attributes that matter most.

Frequently Asked Questions about dotnet-mcaf-nfr

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

FAQPage Schema
How do I write measurable non-functional requirements for a feature?▼

Identify the quality attributes that materially affect the change, then convert vague goals into explicit constraints or testable expectations. Each NFR should be measurable or at least falsifiable, and linked to feature docs, ADRs, and verification steps.

What quality attributes does MCAF NFR guidance cover?▼

The reference library covers accessibility, availability, capacity, compliance, data integrity, disaster recovery, internationalization, interoperability, maintainability, performance, portability, reliability, scalability, and usability. You load only the file matching the active attribute.

When should I document NFRs in an ADR?▼

Document NFRs in an ADR when quality attributes affect design decisions or rollout, such as reliability targets, performance thresholds, or compliance obligations. This keeps architecture, testing, and operations expectations aligned.

When should I not use an NFR definition workflow?▼

Skip it for generic architecture or feature writing with no quality-attribute decision at stake. It is designed for changes where explicit quality attributes and trade-offs need to be captured, not for routine documentation.

How do I turn vague words like fast or reliable into requirements?▼

Tie each word to a measurable threshold and workload, such as latency targets, concurrent user counts, or failure scenarios. Reliability work should be expressed through failure scenarios rather than uptime slogans.