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

tradeoff-analysis

Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.

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

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.6 KB
  • references/example.md2.0 KB

SKILL.md(원문)

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

Tradeoff Analysis

Choose among a small set of real options with the criteria, weights and evidence in plain view. A weighted decision matrix with a sensitivity check and a reversibility check.

When to use

  • Picking a library, vendor, architecture, plan, hire, design or build-vs-buy.
  • "A or B?", "compare these", "which should we pick", "is it worth it".
  • A decision the user must defend to others.

Skip: generating options from scratch (explore first, then come here), reviewing one plan for flaws, or ranking a long backlog.

Before you start

  1. State in one block: Decision (one sentence), Deadline or cost of delay, and Pass (Options, Must-haves, Criteria, Score, Sensitivity, Reversibility, Recommendation).
  2. Gather first. Read docs, benchmarks, pricing, the codebase and constraints before scoring. Every score needs a one-line basis; unsupported scores are marked [ESTIMATED]. Ask up to 3 questions only for goals and constraints tools cannot answer.
  3. Light path. Small ask: 2-3 options, 3 criteria, one-line reasons, a one-sentence sensitivity check.

Steps

1. Options

2-5 genuinely different options, including do nothing or keep current when it is real.

2. Must-haves

Hard constraints (budget cap, compliance, deadline). An option that fails one is out; do not score it.

3. Criteria and weights

3-7 criteria that reflect the goal and do not overlap (avoid counting the same thing twice, such as "speed" and "performance"). Give weights that sum to 100 and say why the top weight is highest.

4. Score

Rate each option per criterion from 1 (poor) to 5 (strong), with a short basis.

Criterion (weight)Option AOption B
... (40)4 - basis3 - basis
Weighted total

5. Sensitivity

Change the largest weight by about 10 points, or the least certain score by one. Does the winner change? Name the one criterion or score that flips the result.

6. Reversibility

How costly is it to undo this choice (switching cost, data lock-in, contract length, time)? Easy to reverse: decide faster and favor learning. Hard to reverse: spend more effort on evidence.

7. Recommendation

The pick, the main reason, the main cost you accept, and what would change the pick. For money or time tradeoffs, add a compact cost-benefit line: expected benefit range minus cost range, with the unit and period.

Pitfalls

  • False precision: a 3.8 vs 3.6 gap is a tie. Say so and decide on sensitivity and reversibility.
  • Weights chosen after seeing the scores. Set them before scoring.
  • Criteria that restate the favorite option ("uses our preferred language").
  • Scores from impressions with no basis. Mark them [ESTIMATED].
  • Ignoring the cost of changing course later.

Worked example: references/example.md.

Checklist

  • Decision and options stated; do-nothing considered
  • Must-haves screened before scoring
  • Criteria are independent; weights set with a reason
  • Every score has a basis or [ESTIMATED]
  • Sensitivity names what flips the result
  • Reversibility assessed
  • Recommendation names the accepted cost and what would change it

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for Fermi estimation, or when a rough number is needed fast: "roughly how many...", "ballpark the cost", "estimate capacity or market size", "is this even feasible?". Decomposes, uses ranges and sanity-checks. Skip when exact data is available or a precise calculation is wanted.

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

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

ysskrishna의 스킬 모두 보기

이 스킬의 문제 신고