user-story-creator

Generate user stories from URLs, ticket numbers, or summaries with acceptance criteria.

5|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/aaronbrethorst/claude-skills --skill user-story-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-creator
Source: https://github.com/aaronbrethorst/claude-skills/tree/main/user-story-creator
Command: npx skills add https://github.com/aaronbrethorst/claude-skills --skill user-story-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation and refinement of user stories, ensuring they are clear, comprehensive, and aligned with project goals, by leveraging context from tickets, codebases, and user input.

Core Features & Use Cases

  • Contextual Story Generation: Creates well-structured user stories from URLs, ticket numbers, or plain text summaries.
  • Automated Context Gathering: Analyzes existing tickets, codebase structure, and dependencies to enrich the story.
  • Guided Clarification: Asks targeted questions to resolve ambiguities and states assumptions explicitly.
  • Integrated Review: Orchestrates parallel security and product management reviews for enhanced quality.
  • Use Case: You have a ticket ID for a new feature. This Skill fetches the ticket details, analyzes the relevant code, asks clarifying questions, and generates a complete user story draft with acceptance criteria, user flows, and technical notes, ready for review.

Quick Start

Use the user-story-creator skill to create a user story from the GitHub issue URL https://github.com/example/repo/issues/123.

Frequently Asked Questions about user-story-creator

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

FAQPage Schema
How do I generate user stories with acceptance criteria from a GitHub issue?

To generate user stories with acceptance criteria, provide a GitHub issue URL or ticket number. The Skill fetches ticket details, analyzes relevant code, asks clarifying questions, and outputs a complete story draft with user flows and technical notes.

What is the best way to write agile user stories that include security and product management reviews?

Writing agile user stories with integrated reviews requires orchestrating parallel security and product management checks. This Skill automates that process by gathering codebase context, resolving ambiguities through targeted questions, and ensuring stories are actionable and well-defined.

How does automated context gathering work when refining requirements from existing tickets?

Automated context gathering for requirements refinement works by analyzing existing tickets, codebase structure, and dependencies. It enriches the user story by extracting relevant technical details and stating assumptions explicitly to resolve ambiguities.

Can I use this approach to create user stories for complex features requiring detailed technical notes?

Yes, you can create user stories for complex features requiring detailed technical notes. The Skill analyzes codebase dependencies and structure, asks targeted clarification questions, and generates comprehensive stories with technical notes and user flows.

What are the limitations of automated user story generation from plain text summaries?

Automated user story generation from plain text summaries depends on the clarity of the initial input. While the Skill asks targeted questions to resolve ambiguities and states assumptions, incomplete summaries may limit the depth of codebase analysis and acceptance criteria accuracy.

Do I need to provide a ticket number to generate acceptance criteria, or can I use a feature summary?

You do not need a ticket number to generate acceptance criteria. You can provide a plain text summary of a feature, and the Skill will gather context, ask clarifying questions, and generate a structured user story with acceptance criteria and technical notes.