user-story-fundamentals

Name: user-story-fundamentals
Availability: InStock
Author: abhilash-nandkumar

Capture user requirements into structured user stories with acceptance criteria.

Updated Nov 8, 2022

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

Ready to run

npx skills add https://github.com/abhilash-nandkumar/dot_config --skill user-story-fundamentals-abhilash-nandkumar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture requirements from the user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.

Core Features & Use Cases

Structured storytelling format: As a user, I want ... so that ...
INVEST-aligned acceptance criteria and story splitting guidance
Quick-start templates to jumpstart backlog creation and refinement

Quick Start

Write a user story in the standard format: As a [user], I want [goal], so that [benefit], and include explicit 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 structured user stories for my product backlog?▼

To write a user story, use the standard format: As a [user], I want [goal], so that [benefit]. This captures requirements from the user perspective and ensures cross-team alignment between product and development.

What is the INVEST principle for acceptance criteria in story splitting?▼

The INVEST principle guides acceptance criteria specification and story splitting to ensure backlog items are Independent, Negotiable, Valuable, Estimable, Small, and Testable. It helps structure story specs that align product and engineering teams.

How do I define acceptance criteria for a feature definition?▼

Define acceptance criteria by attaching explicit, testable conditions to your structured user stories. This formalizes feature definition and ensures cross-team alignment by clarifying exactly when a story meets product requirements.

Can I use this approach for story splitting when a backlog item is too large?▼

Yes, you can apply INVEST-aligned story splitting guidance to break down large backlog items. This refines the structured user stories into smaller, estimable specs that maintain clear user value and testable acceptance criteria.

What is the best way to format user requirements for cross-team alignment?▼

The best way to format user requirements for cross-team alignment is structuring them as user stories. Using the As a... I want... so that... format with explicit acceptance criteria ensures product, design, and engineering share a clear understanding.