user-story-decomposition

Decomposes epics and large user stories into atomic, testable capabilities using 8 splitting patterns.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/eencinasq/cripto-pos --skill user-story-decomposition-eencinasq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-decomposition
Source: https://github.com/eencinasq/cripto-pos/tree/main/.kiro/skills/user-story-decomposition
Command: npx skills add https://github.com/eencinasq/cripto-pos --skill user-story-decomposition-eencinasq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large epics and oversized user stories are hard to estimate, test, and deliver incrementally. This Skill breaks them down into atomic, independently valuable capabilities so product teams can plan sprints with clear acceptance criteria. ## Core Features & Use Cases - 8 Splitting Patterns: Applies workflow steps, CRUD operations, business rules, actor variations, data variations, platform variations, performance variations, and happy-path vs. error-handling splits in a defined order. - Atomicity Checks: Ensures each capability is independently valuable, testable, has fewer than 5 functional requirements, and does not duplicate other capabilities. - Structured Output: Produces capability entries grouped under Capability Groups with MoSCoW priority and pattern attribution, plus a confidence score that flags ambiguous cases for PO clarification. - Use Case: Given an epic like "merchant accepts crypto payments", decompose it into capabilities such as QR code generation, on-chain payment detection, and real-time confirmation, each with MoSCoW priority. ## Quick Start Decompose this epic into atomic, testable capabilities with MoSCoW priorities using the 8 splitting patterns.

Frequently Asked Questions about user-story-decomposition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large user story into smaller stories?▼

Apply the 8 splitting patterns in order: workflow steps, CRUD operations, business rules, actor variations, data variations, platform variations, performance variations, and happy path vs. error handling. Each resulting capability must be independently valuable and testable.

What are the patterns for splitting epics in agile?▼

This Skill uses 8 patterns: workflow steps, CRUD operations, business rules, actor variations, data variations, platform variations, performance variations, and happy path vs. error handling. They are applied sequentially to decompose epics systematically.

How do I know if a user story is small enough?▼

A decomposed capability passes atomicity checks when it is independently valuable to a user, testable with clear acceptance criteria, contains fewer than 5 functional requirements, and has no duplication with other capabilities.

When should story decomposition be escalated to a product owner?▼

Escalate when the confidence score falls below 0.85, which indicates multiple valid decomposition approaches or unclear epic intent. Scores of 1.0 to 0.85 reflect clear to minor-assumption cases handled automatically.

What output does user story decomposition produce?▼

Output consists of capability entries grouped under Capability Groups, each tagged with MoSCoW priority (Must, Should, Could, Won't) and attribution to the splitting pattern used, plus a confidence score for the decomposition.