skills.rest
stefanomartiradonna
stefanomartiradonnaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

user-stories

Generate user stories with acceptance criteria using the 3 C's and INVEST frameworks.

Updated Apr 8, 2026
Search Tags:#acceptance criteria#agile#sprint planning#user stories#backlog#feature breakdown#invest
One-click install
npx skills add https://github.com/stefanomartiradonna/claude-skills --skill user-stories-stefanomartiradonna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/stefanomartiradonna/claude-skills/tree/main/pm-execution-user-stories
Command: npx skills add https://github.com/stefanomartiradonna/claude-skills --skill user-stories-stefanomartiradonna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a feature into well-formed backlog items is slow and inconsistent when done ad hoc: stories end up too large, lack testable acceptance criteria, or mix multiple user journeys into one card. This Skill structures feature breakdowns so every story is independent, estimable, and testable. ## Core Features & Use Cases - 3 C's Framework: Structures each story as Card (title and one-liner), Conversation (intent discussion), and Confirmation (acceptance criteria). - INVEST Validation: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable, sized for one sprint. - Structured Output: Produces stories with title, role-based description, design link, and 4-6 testable acceptance criteria including edge cases and integration points. - Use Case: Given a new checkout feature and a Figma link, generate a complete set of sprint-ready user stories covering each distinct user journey. ## Quick Start Break down the new checkout feature for our e-commerce app into user stories using the Figma design at this link.

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?▼

Write each story as 'As a [user role], I want to [action], so that [benefit]', then add 4-6 testable acceptance criteria covering observable behavior, edge cases, and integration points. This Skill automates that structure using the 3 C's framework.

How to break down a feature into backlog items?▼

Identify distinct user roles and journeys within the feature, then create one story per journey following the INVEST criteria so each is independent and sized for a single sprint. Provide the feature description and design link to generate the full set.

What is the INVEST criteria for user stories?▼

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. Stories meeting these criteria can be developed in any order and completed within one sprint cycle.

What inputs does this user story generator need?▼

It accepts four arguments: the product name, the feature to break down, a link to design files such as Figma or Miro, and key assumptions or context. The design link is embedded in each generated story for visual reference.

When should I not split work into user stories?▼

User stories fit user-facing functionality with clear roles and benefits. Purely technical tasks like refactoring, infrastructure setup, or dependency upgrades are often better tracked as technical tasks or spikes rather than forced into the story format.

Related Skills

Explore More Product & Management Skills→
saranskumarsaranskumar

product

Plan and validate product features by defining user problems and writing user stories.

Community
Intermediate
rpmcdougallrpmcdougall

agile-project-manager

Generates user stories, sprint plans, backlog priorities, and retro action items for agile teams.

Community
Intermediate
misty-stepmisty-step
2

groom

Structure raw ideas into backlog.d items with defined context and scope.

Official
Advanced
jason23452jason23452

job-stories

Write Jobs-to-be-Done job stories with situation, motivation, and outcome.

Community
Basic