i2r-nfr-authoring-mode

Generate ISO/IEC 25010:2023 NFRs with fit criteria into a JSON file.

Updated May 28, 2026
One-click install
npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-nfr-authoring-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i2r-nfr-authoring-mode
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/i2r-nfr-authoring-mode
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-nfr-authoring-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires i2r.py, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating detailed, measurable Non-Functional Requirements (NFRs) for ISO/IEC 25010:2023, ensuring quality and compliance in software development.

Core Features & Use Cases

  • Systematic NFR Generation: Automatically derive NFRs from ISO/IEC 25010:2023 quality characteristics.
  • Fit Criterion Attachment: Attach specific, measurable fit criteria to each NFR.
  • Output Validation: Outputs a JSON file that can be validated against the NFR schema.

Quick Start

Run the i2r-nfr-authoring-mode skill to generate NFRs for your product.

Frequently Asked Questions about i2r-nfr-authoring-mode

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

FAQPage Schema
How do I generate measurable Non-Functional Requirements for ISO/IEC 25010:2023?

To generate measurable Non-Functional Requirements for ISO/IEC 25010:2023, you run this Skill to automatically derive NFRs from quality characteristics and output a validated JSON file containing specific fit criteria.

What is the best way to attach fit criteria to non-functional requirements?

The best way to attach fit criteria to non-functional requirements is to automate the derivation from ISO/IEC 25010:2023 characteristics, which systematically produces measurable constraints attached directly to each generated NFR.

Do I need a functional requirements JSON file to create NFRs?

Yes, you need to provide an input file named '04-functional.json' containing your functional requirements to successfully generate and validate corresponding non-functional requirements.

How does Python validate output for non-functional requirements?

Python validates output for non-functional requirements by running built-in scripts that check the generated JSON file against the required NFR schema, ensuring structural compliance and data integrity.

Why use ISO/IEC 25010:2023 for software quality requirements generation?

Using ISO/IEC 25010:2023 for software quality requirements generation ensures systematic coverage of standardized quality characteristics, automating compliance and producing detailed, measurable NFRs for your software development process.

Are there limitations when automating NFR authoring for ISO/IEC 25010:2023?

The primary limitation when automating NFR authoring is the strict dependency on the '04-functional.json' input file and Python scripts, meaning generation will fail if the prerequisite functional data is missing or malformed.