πŸ“
WritingJavaScript

User Stories

by product-on-purpose

User Stories is a Writing skill for Claude Code, published by product-on-purpose in pm-skills.

565 stars74 forkson product-on-purpose/pm-skillsAdded 2026/08/25+3% in starsRepository updated 2026/08/25
agent-skillsagentskillsai-skillsclaude-codeclaude-desktopcodexdesign-sprintfoundation-sprintopenskillsproduct-managementskill-familiestriple-diamond
Install in seconds
Install User Stories
Copy User Stories into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-user-stories ~/.claude/skills/deliver-user-stories

Requires Node.js. Downloads this skill only β€” not the rest of the repository β€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/product-on-purpose/pm-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/deliver-user-stories/SKILL.md in product-on-purpose/pm-skills
Installs to
~/.claude/skills/deliver-user-stories
Collection
One of 25 skills cataloged from this repository
Category
Writing β€” 1012 skills

What User Stories does

User Stories generates persona-based user stories from product requirements or feature descriptions. Use it when breaking work into sprint items, writing engineering tickets, or communicating scope.

User Stories is cataloged under Writing on DirSkills. User Stories comes from a repository tagged agent-skills, agentskills, ai-skills, claude-code and claude-desktop.

Documentation

README

User Stories

User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.

When to Use

  • After PRD approval, when breaking down features for implementation
  • During sprint planning to create actionable work items
  • When writing tickets for engineering teams
  • When communicating requirements to stakeholders in accessible terms
  • When prioritizing a backlog based on user value

This is the opening of the README. Read the full README on GitHub.

Frequently asked about User Stories

  • What else does product-on-purpose publish alongside User Stories?

    User Stories is one of 25 skills that DirSkills catalogs from product-on-purpose/pm-skills, the repository it ships in. Its siblings there include Acceptance Criteria, Architecture Decision Record and Build Risk Review. Each one is a separate skill with its own page in this directory, installs the same way User Stories does, and is maintained by product-on-purpose in that same repository. The rest of the collection is listed on the product-on-purpose/pm-skills page.

  • How does User Stories compare to other Writing skills?

    User Stories ranks #715 by stars among the 1012 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of User Stories against them. Open each page to compare what they document and how they install.

More from product-on-purpose/pm-skills

User Stories is one of 25 skills cataloged on DirSkills from product-on-purpose/pm-skills.

See all 25 skills β†’
βœ…
6d ago

Acceptance Criteria

Acceptance Criteria generates testable Given/When/Then scenarios for a user story or feature slice. Use it when turning requirements into engineering handoff and QA sign-off criteria.
Quality
56574
πŸ“
6d ago

Architecture Decision Record

Architecture Decision Record documents a significant technical decision, its context, and consequences. Use it when choosing architecture, technology, or development patterns that future teams need to understand.
Writing
56574
🧭
6d ago

Build Risk Review

Build Risk Review names the single assumption most likely to make a product idea, feature request, or scope change fail, then returns a verdict and a no-code validation step. Use it before committing build effort or writing a PRD.
AI Engineering
56574
πŸ“Š
6d ago

Competitive Analysis

Competitive Analysis creates a structured comparison of 3-5 competitors across features, pricing, positioning, and strengths. Use it before entering a market, planning differentiation, or after losing deals.
Writing
56574
πŸ—ΊοΈ
6d ago

Customer Journey Map

Customer Journey Map maps a customer experience across stages, touchpoints, emotions, pain points, and moments of truth. Use it when synthesizing research into an end-to-end or phase-specific journey, and it refuses unsupported emotional or behavioral claims.
Data
56574
πŸ§ͺ
6d ago

Define Hypothesis

Define Hypothesis turns an assumption into a falsifiable statement with a target user, success metrics, and a validation approach. Use it before designing an experiment or A/B test to align on what success looks like.
AI Engineering
56574