user-story

Generate user stories with Gherkin acceptance criteria and YAML frontmatter templates.

6.4k|767|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill user-story-deanpeters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill user-story-deanpeters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams translate needs into actionable work by generating clear, concise user stories using Mike Cohn's Use Case format paired with Gherkin-style acceptance criteria. It aligns stakeholders, reduces back-and-forth, and creates testable conditions for validation.

Core Features & Use Cases

  • Structured Use Case: As a [persona], I want to [action] so that [outcome], enabling consistent storytelling across teams.
  • Gherkin Acceptance Criteria: Given/When/Then scenarios that translate the story into verifiable tests.
  • Templates & Quick Start: Ready-to-use prompts and templates to accelerate backlog refinement and sprint planning.

Quick Start

  • Use the included templates to draft a story quickly, or run the CLI script to generate a starter story from simple inputs (e.g., persona, action, and outcome).

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I write user stories with Gherkin acceptance criteria for backlog refinement?

User stories with Gherkin acceptance criteria combine Mike Cohn's persona-action-outcome format with Given/When/Then scenarios, translating product needs into verifiable tests for backlog refinement and sprint planning.

What is the best way to turn product requirements into testable user stories?

The best way to turn requirements into testable user stories is applying a structured Use Case format paired with Gherkin acceptance criteria, aligning stakeholders and creating verifiable conditions for development validation.

Can I generate a starter user story from simple inputs like persona and action?

Yes, you can generate a starter user story from simple inputs like persona, action, and outcome using provided Quick Start templates, which accelerate drafting consistent narratives for sprint planning.

When do I need Gherkin-style acceptance criteria in user story writing?

You need Gherkin-style acceptance criteria in user story writing when translating narratives into verifiable tests, ensuring product discovery outputs have clear Given/When/Then conditions for validation.

Does this user story format work for sprint planning and product discovery?

Yes, this user story format works for sprint planning and product discovery, applying concise narratives and Gherkin acceptance criteria to guide development and reduce stakeholder back-and-forth.

Why use Mike Cohn's format for writing user stories over other approaches?

Mike Cohn's format structures user stories as persona, action, and outcome, enabling consistent storytelling across teams while pairing with Gherkin scenarios to guarantee testable, actionable outputs.