Back to Skills
Specs

User Story Writer

Write clear user stories with acceptance criteria following the INVEST principles.

/user-story-writer

Time Saved

30 min → 5 min per story

Compared to doing it manually

Slash Command

/user-story-writer

Type this in Claude to run the skill

The Problem

User stories are either too big to estimate, too vague to test, or so detailed they constrain engineering creativity. Sprint planning grinds to a halt.

What You Get

  • ✓INVEST-validated stories
  • ✓BDD acceptance criteria (Given/When/Then)
  • ✓Edge cases identified
  • ✓Technical notes for engineering
  • ✓Out of scope explicitly stated
  • ✓Sprint-ready format
Want this automated?

This skill runs inside a workflow

Agent workflows chain multiple skills into one command.

Problem to PRD

Agent workflow

From problem statement to engineering-ready.

4 skills automated
3 hrs → 20 min

How to use this skill

  1. 1Download the skill file using the button on this page
  2. 2Add the file to your .claude/skills/ folder in your project
  3. 3Type /user-story-writer in Claude to run the skill

Best For

Backlog groomingSprint planningJunior PM trainingEngineering handoff

Related Skills

One-Pager Creator

/one-pager-creator

Create compelling one-page feature briefs that align stakeholders quickly.

Product Brief Writer

/product-brief-writer

Write one-page product briefs to get buy-in before investing in full specs.

Onboarding Flow Designer

/onboarding-flow-designer

Design onboarding flows that guide users to value quickly without being annoying.

Technical Spec Writer

/technical-spec-writer

Write technical specifications with architecture, data models, and API designs.

Frequently Asked Questions

A user story is a short description of a feature from the user's perspective: "As a [user type], I want [goal] so that [benefit]." It focuses on user value, not implementation details.

Detailed enough to estimate and build, but not so detailed they become specs. Include acceptance criteria (how you'll know it's done) but leave implementation decisions to engineering.

A user story describes user value ("As a user, I want to reset my password"). Tasks are implementation steps ("Add forgot password link", "Create reset email template"). Stories are split into tasks during sprint planning.

Good acceptance criteria are testable, specific, and user-focused. Use "Given/When/Then" format: "Given I'm logged out, when I click forgot password, then I receive a reset email within 5 minutes."

View Workflow →