skills.rest
Prorise-cool
Prorise-coolCOMMUNITY
Explore all skills by this author →
GitHub

user-story

Generate user stories with Gherkin acceptance criteria from PRD requirements.

24|3|Updated Jan 24, 2026
Search Tags:#development#product management#acceptance criteria#agile#gherkin#user story
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill user-story-prorise-cool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/user-story
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill user-story-prorise-cool

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 actionable development tasks by creating well-defined user stories with clear, testable acceptance criteria.

Core Features & Use Cases

  • User Story Creation: Generates stories using the "As a / I want / so that" format.
  • Gherkin Acceptance Criteria: Adds testable conditions using "Given / When / Then".
  • Use Case: You're a Product Manager about to start a new feature. Use this Skill to write a user story for the login functionality, ensuring both the development team and QA understand exactly what needs to be built and how to test it.

Quick Start

Use the user-story skill to create 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 Gherkin acceptance criteria for agile development?▼

User stories with Gherkin acceptance criteria are written using the "As a / I want / so that" format combined with "Given / When / Then" conditions to translate user needs into actionable, testable development tasks for agile teams.

What is the best way to convert PRD requirements into actionable development tasks?▼

Converting PRD requirements into actionable development tasks involves generating user stories following the Mike Cohn format and adding Gherkin-style acceptance criteria to ensure development and QA teams understand exact outcomes and testable conditions.

How does the Given When Then format work for user story acceptance criteria?▼

The Given When Then format works by defining testable acceptance criteria for user stories: Given establishes preconditions, When specifies the action, and Then describes the expected outcome for QA validation.

Can I use Gherkin acceptance criteria for B2B SaaS feature development?▼

Gherkin acceptance criteria can be used for B2B SaaS feature development to generate clear user stories for new functionalities like notification systems, ensuring both development and QA teams understand exactly what needs to be built and tested.

Do I need prior product management experience to create standard user stories?▼

No prior product management experience is needed to create standard user stories. This approach generates stories using the established "As a / I want / so that" format, providing a structured template for translating user needs into development-ready work.

Related Skills

Explore More Product & Management Skills→
hfadhlullahhfadhlullah

PRD Generator

Generate Product Requirements Documents through an interview process.

Community
Advanced
KentoShimizuKentoShimizu
7

user-story-writing

Convert prioritized requirements into sprint-ready user stories with acceptance criteria.

Community
Advanced
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
GainInsightDevGainInsightDev

af-write-scenario-specs

Generate BDD Markdown scenario specifications with preconditions, steps, and expected outcomes.

Official
Basic