user-stories

Name: user-stories
Availability: InStock
Author: raphaelmans

Convert PRDs, specs, or descriptions into domain-based user stories with acceptance criteria.

Updated Feb 28, 2026

Search Tags:#requirements #agile #user-stories #acceptance-criteria #story-generation #domain-based

Ready to run

npx skills add https://github.com/raphaelmans/agent-skills --skill user-stories-raphaelmans

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured user stories with acceptance criteria from any input, accelerating product planning and cross-team alignment.

Core Features & Use Cases

Converts PRDs, feature specs, verbal descriptions, or exploratory findings into domain-based user stories with clear acceptance criteria.
Enforces consistent naming and numbering (US-{DOMAIN}-{NNN}) per sub-feature and maintains a domain index for quick navigation.
Provides a ready-to-use Domain/Index structure that teams can populate with US- files to track features and scope.

Quick Start

Describe the feature or PRD you want to convert into user stories, and I will generate domain-focused US- files and acceptance criteria.

Frequently Asked Questions about user-stories

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

FAQPage Schema

How do I convert a PRD into structured user stories with acceptance criteria?▼

To convert a PRD into structured user stories, input your feature specs and the tool generates domain-focused stories with acceptance criteria. It organizes requirements by domain and sub-feature, applying stable US- numbering for easy tracking.

How does domain-based user story generation work for agile planning?▼

Domain-based user story generation works by parsing your input descriptions and categorizing them into specific domains. It maintains a domain index and applies consistent US-{DOMAIN}-{NNN} naming to keep stories discoverable for cross-team alignment.

Can I generate user stories from verbal descriptions or exploratory findings?▼

Yes, you can generate user stories from verbal descriptions or exploratory findings. The tool processes any unstructured input, applying acceptance criteria templates and domain-based naming to accelerate product planning.

What is the best way to organize user stories by sub-feature for development teams?▼

The best way to organize user stories by sub-feature is using a structured Domain/Index format. This approach maintains a domain index for quick navigation and uses consistent numbering per sub-feature to track scope effectively.

Do I need a specific format to generate acceptance criteria for agile requirements?▼

No specific format is required to generate acceptance criteria for agile requirements. You can provide PRDs, specs, or verbal descriptions, and the tool applies standardized acceptance criteria templates to structure them.

When should I not use automated user story generation for requirements?▼

You should not use automated user story generation when requirements are highly abstract or lack sufficient detail. The tool relies on input descriptions to generate domain-focused stories, so unclear inputs may yield incomplete acceptance criteria.