CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-sprint-planning

Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with concrete commands, parsing rules, and templates, and has a clear sequenced workflow. It loses points for duplicated status definitions, a missing fix-and-retry validation loop, and a monolithic inline structure with no progressive disclosure.

Suggestions

Remove the duplicated status state-machine content — keep a single definition (either the Step 4 inline comments or the "Status State Machine" section) to reduce redundancy and token cost.

Add an explicit fix-and-retry feedback loop to Step 5 validation (e.g., "if any check fails, correct the YAML and re-run validation before reporting completion") to gate the batch file-generation.

Move the large sprint-status.yaml template and status definitions into a reference file (e.g., references/sprint-status-template.yaml) and link to it, enabling one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain-specific guidance, but the status state-machine definitions are duplicated (inline YAML comments in Step 4 and again in the "Status State Machine" section), and the large templated YAML block could be tightened.

2 / 3

Actionability

It provides executable commands (resolve_customization.py invocation), concrete parsing patterns ("## Epic 1:", "### Story 1.1:"), explicit ID conversion rules, and a complete copy-paste-ready YAML template.

3 / 3

Workflow Clarity

A clear 5-step sequence with a Step 5 validation checklist is present, but validation is post-hoc with no explicit fix-and-retry feedback loop for the batch file-generation operation.

2 / 3

Progressive Disclosure

Content is organized into sections and steps, but everything is inline in SKILL.md with no bundle files or one-level-deep references; the large YAML template and status reference material should live in separate files.

2 / 3

Total

9

/

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 strong: it states a concrete capability, includes natural explicit triggers, and answers both what and when. Its only weakness is listing a single action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

The phrase "Generate sprint status tracking from epics" names the domain and one concrete action, but only a single action is listed rather than multiple specific concrete actions.

2 / 3

Completeness

It explicitly answers both what ("Generate sprint status tracking from epics") and when ("Use when the user says...") with an explicit trigger clause.

3 / 3

Trigger Term Quality

The triggers "run sprint planning" and "generate sprint plan" are natural phrases a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

Sprint-status generation from epics is a clear niche with distinct triggers unlikely to conflict with unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bmad-code-org/BMAD-METHOD
Reviewed

Table of Contents

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.