skills.rest
7a336e6e
7a336e6eCOMMUNITY
Explore all skills by this author →
GitHub

Defining User Stories

Translate high-level product requirements into user stories with acceptance criteria.

1|2|Updated Feb 5, 2026
Search Tags:#requirements#product management#acceptance criteria#agile#user stories
One-click install
npx skills add https://github.com/7a336e6e/skills --skill defining-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Defining User Stories
Source: https://github.com/7a336e6e/skills/tree/main/product/defining-user-stories
Command: npx skills add https://github.com/7a336e6e/skills --skill defining-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms high-level requirements into clear, actionable user stories with defined acceptance criteria, ensuring everyone understands what needs to be built and why.

Core Features & Use Cases

  • User Story Formulation: Crafts stories using the standard "As a <role>, I want to <action>, So that <value>" format.
  • INVEST Compliance: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • Acceptance Criteria: Defines clear, testable conditions for story completion.
  • Use Case: After a product manager outlines a new feature for a mobile app, this Skill helps break it down into specific user stories like "As a registered user, I want to reset my password via email, so that I can regain access to my account if I forget it."

Quick Start

Use the defining user stories skill to create a user story for the new login feature.

Frequently Asked Questions about Defining User Stories

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

FAQPage Schema
How do I write user stories from product requirements?▼

Translating product requirements into user stories involves structuring features using the standard format: "As a <role>, I want to <action>, so that <value>." This ensures development teams understand what to build and why.

What are acceptance criteria in agile user stories?▼

Acceptance criteria in agile user stories are clear, testable conditions that define when a story is complete. They ensure features are testable and valuable before development begins.

How does the INVEST criteria apply to user story management?▼

The INVEST criteria ensures user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. Applying INVEST facilitates agile development by keeping stories actionable and well-defined.

Can I use this to break down a large feature into smaller agile stories?▼

Yes, breaking down large features into smaller agile stories is supported. The process ensures each story is small, estimable, and independent, adhering to INVEST principles for effective story management.

What is the best way to format user stories for agile development?▼

The best way to format user stories for agile development is using the "As a <role>, I want to <action>, So that <value>" structure, paired with defined acceptance criteria to ensure they are testable.

Related Skills

Explore More Product & Management Skills→
wpankwpank
11

feature-specification

Convert persona documentation into feature specifications with acceptance criteria and user stories.

Community
Intermediate
SynkraAISynkraAI
3.1k

aiox-po

Manage product backlogs, refine user stories, and support sprint planning decisions.

Official
Intermediate
foomakersfoomakers
6

refine-story

Refine user stories by adding acceptance criteria and technical analysis.

Official
Advanced
w95w95
145

prd-writer

Generate structured Product Requirements Documents with user stories and prioritization frameworks.

Community
Advanced