跳到正文
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

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

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

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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日 更新

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日 更新

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日 更新

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日 更新

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日 更新

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 的全部技能

报告此技能的问题