skills.rest
sicktastic
sicktasticCOMMUNITY
Explore all skills by this author →
Website𝕏@sicktasticGitHub

user-story

Create Mike Cohn user stories with Gherkin acceptance criteria.

Updated Apr 6, 2026
Search Tags:#gherkin#product-management#acceptance-criteria#user-story#story-writing#mike-cohn
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill user-story-sicktastic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/user-story
Command: npx skills add https://github.com/sicktastic/skill-issue --skill user-story-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill turns vague requirements into well-structured user stories that highlight who benefits, what they do, why it matters, and how the work will be tested so teams no longer debate story intent.

Core Features & Use Cases

  • Mike Cohn structure: Guides you through the As a / I want / so that framework with reminders to keep the persona, action, and outcome specific.
  • Gherkin acceptance criteria: Requires a single Scenario and aligned Given/When/Then statements so every story includes a testable success path.
  • Use case: During backlog grooming, convert a new notification requirement into a concise story with clear context, value, and verification steps before assigning it to engineering.

Quick Start

Ask the user-story skill to write a Mike Cohn user story with Gherkin acceptance criteria for your next notification feature.

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 grooming?▼

To write user stories with Gherkin acceptance criteria, structure requirements using the Mike Cohn As a / I want / so that framework, then define a single testable Scenario with Given/When/Then statements to ensure development-ready work.

What is the Mike Cohn user story format and when should I use it?▼

The Mike Cohn user story format defines who benefits, what they do, and why it matters using the As a / I want / so that structure. Apply it during sprint planning or backlog grooming to convert vague requirements into clear product outcomes.

Can I use Gherkin Given When Then statements to make acceptance criteria testable?▼

Yes, Gherkin Given/When/Then statements make acceptance criteria testable by aligning a single Scenario with a clear success path, ensuring every user story includes verifiable conditions before assigning it to engineering.

What context is required before drafting a user story for engineering?▼

Before drafting a user story, you must provide context on the persona, problem, desired outcome, and constraints. This keeps the Mike Cohn story specific and the Gherkin acceptance criteria testable.

What's the best way to convert vague product requirements into actionable user stories?▼

The best way to convert vague product requirements into actionable user stories is applying the Mike Cohn structure alongside Gherkin acceptance criteria, eliminating story intent debate by highlighting who benefits and how the work will be tested.

Related Skills

Explore More Product & Management Skills→
archerliarcherli

problem-statement

Guide users through empathy mapping to construct user-centered problem statements.

Community
Intermediate
newkayak12newkayak12
1

user-story

Generate user stories with Mike Cohn format and Gherkin acceptance criteria.

Community
Intermediate
slabgorbslabgorb
2

sprint

Organize sprint status, backlog, and story workflows via the pf sprint CLI.

Community
Advanced
AustinZ21AustinZ21
4

speckit-specify

Generate standardized feature specifications from natural language descriptions.

Community
Intermediate