Jtbd interviews
Skill eltntawy/idea-discovery-playbook/skills/jtbd-interviews
16 agent skills to validate software ideas before you build — Mom Test interviews, JTBD, market research, pretotype tests, unit economics, and go/no-go scorecards. For Cursor, Claude Code & skills.sh.
npx -y skills add eltntawy/idea-discovery-playbook --skill jtbd-interviewsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Designs and synthesizes Jobs-to-be-Done switch interviews—hiring triggers, struggle timeline, alternatives, and job statements—for software ideas. Use for JTBD interviews, switch interviews, why customers buy, or switching behavior.
SKILL.md
2.6 KB, as published. Nobody here has run it
JTBD Interviews
Complements problem-discovery (Mom Test / problem pain). Use JTBD when the risk is why people switch or what progress they hire a solution for.
Best respondents: people who recently switched to or from a solution in the last ~90 days.
When to use
| Situation | Use |
|---|---|
| New idea, problem unclear | problem-discovery first |
| Positioning, category, messaging | This skill + positioning-wedge |
| Churn / why they left | Switch interview on departures |
Switch timeline (question flow)
- First thought — when did they first think they needed something new?
- Passive looking — what did they notice before acting?
- Trigger — what event pushed them to act?
- Active looking — what alternatives did they consider? Why rule each out?
- Hiring criteria — what had to be true to buy?
- Purchase moment — what tipped the decision?
- Consumption — what happened after? Ongoing struggles?
Core questions
- "Walk me through the last time you switched [category / tool]."
- "What were you trying to get done?"
- "What almost stopped you?"
- "What would you hire instead if this disappeared tomorrow?" (reveals true substitute)
Notes columns
| Column | Capture |
|---|---|
| Push | Pain with status quo |
| Pull | Attraction to new solution |
| Anxiety | Fear of switching |
| Habit | Inertia keeping old way |
Synthesis outputs
After 5+ interviews, produce:
- Job statements: "When [situation], I want to [motivation], so I can [outcome]."
- Forces diagram summary (push/pull vs anxiety/habit)
- Consideration set — what they compared (including non-obvious substitutes)
- Opportunity areas: "Help [persona] [job] without [struggle]."
- What we did not hear — expected jobs absent from data
Rules
- Past behavior only; no "would you buy our idea?"
- Substitutes include spreadsheets, agencies, manual process — not only SaaS logos
Output
Save to discovery/<topic-slug>/briefs/YYYY-MM-DD-<slug>-jtbd.md or a section in the latest brief.
Escalate positioning implications → positioning-wedge.