skills.rest
moonzff
moonzffCOMMUNITY
Explore all skills by this author →
GitHub

job-stories

Generate JTBD job stories with acceptance criteria from product and feature inputs.

1|Updated May 6, 2026
Search Tags:#requirements#acceptance criteria#backlog#product planning#jtbd#user motivation#job stories
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill job-stories-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/moonzff/Codex_up/tree/main/skills/product-planning/job-stories
Command: npx skills add https://github.com/moonzff/Codex_up --skill job-stories-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing backlog items that focus on user roles instead of real situations often produces vague requirements. This Skill structures feature ideas into Jobs-to-be-Done job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format, each with measurable acceptance criteria. ## Core Features & Use Cases - JTBD Story Generation: Converts a product, feature, and context into job stories centered on user situations and motivations rather than personas. - Acceptance Criteria: Produces 6-8 observable, outcome-focused acceptance criteria per story, covering progress feedback, edge cases, and notifications. - Design Linking: Attaches Figma or Miro design references to each story for traceability. - Use Case: A product manager planning a budget-tracking feature can turn it into stories like tracking weekly spending, each with criteria such as real-time updates, progress indicators, and threshold notifications. ## Quick Start Ask the assistant to create job stories for your feature, providing the product name, the feature to break down, any design links, and the user situations or context.

Frequently Asked Questions about job-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a job story for a product feature?▼

Use the format 'When [situation], I want to [motivation], so I can [outcome]'. Identify the triggering situation, the underlying motivation, and the desired outcome, then add 6-8 acceptance criteria that verify the outcome is achieved.

What is the difference between job stories and user stories?▼

Job stories focus on the situation, motivation, and outcome rather than a user role or persona. This JTBD approach captures context and causality, making it better when user roles are diverse or poorly defined.

How many acceptance criteria should a job story have?▼

This workflow produces 6-8 acceptance criteria per story. They should be observable and measurable, covering situation recognition, progress feedback, outcome achievement, edge cases, and integrations or notifications.

Can job stories link to Figma design files?▼

Yes. Each job story includes a Design field for linking Figma, Miro, or other design references, keeping the story traceable to mockups and prototypes during development.

When should I use job stories instead of personas?▼

Use job stories when the same feature serves many roles or when context drives behavior more than identity. Personas are better when demographic or role-specific attributes materially change the requirement.

Related Skills

Explore More Product & Management Skills→
Lev-itLev-it

job-stories

Generate job stories with acceptance criteria from product and feature inputs.

Official
Basic
Omar-ObandoOmar-Obando
44

product-owner

Structure user stories and acceptance criteria for agile backlog refinement.

Community
Basic
bketelsenbketelsen
1

browser-journey-test

Simulate real user journeys in a live browser to validate acceptance criteria.

Community
Intermediate
tikazyqtikazyq
5

user-story-format

Validate User Stories against the As-I-Want-So structure and quality criteria.

Community
Intermediate