bmad-create-story

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%

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

The content is highly actionable and well-sequenced with proper validation checkpoints, but it is verbose in places and bundles a large inline workflow while referencing bundle files that are not actually present.

Suggestions

Remove the duplicated auto-discover parsing block in step 1 and tone down hortatory emphasis ('EXHAUSTIVE ANALYSIS REQUIRED!', 'do NOT be lazy') to tighten conciseness.

Provide the referenced bundle files (`discover-inputs.md`, `checklist.md`, template.md) or replace bare-path references with inline content so the skill is self-contained.

Extract the large inline <workflow> XML into a referenced workflow file to better separate overview from detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable but padded with hortatory emphasis ('EXHAUSTIVE ANALYSIS REQUIRED!', 'do NOT be lazy or skim!') and a near-duplicate auto-discover block in step 1 that repeats the same parsing logic twice, so tokens do not all earn their place.	2 / 3
Actionability	Provides concrete executable commands (`python3 {project-root}/_bmad/scripts/resolve_customization.py ...`), specific path patterns, and copy-paste-ready instructions throughout.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with explicit validation checkpoints (step 6 validates against `./checklist.md`, verifies prior 'backlog' status before transitioning) and HALT/error-recovery branches.	3 / 3
Progressive Disclosure	Sections and one-level references are signaled (e.g. `./discover-inputs.md`, `./checklist.md`, template.md), but the bundle directories and referenced files do not exist in the skill, and the large inline XML workflow makes it closer to a monolithic structure than a clean overview-plus-references split.	2 / 3
	Total	10 / 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.

The description is concise, uses third person, and clearly answers both what the skill does and when to trigger it with natural user phrasing. Its only weakness is modest specificity, naming one main action rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	Names the domain (story file creation for implementation context) and the core action ('Creates a dedicated story file with all the context'), but does not enumerate multiple distinct capabilities, so it is not comprehensive enough for a 3.	2 / 3
Completeness	Explicitly states both what it does ('Creates a dedicated story file...') and when to use it ('Use when the user says...'), satisfying the 'what AND when' anchor.	3 / 3
Trigger Term Quality	Quotes the exact natural phrasing a user would say ('create the next story' or 'create story [story identifier]'), giving strong coverage of real trigger terms.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow BMad story-creation niche with distinctive trigger phrasing, making conflict with other 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/4-implementation/bmad-create-story/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.