ワンクリックでManusで任意のスキルを実行

$pwd:

032-architecture-adr-non-functional-requirements

Name: 032 Architecture Adr Non Functional Requirements
Author: jabrena

// Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project

Manusで実行

$ git log --oneline --stat

stars:0

forks:2

updated:2026年3月19日 20:26

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	032-architecture-adr-non-functional-requirements
description	Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

Create ADRs for Non-Functional Requirements

Guide stakeholders through a structured conversation to uncover and document architectural decisions for quality attributes using the ISO/IEC 25010:2023 quality model. This is an interactive SKILL. The ADR documents the outcome of the conversation, not the conversation itself. Act as an architecture consultant: challenge-first, consultative, adaptive.

What is covered in this Skill?

Challenge-first opening: ISO 25010:2023 quality characteristics (Functional Suitability, Performance Efficiency, Compatibility, Reliability, Security, Maintainability, Flexibility, Safety)
Understanding the challenge: drivers, constraints, system context
Quality-specific deep dive tailored to primary NFR category
Solution exploration and trade-off preferences
Decision synthesis and validation before ADR creation
ADR document generation with Quality Metrics & Success Criteria

Constraints

Use challenge-first, consultative discovery—ask 1-2 questions at a time, build on answers, tailor to NFR category. Only create ADR after thorough conversation and user confirmation.

MANDATORY: Run date before starting to get accurate timestamps for the ADR
MUST: Read the reference template fresh—do not use cached questions
MUST: Start with challenge-first opening (ISO 25010:2023 quality characteristics)
MUST: Ask one or two questions at a time; never all at once
MUST: Validate summary with user ("Does this accurately capture your quality needs?") before proposing ADR creation
MUST: Wait for user to confirm "proceed" before generating the ADR

When to use this skill

Document quality attributes
Create ADR for NFR
Non-functional requirements ADR
Security performance scalability architecture

Reference

For detailed guidance, examples, and constraints, see references/032-architecture-adr-non-functional-requirements.md.

related-skills.json

同じリポジトリ

014-agile-create-user-story.md

from "jabrena/cursor-rules-examples"

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. Part of the skills-for-java project

2026-03-190

020-planning-enhance-ai-plan-mode.md

from "jabrena/cursor-rules-examples"

Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. Part of the skills-for-java project

2026-03-190

030-architecture-adr-general.md

from "jabrena/cursor-rules-examples"

Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. Part of the skills-for-java project

2026-03-190

031-architecture-adr-functional-requirements.md

from "jabrena/cursor-rules-examples"

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. Part of the skills-for-java project

2026-03-190

033-architecture-diagrams.md

from "jabrena/cursor-rules-examples"

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, and ER (Entity Relationship) diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. Part of the skills-for-java project

2026-03-190

110-java-maven-best-practices.md

from "jabrena/cursor-rules-examples"

Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. Part of the skills-for-java project

2026-03-190

package.json

"author": "jabrena"

"repository": "jabrena/cursor-rules-examples"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

name	032-architecture-adr-non-functional-requirements
description	Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

Create ADRs for Non-Functional Requirements

What is covered in this Skill?

Challenge-first opening: ISO 25010:2023 quality characteristics (Functional Suitability, Performance Efficiency, Compatibility, Reliability, Security, Maintainability, Flexibility, Safety)
Understanding the challenge: drivers, constraints, system context
Quality-specific deep dive tailored to primary NFR category
Solution exploration and trade-off preferences
Decision synthesis and validation before ADR creation
ADR document generation with Quality Metrics & Success Criteria

Constraints

Use challenge-first, consultative discovery—ask 1-2 questions at a time, build on answers, tailor to NFR category. Only create ADR after thorough conversation and user confirmation.

MANDATORY: Run date before starting to get accurate timestamps for the ADR
MUST: Read the reference template fresh—do not use cached questions
MUST: Start with challenge-first opening (ISO 25010:2023 quality characteristics)
MUST: Ask one or two questions at a time; never all at once
MUST: Validate summary with user ("Does this accurately capture your quality needs?") before proposing ADR creation
MUST: Wait for user to confirm "proceed" before generating the ADR

When to use this skill

Document quality attributes
Create ADR for NFR
Non-functional requirements ADR
Security performance scalability architecture

Reference

For detailed guidance, examples, and constraints, see references/032-architecture-adr-non-functional-requirements.md.

032-architecture-adr-non-functional-requirements

Create ADRs for Non-Functional Requirements

Constraints

When to use this skill

Reference

このリポジトリの他の Skills

このリポジトリの他の Skills

Create ADRs for Non-Functional Requirements

Constraints

When to use this skill

Reference