user-story-splitting

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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/user-story-splitting/SKILL.md

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content delivers a well-sequenced, highly actionable splitting workflow with strong validation, but is let down by minor verbosity and by progressive-disclosure references that point to bundle files which are not actually present.

Suggestions

Add the missing bundle files 'template.md' and 'examples/sample.md' (or remove the references and inline the template/example content) so the signaled navigation resolves to real material.

Trim the 'Why Split Stories?' benefits list and drop the verbatim repeat of the frontmatter intent in the Purpose section to reduce token overhead.

Expand the description's specificity by listing a couple of the concrete split patterns (e.g. workflow steps, business rule variations) rather than only the single 'break into smaller stories' action.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete per-pattern examples, but includes unnecessary padding such as a Purpose paragraph that repeats the frontmatter intent verbatim and a motivational 'Why Split Stories?' section that states fairly self-evident agile benefits, placing it at the mostly-efficient anchor.	3 / 5
Actionability	Each of the 8 patterns pairs an explicit 'Ask' with a concrete before/after split example, and Step 3 provides a fill-in output template, giving mostly executable guidance; the gap is reliance on a referenced 'template.md' for the full structure that is not present in the bundle.	4 / 5
Workflow Clarity	The Application section gives a clear 4-step sequence (identify, apply patterns in order stopping at the first match, write splits, validate) with an explicit validation checklist in Step 4 and a feedback loop ('If any answer is no, revise'), matching the top anchor for explicit checkpoints and error recovery.	5 / 5
Progressive Disclosure	Section structure is clear (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) and references are signaled one level deep, but the referenced files 'template.md' and 'examples/sample.md' do not exist in any bundle directory, so the promised navigation leads to missing material.	3 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-balanced description that clearly states both capability and trigger conditions in third person with concrete language. Its main limitation is specificity, naming one core action rather than enumerating the range of split behaviors it supports.

Dimension	Reasoning	Score
Specificity	The description names the domain ('large story or epic') and one concrete action ('Break... into smaller deliverable stories using proven split patterns'), but does not enumerate several distinct actions, matching the anchor for 1-2 concrete actions rather than the multi-action anchors at 4-5.	3 / 5
Completeness	It explicitly answers both 'what' ('Break a large story or epic into smaller deliverable stories using proven split patterns') and 'when' ('Use when backlog items are too big for estimation, sequencing, or independent release') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Phrases like 'backlog items are too big for estimation, sequencing, or independent release' and 'story or epic' are natural terms a user would say, giving good keyword coverage, though common variations like 'sprint' or 'split this story' are absent so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The story/epic-splitting niche is mostly distinct with specific triggers, but 'backlog items too big for estimation' has minor overlap risk with general agile estimation or backlog-grooming skills, so it sits just below the minimal-conflict anchor.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/user-story-splitting/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.