AutoGineer
Generated banner for Job Stories
Generated logo for Job Stories

Job Stories

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill assists product managers and teams in drafting job stories based on the Jobs-to-be-Done (JTBD) framework. By focusing on user situations, motivations, and desired outcomes rather than specific user roles, it helps teams create more context-aware backlog items. The skill produces a standardized format including a narrative description and a comprehensive list of acceptance criteria to ensure features meet user needs effectively.

What it does

  • Formats user requirements into the 'When, I want, so I can' structure.
  • Generates detailed acceptance criteria for each job story.
  • Integrates design references into the story documentation.
  • Ensures acceptance criteria cover edge cases and system feedback.
  • Focuses on measurable outcomes rather than role-based definitions.

When to use it

  • When defining new features for a product backlog.
  • When shifting focus from user personas to user situations.
  • When you need to clarify the 'why' behind a specific user behavior.
  • When preparing documentation for development teams to ensure outcome alignment.

Advantages

  • Promotes a deeper understanding of user motivations.
  • Standardizes the format of backlog items across the team.
  • Ensures acceptance criteria are outcome-oriented and measurable.
  • Helps bridge the gap between design mockups and functional requirements.

Usage examples

“Create job stories for a new 'Dark Mode' feature in our mobile app.”
The agent will generate a set of job stories using the JTBD format, detailing scenarios where users need to adjust visual settings, accompanied by specific acceptance criteria for UI transitions and system persistence.
“Write a job story for a user trying to export their monthly report.”
The agent will produce a story titled 'Export Monthly Report' with the description 'When I am reviewing my monthly performance, I want to export my data to a PDF, so I can share it with my manager,' followed by 6-8 specific acceptance criteria.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/phuryn/job-stories/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip job-stories.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "job-stories", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/job-stories · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download job-stories.zip