All skills
deanpeters avatar

/user-story-splitting

@b68bf96

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.

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

This session only. Nothing lands on disk.

examplessample.md

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

User Story Splitting Examples

Example 1: Splitting by Workflow Steps

Original Story:

### User Story 100: Complete Checkout Process

**Use Case:**
- **As a** shopper
- **I want to** complete checkout, including entering shipping, payment, and confirming my order
- **so that** I can receive my items

**Acceptance Criteria:**
- **Given:** I have items in my cart
- **When:** I enter shipping address, payment info, and confirm
- **Then:** My order is placed

Why it needs splitting: Multiple workflow steps bundled together.

Split using Workflow Steps:

### Split 1: Enter Shipping Address

**User Story 101:**
- **Summary:** Enter shipping address during checkout

**Use Case:**
- **As a** shopper
- **I want to** enter my shipping address
- **so that** my items are delivered to the right location

**Acceptance Criteria:**
- **Given:** I have items in my cart
- **When:** I enter a valid shipping address and click "Continue"
- **Then:** I proceed to payment entry

---

### Split 2: Enter Payment Information

**User Story 102:**
- **Summary:** Enter payment info during checkout

**Use Case:**
- **As a** shopper
- **I want to** enter my credit card information
- **so that** I can pay for my order

**Acceptance Criteria:**
- **Given:** I have entered a shipping address
- **When:** I enter valid payment info and click "Continue"
- **Then:** I proceed to order confirmation

---

### Split 3: Confirm Order

**User Story 103:**
- **Summary:** Review and confirm order

**Use Case:**
- **As a** shopper
- **I want to** review my order details and confirm
- **so that** my order is placed

**Acceptance Criteria:**
- **Given:** I have entered shipping and payment info
- **When:** I review the order summary and click "Place Order"
- **Then:** My order is submitted and I receive a confirmation

Example 2: Splitting by Acceptance Criteria Complexity

Original Story:

### User Story 200: Manage Team Members

**Use Case:**
- **As a** team admin
- **I want to** manage team members
- **so that** I can control access

**Acceptance Criteria:**
- **When:** I add a member, Then they receive an invite
- **When:** I remove a member, Then they lose access
- **When:** I change a member's role, Then their permissions update

Why it needs splitting: Multiple "When/Then" statements.

Split using Acceptance Criteria Complexity:

### Split 1: Add Team Members

**User Story 201:**
- **Summary:** Invite new team members

**Use Case:**
- **As a** team admin
- **I want to** invite new members to my team
- **so that** they can access shared resources

**Acceptance Criteria:**
- **Given:** I have admin permissions
- **When:** I enter an email and click "Invite"
- **Then:** The recipient receives an email invitation

---

### Split 2: Remove Team Members

**User Story 202:**
- **Summary:** Remove team members

**Use Case:**
- **As a** team admin
- **I want to** remove members from my team
- **so that** they no longer have access

**Acceptance Criteria:**
- **Given:** I have admin permissions
- **When:** I click "Remove" next to a member's name
- **Then:** That member loses access immediately

---

### Split 3: Change Member Roles

**User Story 203:**
- **Summary:** Update team member roles

**Use Case:**
- **As a** team admin
- **I want to** change a member's role
- **so that** their permissions match their responsibilities

**Acceptance Criteria:**
- **Given:** I have admin permissions
- **When:** I select a new role for a member and save
- **Then:** Their permissions update to match the new role

Source: SKILL.md on GitHub

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

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
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