025-quality-attribute-discovery

Featured

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

AI & Automation 427 stars 90 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 disco...

Details

Author
jabrena
Repository
jabrena/plinth
Created
1 years ago
Last Updated
today
Language
Java
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

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

427 Updated today
jabrena
Web & Frontend Featured

034-architecture-design-exploration

Use when a sanitized issue summary, requirement summary, or design brief needs technical design exploration before creating ADRs, specifications, or implementation plans. This skill inspects repository context, clarifies material ambiguity, compares feasible approaches and trade-offs, recommends a direction, obtains approval, and identifies ADR candidates. This should trigger for requests such as Explore a design; Compare implementation approaches; Recommend an architecture direction; Clarify technical options before planning. Part of Plinth Toolkit

427 Updated today
jabrena
AI & Automation Listed

product-discovery

Product discovery and prioritization framework. Use when planning features, validating assumptions (OST), prioritizing work (RICE), analyzing jobs-to-be-done (JTBD), or testing hypotheses before building. Triggers: "prioritize", "what to build", "RICE", "JTBD", "OST", "validate assumption", "opportunity sizing", "feature priority", "should we build", "discovery", «приоритизируй», «что строить»

0 Updated 3 weeks ago
akuroglo