skilld
All skills
deanpeters avatar

/user-story-splitting

@b68bf96
by Dean Petersdeanpeters/product-manager-skills7.1k stars
851

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/user-story-splitting

This session only. Nothing lands on disk.

template.md

≈288 tokens on demand. Your agent reads this file only when SKILL.md points to it.

User Story Splitting Template

Use this template to split a large story into smaller, independently deliverable user stories.

Provenance

Adapted from prompts/user-story-splitting-prompt-template.md in the https://github.com/deanpeters/product-manager-prompts repo.

Splitting Logic (Use in Order)

  1. Workflow steps
  2. Business rule variations
  3. Data variations
  4. Acceptance criteria complexity (multiple When/Then pairs)
  5. Major effort milestones
  6. External dependencies
  7. DevOps steps
  8. Tiny Acts of Discovery (TADs) if none apply

Output Template

### Original Story
[Story written using `skills/user-story/template.md`]

### Suggested Splits
1. Split 1 using **[rule name]**:
   - [Left split story, using `skills/user-story/template.md`]
   - [Right split story, using `skills/user-story/template.md`]
2. Split 2 using **[rule name]**:
   - [Left split story]
   - [Right split story]
3. Split 3 using **[rule name]**:
   - [Left split story]
   - [Right split story]

Notes

  • Each split should deliver user value on its own.
  • If no rule applies, propose TADs to de-risk and clarify before writing stories.

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a framework and templates for product managers to break down large user stories and epics. It operates purely as a set of instructions for text analysis and does not contain any executable code, network operations, or sensitive data access patterns.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    3 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at b68bf96. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago

Capability

argument-hint
[story or epic to split]
type
component
theme
pm-artifacts
Other metadata
intent
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.
best_for
[
  "Breaking a story that's too big to estimate or finish in a sprint",
  "Applying proven split patterns instead of splitting by component",
  "Keeping each slice independently valuable and releasable"
]
scenarios
[
  "This story is too big for a sprint and splitting by frontend/backend isn't working",
  "Our backlog items keep carrying over — I need real split patterns"
]
estimated_time
15-25 min

README badge

README badge for deanpeters/product-manager-skills/user-story-splitting