What problem does it solve? Teams argue about features before agreeing on what progress the customer is actually trying to make, and discovery notes often collapse into feature lists that go stale with every roadmap change. This Skill runs a structured Jobs-to-be-Done exercise that separates the stable customer job from the churning solution. ## Core Features & Use Cases - Job statement and job story: Writes Ulwick's verb-object-clarifier main job plus a situational job story, then validates both with solution-swap and stability checks. - Full JTBD canvas: Captures functional, emotional, and social job dimensions, the four forces of progress (push, pull, habit, anxiety), pains and gains, and measurable desired outcome statements rated on importance and satisfaction. - Facilitated discovery loop: Asks up to four targeted questions with context-aware options, collapses to zero questions when transcripts or a proto-persona arrive upstream, and labels every claim as Fact, Inference, or Assumption. - Use Case: A product team scoping a self-service dispute flow pastes three support call transcripts; the Skill extracts the functional job and pains, identifies the missing anxiety column, asks one targeted question to fill it, and emits a JTBD.md canvas ready to feed a problem statement or opportunity solution tree. ## Quick Start Run the jobs-to-be-done skill to build a JTBD canvas for our target persona using these interview notes and tell me which assumptions still need validation.
