agentleFS
Adelie-SquadAdelie-Squad/solosquad/skills/interview-script/SKILL.md

interview-script

Skill25 starsChanged 8 days agoMITView on GitHub

Chief 가 사용자에게 보낼 user-interview script 생성. Mom Test 기반 — leading 질문 금지. 사용자가 실제 고객과 인터뷰 진행 후 transcript 업로드.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 7 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 7 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 7 projects that use this

  • +6 more from skytiger6724

The file

Files
SKILL.md

Interview Script Author Skill

PM 또는 chief 가 호출. 사용자(founder)가 직접 실제 고객과 인터뷰 진행할 때 사용할 script 생성. PM 이 직접 인터뷰하지 않는다.

입력

  • target segment 정의
  • 검증하려는 hypothesis (XYZ format)
  • 기존 customer 가설 (<org>/domain/customers.md)

Mom Test 원칙 (Rob Fitzpatrick)

  1. 사람들의 의견 묻지 마라. 그들의 삶을 물어라.
  2. 미래 가설 묻지 마라. 과거 행동을 물어라.
  3. 칭찬 받지 마라. 사실을 받아라.

→ "X 기능 좋아하실까요?" ❌ → "마지막으로 [pain] 을 겪었을 때 어떻게 해결하셨나요?" ✅

산출

# Interview Script — {{topic}}

## 목적
{{검증할 hypothesis 1줄}}

## 인터뷰 대상
- Segment: ...
- Recruit criteria: ...
- 최소 N=5

## 진행 (25-30분)

### Warm-up (3분)
- 자기소개
- 최근 어떻게 지내셨는지 (light)

### 과거 행동 탐색 (15분)
1. 가장 최근 [domain] 관련 작업이 언제였나요? 어떤 상황이었나요?
2. 그 작업에서 가장 답답했던 순간은?
3. 그 순간을 어떻게 처리하셨나요? 어떤 도구/방법을 썼나요?
4. (위 도구/방법에 만족 못 한 경우) 다른 시도 해보셨나요?
5. 이 작업에 보통 시간/돈을 얼마 쓰시나요?

### Constraint 탐색 (7분)
- 만약 [hypothetical solution] 이 있다면, 지금 쓰시는 [current solution] 을 *대체* 하시겠어요? 무엇이 *전환* 결정 요인일까요?
- (전환 안 한다면) 어떤 조건이면 전환하시겠어요?

### Wrap-up (3분)
- 우리가 안 물어본 질문 중 이 주제에 중요한 게 있나요?
- 비슷한 고민하시는 분 소개 가능하실까요?

## Scoring Rubric

각 응답을 다음 기준으로 채점:
- Demand evidence: 0-3 (0=interest, 3=actual demand with payment/workaround)
- Specificity: 0-3 (0=vague, 3=specific instance with date+context)
- Switching cost signal: 0-3

HARD GATE

- [ ] 모든 질문이 Mom Test 통과 (no leading, no hypothetical)
- [ ] 과거 행동 질문 ≥ 5
- [ ] scoring rubric 첨부
- [ ] minimum sample N=5 명시

Reference

  • Mom Test by Rob Fitzpatrick
  • phuryn/pm-skills/pm-product-discovery/interview-script
  • v1.1 PRD §9.1 (discovery)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.