user-stories

User Stories - Intelligent User Story Generator

Skill Overview

The User Stories skill automatically generates structured user stories based on the 3C principles and INVEST criteria. Each story includes a description, design link, and acceptance criteria, helping product managers and agile teams quickly convert feature requirements into actionable stories.

Applicable Scenarios

Writing User Stories: When a product manager needs to convert a new feature into a standardized Story format, this skill can automatically generate a user story that follows the 3C framework based on the product name, feature description, and design link.

Feature Decomposition: During Sprint planning or requirements reviews, complex features can be broken down into multiple independent, estimable, and testable small stories. Each story can be completed within a single iteration.

Defining Acceptance Criteria: Generate 4–6 clear acceptance criteria for each user story, including edge-case handling, performance requirements, and integration points, ensuring that the development team understands the definition of “done.”

Core Features

3C Framework Generation: Automatically applies the three-layer structure of Card (card title), Conversation (detailed discussion), and Confirmation (acceptance confirmation). Each story includes a concise one-sentence description, contextual information, and testable acceptance criteria.

INVEST Criteria Validation: Ensures that each generated story is Independent, Negotiable, Valuable, Estimable, Small, and Testable.

Structured Output: Produces a complete format containing a title, description, design link, and 4–6 acceptance criteria. It supports integration with design tools such as Figma and Miro and can be used directly in project management tools such as Jira and Trello.

Frequently Asked Questions

What are the 3C principles of user stories?

The 3C principles were proposed by Ron Jeffries and refer to Card, Conversation, and Confirmation. Card is a one-sentence description of the story and serves as the starting point for team discussions. Conversation is the ongoing dialogue between the product manager and development team to clarify requirements and design details. Confirmation consists of explicit acceptance criteria that define the “done” state. This skill automatically generates all three layers for each story.

What does INVEST stand for?

INVEST is a set of criteria for high-quality user stories: Independent — stories do not depend on one another and can be developed in any order; Negotiable — details can be discussed and are not rigid contracts; Valuable — the story provides clear value to users or the business; Estimable — the team can assess the required effort; Small — the scope is small enough to be completed within a single Sprint; Testable — the story has clear acceptance criteria. This skill follows these principles during generation.

What elements should a user story contain?

A complete user story should include: a title (feature name), a description (As a [role], I want to [action], so that [value]), a design link (a visual design from Figma, Miro, or another tool), and acceptance criteria (4–6 testable conditions covering the normal flow, edge cases, performance requirements, integration points, and more). Based on the product name, feature description, and design link you provide, this skill automatically generates all of these elements.