skills.rest
EchoNoReturn
EchoNoReturnCOMMUNITY
Explore all skills by this author →
GitHub

user-story

Convert user needs into testable user stories with Gherkin acceptance criteria.

Updated Mar 25, 2026
Search Tags:#templates#backlog#gherkin#acceptance-criteria#user-story#story-splitting#mike-cohn
One-click install
npx skills add https://github.com/EchoNoReturn/task-manager --skill user-story-echonoreturn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/EchoNoReturn/task-manager/tree/main/.agents/skills/user-story
Command: npx skills add https://github.com/EchoNoReturn/task-manager --skill user-story-echonoreturn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Convert user needs into testable, well-scoped user stories by combining Mike Cohn's use-case format with Gherkin-style acceptance criteria, enabling shared understanding and verifiable delivery.

Core Features & Use Cases

  • Use Case structure: As a [persona], I want to [action], so that [outcome].
  • Acceptance Criteria alignment: Given/When/Then style to translate requirements into testable conditions.
  • Templates and examples: Includes a Markdown template, examples and a CLI helper to generate consistent stories.

Quick Start

Provide a complete user story in Mike Cohn + Gherkin format for a given scenario.

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I write testable user stories from product requirements?▼

Writing testable user stories involves combining Mike Cohn's use-case structure with Gherkin-style acceptance criteria, translating requirements into Given/When/Then conditions to enable shared understanding and verifiable delivery for new features.

What is the best way to format acceptance criteria for backlog grooming?▼

Formatting acceptance criteria for backlog grooming is best done using Gherkin style (Given/When/Then), which translates requirement conditions into clear, testable scenarios that enforce validation across sprint planning.

How does Gherkin structure work with Mike Cohn's user story format?▼

Gherkin structure works with Mike Cohn's user story format by applying the As a/I want to/So that use-case for narrative scope, then adding Given/When/Then rules to define specific, testable acceptance criteria for the feature.

Can I generate user story templates automatically for sprint planning?▼

You can generate user story templates automatically using the provided CLI helper, which outputs consistent Markdown files enforcing the Mike Cohn and Gherkin structure for immediate use in sprint planning.

Does this user story format work for story splitting in agile?▼

This user story format works for story splitting because the testable Gherkin acceptance criteria clearly expose distinct logical paths, allowing you to isolate and split requirements into smaller backlog items during grooming.

Related Skills

Explore More Product & Management Skills→
alexsandrocruzalexsandrocruz

requirements-engineering

Convert stakeholder needs into structured, testable specifications with templates.

Community
Basic
RyanJarvRyanJarv

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning.

Community
Advanced
whimzyLivewhimzyLive
3

user-story

Generate user stories with structured Gherkin acceptance criteria.

Community
Intermediate
yuyuxinliyuyuxinli
1

user-story-splitting

Split large user stories into smaller deliverable stories using eight patterns.

Official
Intermediate