Translate Service Level Objectives into measurable non-functional requirements.
npx skills add https://github.com/wfukatsu/nexus-architect --skill define-nfr
Please help me install this Agent Skill. Skill: define-nfr Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/product/define-nfr Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill define-nfr
This Skill turns Service Level Objectives (SLOs) into actionable non-functional requirements (NFRs), providing a measurable and traceable set of goals for system design and implementation.
Generate non-functional requirements from SLOs using the command: /product:define-nfr
High-intent search queries and answers about installing and using this skill.
To translate SLOs into measurable non-functional requirements, you input SLA/SLO documents and bounded context information to generate specific NFRs like availability, latency, and throughput, ensuring alignment with business objectives.
Aligning system design with business objectives is achieved by converting Service Level Objectives into traceable non-functional requirements, providing a measurable set of goals that link every architectural decision back to business rationale.
Defining availability and latency objectives during product architecture design requires parsing existing SLO documents to extract and convert them into specific, measurable non-functional requirements tailored to your system's bounded context.
Yes, you can generate traceable NFRs from existing SLA documents by processing the SLOs within them. Each generated non-functional requirement is explicitly linked back to its originating SLO for clear business rationale.
To define non-functional requirements accurately, you need bounded context information alongside your SLO documents to ensure the generated NFRs operate correctly within your specific product architecture and business domain.
gtonicElicit and document Non-Functional Requirements using ISO 25010 and TOGAF.
rsmdtValidate implementations against documented specifications with structured compliance reporting.
mkalkereEvaluate and design system architecture and API design with ADRs.
infinith4Translate product ideas into structured requirements documentation with traceability matrix.
