Agent skill

user-story-splitting

Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill user-story-splitting --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/user-story-splitting/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Purpose Break down large user stories, epics, or features into smaller, independently deliverable stories using systematic splitting patterns. Use this to make work more manageable, reduce risk, enable faster feedback cycles, and maintain flow in agile development. This skill applies to user stories, epics, and any work that's too large to complete in a single sprint. This is not arbitrary slicing—it's strategic decomposition that preserves user value while reducing complexity. ## Input **Works best with:** The story or epic that's too big — paste it as written. **Also useful:** Why it's too big (can't estimate, can't finish in a sprint, can't release independently) and your team's sizing ceiling. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks for the story text, then walks the split patterns against it. **Example invocation:** `Split this: 'As an admin, I can bulk-import users from CSV, Excel, or our HR system with field mapping and error handling.'` ## Ke

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. The Story Splitting Framework
  5. Why Split Stories?
  6. Anti-Patterns (What This Is NOT)
  7. When to Use This
  8. When NOT to Use This
  9. Application
  10. Step 1: Identify the Original Story
  11. Step 2: Apply the Splitting Logic
  12. Step 3: Write the Split Stories
  13. Step 4: Validate the Splits
  14. Examples
Ships with 2 files
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the user-story-splitting skill do?

Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill user-story-splitting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going