skills.rest
officebeats
officebeatsCOMMUNITY
Explore all skills by this author →
Website𝕏@officebeatsGitHub

user-stories

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

8|1|Updated Dec 28, 2025
Search Tags:#product management#acceptance criteria#agile#user stories#backlog#feature breakdown
One-click install
npx skills add https://github.com/officebeats/beats-pm-kit --skill user-stories-officebeats
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/officebeats/beats-pm-kit/tree/main/.agent/skills/user-stories
Command: npx skills add https://github.com/officebeats/beats-pm-kit --skill user-stories-officebeats

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, follow best practices, and include all necessary components for development.

Core Features & Use Cases

  • 3 C's Framework: Generates stories based on 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 breaking down a new feature like "user profile editing" into manageable backlog items, this Skill helps generate individual user stories with detailed acceptance criteria and links to relevant Figma designs.

Quick Start

Use the user-stories skill to generate user stories for the new user profile editing feature, linking to the Figma designs at https://figma.com/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 for agile feature breakdown?▼

To write user stories for agile feature breakdown, generate them using the 3 C's framework (Card, Conversation, Confirmation) and INVEST criteria. This ensures each story includes clear descriptions, design links, and testable acceptance criteria.

What is the best way to structure backlog items using INVEST criteria?▼

Structuring backlog items using INVEST criteria means ensuring stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This approach creates well-defined items with necessary components for development readiness.

Can I include design links like Figma URLs when generating agile user stories?▼

Yes, you can include design links like Figma URLs when generating agile user stories. The structured output format supports attaching design references directly to individual stories for comprehensive feature breakdown.

How does the 3 C's framework work for defining product management user stories?▼

The 3 C's framework works by structuring product management user stories into Card, Conversation, and Confirmation. This defines the story description, facilitates ongoing dialogue, and establishes clear confirmation through testable acceptance criteria.

Do I need plain language for user story generation and backlog definition?▼

Yes, plain language is required for user story generation and backlog definition. Adhering to plain language ensures structured output formats remain clear, actionable, and easily understood by both development and business stakeholders.

Related Skills

Explore More Product & Management Skills→
abhishekchoudhariabhishekchoudhari
1

user-stories

Create user stories using 3 C's and INVEST criteria.

Community
Intermediate
co-cddoco-cddo

Scrum Master

Break epics into user stories with acceptance criteria and Fibonacci story points.

Official
Basic
grandcamelgrandcamel
42

jira-agile-management

Manage Jira Agile workflows for epics, sprints, backlogs, and story points.

Community
Intermediate
AZANIRAZANIR
2

qa-spec-writer

Transform requirements into technical specifications with Gherkin acceptance criteria.

Community
Intermediate