user-story

Translate user needs into user stories with Gherkin acceptance criteria.

Updated Mar 30, 2026

Search Tags:#agile #backlog #gherkin #acceptance-criteria #user-story #story-splitting #mike-cohn

Ready to run

npx skills add https://github.com/omeragaakbas/zoyare --skill user-story-omeragaakbas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/user-story
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill user-story-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps product teams consistently transform user needs into concise, testable stories that pair Mike Cohn's Use Case format with Gherkin-style acceptance criteria. It ensures stories are outcome-focused, actionable, and ready for discussion between product, design, and engineering.

Core Features & Use Cases

Use Mike Cohn's Use Case (As a..., I want to..., so that ...)
Incorporate Gherkin acceptance criteria (Scenario, Given, When, Then) for testable definitions.
Supports story-splitting guidance via the 'user-story-splitting' Skill and provides prompts to maintain clarity and scope.

Quick Start

Provide a persona, action, and outcome to generate a ready-to-use user story skeleton.

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 combine Mike Cohn's Use Case format (As a..., I want to..., so that...) with Gherkin-style acceptance criteria (Given, When, Then) to ensure outcomes are measurable and verifiable across product, design, and engineering teams.

What is the best way to format a user story for sprint planning?▼

The best way to format a user story for sprint planning is using a Use Case structure that defines a specific persona, action, and outcome, paired with clear Gherkin scenarios to guide development and testing discussions.

How do I split large user stories in an agile backlog?▼

You can split large user stories by applying story-splitting guidance to break down broad outcomes into smaller, testable units, ensuring each divided story retains clear persona, problem, and verifiable acceptance criteria.

Can I generate a user story from just a persona and desired outcome?▼

Yes, generating a user story requires clear inputs for persona, action, and outcome. Providing these three elements produces a ready-to-use user story skeleton complete with testable Gherkin acceptance criteria.

Why should I use Gherkin syntax for user story acceptance criteria?▼

Gherkin syntax structures acceptance criteria into Given, When, Then scenarios, ensuring that user story requirements are measurable and verifiable while providing clear conversation starters for engineering and design teams.

When do I need to use the user-story format for backlog grooming?▼

You need the user-story format during backlog grooming to transform ambiguous user needs into concise, outcome-focused, and actionable items that are ready for discussion between product, design, and engineering stakeholders.