Elicit and document Non-Functional Requirements using ISO 25010 and TOGAF.
npx skills add https://github.com/gtonic/ea-skills --skill nfr-checklist
Please help me install this Agent Skill. Skill: nfr-checklist Source: https://github.com/gtonic/ea-skills/tree/main/.skills/nfr-checklist Command: npx skills add https://github.com/gtonic/ea-skills --skill nfr-checklist
This Skill streamlines the often-overlooked but critical process of defining, documenting, and prioritizing Non-Functional Requirements (NFRs), ensuring that crucial quality attributes like performance, security, and reliability are addressed early in the architecture and development lifecycle.
Use the nfr-checklist skill to start gathering non-functional requirements for the new banking application.
High-intent search queries and answers about installing and using this skill.
To define non-functional requirements (NFRs), systematically elicit quality attributes via interactive dialog, document measurable scenarios, and prioritize them using MoSCoW and architecture relevance to output a structured NFR catalog. This ensures critical attributes like performance and security are addressed early in the lifecycle.
Mapping ISO 25010 quality attributes to architecture tactics involves defining quality attribute scenarios with clear stimuli and response measures, then deriving concrete architecture tactics while identifying trade-offs. This process translates standard quality categories directly into actionable architectural decisions.
Writing measurable quality attribute scenarios for SLA specification requires defining specific stimuli, response measures, and thresholds. This ensures service level agreements for attributes like availability and performance are quantifiable, such as specifying 99.95% uptime or P95 API response times under 200ms.
Yes, you can use TOGAF principles for NFR gathering by systematically eliciting and documenting requirements across 11 quality attributes. This facilitates architecture-driven requirement analysis by evaluating architecture relevance and generating implication reports for solution architecture planning.
Documenting non-functional requirements generates structured outputs including comprehensive NFR catalogs, summary tables, individual NFR cards, and architecture implication reports. These formats ensure quality attributes are clearly communicated and actionable for design and review processes.
igpastorAnalyze codebases and generate GitHub-ready requirements documents with acceptance criteria.
vamseeachantaTranslate system goals into SPARC-compliant architecture artifacts.
0xRayAIProvides tools for system design, architecture planning, and decision documentation.
jabrenaCreate Architectural Decision Records for non-functional requirements using the ISO/IEC 25010:2023 quality model.
