- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 025-quality-attribute-discovery -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/jabrena/plinth/tree/HEAD/skills/025-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?
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.
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 Qua
---name: 025-quality-attribute-discoverydescription: Use when a problem under exploration needs its quality attributes (non-functional requirements) identified and…---# skills/025-quality-attribute-discovery/SKILL.md개요
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
FAQ
게시자에게서 skills/025-quality-attribute-discovery/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/jabrena/plinth에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.