user-stories

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/bowiemax/pm-skills --skill user-stories-bowiemax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/bowiemax/pm-skills/tree/main/pm-execution/skills/user-stories
Command: npx skills add https://github.com/bowiemax/pm-skills --skill user-stories-bowiemax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of user stories, ensuring they are well-defined, actionable, and adhere to best practices for agile development.

Core Features & Use Cases

  • 3 C's Framework: Generates stories following Card, Conversation, and Confirmation.
  • INVEST Criteria: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • Acceptance Criteria: Defines clear, testable conditions for story completion.
  • Use Case: When a new feature like "user profile editing" is defined, this skill can break it down into multiple, well-formed user stories for the development backlog.

Quick Start

Use the user-stories skill to create user stories for the 'shopping cart' feature, linking to the provided Figma designs.

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 that include clear acceptance criteria?

Generate user stories with clear acceptance criteria by applying the 3 C's framework and INVEST criteria to define testable conditions, detailed descriptions, and comprehensive development goals for product features.

What is the best way to break down product features into agile backlog items?

Break down product features into agile backlog items by generating manageable user stories that follow INVEST criteria, ensuring each item is independent, valuable, estimable, and small enough for development.

How does the 3 C's framework apply to scrum user stories?

The 3 C's framework structures scrum user stories by using Card for the basic description, Conversation for linking design assets, and Confirmation for establishing comprehensive acceptance criteria.

Can I link design assets like Figma files directly to a user story?

Link design assets like Figma files directly within user stories as part of the Conversation component, providing developers with immediate access to visual references during implementation.

Why should I use INVEST criteria when creating a product backlog?

Using INVEST criteria when creating a product backlog ensures user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable, making them actionable and well-defined for agile development.

Does this user story generation method work for complex feature breakdowns?

This user story generation method works for complex feature breakdowns by splitting large product features into multiple well-formed stories, ensuring manageable backlog items and clear development goals.