What problem does it solve?
Product teams often struggle to translate feature ideas and designs into outcome-focused, testable backlog items. This Skill standardizes the conversion of product context into clear "When [situation], I want to [motivation], so I can [outcome]" job stories with measurable acceptance criteria so teams can prioritize, build, and validate with confidence.
Core Features & Use Cases
- Structured JTBD Formatting: Produce job stories using the canonical "When / I want / so I can" pattern that emphasize situations and outcomes rather than roles.
- Measurable Acceptance Criteria: Generate 6-8 acceptance criteria per story using observable, testable language and include edge cases and integration points.
- Design & Prototype Integration: Link stories to design files or prototypes (Figma, Miro) and surface relevant UI or interaction notes.
- Use Cases: Convert product specs into backlog-ready JTBD items, prepare discovery artifacts for testing, and create user-centered acceptance criteria for engineering and QA.
Quick Start
Create 6 job stories for the "Checkout Redesign" feature with acceptance criteria and include a link to the Figma prototype.