stories

Generate job stories and acceptance criteria from product requirements.

42|5|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kazdenc/builder-skills --skill stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stories
Source: https://github.com/kazdenc/builder-skills/tree/main/.claude/skills/product/define/stories
Command: npx skills add https://github.com/kazdenc/builder-skills --skill stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level product requirements into clear, actionable job stories or user stories with precise acceptance criteria, bridging the gap between product vision and development execution.

Core Features & Use Cases

  • Job Story Generation: Creates stories following the "When [situation], I want to [job], so I can [need]" format, prioritizing context over personas.
  • Acceptance Criteria: Defines testable conditions using Given/When/Then syntax to ensure clarity on expected behavior.
  • Use Case: You have a feature brief for a new e-commerce checkout flow. Use this Skill to break down the requirements into a series of job stories and their corresponding acceptance criteria, ready for the development team.

Quick Start

Use the stories skill to write job stories for the attached product requirements document.

Frequently Asked Questions about stories

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

FAQPage Schema
How do I write acceptance criteria for product requirements using Given/When/Then?

Acceptance criteria for product requirements are defined using Given/When/Then syntax to ensure clear, testable conditions for expected behavior. This format translates feature briefs into implementable units that agile development teams can directly verify.

What is the best way to generate job stories from feature briefs?

Generating job stories from feature briefs is done using the JTBD framework, following the "When [situation], I want to [job], so I can [need]" format. This approach prioritizes user context over personas to create actionable development tasks.

How does the job story format differ from traditional user stories in agile development?

The job story format differs from traditional user stories by prioritizing the situation and the job to be done over specific personas. It uses the "When [situation], I want to [job], so I can [need]" structure to focus on the contextual need driving the feature.

Can I use this to break down high-level e-commerce requirements into implementable units?

Yes, you can break down high-level e-commerce requirements into implementable units. The Skill transforms feature briefs, like an e-commerce checkout flow, into a series of job stories and corresponding acceptance criteria ready for development.

Do I need a specific format for my product requirements to generate job stories?

You do not need a specific format for product requirements to generate job stories. You can attach a product requirements document, and the Skill will translate the high-level briefs into actionable job stories and acceptance criteria.

When do I need acceptance criteria with Given/When/Then syntax for agile development?

You need acceptance criteria with Given/When/Then syntax when translating feature briefs into testable units for agile development. This format ensures precise clarity on expected behavior, bridging the gap between product vision and development execution.