job-stories

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Lev-it/lev-skills --skill job-stories-lev-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/Lev-it/lev-skills/tree/main/.claude/skills/job-stories
Command: npx skills add https://github.com/Lev-it/lev-skills --skill job-stories-lev-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams create detailed, user-focused job stories, streamlining the process of defining user needs and feature requirements.

Core Features & Use Cases

  • Job Story Creation: Guides users through the creation of job stories using a standardized format.
  • Acceptance Criteria Generation: Automatically generates acceptance criteria based on the job story.
  • Use Case: Ideal for product managers and developers looking to articulate user needs and ensure feature delivery aligns with user outcomes.

Quick Start

Generate a job story for a new feature by entering the product name, feature, design link, and context: job-stories generate -p "Product Name" -f "Feature Name" -d "Design Link" -c "Context".

Frequently Asked Questions about job-stories

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

FAQPage Schema
What is a job story and how does it define user needs for feature requirements?

A job story defines user needs by structuring feature requirements around specific situations and motivations, formatted as 'When [situation], I want to [motivation], so I can [outcome]' to focus on user outcomes.

How do I write job stories and generate acceptance criteria for product development?

You generate job stories and acceptance criteria by providing structured input including the product name, feature name, design link, and context to automatically articulate user situations and expected outcomes.

Can I use job stories instead of user stories to articulate feature requirements?

Yes, job stories are designed for product development to articulate user needs by focusing strictly on user situations and motivations rather than personas, ensuring feature delivery aligns with user outcomes.

What context do I need to provide to generate a job story for a new feature?

To generate a job story, you need to provide the product name, feature name, design link, and contextual background to ensure the output accurately reflects the specific user situation and motivation.

Why use job stories for defining user needs over traditional product development methods?

Job stories help product teams define user needs by streamlining the creation of detailed, user-focused narratives that directly tie feature requirements to specific user situations and motivations.