skills.rest
gabriellst
gabriellstCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

user-stories

Generate structured user stories with acceptance criteria from feature requests.

4|Updated Jul 30, 2026
Search Tags:#requirements#product management#acceptance criteria#agile#user stories#prd#feature request
One-click install
npx skills add https://github.com/gabriellst/codm --skill user-stories-gabriellst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/user-stories
Command: npx skills add https://github.com/gabriellst/codm --skill user-stories-gabriellst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague feature request or PRD excerpt into implementable, testable work items is slow and error-prone. This Skill transforms business requirements into structured user stories with clear acceptance criteria, so scope is defined before technical work begins. ## Core Features & Use Cases - Structured Story Generation: Produces stories in US-XXX format with actor, action, benefit, acceptance criteria, and notes. - Completeness Validation: Checks each story for testable criteria, real actors, independence, and documented edge cases. - Clarifying Questions & Assumptions: Surfaces open questions with impact classification and documents assumptions with risk levels. - Use Case: A product manager receives a stakeholder request for a new notification feature and uses this Skill to break it into independent, testable stories with acceptance criteria before handing them to engineering. ## Quick Start Ask the agent to generate user stories with acceptance criteria from your feature request or PRD excerpt.

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

Provide a feature request or requirement description, and the Skill extracts actors, actions, data, and business rules, then generates stories in US-XXX format. Each story includes acceptance criteria, notes on edge cases, and open questions.

How to break down a feature request into implementable stories?▼

The Skill analyzes the requirement's domain, actors, and rules, then produces independent stories with testable acceptance criteria. It validates completeness and surfaces clarifying questions before finalizing.

When should I not use user story generation?▼

Do not use it for architectural component breakdown, implementation sequencing, or reviewing existing plans. Those tasks belong to planning, task-breakdown, or spec-review workflows instead.

What makes a good acceptance criterion in a user story?▼

Acceptance criteria must be measurable, verifiable, and free of implementation details. The Skill's checklist rejects criteria that imply specific technical solutions and ensures edge cases are documented in story notes.

Can user stories be generated from a PRD document?▼

Yes, a PRD excerpt or natural language description works as input. The Skill extracts the bounded context, actors, and business rules, then asks clarifying questions when ambiguity affects scope or contracts.

Related Skills

Explore More Product & Management Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
alirezarezvanialirezarezvani
110

roadmap-generator

Convert architecture designs into phased roadmaps with Epics, Stories, and Tasks.

Community
Advanced
MharbulousMharbulous

conflict-detection

Detect duplicate and overlapping stories in the story-tree database.

Community
Intermediate
bnadlerjrbnadlerjr
5

breaking-down-stories

Break down user stories into actionable tasks for sprint planning.

Community
Intermediate