from dotnet-skills331
Turn vague quality goals into explicit, testable non-functional requirements (accessibility, reliability, performance, scalability, maintainability, compliance)
This skill guides agents through capturing and refining non-functional requirements (NFRs) using the MCAF approach. It turns vague terms like "fast" or "secure" into measurable quality attributes, links them to architecture/ADRs, and produces concrete artifacts (docs, tests, CI config, or code changes) that enforce and validate those attributes.
Use this skill when a feature or architectural change requires explicit quality attributes, when documentation and tests are out of sync, or when teams use ambiguous language about reliability, performance, or security. Ideal for planning rollouts, drafting ADRs, and adding verification steps to CI.
Likely works with code-capable agents and assistants that can read repo files and modify code/docs (Codex, Copilot-style agents, Claude Code, Gemini CLI).
Pure instructional skill with no executable scripts. Provides a structured workflow (Ralph Loop) for turning vague quality goals into explicit, testable non-functional requirements. Well-organized with per-NFR reference files in a references/ directory. The SKILL.md is a detailed prompt template rather than an automated tool — it guides an agent through brainstorming, planning, and validating NFRs. Niche audience (MCAF/.NET teams).
The skill_md_body was null in the fetch result, likely due to the slug/path mismatch (dotnet-mcaf-nfr vs mcaf-nfr in the GitHub repo). Had to manually resolve the correct path. The skill is well-structured as a prompt template but lacks any automation — it's essentially a structured set of instructions for an agent to follow when defining NFRs.
