Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

user-stories — Claude Code skill: what it does, how to install

This skill turns a feature brief into independent user stories with design links and acceptance criteria. Use it when shaping a backlog.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add phuryn/pm-skills --skill user-stories -a claude-code
Open on GitHub

What user-stories does

The skill breaks a new feature into user stories by identifying user roles and distinct journeys. Each story follows the 3 C's: Card, Conversation, and Confirmation. The output includes a title, a user-focused description, a design link, and testable acceptance criteria.

It applies the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable. The process uses plain language, incorporates the supplied context, and links stories to design files for visual reference. You can provide a product or system name, the feature to split, a design link, and key assumptions.

Prepare the design link and context before running it. Otherwise, the story details will be based on the feature description alone.

What it helps with

  • split a feature into independent user stories
  • describe requirements from each user role's perspective
  • attach design references to backlog items
  • write observable acceptance criteria
  • check stories against the INVEST criteria

Example prompts for the agent

  • Use `user-stories` to break `$FEATURE` for `$PRODUCT` into independent user stories.
  • Create stories for `$FEATURE` using the design link `$DESIGN` and the assumptions `$ASSUMPTIONS`.
  • Apply the 3 C's and INVEST to this feature, then add descriptions and acceptance criteria.

How to install user-stories

1Skills CLI (Vercel)

npx skills add phuryn/pm-skills --skill user-stories -a claude-code

2Manually: put the files in place

~/.claude/skills/user-stories/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/user-stories/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Similar

ralph snarktank Turns an existing PRD into prd.json for the Ralph autonomous agent system. Use it when requirements need to become small, verifiable stories. Claude Code CX Codex Cursor +1 887installs gitnexus-cli abhigyanpatwari This skill runs GitNexus commands to index a repository, inspect index status, clean stored data, and generate a wiki. Use it when an agent needs project context. Claude Code CX Codex Cursor +1 866installs paseo-help getpaseo Answers questions about Paseo setup, connections, providers, logs, and failures. Use it when you need to understand the daemon, workspaces, or app configuration. Claude Code CX Codex Cursor +1 1,400installs ascii-art 0xbyt4, Hermes Agent Renders text banners, borders, speech bubbles and converts images to ASCII art using pyfiglet, cowsay, boxes and image converters. Claude Code CX Codex Cursor +1 423installs resume-quantifier Paramchoudhary A skill that spots resume bullets without numbers and helps estimate metrics when exact data is missing. Useful when your experience section has no quantifiable results. Claude Code CX Codex Cursor +1 10,000installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. Claude Code Claude.ai 414,180installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs

Questions about user-stories

How do I install user-stories in Claude Code?

Run npx skills add phuryn/pm-skills --skill user-stories -a claude-code, then run npx skills add phuryn/pm-skills --skill user-stories -a claude-code again. The installed skill is available at ~/.claude/skills/user-stories/SKILL.md.

What does user-stories do?

It turns a feature brief into user stories with roles, descriptions, design links, and acceptance criteria. It also checks the stories against the 3 C's and INVEST.

What should I provide to user-stories?

Provide a product or system name, the feature to break down, a design link, and key assumptions. The skill uses them to analyze the feature and structure the stories.

Source text

SKILL.md · MIT
---
name: user-stories
description: "Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria."
---
# User Stories

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.

**Use when:** Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.

**Arguments:**
- `$PRODUCT`: The product or system name
- `$FEATURE`: The new feature to break into stories
- `$DESIGN`: Link to design files (Figma, Miro, etc.)
- `$ASSUMPTIONS`: Key assumptions or context

## Step-by-Step Process

1. **Analyze the feature** based on provided design and context
2. **Identify user roles** and distinct user journeys
3. **Apply 3 C's framework:**
   - Card: Simple title and one-liner
   - Conversation: Detailed discussion of intent
   - Confirmation: Clear acceptance criteria
4. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable
5. **Use plain language** a primary school graduate can understand
6. **Link to design files** for visual reference
7. **Output user stories** in structured format

## Story Template

**Title:** [Feature name]

**Description:** As a [user role], I want to [action], so that [benefit].

**Design:** [Link to design files]

**Acceptance Criteria:**
1. [Clear, testable criterion]
2. [Observable behavior]
3. [System validates correctly]
4. [Edge case handling]
5. [Performance or accessibility consideration]
6. [Integration point]

## Example User Story

**Title:** Recently Viewed Section

**Description:** As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.

**Design:** [Figma link]

**Acceptance Criteria:**
1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
2. It is not displayed for users visiting the first product page of their session.
3. The current product itself is excluded from the displayed items.
4. The section showcases product cards or thumbnails with images, titles, and prices.
5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
6. Clicking on a product card leads the user to the corresponding product page.

## Output Deliverables

- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation

---

### Further Reading

- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)

© phuryn · MIT · phuryn/pm-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor