Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/025-quality-attribute-discovery
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
Passed 14 of 22 test cases with the skill, and 9 of 22 without it.
and 8 more in the full report
8 fixed6 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are preparing to build an automated patient notification system for urgent lab results. Here is our problem background, context map, and initial assumptions regarding high volume spikes and HIPAA compliance requirements. Before our engineering team meets to make any technology selections or write ADRs, please analyze our context and provide a prioritized list of relevant non-functional requirements/quality attributes ranked by business impact and operational risk. Make sure to call out any areas where information is too vague to determine a priority.
| Checked | Without skill | With skill |
|---|---|---|
| Asks clarifying questions regarding missing details on volume spikes. | Passed | Passed |
| Avoids making architectural decisions. | Missed | Passed |
| Stops output at the prioritized quality attribute discovery list. | Missed | Passed |
The instructions your model reads when the skill loads.
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?
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.
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.