user-story-fundamentals

Name: user-story-fundamentals
Availability: InStock
Author: Suwandre

Capture requirements using structured user stories with acceptance criteria.

Updated Apr 26, 2026

Search Tags:#requirements #backlog #invest #product-management #acceptance-criteria #story-template #user-story

Ready to run

npx skills add https://github.com/suwandre/my-opencode-config --skill user-story-fundamentals-suwandre

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture requirements from the user perspective using structured user stories to guide backlog items, acceptance criteria, prioritization, and cross-functional communication between product and development.

Core Features & Use Cases

Structured User Stories: provide a consistent template to articulate WHO, WHAT, and WHY.
Acceptance Criteria Guidance: define clear, testable criteria to validate completion.
Story Splitting & Prioritization: techniques to break epics into actionable tasks and rank work by value.

Quick Start

Write a single user story in the format 'As a [user], I want [goal], so that [benefit]' and attach clear acceptance criteria.

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 a user story for my product backlog?▼

To write a user story for your product backlog, use the standard format: 'As a [user], I want [goal], so that [benefit].' This structure captures the who, what, and why from the user's perspective to guide development.

What is the INVEST criteria for user stories?▼

The INVEST criteria is a quality checklist for user stories, ensuring they are Independent, Negotiable, Valuable, Estimable, Small, and Testable. Applying these criteria helps maintain a high-quality, actionable backlog.

How do I split large epics into actionable user stories?▼

You can split large epics into actionable user stories by applying practical story splitting techniques. This process breaks broad requirements into smaller, testable backlog items that deliver distinct value.

How do I write clear acceptance criteria for a backlog item?▼

Clear acceptance criteria for a backlog item are defined by outlining specific, testable conditions that validate the story's completion. This ensures the development team and product management share a clear definition of done.

When should I use user stories instead of detailed requirements documents?▼

Use user stories instead of detailed requirements documents when you need to capture requirements from the user perspective and foster cross-functional communication. They articulate the who, what, and why without overwhelming the backlog.