create-user-stories

Generate AMP-style user stories from UI screens with backlog metadata.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/BenGWeeks/.claude --skill create-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-user-stories
Source: https://github.com/BenGWeeks/.claude/tree/main/skills/create-user-stories
Command: npx skills add https://github.com/BenGWeeks/.claude --skill create-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating comprehensive, component-based User Stories from UI screens is time-consuming and error-prone. This guide helps product teams systematically decompose interfaces into actionable stories with AMP-style acceptance criteria.

Core Features & Use Cases

  • Component-based decomposition of UI screens to generate discrete User Stories.
  • Automated generation of AMP acceptance criteria (Acceptance, Measure, Proof) for each story.
  • Alignment with the T-Minus-15 process template to streamline planning and prioritization.
  • Metadata-rich stories suitable for backlog items and sprint planning.

Quick Start

Describe the UI screens or attach screenshots to generate initial User Stories.

Frequently Asked Questions about create-user-stories

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

FAQPage Schema
How do I generate user stories from UI screens?▼

You can generate user stories from UI screens by providing UI descriptions or screenshots, which the Skill decomposes into discrete backlog-ready items using AMP-style acceptance criteria.

What is the AMP acceptance criteria format for agile user stories?▼

The AMP acceptance criteria format for agile user stories structures requirements into Acceptance, Measure, and Proof components, which this Skill automatically generates for each decomposed UI element.

How do I align user stories with the T-Minus-15 process template?▼

You align user stories with the T-Minus-15 process template by structuring output metadata into standardized fields including Title, State, Owner, Area, Iteration, Persona(s), Description, and Acceptance Criteria.

Can I use screenshots to create backlog-ready user stories?▼

Yes, you can use screenshots to create backlog-ready user stories by providing UI screen images to the Skill, which systematically decomposes them into actionable items with complete metadata.

What is component-based decomposition for agile requirements?▼

Component-based decomposition for agile requirements is a strategy that breaks down complex UI screens into discrete, manageable user stories, ensuring each interface element receives dedicated acceptance criteria and backlog metadata.