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

product-thinking

Run structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief

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

qa-aman/claude-skills
설치 방법 보기

포함된 파일(2)

  • SKILL.md3.7 KB
  • references/11-star-framework.md2.4 KB

SKILL.md(원문)

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

Product Thinking

Interactive skill that builds product thinking through 5 structured exercises. Outputs a Product Thinking Brief that feeds into spec writing.

This is the "thinking before writing" layer — run this BEFORE drafting any spec.

Workflow

  1. Gather context — Ask user for: feature idea, target users, motivation
  2. Read source files — Personas, product context, feedback, competitors (only relevant files)
  3. Run 5 exercises — Present findings, get user validation at each step
  4. Write brief — Output to file or print

The 5 Exercises

Exercise 1: Problem Statement

Answer four questions with evidence:

DimensionWhat to Answer
WhoSpecific persona (not generic "users")
EvidenceCite feedback, pilot data, research — not assertions
Impact if unsolvedQuantify or describe the cost of inaction
Why unsolvedTechnical, behavioral, or systemic barriers

Exercise 2: 11-Star Experience Ladder

For THIS specific feature, describe star levels 1, 3, 5, 7, 9, 11. Identify realistic target for current phase.

See references/11-star-framework.md for the full framework.

Output: Table + "Target Star Level: {N} — {rationale}"

Exercise 3: Positioning Statement

Geoffrey Moore's framework:

"For [target users], who [need/pain], [product/feature] is a [category] that [key benefit]. Unlike [competitors], it [differentiator]."

  • Pull target users from persona files
  • Include "current manual process" as a competitor if no direct competitor exists

Exercise 4: Product Principles

Define 3-5 guardrails for this feature:

PrincipleDescriptionFollowing ItViolating It
e.g., "Offline-first"Works without internetAuto-sync when connectedRequire internet for core flow

Exercise 5: Success Vision

Answer in 2-3 paragraph narrative:

  • Done well in 6 months — Describe the ideal outcome
  • Behavior change expected — How will users act differently?
  • Kill criteria — What evidence would make us kill this feature?

Output Format

# Product Thinking Brief — {Feature Name}

**Date:** {DD-MM-YYYY}
**Author:** [your name]

## 1. Problem Statement
[table from Exercise 1]

## 2. 11-Star Experience
[table from Exercise 2]
**Target Star Level:** {N} — {rationale}

## 3. Positioning Statement
> For [target users], who [need/pain]...

## 4. Product Principles
[table from Exercise 4]

## 5. Success Vision
[narrative from Exercise 5]

## Next Step
Use this brief as input for your PRD/spec writing skill.

Anti-Patterns

  • Don't skip the problem statement — it's the foundation
  • Don't set target star level above 7 for early phases — be realistic
  • Don't write generic principles — they should be specific enough to be falsifiable
  • Don't skip kill criteria — knowing when to stop is as important as knowing what to build

Quality Checklist

  • Problem statement has evidence, not just assertions
  • 11-star ladder is specific to THIS feature, not generic
  • Positioning statement names a real competitor or current process
  • Principles are falsifiable (you can tell when they're violated)
  • Kill criteria are defined

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

11-star-framework

무료

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

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

qa-aman/claude-skills212026년 10월 19일 업데이트

ab-copy-writer

무료

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

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

qa-aman/claude-skills212026년 10월 19일 업데이트

ab-test-design

무료

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

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

qa-aman/claude-skills212026년 10월 19일 업데이트

acceptance-criteria-writer

무료

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

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

qa-aman/claude-skills212026년 10월 19일 업데이트

account-plan

무료

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

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

qa-aman/claude-skills212026년 10월 19일 업데이트

ad-campaign-writer

무료

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

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

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고