What problem does it solve? Teams often write user stories around personas that carry no real information, producing vague requirements that fail to capture why a need exists. This Skill provides the Jobs-to-be-Done job-story format — "When [situation], I want [motivation], so [outcome]" — so product work is framed around the trigger and motivation that actually predict behavior. ## Core Features & Use Cases - Job-Story Format Guidance: Teaches the situation-motivation-outcome structure with concrete good and weak examples, plus the four forces (push, pull, anxiety, habit) behind a product switch. - Research Synthesis: Shows how to harvest job stories from interviews, tickets, and journey maps, and how to force-rank situations by frequency times intensity. - Job Story vs INVEST Distinction: Clarifies when to use a discovery-stage job story versus a delivery-ready INVEST user story, with a comparison table and anti-pattern list. - Use Case: After a round of user interviews, a product manager synthesizes raw quotes into ranked job stories, then feeds the top opportunities into an opportunity solution tree before writing INVEST stories for engineering. ## Quick Start Ask the agent to turn these interview notes about users struggling with manual data exports into prioritized JTBD job stories.
