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. Part of the skills-for-java project
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with excellent completeness and distinctiveness. It clearly identifies its niche (ADRs for NFRs using a specific ISO standard) and provides explicit 'Use when' guidance with relevant trigger terms. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond 'facilitates conversational discovery'.
Suggestions
Expand the capabilities section with more concrete actions (e.g., 'generates ADR templates', 'maps requirements to ISO 25010 quality characteristics', 'produces measurable acceptance criteria')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ADRs, non-functional requirements, ISO/IEC 25010:2023) and describes the general action ('Facilitates conversational discovery to create'), but doesn't list multiple specific concrete actions like 'generate templates', 'validate against standards', or 'export documents'. | 2 / 3 |
Completeness | Clearly answers both what ('Facilitates conversational discovery to create ADRs for non-functional requirements using ISO/IEC 25010:2023') and when ('Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ADRs', 'quality attributes', 'NFR decisions', 'security', 'performance', 'scalability', 'architecture', 'design systems', 'measurable quality criteria'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: ADRs + non-functional requirements + ISO/IEC 25010:2023 quality model. The combination of these specific triggers makes it unlikely to conflict with general documentation or architecture skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates an interactive discovery process for NFR ADRs. The workflow is clear with explicit validation checkpoints, and the progressive disclosure is appropriate. The main weakness is that actionability relies heavily on the referenced file, with no inline examples of conversation patterns or sample outputs.
Suggestions
Add 1-2 example challenge-first opening questions to make the skill more immediately actionable without requiring reference file lookup
Include a brief example of what a validated summary looks like before ADR creation to clarify the checkpoint
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing only what Claude needs to know without explaining basic concepts. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear constraints and workflow steps, but lacks concrete examples of questions to ask, sample conversation flows, or example ADR output. The actual guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | Clear sequential workflow from challenge-first opening through validation to ADR creation. Explicit checkpoints ('validate summary with user', 'wait for user to confirm') provide good feedback loops for this interactive process. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections. Appropriately references detailed guidance in a single external file with clear signaling. Content is appropriately split between overview and reference. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
7772a1b
- 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.