# User Story

> Write role-based user stories from an agreed product definition.

- Skill: `irwebtools/user-story` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add irwebtools/user-story`
- Raw SKILL.md: https://api.skillmd.com/api/skills/irwebtools/user-story/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: irwebtools (https://skillmd.com/u/irwebtools)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/irwebtools/user-story

---


# user-story

## When to use

Use when the task matches: user-story, user stories, as a user.

## Purpose

Break product intent into stories Development and AI can implement.

## Inputs

- Feature brief
- Users in scope
- Business rules

## Process

1. Write stories as role + need + outcome.
2. Keep one primary outcome per story.
3. Mark priority and dependencies between stories.
4. Exclude technical tasks disguised as stories.

## Outputs

- User stories
- Story priority notes
- Out-of-scope story list

## Verification

- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.

## Restrictions

- Do not encode architecture choices inside stories.
- Do not invent personas without Product agreement.
- Do not skip acceptance-criteria linkage.