本文へ移動
cccskills
無料GitHub で公開

product-discovery

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md3.2 KB
  • references/discovery-frameworks.md1.8 KB
  • scripts/assumption_mapper.py4.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Product Discovery

Run structured discovery to identify high-value opportunities and de-risk product bets.

When To Use

Use this skill for:

  • Opportunity Solution Tree facilitation
  • Assumption mapping and test planning
  • Problem validation interviews and evidence synthesis
  • Solution validation with prototypes/experiments
  • Discovery sprint planning and outputs

Core Discovery Workflow

  1. Define desired outcome
  • Set one measurable outcome to improve.
  • Establish baseline and target horizon.
  1. Build Opportunity Solution Tree (OST)
  • Outcome -> opportunities -> solution ideas -> experiments
  • Keep opportunities grounded in user evidence, not internal opinions.
  1. Map assumptions
  • Identify desirability, viability, feasibility, and usability assumptions.
  • Score assumptions by risk and certainty.

Use:

python3 scripts/assumption_mapper.py assumptions.csv
  1. Validate the problem
  • Conduct interviews and behavior analysis.
  • Confirm frequency, severity, and willingness to solve.
  • Reject weak opportunities early.
  1. Validate the solution
  • Prototype before building.
  • Run concept, usability, and value tests.
  • Measure behavior, not only stated preference.
  1. Plan discovery sprint
  • 1-2 week cycle with explicit hypotheses
  • Daily evidence reviews
  • End with decision: proceed, pivot, or stop

Opportunity Solution Tree (Teresa Torres)

Structure:

  • Outcome: metric you want to move
  • Opportunities: unmet customer needs/pains
  • Solutions: candidate interventions
  • Experiments: fastest learning actions

Quality checks:

  • At least 3 distinct opportunities before converging.
  • At least 2 experiments per top opportunity.
  • Tie every branch to evidence source.

Assumption Mapping

Assumption categories:

  • Desirability: users want this
  • Viability: business value exists
  • Feasibility: team can build/operate it
  • Usability: users can successfully use it

Prioritization rule:

  • High risk + low certainty assumptions are tested first.

Problem Validation Techniques

  • Problem interviews focused on current behavior
  • Journey friction mapping
  • Support ticket and sales-call synthesis
  • Behavioral analytics triangulation

Evidence threshold examples:

  • Same pain repeated across multiple target users
  • Observable workaround behavior
  • Measurable cost of current pain

Solution Validation Techniques

  • Concept tests (value proposition comprehension)
  • Prototype usability tests (task success/time-to-complete)
  • Fake door or concierge tests (demand signal)
  • Limited beta cohorts (retention/activation signals)

Discovery Sprint Planning

Suggested 10-day structure:

  • Day 1-2: Outcome + opportunity framing
  • Day 3-4: Assumption mapping + test design
  • Day 5-7: Problem and solution tests
  • Day 8-9: Evidence synthesis + decision options
  • Day 10: Stakeholder decision review

Tooling

scripts/assumption_mapper.py

CLI utility that:

  • reads assumptions from CSV or inline input
  • scores risk/certainty priority
  • emits prioritized test plan with suggested test types

See references/discovery-frameworks.md for framework details.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

aeo

無料

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

alirezarezvani のスキルをすべて見る

このスキルの問題を報告する