story-split

Split large user stories into smaller independent stories using eight splitting patterns.

1|Updated Apr 8, 2026

Search Tags:#template #documentation #agile #invest #gherkin #user-stories #story-splitting

Ready to run

npx skills add https://github.com/dariopalminio/agile-sddf --skill story-split

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-split
Source: https://github.com/dariopalminio/agile-sddf/tree/main/.claude/skills/story-split
Command: npx skills add https://github.com/dariopalminio/agile-sddf --skill story-split

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Divide una historia de usuario grande en historias más pequeñas e independientes utilizando los 8 patrones de splitting. Cada historia resultante sigue el template story-gherkin-template.md y cumple INVEST, asegurando que cada entrega aporte valor.

Core Features & Use Cases

Aplica los 8 patrones de splitting para transformar una historia grande en historias viables y manejables.
Garantiza que cada historia siga el template canónico story-gherkin y cumpla los criterios INVEST.
Genera artefactos en formato Markdown listos para revisión y documentación en docs/specs/stories/.

Quick Start

Proporciona una historia grande para que el Skill genere historias divididas y las guarde en docs/specs/stories/.

Frequently Asked Questions about story-split

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

FAQPage Schema

How do I split large user stories into smaller agile deliverables?▼

To split large user stories into smaller agile deliverables, apply the eight splitting patterns to isolate independent, value-delivering increments from complex acceptance criteria. This ensures each resulting story remains manageable and independently shippable.

What is the best way to break down a user story with multiple Gherkin scenarios?▼

The best way to break down a user story with multiple Gherkin scenarios is to analyze the individual scenario paths and apply story-splitting patterns to separate them into distinct, independent user stories. Each split story retains its specific Gherkin acceptance criteria.

How do I validate if my split user stories meet agile INVEST criteria?▼

To validate if split user stories meet agile INVEST criteria, enforce the INVEST checks (Independent, Negotiable, Valuable, Estimable, Small, Testable) on each generated story. This ensures every divided story delivers standalone value and remains viable for development.

How do I generate markdown documentation for split user stories in agile projects?▼

To generate markdown documentation for split user stories in agile projects, output each divided story as a separate markdown file following a canonical story-gherkin template. These files are automatically saved under the docs/specs/stories/ directory structure.

Can I use story-splitting patterns on user stories with complex acceptance criteria?▼

Yes, you can use story-splitting patterns on user stories with complex acceptance criteria. The process specifically handles complex acceptance criteria by transforming them into multiple smaller, manageable stories that each deliver value and comply with the canonical template.