Splitting User Stories
Split user stories into small, valuable, independently-shippable slices using INVEST (Bill Wake), Richard Lawrence's 9-pattern flowchart, Mike Cohn's SPIDR, Gojko Adzic's hamburger method, Jeff Patton's story mapping, and Henrik Kniberg's MVP analogies. Use when a story is too big to ship in one sprint, when "we'll do it all at once" feels risky, when carving an MVP, when planning incremental delivery, or when a story has hidden complexity that needs to be exposed in slices.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill splitting-user-storiesgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/splitting-user-stories ~/.claude/skills/splitting-user-storiesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Splitting User Stories
Apply this skill whenever a story feels too large to deliver confidently in a short cycle, when scope is uncertain, when you need to ship value sooner than the full feature, or when a "big bang" delivery would carry too much risk. The goal is **small, vertical, valuable slices** — each one shippable, each one teaching you something about the next.
## Core Philosophy
**Smaller is better.** Small stories ship faster, get feedback sooner, carry less risk, and reveal misunderstandings earlier. The cost of splitting is almost always less than the cost of working with a big story.
**Slice vertically, not horizontally.** A vertical slice goes through every layer (UI → API → domain → DB) for one narrow behavior. A horizontal slice ("build the database first") delivers no value until everything is done.
**Each slice must deliver value.** Not necessarily user-facing value on day one — but feedback, learning, or progress toward a verifiable outcome. "Set up the database" is not a slice; "users can register with an email" is.
**Splitting is a design activity, not a bookkeeping one.** Done well, it surfaces requirements, exposes risk, and shapes architecture. Done badly, it becomes ceremony.
**You can always go smaller.** When in doubt, split again. The smallest valuable slice is almost always smaller than your first instinct suggests.
---
## INVEST: Criteria for a Good Story (Bill Wake, 2003)
Every story should be:Details
- Skill name
splitting-user-stories- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/splitting-user-stories/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Splitting User Stories skill do?
Split user stories into small, valuable, independently-shippable slices using INVEST (Bill Wake), Richard Lawrence's 9-pattern flowchart, Mike Cohn's SPIDR, Gojko Adzic's hamburger method, Jeff Patton's story mapping, and Henrik Kniberg's MVP analogies. Use when a story is too big to ship in one sprint, when "we'll do it all at once" feels risky, when carving an MVP, when planning incremental delivery, or when a story has hidden complexity that needs to be exposed in slices.
How do I install the Splitting User Stories skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Splitting User Stories popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Ticket Writer
5vnovakovits/claude-skills
Draft, write, structure, or improve engineering tickets — user stories, bug reports, spikes, feature requests — for any tracker (Jira, Linear, GitHub Issues, Shortcut, Asana). Enforces a problem-first structure (outcome → context → constraints → acceptance criteria → dependencies → open questions) drawn from Daniel Starling's "Anatomy of a Software Ticket", Bill Wake's INVEST and SMART, and Marty Cagan / SVPG's "Empowered Product Teams". Actively rejects the standard anti-patterns — prescribed solutions / "files to change", missing outcome, untestable acceptance criteria, PM-supplied estimates
Server Documentation
8Freddy-CHEN-ux/00_claude_skills
Set up a documentation system that tracks changes and maintains server/project documentation with Claude Code hooks. Provides scripts and workflows for automatic change logging and infrastructure documentation.
Update Workspace Map
8Freddy-CHEN-ux/00_claude_skills
Validate workspace-map.md accuracy against actual 04-workspace/ structure (3 levels deep). Load when user says "validate workspace map", "update workspace map", "check workspace map", or from close-session. Ensures deep structure validation with comprehensive documentation.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.