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

discovery-interview-prep

Generate user research interview scripts using Mom Test principles. Use this skill when: - You are preparing for user interviews or pilot observation sessions - You need a question bank organized by behavior, context, pain points, and workflow - You want interview guides that avoid leading questions and hypotheticals - You need per-persona interview guides - You are preparing for field visits or pilot debriefs

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.4 KB

SKILL.md(原文)

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

Discovery Interview Prep

Generate interview scripts grounded in Mom Test principles (Rob Fitzpatrick). Reads personas and current assumptions from specs, produces question banks and 1-page interview guides per persona type.

Workflow

  1. Research goal — Ask user: "What do you want to learn from these interviews?"
  2. Read personas from your persona files or user research directory
  3. Read assumptions — If a spec exists, read the Risks/Assumptions section for assumptions to validate
  4. Generate question bank organized by category
  5. Generate interview guide — 1-page per persona type
  6. Output — Print to conversation or write to file

Mom Test Rules

Core principles (Rob Fitzpatrick):

  • Ask about their life, not your idea
  • Ask about specifics in the past, not generics or hypotheticals
  • Talk less, listen more
  • Seek concrete facts, not compliments or opinions

Question Categories

Behavior — What they actually do

  • "Walk me through the last time you [relevant activity]..."
  • "What happened after [specific event]?"
  • "How often does [situation] come up?"
  • "Show me how you currently do [task]."

Context — Environment and constraints

  • "Where were you when you were doing this?"
  • "What else was going on around you?"
  • "What tools/devices were you using?"
  • "Who else was involved?"

Pain Points — Problems and frustrations

  • "What's the hardest part about [activity]?"
  • "Tell me about the last time that was frustrating..."
  • "What have you tried to solve this? What happened?"
  • "How much time/effort does this cost you?"

Workflow — Process and sequence

  • "What do you do first when you [start activity]?"
  • "After [step], what happens next?"
  • "Where does this process break down?"
  • "What workarounds have you developed?"

Questions to AVOID

These produce unreliable data:

  • "Would you use a feature that does X?" (hypothetical)
  • "Do you think X is a good idea?" (opinion, not behavior)
  • "Would you pay for X?" (hypothetical)
  • "How much would you pay?" (unreliable)
  • "Is [problem] important to you?" (leading)
  • Any question starting with "Would you..." or "Do you think..."
  • "On a scale of 1-10..." (no context, no actionable data)

Output Format

# Interview Guide — {Feature/Research Area}

**Research Goal:** {what we want to learn}
**Date:** {DD-MM-YYYY}
**Duration:** {suggested minutes per interview}

## Assumptions to Validate

| # | Assumption | Source | Question to Ask |
|---|-----------|--------|----------------|
| 1 | {from spec} | {spec section} | {Mom Test question} |

---

## Interview Script: {Persona Type}

### Opening (2 min)
- Introduce yourself, explain purpose
- "We're here to learn from you, not to test you"
- "There are no right or wrong answers"

### Warm-up (3 min)
- {2-3 easy context-setting questions}

### Core Questions (15-20 min)

#### Behavior
1. {question}
2. {question}
3. {question}

#### Pain Points
1. {question}
2. {question}
3. {question}

#### Workflow
1. {question}
2. {question}

### Wrap-up (2 min)
- "Is there anything I didn't ask about that you think is important?"
- "Who else should I talk to about this?"

---

## Questions to Avoid
{list of anti-patterns specific to this research area}

## Observer Notes Template

| Time | Observation | Category | Follow-up? |
|------|------------|----------|-----------|
| | | Behavior/Pain/Context/Workflow | Y/N |

Anti-Patterns

  • Don't write leading questions disguised as open ones
  • Don't ask hypotheticals — they produce unreliable data
  • Don't skip the warm-up — it builds rapport
  • Don't combine behavior and opinion questions in one

Quality Checklist

  • Every question is grounded in past behavior, not hypotheticals
  • Questions are open-ended, not yes/no
  • Each persona gets a tailored script
  • Assumptions to validate are linked to spec sections
  • Observer notes template is included
  • No leading questions remain

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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-skills202026年9月10日 更新

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-skills202026年9月10日 更新

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-skills202026年9月10日 更新

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-skills202026年9月10日 更新

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-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

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

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

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