skills.rest
newkayak12
newkayak12COMMUNITY
Explore all skills by this author →
GitHub

user-story

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

1|Updated Mar 11, 2026
Search Tags:#requirements#product management#acceptance criteria#agile#gherkin#user story
One-click install
npx skills add https://github.com/newkayak12/claude-skills --skill user-story-newkayak12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/newkayak12/claude-skills/tree/main/plugins/newkayak12-skills/skills/user-story
Command: npx skills add https://github.com/newkayak12/claude-skills --skill user-story-newkayak12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you translate user needs into development-ready work by creating clear, concise user stories with Gherkin-style acceptance criteria, ensuring shared understanding and testable outcomes.

Core Features & Use Cases

  • User Story Creation: Formulates stories using the "As a / I want to / so that" format.
  • Acceptance Criteria: Defines testable conditions using Gherkin's "Given / When / Then" structure.
  • Use Case: You need to define a new feature for your product. Use this Skill to write a user story for "allowing users to reset their password" with clear steps on how to verify it works.

Quick Start

Use the user-story skill to write a user story for a new notification system in our B2B SaaS app.

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 acceptance criteria for agile development?▼

To write user stories for agile development, formulate stories using the Mike Cohn "As a / I want to / so that" format, then define testable acceptance criteria using Gherkin's "Given / When / Then" structure to ensure clear, actionable outcomes.

What is the best way to translate product requirements into testable Gherkin acceptance criteria?▼

The best way to translate product requirements into testable Gherkin acceptance criteria is to map user needs directly into "Given / When / Then" statements, ensuring every development task has clear outcomes and verifiable conditions for sprint planning.

Can I use Gherkin format for backlog grooming in B2B SaaS products?▼

Yes, you can use the Gherkin format for backlog grooming in B2B SaaS products by defining testable conditions for new features like a notification system, ensuring stories remain user-centric and outcome-focused.

How to structure outcome-focused user stories for sprint planning?▼

To structure outcome-focused user stories for sprint planning, combine the "As a / I want to / so that" format with Gherkin-style acceptance criteria, translating user needs into development-ready work with shared understanding.

Does generating user stories require prior knowledge of the Mike Cohn format?▼

Generating user stories using this approach applies the Mike Cohn format automatically, so you do not need deep prior expertise to formulate user-centric stories and translate product needs into development tasks.

Related Skills

Explore More Product & Management Skills→
wilstowilsto

user-story

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

Community
Basic
inho-teaminho-team
6

Qpm-user-story

Translate user needs into INVEST-form user stories with Gherkin acceptance criteria.

Official
Intermediate
blazefluzblazefluz

Work Intake Manager

Convert natural language requests into structured user stories, epics, and bug reports.

Community
Advanced
mlbrightmlbright

feature-spec

Guide structured interviews to create feature specifications with Gherkin scenarios.

Community
Intermediate