jtbd

Jobs to Be Done — Megaskill

Product Brief → Research → Personas → Competitors → Landing Page → Ad Scripts

Current date: !date +"%B %d, %Y" Prior JTBD files in working dir: !ls jtbd-*.md 2>/dev/null && echo "⚠️ Found — offer to load relevant ones before starting" || echo "none"

---

Invocation

If $ARGUMENTS contains a MODE number (e.g. "MODE 3"), jump directly to that mode — run required-inputs check first. If $ARGUMENTS contains a product brief, start with MODE 0. Checkpoint after each mode before continuing. If $ARGUMENTS is empty, print the MODE GUIDE and ask which mode to run.

Chain Checkpoints (mandatory after every mode)

After each mode, show:

━━━ CHECKPOINT ━━━
MODE [N] complete.
💾 Export? [Y] Save to jtbd-[product-slug]-mode[N]-[YYYY-MM-DD].md  [N] Chat only
Continue to MODE [N+1] — [Name]? What you'll get: [one-line]

Default: export + proceed. Silence/"yes"/"continue" = export and go.

Export Protocol

Filename: jtbd-[product-slug]-mode[N]-[YYYY-MM-DD].md (slug = lowercase, spaces → hyphens). Contents: # JTBD [Mode Name] — [Product Name] · Date · Confidence (High/Medium/Low) · Inputs · full output · Generated by jobs-to-be-done-megaskill. Write to working directory.

Conversational Routing

If user describes their situation without invoking a mode explicitly:

• Product idea / brief → suggest MODE 0
• Has reviews, transcripts, tickets → suggest MODE 1
• Has research output, needs personas → suggest MODE 2
• Has job + persona, needs positioning → suggest MODE 2B
• Ready to write copy → suggest MODE 3
• Needs ad scripts → suggest MODE 4

Always confirm before proceeding.

---

MODE GUIDE

┌─────────────────────────────────────────────────────────────────────────────┐
│  WHAT DO YOU HAVE?                        → START HERE                      │
├─────────────────────────────────────────────────────────────────────────────┤
│  Only a product idea or one-liner brief   → MODE 0  Synthetic Research      │
│  Real interviews, transcripts, reviews    → MODE 1  Discovery & Analysis    │
│  JTBD research (from Mode 0 or 1)         → MODE 2  Persona Definition      │
│  A focus job + primary persona            → MODE 2B Competitor Analysis     │
│  Focus job + persona + competitive gap    → MODE 3  Landing Page Copy       │
│  Focus job + persona + outcome to lead    → MODE 4  Ad Scripts              │
└─────────────────────────────────────────────────────────────────────────────┘

• MODE 0 — Spawns 🔍 RESEARCHER for real market data, then synthesizes job performers, four forces, opportunity scores, interview guide. → commands/mode-0-research.md
• MODE 1 — Spawns parallel 🧪 ANALYST agents per qualitative source. → commands/mode-1-discovery.md
• MODE 2 — Builds 2–3 situation-based personas ranked by commercial value. → commands/mode-2-personas.md
• MODE 2B — Spawns 4 parallel 🕵️ SCOUT agents (one per competitor tier), builds differentiation matrix + positioning. → commands/mode-2b-competitors.md
• MODE 3 — Spawns 7 parallel ✍️ COPYWRITER agents (one per page section), assembles + consistency-checks. → commands/mode-3-landing-page.md
• MODE 4 — Spawns parallel 🎬 SCRIPTWRITER agents (one per platform), 3 angles each. → commands/mode-4-ad-scripts.md

---

Agent Roster

Agent	Role	Used in
🔍 RESEARCHER	Web search: market data, competitors, App Store reviews	MODE 0
🧪 ANALYST	Extracts JTBD signal from one qualitative source	MODE 1
🕵️ SCOUT	Researches one competitor tier	MODE 2B
✍️ COPYWRITER	Writes one landing page section	MODE 3
🎬 SCRIPTWRITER	Writes 3-angle scripts for one platform	MODE 4

---

The Four Forces of Progress

Canonical reference. Every mode, agent, and reference file cites the names below verbatim. Don't rename, expand, or redefine elsewhere.

Forces

Force	Definition	Direction
Push force	Frustration with current situation. Drives user from status quo.	toward change
Pull force	Attraction to specific better outcome. Draws user toward new solution.	toward change
Habit force	Inertia, sunk cost, "good enough". User's routine resisting disruption.	toward status quo
Anxiety force	Fear of switching cost, learning curve, social risk, wrong choice.	toward status quo

Progress equation

Push force + Pull force  >  Habit force + Anxiety force   ⇒  switch happens

Progress only when change-forces outweigh status-quo-forces. Map every customer signal to a force. Signal that can't map = noise.

Three job layers

Every real job has all three. Never just one.

• Functional — practical task ("send thoughtful birthday message")
• Emotional — feeling to gain or escape ("stop feeling like bad friend")
• Social — perception to project ("be seen as someone who remembers")

Anchor IDs (cite from reference files)

Reference files map work to a force → link to anchor below. Don't paraphrase definitions locally.

Anchor	Use in
#forces → Push force	Problem section · Pain hook · Pain angle · Tier 3/4 SCOUT findings
#forces → Pull force	Value Prop section · Outcome hook · Outcome angle · opportunity scoring
#forces → Habit force	How-It-Works section · Workarounds SCOUT · Do-Nothing SCOUT
#forces → Anxiety force	FAQ section · Social Proof testimonial C · switching-cost ANALYST signals
#progress-equation	Final CTA · Hero CTA framing · every persona card
#three-job-layers	Persona definition · ad angle selection · hook formula choice

Vocabulary rules (prevent drift)

• Always Push force — not Push, Push Force, push. Same for Pull / Habit / Anxiety.
• Equation always written Push force + Pull force > Habit force + Anxiety force. Never abbreviated P+P > H+A.
• Three layers always Functional / Emotional / Social in that order.
• Reference files map section → force in format <Force name> → <section element> (e.g., Push force → pain points).