CtrlK
BlogDocsLog inGet started
Tessl Logo

032-architecture-adr-non-functional-requirements

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. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable overview with clear sequencing and validation checkpoints and proper one-level-deep progressive disclosure. The main weakness is redundancy across the When-to-use, Constraints, and Workflow sections.

Suggestions

Remove the 'When to use this skill' section or replace it with a pointer, since its trigger phrases duplicate the frontmatter description verbatim.

Consolidate the 'Constraints' and 'Workflow' step constraints — the MUST items are restated in both sections; keep them once near the workflow steps they govern.

Trim the 'What is covered in this Skill?' bullet list, which largely restates the Workflow steps; let the workflow itself convey the coverage.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the 'When to use this skill' section duplicates the frontmatter trigger phrases and the Constraints, 'What is covered', and Workflow sections overlap, so it could be tightened.

2 / 3

Actionability

Provides concrete, executable guidance for an instruction skill: the `date` shell command, an explicit reference file path to load, and exact validation phrases ('Does this accurately capture your quality needs?').

3 / 3

Workflow Clarity

Steps 0–3 are clearly sequenced with explicit validation checkpoints — validate the summary with the user before proposing ADR creation and wait for explicit confirmation before generating the ADR.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that points to a single, real, one-level-deep reference file (references/032-architecture-adr-non-functional-requirements.md) via a clearly signaled link.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when to invoke it, with natural trigger terms and a distinct niche. No fluff or over-claims.

DimensionReasoningScore

Specificity

Names the domain (ADRs for non-functional requirements via ISO/IEC 25010:2023) and lists multiple concrete actions such as documenting quality attributes, NFR decisions, and security/performance/scalability architecture.

3 / 3

Completeness

Explicitly answers both 'what' ('Facilitates conversational discovery to create ADRs...') and 'when' via an explicit 'Use when the user wants to...' clause with concrete trigger examples.

3 / 3

Trigger Term Quality

Includes natural trigger phrasings users would actually say — 'Create ADR for Non-functional requirements', 'Document...', 'Capture...', 'Generate...' — alongside 'security/performance/scalability architecture'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (ADRs for NFRs using the ISO/IEC 25010:2023 quality model) with distinct triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.