025-quality-attribute-discovery — Claude Code skill: requirements
The 025-quality-attribute-discovery skill finds and ranks a solution’s quality attributes before architecture work begins. It ties each candidate to evidence from the problem and its context.
Apache-2.0 143 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a claude-codeWhat 025-quality-attribute-discovery does
The skill considers qualities such as performance, security, availability, and maintainability. It draws on the problem frame, root causes, assumptions, and context map, then ranks candidates by stakeholder impact and the risk of leaving them unmet. That keeps the result tied to the problem rather than an unfiltered checklist.
Read references/025-quality-attribute-discovery.md before using the guidance. The deliverable is a prioritized discovery list; the skill does not choose a design direction or create an ADR. When the available evidence is unclear, it flags a question for clarification instead of assigning a quality or priority. If you need an architecture decision, this skill stops short of that work.
What it helps with
- identify non-functional requirements before design work
- ground system qualities in problem evidence and context
- rank candidate requirements by impact and risk
- draft the Quality Attribute Discovery section of a Functional Specification
Example prompts for the agent
- Identify this problem’s quality attributes and rank them by priority.
- Find the non-functional requirements for this issue before design begins.
- Draft the Quality Attribute Discovery section for the Functional Specification and flag open questions.
How to install 025-quality-attribute-discovery
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a claude-code2Manually: put the files in place
~/.claude/skills/025-quality-attribute-discovery/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/025-quality-attribute-discovery/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a codex2Manually: put the files in place
.agents/skills/025-quality-attribute-discovery/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a cursor2Manually: put the files in place
.cursor/skills/025-quality-attribute-discovery/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/025-quality-attribute-discovery2Manually: put the files in place
.github/skills/025-quality-attribute-discovery/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/025-quality-attribute-discoveryManually: put the files in place
.devin/skills/025-quality-attribute-discovery/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 025-quality-attribute-discovery
How do I install 025-quality-attribute-discovery in Claude Code?
Run npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a claude-code. The skill file is at ~/.claude/skills/025-quality-attribute-discovery/SKILL.md.
What does 025-quality-attribute-discovery do?
It identifies candidate quality attributes and prioritizes them by stakeholder impact and risk. It stops before selecting an architecture or recording an ADR.
What happens when the evidence is ambiguous?
The skill flags the gap for clarification instead of inventing a quality attribute or assigning it a priority.
Source text
SKILL.md · Apache-2.0
--- name: 025-quality-attribute-discovery description: Use when a problem under exploration needs its quality attributes (non-functional requirements) identified and prioritized before architecture and design begin. This should trigger when an issue's Quality Attribute Discovery point of view needs evaluation, or when a maintainer directly asks to discover and prioritize candidate quality attributes for a problem, before any ADR or design work starts. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Quality Attribute Discovery Guide identification and prioritization of the quality attributes a future solution must satisfy, before architecture and design decisions begin. **This is an interactive SKILL**. **What is covered in this Skill?** - Identifying candidate quality attributes (for example performance, security, availability, maintainability, scalability, usability, observability) relevant to the problem - Grounding each candidate in evidence from the problem frame, root causes, assumptions, and context map, not a generic checklist - Prioritizing candidate quality attributes by stakeholder impact and risk - Stopping at a prioritized discovery list rather than selecting or recording an architectural decision - Explicitly not producing ADRs or an architecture direction itself ## Constraints Discover and prioritize candidate quality attributes as input to later architecture work; do not make or record the architecture decision here. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly. - **MUST** read `references/025-quality-attribute-discovery.md` before applying Quality Attribute Discovery guidance - **MUST** ground each candidate quality attribute in evidence from the problem frame, root causes, assumptions, or context map - **MUST** prioritize candidate quality attributes by stakeholder impact and risk, not list them unordered - **MUST** stop at a prioritized discovery list without selecting or recording an architecture decision - **MUST NOT** record an architectural decision, ADR, or design direction as part of this skill's output - **MUST NOT** invent a quality attribute or priority when the available content is vague or ambiguous; flag the gap for a clarifying question instead ## When to use this skill - Discover the quality attributes for this problem - Identify non-functional requirements before design begins - Prioritize candidate quality attributes for this issue - Apply quality attribute discovery before architecture decisions - Draft the Quality Attribute Discovery section of a Functional Specification ## Workflow 1. **Read the Reference** Read `references/025-quality-attribute-discovery.md`, then review the problem frame, root-cause findings, assumptions, and context map for evidence of quality pressure. 2. **Identify Candidate Quality Attributes** Identify candidate quality attributes grounded in that evidence, avoiding a generic unfiltered checklist. 3. **Prioritize by Impact and Risk** Prioritize the candidate quality attributes by stakeholder impact and risk if unmet. 4. **Stop Before Architecture Decisions** Stop at the prioritized discovery list; do not select an architecture approach or record an ADR here. 5. **Report the Discovery List** Report the prioritized quality attributes, stating explicitly that the output stops at this discovery list and does not select or record an architecture decision; flag any item left open pending a clarifying answer. ## Reference For detailed guidance, examples, and constraints, see [references/025-quality-attribute-discovery.md](references/025-quality-attribute-discovery.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth