user-story-writing

Create user stories with acceptance criteria and definitions of done.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/salesadriano/eventos --skill user-story-writing-salesadriano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-writing
Source: https://github.com/salesadriano/eventos/tree/main/.github/agents/skills/user-story-writing
Command: npx skills add https://github.com/salesadriano/eventos --skill user-story-writing-salesadriano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent, user-focused stories with clear acceptance criteria to guide development and ensure alignment between product goals and delivery.

Core Features & Use Cases

  • Template-driven storytelling: provides a standard format for user stories, acceptance criteria, Done criteria, and dependencies.
  • Refinement and splitting guidance: offers INVEST-based evaluation and actionable steps to break large stories into smaller pieces.
  • Process scaffolding: delivers best practices, notes, and guidance for backlog grooming, estimation, and sprint planning.

Quick Start

Create a complete user story using the standard template and clearly defined acceptance criteria.

Frequently Asked Questions about user-story-writing

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

FAQPage Schema
How do I write user stories with clear acceptance criteria for sprint planning?

To write user stories with clear acceptance criteria, apply a standard template that enforces a consistent format, documents the definition of done, and outlines actionable development tasks for sprint planning.

What is the best way to split large user stories in an agile backlog?

The best way to split large user stories in an agile backlog is through INVEST-aligned evaluation, which provides actionable refinement steps to break epics into smaller, testable pieces.

How does INVEST evaluation work for backlog refinement?

INVEST evaluation works for backlog refinement by assessing stories against Independent, Negotiable, Valuable, Estimable, Small, and Testable criteria to ensure they are ready for development.

What should be included in a user story template for feature scoping?

A user story template for feature scoping should include the core requirement, documented acceptance criteria, dependencies, and the definition of done to align product goals with delivery.

When do I need to apply story splitting tactics during product management?

Apply story splitting tactics during product management when a user story is too large for a single sprint, failing INVEST checks, or blocking estimation and feature scoping across product teams.