User Story Writing

Takes the guesswork out of writing user stories by giving you templates and acceptance criteria patterns that actually work. Covers the full lifecycle from breaking down requirements to story splitting and estimation. The Gherkin-style Given/When/Then format keeps acceptance criteria testable, and the reference guides show you how to handle common situations like splitting oversized stories or refining vague requirements. Honest take: the best part is the DO/DON'T list that saves you from common mistakes like writing task-focused stories or skipping edge cases. If you're setting up a product backlog or planning sprints, this gives you a repeatable structure that keeps stories small, clear, and actually shippable in one iteration.

skills.sh installs: 793
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill user-story-writing --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Well-written user stories communicate requirements in a user-focused way, facilitate discussion, and provide clear acceptance criteria for developers and testers.

When to Use

Breaking down requirements into development tasks
Product backlog creation and refinement
Agile sprint planning
Communicating features to development team
Defining acceptance criteria
Creating test cases

Quick Start

Minimal working example:

# User Story Template

**Title:** [Feature name]

**As a** [user role/persona]
**I want to** [action/capability]
**So that** [business value/benefit]

---

## User Context

- User Role: [Who is performing this action?]
- User Goals: [What are they trying to accomplish?]
- Use Case: [When do they perform this action?]

---

## Acceptance Criteria

Given [precondition]
When [action]
Then [expected result]

Example:
// ... (see reference guides for full implementation)