What problem does it solve? Role-based user stories often miss the context and trigger behind a requirement, producing shallow specifications. This Skill structures requirements as job stories that capture the situation, motivation, and desired outcome so teams understand why a feature matters. ## Core Features & Use Cases - Job Story Format: Enforces the "When [situation/trigger], I want to [motivation/action], so I can [observable outcome]" structure. - Acceptance Criteria Seeds: Generates Given/When/Then criteria covering permissions, empty states, invalid data, conflicts, and failures. - Use Case: During requirements gathering for a notification feature, write "When a payment fails, I want to receive an alert, so I can retry before the order is cancelled" instead of a generic user story. ## Quick Start Rewrite my role-based user stories for the checkout flow as job stories with acceptance criteria.