jtbd

What problem does it solve? Product teams often describe jobs-to-be-done inconsistently, making them impossible to compare, deduplicate, or trace through epics and stories. This Skill enforces one consistent job statement format and maps what serving the job requires, so epics inherit a solid foundation instead of invented demand. ## Core Features & Use Cases - Standardized Job Statements: Writes every job in the shape "When [situation], [person] wants to [progress], so they can [outcome]" with rules that keep it honest — real people, concrete situations, progress over features. - Requirements Mapping: Separates what must be true for the person (story candidates) from what must be true of the system (task candidates), plus explicit out-of-scope items that become epic non-goals. - Traceability to Problems: Requires every job to cite a problem-definition brief or discovery source, blocking invented demand. - Use Case: Before writing an epic about media offloading, use this Skill to define the job — "When the shoot is done and the cards are full, a videographer wants to get the day's footage somewhere safe, so they can stop worrying about losing work" — and map its requirements for the epic to cite. ## Quick Start Ask the assistant to define the job-to-be-done behind a problem you are exploring, and it will produce a consistent job statement with a requirements map ready for epic-builder to cite.