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
58
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/025-quality-attribute-discovery/SKILL.mdGuide 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?
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.
references/025-quality-attribute-discovery.md before applying Quality Attribute Discovery guidanceRead references/025-quality-attribute-discovery.md, then review the problem frame, root-cause findings, assumptions, and context map for evidence of quality pressure.
Identify candidate quality attributes grounded in that evidence, avoiding a generic unfiltered checklist.
Prioritize the candidate quality attributes by stakeholder impact and risk if unmet.
Stop at the prioritized discovery list; do not select an architecture approach or record an ADR here.
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.
For detailed guidance, examples, and constraints, see references/025-quality-attribute-discovery.md.
26b0e71
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.