job-stories

Generate JTBD job stories with measurable acceptance criteria from product context.

5|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tarunccet/pm-skills --skill job-stories-tarunccet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/tarunccet/pm-skills/tree/main/pm-execution/skills/job-stories
Command: npx skills add https://github.com/tarunccet/pm-skills --skill job-stories-tarunccet

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about job-stories

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

FAQPage Schema
How do I convert feature specs into job stories with acceptance criteria?

To convert feature specs into job stories, this Skill transforms product context into the canonical "When [situation], I want to [motivation], so I can [outcome]" JTBD format and generates 6-8 measurable acceptance criteria with observable success conditions for each backlog item.

What is the best way to write JTBD user stories from discovery notes?

The best way to write JTBD user stories from discovery notes is applying the "When / I want / so I can" pattern to emphasize situations and outcomes, which this Skill uses to produce standardized, testable backlog items ready for engineering and QA validation.

Can I link design prototypes to generated job stories and acceptance criteria?

Yes, the generated job stories include integration points for design files and prototypes, allowing you to link stories directly to Figma or Miro references while surfacing relevant UI and interaction notes for engineering context.

Does this approach generate enough acceptance criteria for QA testing?

Yes, this approach generates 6-8 acceptance criteria per job story using observable, testable language that covers edge cases and integration points, providing sufficient depth for QA testing and engineering validation.

How do I standardize product backlog items using the JTBD framework?

You standardize product backlog items by translating feature ideas into outcome-focused job stories using the "When / I want / so I can" JTBD framework, ensuring every item has measurable acceptance criteria so teams can prioritize and build with confidence.