user-stories

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

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill user-stories-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/moonzff/Codex_up/tree/main/skills/product-planning/user-stories
Command: npx skills add https://github.com/moonzff/Codex_up --skill user-stories-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a feature into well-formed backlog items is slow and inconsistent when done ad hoc. This Skill turns a feature description, design reference, and product context into structured user stories that follow the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, so teams get sprint-ready stories with clear acceptance criteria. ## Core Features & Use Cases - Structured Story Generation: Produces stories with title, role-based description, design link, and 4-6 testable acceptance criteria. - Framework Enforcement: Applies the 3 C's and INVEST criteria so stories are independent, estimable, and sized for one sprint. - Use Case: Given a new checkout feature and a Figma link, generate a complete set of user stories covering each user journey, ready to paste into a backlog tool. ## Quick Start Ask the assistant to break down your feature into user stories using the 3 C's and INVEST criteria, providing the feature description and design 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?▼

Use the 3 C's framework: a Card with a simple title, a Conversation describing intent as 'As a [role], I want [action], so that [benefit]', and Confirmation with 4-6 testable acceptance criteria. Validate each story against INVEST criteria before adding it to the backlog.

What are 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, sized for one sprint, and verified through clear acceptance criteria.

How many acceptance criteria should a user story have?▼

This workflow recommends 4-6 acceptance criteria per story, covering observable behavior, system validation, edge cases, performance or accessibility, and integration points. Each criterion must be clear and testable.

When should I not split a feature into user stories?▼

Avoid splitting when the feature is already small enough for one sprint or when splitting would create dependent stories that cannot be developed independently. INVEST's Independent and Small criteria guide this decision.