Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/025-quality-attribute-discovery/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/025-quality-attribute-discovery/

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

Similar skills

All skills for Design →

From the same set123

The whole set →
813-regulations-iso-42001 813-regulations-iso-42001 reviews Java systems that use GenAI against ISO/IEC 42001 concerns and turns findings into engineering controls, evidence, and owner handoffs. CX Codex +1 165installs 812-regulations-eu-product-liability-directive 812-regulations-eu-product-liability-directive turns EU Product Liability Directive 2024/2853 checks into engineering artefacts: scope inventory, hazardous-scenario tests, update history and user warnings for Java and AI products. CX Codex +1 165installs 810-regulations-eu-mifid-ii 810-regulations-eu-mifid-ii reviews Java enterprise applications for MiFID II investment service controls and audit evidence prior to release. CX Codex +1 165installs 022-root-cause-analysis 022-root-cause-analysis — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that runs structured root cause analysis using Five Whys, Fishbone (Ishikawa), and Current Reality Tree. CX Codex +1 144installs 024-context-mapping 024-context-mapping is a Claude Code skill that maps existing systems, integrations, owners, and external dependencies before design when system boundaries are undefined. CX Codex +1 142installs 023-assumption-analysis 023-assumption-analysis is a skill that identifies and ranks assumptions and unknowns in a framed problem before design, then outlines validation checks. CX Codex +1 140installs 021-problem-framing 021-problem-framing structures problem statements, current and desired states, stakeholders, and success criteria before engineers jump into implementation. CX Codex +1 139installs 059-design-atdd 059-design-atdd is a Claude Code skill that checks whether an OpenSpec change’s goal, acceptance criteria, and implementation or verification tasks agree. It produces an evidence-backed report of gaps and mismatches. CX Codex +1 135installs

Project sponsors

Companies that keep this analytics open