User story writing

Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/user-story-writing

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install

npx -y skills add ulpi-io/plugin-marketplace --skill user-story-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write effective user stories that capture requirements from the user's perspective. Create clear stories with detailed acceptance criteria to guide development and define done.

SKILL.md

2.6 KB, as published. Nobody here has run it

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)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
Story Refinement Process	Story Refinement Process
Acceptance Criteria Examples	Acceptance Criteria Examples
Story Splitting	Story Splitting
Story Estimation	Story Estimation

Best Practices

✅ DO

Write from the user's perspective
Focus on value, not implementation
Create stories small enough for one sprint
Define clear acceptance criteria
Use consistent format and terminology
Have product owner approve stories
Include edge cases and error scenarios
Link to requirements/business goals
Update stories based on learning
Create testable stories

❌ DON'T

Write technical task-focused stories
Create overly detailed specifications
Write stories that require multiple sprints
Forget about non-functional requirements
Skip acceptance criteria
Create dependent stories unnecessarily
Write ambiguous acceptance criteria
Ignore edge cases
Create too large stories
Change stories mid-sprint without discussion