본문으로 건너뛰기
cccskills
무료GitHub에 공개

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.7 KB
  • references/025-quality-attribute-discovery.md6.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 discovery list without selecting or recording an architecture decision
  • MUST NOT record an architectural decision, ADR, or design direction as part of this skill's output
  • MUST NOT invent a quality attribute or priority when the available content is vague or ambiguous; flag the gap for a clarifying question instead

When to use this skill

  • Discover the quality attributes for this problem
  • Identify non-functional requirements before design begins
  • Prioritize candidate quality attributes for this issue
  • Apply quality attribute discovery before architecture decisions
  • Draft the Quality Attribute Discovery section of a Functional Specification

Workflow

  1. Read the Reference

Read references/025-quality-attribute-discovery.md, then review the problem frame, root-cause findings, assumptions, and context map for evidence of quality pressure.

  1. Identify Candidate Quality Attributes

Identify candidate quality attributes grounded in that evidence, avoiding a generic unfiltered checklist.

  1. Prioritize by Impact and Risk

Prioritize the candidate quality attributes by stakeholder impact and risk if unmet.

  1. Stop Before Architecture Decisions

Stop at the prioritized discovery list; do not select an architecture approach or record an ADR here.

  1. Report the Discovery List

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.

Reference

For detailed guidance, examples, and constraints, see references/025-quality-attribute-discovery.md.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 21일 업데이트

jabrena의 스킬 모두 보기

이 스킬의 문제 신고