# User Story Writing

> Write effective user stories and acceptance criteria that communicate intent, value, and testable outcomes to delivery teams. Use when breaking work into backlog items, refining stories, or improving collaboration between product, design, and engineering.

- Skill: `itsual/user-story-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add itsual/user-story-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/user-story-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/itsual/user-story-writing

---


# User Story Writing

## Overview

User stories are a lightweight way to express desired outcomes from a user’s perspective. They work best when paired with clear acceptance criteria and conversation.

## When to Use

- Building and refining a product backlog
- Sprint or iteration planning inputs
- Aligning on what “done” means for a piece of value

## Format Guidance

**Story**  
As a [type of user], I want [goal] so that [benefit].

**Acceptance Criteria**  
- Prefer Given / When / Then or clear checklist-style criteria
- Cover happy path and important edge cases
- Make criteria testable and unambiguous

## Principles

- Focus on user value, not implementation detail
- Keep stories small enough to complete in a reasonable cycle
- Acceptance criteria define “done,” not the design solution
- Stories are prompts for conversation, not legal contracts
- Include non-functional needs when they matter (performance, accessibility, security)

## Verification

- [ ] The story describes value for a real user
- [ ] Acceptance criteria are testable
- [ ] Scope is small enough to discuss and deliver incrementally