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; Create ADR for performance scalability or security requirements. Part of Plinth Toolkit

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/032-architecture-adr-non-functional-requirements/SKILL.md

Quality

Content

70%Weight 40%Scale 1-5

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

The content is a lean, well-structured overview that delegates detail to one real bundled reference and sequences the interactive workflow with explicit validation checkpoints. Its main weakness is actionability: concrete example discovery questions, an ADR template skeleton, or per-NFR-category prompts would let Claude execute without leaning entirely on the reference.

Suggestions

Inline a short ADR template skeleton (sections like Context, Decision, Quality Metrics, Success Criteria) so Claude can generate the document without opening the reference.

Add 1-2 example discovery questions per primary NFR category (e.g. performance, security) to make the consultative step concrete.

Add a feedback loop for when the user rejects the validation summary (e.g. revise assumptions and re-summarize) to satisfy the workflow-clarity recovery guidance.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, covering role, constraints, triggers, and a numbered workflow in ~50 lines without explaining well-known concepts like ADRs or ISO 25010; the 'When to use' and 'What is covered' lists mildly duplicate the frontmatter description.	4 / 5
Actionability	Guidance is concrete at the step level (run `date`, load the named reference path, ask one-two questions, wait for confirmation) but offers no example ADR skeleton, no example discovery questions per NFR category, and no template fields, so execution relies heavily on the bundled reference.	3 / 5
Workflow Clarity	The numbered Workflow (0-3) is clearly sequenced with explicit validation checkpoints ('Validate summary with user before proposing ADR', 'Wait for user to confirm proceed before generating the ADR'), but it lacks an error-recovery/feedback loop for cases where the summary is rejected or validation fails.	4 / 5
Progressive Disclosure	The body is a concise overview with a single well-signaled, one-level-deep reference (references/032-architecture-adr-non-functional-requirements.md) that exists in the bundle, keeping detail off the main file and navigation explicit.	5 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

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

The description clearly states both what the skill does and when to use it, with concrete trigger phrases tied to ADR/NFR authoring and the ISO 25010 quality model. It is specific and largely distinctive, with only minor gaps in trigger synonym coverage and a slight risk of overlap with generic architecture-documentation skills.

Dimension	Reasoning	Score
Specificity	Names the domain (ADR creation for non-functional requirements via ISO/IEC 25010:2023) and several concrete actions (document quality attributes, NFR decisions, security/performance/scalability architecture), but the actions overlap and lack breadth beyond the ADR framing.	4 / 5
Completeness	Explicitly answers both 'what' (facilitates conversational discovery to create ADRs for NFRs using ISO/IEC 25010:2023) and 'when' ('Use when... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would actually say ('Create ADR for Non-functional requirements', 'Document Non-functional requirements', 'Capture Non-functional requirements') with good coverage, though synonyms and the ADR acronym are not exhaustively varied.	4 / 5
Distinctiveness Conflict Risk	The ISO/IEC 25010:2023 NFR-ADR niche is fairly distinct and unlikely to trigger for unrelated skills, though 'document non-functional requirements' could mildly overlap with generic documentation or architecture skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/032-architecture-adr-non-functional-requirements/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.