skills.rest
flpbalada
flpbaladaCOMMUNITY
Explore all skills by this author →
GitHub

user-story-fundamentals

Transform user requirements into structured user stories using the INVEST criteria.

23|4|Updated Jan 4, 2026
Search Tags:#requirements#backlog#invest#product-management#acceptance-criteria#user-story#story-splitting
One-click install
npx skills add https://github.com/flpbalada/thinking-toolkit --skill user-story-fundamentals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-fundamentals
Source: https://github.com/flpbalada/thinking-toolkit/tree/main/plugins/user-story-fundamentals/skills/user-story-fundamentals
Command: npx skills add https://github.com/flpbalada/thinking-toolkit --skill user-story-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture requirements from the user perspective using structured user stories, guiding backlog creation, acceptance criteria, prioritization, and clear communication between product and development.

Core Features & Use Cases

  • User Story Format: Use the standard template to articulate who, what, and why.
  • INVEST Criteria: Ensure independence, value, estimability, scoping, and testability.
  • Acceptance Criteria: Define specific, testable conditions for completion.
  • Use Case Scenarios: Break epics into granular stories for planning and delivery.
  • Use Case example: Writing a backlog item to define a feature and its success metrics.

Quick Start

Create a user story using the "As a [role], I want [goal], so that [benefit]" template and develop acceptance criteria using the INVEST checklist.

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 using the standard format?▼

To write a user story, use the 'As a [role], I want [goal], so that [benefit]' template to articulate who needs the feature, what they want to achieve, and the expected value.

What is the INVEST criteria for backlog items?▼

INVEST criteria ensures backlog items are Independent, Negotiable, Valuable, Estimable, Small, and Testable, helping teams validate that user stories are well-scoped and ready for development.

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

Define acceptance criteria by establishing specific, testable conditions that a user story must meet for completion, ensuring clear communication of feature success metrics between product and development teams.

What is the best way to split large epics into granular user stories?▼

Break epics into granular user stories by applying the INVEST checklist to each backlog item, ensuring they are appropriately scoped for planning and delivery while maintaining user perspective.

When do I need structured user stories for product management?▼

You need structured user stories when capturing requirements from the user perspective for backlog creation, prioritization, and aligning product goals with development execution through clear communication.

Related Skills

Explore More Product & Management Skills→
ryan-mtryan-mt
3

product-marketing-context

Create and update product marketing context documents from codebases and user input.

Community
Advanced
vndkubivndkubi

sprint-planning

Decompose PBIs into technical tasks and estimate effort using Fibonacci or T-shirt sizes.

Community
Intermediate
nicepkgnicepkg
276

agile

Guide Agile product management with Scrum, Kanban, and SAFe practices.

Official
Advanced
yuvarajd85yuvarajd85
1

generate-tech-spec

Translate natural-language workload descriptions into AWS technical specifications and architecture diagrams.

Community
Advanced