user-stories

Generate structured user stories with 3 C's and INVEST criteria.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/cano721/ai-harness --skill user-stories-cano721
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/cano721/ai-harness/tree/main/teams/planning/bundle-claude/skills/user-stories
Command: npx skills add https://github.com/cano721/ai-harness --skill user-stories-cano721

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to craft consistent, sprint-ready user stories that align with product goals, acceptance criteria, and design references.

Core Features & Use Cases

  • Generates structured user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria.
  • Produces a Title, Description, Design link, and clear Acceptance Criteria for each story.
  • Useful for backlog grooming, feature breakdown, and defining testable criteria across teams.

Quick Start

Generate a complete, sprint-ready set of user stories for the given product and feature using the 3 C's and INVEST criteria, including design links and acceptance criteria.

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 are ready for sprint planning?

Sprint-ready user stories require structured narratives using the 3 C's framework and INVEST criteria. Each story must include a title, description, design link, and testable acceptance criteria to ensure it is independent and immediately ready for development.

What is the 3 C's framework for backlog creation and feature breakdown?

The 3 C's framework structures user stories into Card, Conversation, and Confirmation. Applying this to feature breakdown produces clear titles, descriptive narratives, and testable acceptance criteria that align with product goals and design references.

How do I add testable acceptance criteria to product backlog items?

Acceptance criteria for product backlog items are defined during story confirmation. Applying the INVEST criteria ensures each generated story receives clear, testable conditions that verify the feature meets product requirements and design links.

Can I generate independent user stories that can be developed in any order?

Yes, generating independent user stories is achieved by applying the INVEST criteria during feature breakdown. This process ensures stories are sprint-sized, self-contained, and can be developed in any order while linking to relevant design documentation.

What is the best way to link design references to user stories?

The best way to link design references is to include a dedicated design link field within each story's structure. Generating stories with the 3 C's framework ensures design documentation is explicitly connected to the narrative and acceptance criteria.