user-story-fundamentals

Write user stories and acceptance criteria using INVEST and prioritization methods.

5|Updated Oct 17, 2011

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

Ready to run

npx skills add https://github.com/klen/dotfiles --skill user-story-fundamentals-klen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story-fundamentals
Source: https://github.com/klen/dotfiles/tree/main/.config/opencode/skills/user-story-fundamentals
Command: npx skills add https://github.com/klen/dotfiles --skill user-story-fundamentals-klen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you define and refine product requirements from a user's perspective, ensuring clarity and focus in development.

Core Features & Use Cases

User Story Format: Learn the standard "As a [user], I want [goal], so that [benefit]" structure.
INVEST Criteria: Ensure stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Acceptance Criteria: Define clear, testable conditions for story completion.
Prioritization: Understand methods like RICE and MoSCoW.
Story Splitting: Techniques to break down large stories into manageable pieces.
Use Case: When writing backlog items for a new feature, use this Skill to structure each requirement as a user story with clear acceptance criteria, making it easy for the development team to understand and estimate.

Quick Start

Use the user-story-fundamentals skill to write a user story for a new feature.

Frequently Asked Questions about user-story-fundamentals

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

FAQPage Schema

How do I write effective user stories for my product backlog?▼

To write effective user stories, use the standard format: "As a [user], I want [goal], so that [benefit]." This structure ensures clarity and focuses development on delivering value from the user's perspective.

What are the INVEST criteria for agile user stories?▼

The INVEST criteria for agile user stories ensure each item is Independent, Negotiable, Valuable, Estimable, Small, and Testable. Applying this framework guarantees your backlog items are well-defined and ready for development.

How do I split large user stories into manageable pieces?▼

To split large user stories, apply specific story splitting techniques to break them down into smaller, manageable pieces. This ensures your backlog items remain estimable and testable for the development team.

What is the best way to prioritize product backlog items?▼

The best way to prioritize product backlog items is using methods like RICE or MoSCoW. These prioritization frameworks help evaluate requirements and rank user stories based on their value and urgency.

How do I define acceptance criteria for a user story?▼

To define acceptance criteria for a user story, establish clear, testable conditions for story completion. This provides the development team with exact requirements needed to estimate and verify the feature.