user-story

Translate user needs into structured stories with Gherkin acceptance criteria.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill user-story-yuyuxinli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/yuyuxinli/moodcoco/tree/main/.claude/skills/user-story
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill user-story-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams translate vague user needs into clear, testable user stories by combining Mike Cohn's Use Case format with Gherkin-style acceptance criteria.

Core Features & Use Cases

  • Structured Use Case writing (As a / I want to / so that) aligned with Mike Cohn's method
  • Gherkin-style Acceptance Criteria using Given/When/Then for testability
  • Guidance for splitting large stories into smaller, deliverable units
  • Templates and best practices to foster shared understanding between product and engineering

Quick Start

Generate a concise user story for a feature you are planning, using the Mike Cohn format and Gherkin criteria.

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 with Gherkin acceptance criteria?▼

Testable user stories are written by combining Mike Cohn's Use Case format (As a / I want to / so that) with Gherkin-style Given/When/Then acceptance criteria to ensure measurable, verifiable outcomes.

What is the best way to structure user stories for backlog grooming?▼

Structuring user stories for backlog grooming involves translating needs into development-ready stories using a single When/Then pair, ensuring success criteria are measurable and supporting story splitting when necessary.

How do I split large user stories into smaller deliverable units?▼

Splitting large user stories involves applying structured guidance to break down complex needs while maintaining a single When/Then pair per story, ensuring each unit remains testable and deliverable.

When should I use Mike Cohn's Use Case format for product management?▼

Mike Cohn's Use Case format should be used during discovery, backlog grooming, and sprint planning to translate vague user needs into structured, development-ready stories that foster shared understanding between product and engineering.

Why does each user story need a single When/Then pair?▼

Each user story needs a single When/Then pair to maintain focus, ensure testability, and make success criteria measurable and verifiable, preventing scope creep within individual development-ready stories.

Can I generate Gherkin acceptance criteria for sprint planning without prior test data?▼

Yes, you can generate Gherkin acceptance criteria for sprint planning by translating user needs directly into Given/When/Then structures, ensuring development-ready stories with verifiable outcomes without requiring pre-existing test data.