job-stories
This Claude Code skill generates job stories in the "When [situation], I want to [motivation], so I can [outcome]" format with detailed acceptance criteria. Use it when creating Jobs-to-be-Done style backlog items, writing user-centered requirements that emphasize context and motivations over roles, or breaking down features into stories focused on user situations and desired outcomes rather than traditional user roles.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/job-stories && cp -r /tmp/job-stories/pm-execution/skills/job-stories ~/.claude/skills/job-storiesSKILL.md
# Job Stories Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format. Generates stories with detailed acceptance criteria focused on user situations and outcomes. **Use when:** Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles. **Arguments:** - `$PRODUCT`: The product or system name - `$FEATURE`: The new feature to break into job stories - `$DESIGN`: Link to design files (Figma, Miro, etc.) - `$CONTEXT`: User situations or job scenarios ## Step-by-Step Process 1. **Identify user situations** that trigger the need 2. **Define motivations** underlying the user's behavior 3. **Clarify outcomes** the user wants to achieve 4. **Apply JTBD framework:** Focus on the job, not the role 5. **Create acceptance criteria** that validate the outcome is achieved 6. **Use observable, measurable language** 7. **Link to design mockups** or prototypes 8. **Output job stories** with detailed acceptance criteria ## Story Template **Title:** [Job outcome or result] **Description:** When [situation], I want to [motivation], so I can [outcome]. **Design:** [Link to design files] **Acceptance Criteria:** 1. [Situation is properly recognized] 2. [System enables the desired motivation] 3. [Progress or feedback is visible] 4. [Outcome is achieved efficiently] 5. [Edge cases are handled gracefully] 6. [Integration and notifications work] ## Example Job Story **Title:** Track Weekly Snack Spending **Description:** When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), so I can make sure I don't run out of money before the weekend (outcome). **Design:** [Figma link] **Acceptance Criteria:** 1. Display Spending Summary with 'Weekly Spending Overview' section 2. Real-Time Update when expense logged 3. Progress Indicator (progress bar showing 0-100% of weekly budget) 4. Remaining Budget Highlight in prominent color 5. Detailed Spending Log with breakdown by category 6. Notifications at 80% budget threshold 7. Weekend-Specific Reminder at 90% by Thursday evening 8. Easy Access and Navigation to detailed breakdown ## Output Deliverables - Complete set of job stories for the feature - Each story follows the 'When...I want...so I can' format - 6-8 acceptance criteria focused on outcomes - Stories emphasize user situations and motivations - Clear links to design and prototypes --- ### Further Reading - [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.