jobs-stories

Generate Job Stories, User Stories, and Gherkin acceptance criteria from product briefs.

17|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Adelie-Squad/solosquad --skill jobs-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-stories
Source: https://github.com/Adelie-Squad/solosquad/tree/main/skills/jobs-stories
Command: npx skills add https://github.com/Adelie-Squad/solosquad --skill jobs-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams generate consistent Job Stories, User Stories, and Gherkin acceptance criteria from briefs, aligning stakeholders and speeding PRD development.

Core Features & Use Cases

  • Generate Job Stories and User Stories using 3C/INVEST guidelines.
  • Produce Gherkin-style acceptance criteria with at least two scenarios per story.
  • Deliver PRD-ready artifacts that support planning, validation, and testing.

Quick Start

Generate Job Stories, User Stories, and Gherkin acceptance criteria from a product brief.

Frequently Asked Questions about jobs-stories

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

FAQPage Schema
How do I generate user stories and Gherkin acceptance criteria from a product brief?

To generate user stories and Gherkin acceptance criteria from a product brief, input the brief into the skill to automatically produce PRD-ready artifacts. It applies INVEST and 3C guidelines, outputting testable stories with clear Gherkin syntax and at least two scenarios per story.

What is the difference between a job story and a user story when writing a PRD?

Job stories focus on situational motivations while user stories capture feature requests from a persona's perspective. This skill generates both formats from your product brief, applying 3C framing for job stories and INVEST criteria for user stories to align stakeholders during PRD planning.

How do I write Gherkin acceptance criteria with multiple scenarios for feature planning?

Writing Gherkin acceptance criteria requires structuring Given-When-Then syntax for each scenario. This skill automatically generates Gherkin-style acceptance criteria from product briefs, ensuring every user story includes at least two distinct scenarios to support validation and testing.

Can I use job stories and INVEST criteria for agile feature planning across different teams?

Job stories and INVEST criteria can be used for agile feature planning across teams to ensure independent and testable outputs. This skill produces PRD-ready artifacts that satisfy INVEST principles and 3C framing, making them suitable for cross-team validation and development.

Does this approach produce independent and testable stories for product requirement documents?

This approach produces independent and testable stories for product requirement documents by applying INVEST guidelines and 3C framing. It transforms product briefs into structured job stories, user stories, and Gherkin acceptance criteria ready for planning and testing.

What are the limitations of automatically generating user stories from product briefs?

A limitation of automatically generating user stories from product briefs is that the output quality depends entirely on the clarity of the input brief. While the skill enforces INVEST criteria and Gherkin syntax, stakeholders must still review the generated stories to ensure they capture complex feature requirements accurately.