Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add getcrew44/crew44 --skill user-story-splittinggit clone --depth 1 https://github.com/getcrew44/crew44Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/getcrew44/crew44/user-story-splitting)<a href="https://agentmods.dev/skills/getcrew44/crew44/user-story-splitting"><img src="https://agentmods.dev/badge/skills/getcrew44/crew44/user-story-splitting.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 58 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 179 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 282 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 302 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 58 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 283 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 302 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 284 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.02790 |
| Opus 5 | $0.00019 | $0.01395 |
| Sonnet 5 | $0.00008 | $0.00558 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
user-story-splitting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
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.
This is not arbitrary slicing—it's strategic decomposition that preserves user value while reducing complexity.
Key Concepts
The Story Splitting Framework
Based on Richard Lawrence and Peter Green's "Humanizing Work Guide to Splitting User Stories," the framework provides 8 systematic patterns for splitting work:
- Workflow steps: Split along sequential steps in a user's journey
- Business rule variations: Split by different rule scenarios (permissions, calculations, etc.)
- Data variations: Split by different data types or inputs
- Acceptance criteria complexity: Split when multiple "When" or "Then" statements exist
- Major effort: Split by technical milestones or implementation phases
- External dependencies: Split along dependency boundaries (APIs, third parties, etc.)
- DevOps steps: Split by deployment or infrastructure requirements
- Tiny Acts of Discovery (TADs): When none of the above apply, use small experiments to unpack unknowns
Why Split Stories?
- Faster feedback: Smaller stories ship sooner, allowing earlier validation
- Reduced risk: Less to build = less that can go wrong
- Better estimation: Small stories are easier to estimate accurately
- Maintain flow: Keeps work moving through the sprint without bottlenecks
- Testability: Smaller scope = easier to write and run tests
Anti-Patterns (What This Is NOT)
- Not horizontal slicing: Don't split into "front-end story" and "back-end story" (each story should deliver user value)
- Not task decomposition: Stories aren't tasks ("Set up database," "Write API")
- Not arbitrary chopping: Don't split "Add user management" into "Add user" and "Management" (meaningless)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 304 lines · 38 tokens per session scan A d6cfd484b4a4
user-story-splitting is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,790 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gitlab
Read and manage GitLab projects, issues, merge requests, and pipelines via the GitLab REST API. Use when the user asks about GitLab projects, issues, MRs, or pipelines.
slack
Read, post, react and search in the connected Slack workspace via the Slack Web API, and help the user finish app setup. Use when the user asks to send a Slack message, list channels or users, read a thread, react to a message, or connect/install the Slack app.
product-strategy
A product-planning guide for evaluating requirements, users, scope, priorities, roadmaps, and success measures. It ties proposals to user problems, business value, boundaries, and signals that can be checked.
github
Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.
redmine
Read and manage Redmine projects, issues, and updates via the Redmine REST API. Use when the user asks about Redmine tickets/issues or projects.
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.