bmad-create-epics-and-stories

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/SKILL.md

Quality

Content

50%

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

The body is a well-structured activation/overview document with a clear sequence and a legitimate step-file disclosure design, but it is undermined by redundancy between its rules sections and by a referenced step file that does not exist in the bundle, leaving the core executable content unverifiable.

Suggestions

Include the referenced ./steps/step-01-validate-prerequisites.md (and required bundle files) so the progressive-disclosure chain is complete and the main workflow is actually navigable.

Collapse the duplicated 'Step Processing Rules' and 'Critical Rules (NO EXCEPTIONS)' sections into a single concise list; drop the generic 'partnership, not client-vendor' coaching from 'Your Role'.

Add an explicit output-validation checkpoint (e.g. verify each story has complete acceptance criteria before appending) so the workflow_clarity feedback loop is visible in the skill body rather than only implied in delegated step files.

Dimension	Reasoning	Score
Conciseness	Procedurally efficient overall, but the 'Critical Rules (NO EXCEPTIONS)' block largely restates the preceding 'Step Processing Rules' (e.g. 'read the entire step file' appears twice) and the 'Your Role' partnership coaching is generic padding.	2 / 3
Actionability	Provides one concrete command (resolve_customization.py) and specific config keys, but the main workflow delegates to ./steps/step-01-validate-prerequisites.md which is absent, and most steps hinge on runtime-resolved placeholders.	2 / 3
Workflow Clarity	Activation is clearly numbered with an error-recovery fallback and a completion check, but the substantive validation/feedback loops for the actual epic/story generation live in the missing step files and are not verifiable here.	2 / 3
Progressive Disclosure	The step-file architecture is a sound one-level-deep pattern with clearly signaled references and a path-resolution conventions section, but the primary referenced file (steps/step-01-validate-prerequisites.md) is not present in the bundle, breaking navigation.	2 / 3
	Total	8 / 12 Passed

Description

90%

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 tight, well-constructed description that explicitly pairs what it does with a natural-language when-to-use trigger. It is distinctive and complete; the only minor gap is listing a single action rather than multiple concrete ones.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Break requirements into epics and user stories') and the domain, but lists a single action rather than 'multiple specific concrete actions', matching the score-2 anchor.	2 / 3
Completeness	Clearly answers both what ('Break requirements into epics and user stories') and when via an explicit 'Use when...' clause, satisfying the completeness guideline.	3 / 3
Trigger Term Quality	The explicit 'Use when the user says "create the epics and stories list"' provides a natural phrase a user would actually say, with the core domain terms (epics, user stories) well covered.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear agile requirements-decomposition niche with a distinct trigger, making conflict with unrelated skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bmad-code-org/BMAD-METHOD
Path: src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/SKILL.md
Commit: bb45db4

Reviewed: 1 day 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.