skills.rest
Choi-Keith
Choi-KeithCOMMUNITY
Explore all skills by this author →
GitHub

user-stories

Creates user stories following the 3C and INVEST standards with acceptance criteria.

Updated Aug 10, 2026
Search Tags:#product management#acceptance criteria#agile#user stories#backlog#invest#feature decomposition
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill user-stories-choi-keith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-execution/skills/user-stories
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill user-stories-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often struggle to break features into well-structured, sprint-ready user stories with clear acceptance criteria, leading to ambiguous requirements and misaligned engineering work. ## Core Features & Use Cases - 3C Framework Application: Structures each story as Card (title and one-line description), Conversation (intent discussion), and Confirmation (acceptance criteria). - INVEST Validation: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. - Structured Story Template: Outputs stories with title, role-based description, design file links (Figma, Miro), and 4-6 testable acceptance criteria. - Use Case: Given a new checkout feature and a Figma link, generate a complete set of independent user stories, each sized for a single sprint and covering edge cases like first-time visitors and integration points. ## Quick Start Ask the agent to break down your feature into user stories by providing the product name, the feature to split, a design file link, and any key assumptions.

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

Structure each story with a title, a description in the format 'As a [role], I want [action], so that [value]', a design link, and 4-6 testable acceptance criteria. Apply the 3C framework (Card, Conversation, Confirmation) to keep stories complete.

What is the INVEST criteria for user stories?▼

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. Each story should be developable in any order, sized to fit one sprint, and verifiable through clear acceptance criteria.

How do I split a large feature into user stories?▼

Analyze the feature against its design files, identify distinct user roles and journeys, then create one story per journey segment. Each resulting story should be independent and small enough for a single sprint.

What inputs are needed to generate user stories?▼

Provide the product name, the feature to decompose, a link to design files such as Figma or Miro, and any key assumptions or context. The output includes stories with descriptions, design references, and acceptance criteria.

When should I not use user stories for requirements?▼

User stories are less suitable for non-functional requirements like infrastructure changes or technical debt work with no user-facing value. In those cases, use technical tasks or spikes instead of role-based story formats.

Related Skills

Explore More Product & Management Skills→
dain-agencydain-agency

ux-discovery-questions

Generate structured user discovery question packs for interviews and surveys.

Official
Basic
DauQuangThanhDauQuangThanh
14

project-planning

Plan software projects into epics, user stories, and sprint backlogs.

Community
Advanced
lostitonce420-beeplostitonce420-beep

product-manager

Generate PRDs, user stories, and roadmaps for product planning.

Community
Intermediate
wfukatsuwfukatsu
12

generate-persona

Generate job-to-be-done personas with job stories and persona cards.

Community
Intermediate