025-quality-attribute-discovery
FeaturedUse 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
Install
Quality Score: 92/100
Skill Content
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
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
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
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", «приоритизируй», «что строить»