What problem does it solve? Product teams often write user stories that focus on personas rather than the real situations and motivations driving user behavior, leading to features that miss the mark. This Skill applies the Jobs-to-be-Done framework to produce job stories that capture user context, motivation, and desired outcomes with testable acceptance criteria. ## Core Features & Use Cases - JTBD Story Generation: Produces stories in the "When [situation], I want to [motivation], so I can [outcome]" format, shifting focus from personas to context. - Acceptance Criteria: Generates 6-8 outcome-focused, measurable acceptance criteria per story, covering edge cases, integrations, and notifications. - Design Linking: Connects each story to Figma or Miro design files for traceability. - Use Case: A PM scoping a budget-tracking feature can input the product name, feature, and user context to receive a complete set of job stories ready for sprint planning. ## Quick Start Ask the agent to create job stories for your feature by providing the product name, the feature to break down, and the user context or design link.
