skills.rest
kalilurrahman
kalilurrahmanCOMMUNITY
Explore all skills by this author →
Website𝕏@krahmanGitHub

user-stories

Generates structured user stories with acceptance criteria, edge cases, and dependencies from feature descriptions.

1|Updated Mar 21, 2026
Search Tags:#product management#epic breakdown#acceptance criteria#agile#sprint planning#user stories#backlog
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill user-stories-kalilurrahman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/user-stories
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill user-stories-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing sprint-ready user stories from a rough feature description is time-consuming and often produces vague, untestable stories. This Skill turns a feature description into a complete set of independently deliverable user stories with testable acceptance criteria, edge cases, and dependency mapping. ## Core Features & Use Cases - Epic Breakdown: Splits a feature into an epic summary and independently deliverable user stories with priorities (Must-have / Should-have / Nice-to-have). - Testable Acceptance Criteria: Writes Given/When/Then criteria plus edge cases and unhappy paths (failures, timeouts, invalid input, missing permissions) for every story. - Dependency & Scope Mapping: Documents dependencies between stories, external systems, and explicitly lists what is out of scope. - Use Case: A product manager pastes a description of a new team-invitation feature and receives a stories-team-invitations.md file ready for sprint planning, complete with acceptance criteria a QA engineer can verify without follow-up questions. ## Quick Start Ask the assistant to turn your feature description into user stories with acceptance criteria and save them to a markdown file.

Frequently Asked Questions about user-stories

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

FAQPage Schema
How do I write user stories from a feature description?▼

Provide the feature description and the Skill breaks it into an epic and independently deliverable stories. Each story follows the 'As a [user], I want [action], so that [benefit]' format with Given/When/Then acceptance criteria, edge cases, and priorities.

How to write acceptance criteria in Given When Then format?▼

Each acceptance criterion states a precondition (Given), an action (When), and an expected result (Then). The Skill generates multiple testable criteria per story so a QA engineer can verify each one without asking clarifying questions.

What makes a user story independently deliverable?▼

A story is independently deliverable if it can ship without depending on another unfinished story. If a story cannot ship alone, the Skill either merges it with its dependency or makes the dependency explicit in the dependencies section.

What happens if my feature description is too vague?▼

The Skill lists clarifying questions before writing any stories when the description lacks enough detail. This prevents generating vague stories with circular benefits or unspecified user types.

Does the user story output include edge cases and error handling?▼

Yes, every story includes edge cases covering unusual conditions, error conditions, and boundary conditions. Unhappy paths such as failures, timeouts, invalid input, and missing permissions are always included.

Related Skills

Explore More Product & Management Skills→
I2olanDI2olanD

requirements-elicitation

Transform vague requirements into clear, testable specifications using elicitation techniques and documentation templates.

Community
Advanced
skytiger6724skytiger6724
2

sprint-plan

Plan sprint capacity, story selection, dependencies, and risks for upcoming delivery windows.

Community
Intermediate
violetiovioletio

product-discovery

Identify and validate user problems through a four-stage product discovery process.

Official
Basic
organvm-i-theoriaorganvm-i-theoria

product-requirements-designer

Generates enterprise and lean PRDs with user stories, acceptance criteria, and technical handoff specifications.

Official
Advanced