user-story

Create user stories with Mike Cohn and Gherkin formats.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/archerli/skill-set --skill user-story-archerli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/archerli/skill-set/tree/main/%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86/Product-Manager-Skills-main/skills/user-story
Command: npx skills add https://github.com/archerli/skill-set --skill user-story-archerli

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps in creating user stories that combine Mike Cohn's format with Gherkin-style acceptance criteria, ensuring clear outcomes and testable conditions.

Core Features & Use Cases

  • User Story Creation: Guides the creation of user stories with proper structure and format.
  • Acceptance Criteria: Helps in writing testable acceptance criteria using Gherkin syntax.
  • Use Case: Ideal for product managers and team leads to translate user needs into actionable development work.

Quick Start

Use the user-story skill to create a user story for a new feature in your application.

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I write a user story with Gherkin acceptance criteria?

To write a user story with Gherkin acceptance criteria, you combine Mike Cohn's format for the story body with Given-When-Then syntax for testable conditions, ensuring clear outcomes and development-ready work.

What is the best format for translating user needs into testable development tasks?

The best format for translating user needs into testable development tasks combines Mike Cohn's user story structure with Gherkin-style acceptance criteria, ensuring clear outcomes and testable conditions for software development.

How do I create a user story for a new application feature using Mike Cohn's format?

You create a user story for a new application feature by following Mike Cohn's structure to define the user need, then appending Gherkin-style acceptance criteria to specify testable conditions and clear outcomes.

Do I need product management experience to write user stories with Gherkin syntax?

You need a solid understanding of product management and software development concepts to effectively use this approach, as it requires translating user needs into structured, development-ready work with testable conditions.

When should I use Gherkin acceptance criteria in a user story?

You should use Gherkin acceptance criteria in a user story when you need to translate user needs into actionable development work with clear outcomes and testable conditions, ensuring the team understands the exact requirements.