dotnet-mcaf-nfr

Name: dotnet-mcaf-nfr
Availability: InStock
Author: postpartum-genushyacinthus29

Convert vague quality-attribute goals into measurable non-functional requirements with verification artifacts.

8|Updated Mar 29, 2026

Search Tags:#architecture #documentation #validation #trade-offs #nfr #quality-attributes

Ready to run

npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcaf-nfr-postpartum-genushyacinthus29

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-mcaf-nfr
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-mcaf-nfr
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-mcaf-nfr-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams capture and refine explicit quality attributes (such as accessibility, reliability, scalability, maintainability, performance, and compliance) when a feature or architecture change requires clear trade-offs.

Core Features & Use Cases

Proposes and documents concrete, testable non-functional requirements linked to feature docs, ADRs, and architecture decisions.
Guides verification and validation planning by mapping NFRs to measurable criteria, tests, and reviews.
Generates reusable artifacts and context to accelerate future work when evaluating architecture changes.

Quick Start

Run this skill on the nearest feature or architecture documentation to generate explicit NFRs and a verification plan.

Frequently Asked Questions about dotnet-mcaf-nfr

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

FAQPage Schema

How do I define measurable non-functional requirements for an architecture change?▼

Measurable non-functional requirements are generated by translating vague quality-attribute goals like scalability and reliability into explicit, testable criteria linked to feature documentation and ADRs. This produces verification artifacts for architecture reviews.

What is the best way to document quality attribute trade-offs for an ADR?▼

Documenting quality attribute trade-offs involves proposing concrete non-functional requirements mapped directly to measurable validation criteria and tests. This captures explicit architecture decisions regarding accessibility, performance, and maintainability.

How do I map NFRs to a verification and validation plan?▼

Mapping NFRs to a verification plan requires linking each defined quality attribute to specific tests and review processes. This generates reusable artifacts that accelerate evaluating architecture changes across design, development, and QA.

Can I use this to sync documentation with explicit NFRs?▼

Yes, you can sync documentation with explicit NFRs by running this process on existing feature or architecture docs. It generates explicit non-functional requirements, documentation links, and verification artifacts to align design, development, and QA.

When do I need to define explicit quality attributes for a feature change?▼

Defining explicit quality attributes is needed when a feature change requires clear trade-offs among accessibility, reliability, scalability, or compliance. Capturing these non-functional requirements ensures architecture refactors maintain measurable quality standards.