user-stories

Generate user stories with descriptions, design links, and acceptance criteria.

Updated Feb 6, 2026

Search Tags:#product management #acceptance criteria #agile #user stories #backlog #feature breakdown

Ready to run

npx skills add https://github.com/spandios/vibe-utils --skill user-stories-spandios

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/spandios/vibe-utils/tree/main/skills/user-stories
Command: npx skills add https://github.com/spandios/vibe-utils --skill user-stories-spandios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

User Story Generation: Creates user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria.
Structured Output: Includes descriptions, design links, and acceptance criteria.
Use Case: When breaking down a new feature for a mobile banking app, use this Skill to generate user stories for the "transfer funds" functionality, ensuring each story is independent, valuable, and testable.

Quick Start

Use the user-stories skill to generate user stories for the 'user authentication' feature, linking to the design document at 'http://example.com/design/auth'.

Frequently Asked Questions about user-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate user stories that follow INVEST criteria for agile backlog refinement?▼

Generate user stories adhering to INVEST criteria by breaking down software features into granular work items. The output includes structured descriptions, design links, and testable acceptance criteria, ensuring each story is independent and valuable for agile backlog refinement.

What are the 3 C's in user story generation and how do they structure agile work items?▼

The 3 C's in user story generation are Card, Conversation, and Confirmation. They structure agile work items by producing a card with the story description, facilitating conversation via design links, and providing confirmation through detailed testable acceptance criteria.

How do I write acceptance criteria when breaking down a new software feature?▼

Write acceptance criteria during feature breakdown by generating user stories with built-in confirmation steps. The process outputs structured testable acceptance criteria alongside story descriptions and design links to ensure development teams have clear, actionable definitions of done.

Can I include design document links when creating user stories for product management?▼

Yes, you can include design document links when creating user stories for product management. The generated stories support structured output that incorporates external design links directly into the story card alongside the description and acceptance criteria.

What is the best way to ensure agile user stories are testable and independent?▼

The best way to ensure agile user stories are testable and independent is applying INVEST criteria during feature breakdown. This generates granular stories containing clear descriptions and specific acceptance criteria, facilitating clear confirmation for development teams.