sprint-plan

Capacity-gated sprint planning — runs capacity math, carry-over check, and a definition-of-ready gate before committing scope. Usage: /sprint-plan <goal> [capacity]

Quality

71%

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 ./.gemini/skills/sprint-plan/SKILL.md

Quality

Content

77%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 body is a tight, well-sequenced planning workflow with explicit validation gates and a DoR feedback loop, scoring highly on workflow clarity and actionability. Its main weakness is the 'Repo Assets (verified paths)' section, which asserts verified bundle files that are not actually present in this workspace.

Suggestions

Verify or remove the 'Repo Assets (verified paths)' section: the listed template, guide, and generator paths do not exist in the bundle here, so the 'verified' label is misleading — either include the files or drop the section.

Tighten the opening: the first paragraph and the Usage block largely restate the frontmatter description and argument-hint, so one of them can be trimmed for token efficiency.

If the story-generator command is the only runnable script, surface it inline in the DoR phase with a brief usage example rather than only as a repo-asset path.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's agile competence — only specific thresholds (focus factor 0.7, 10% ceremonies, >15% velocity cap, 30% carry-over flag) are given — but the opening paragraph and Usage block restate the frontmatter, adding minor padding.	4 / 5
Actionability	Provides concrete executable guidance — exact capacity formulas, line-by-line deductions, a copy-paste story-generator command, a defined output table, and a DoR checklist — with minor gaps (no runnable command for the arithmetic itself, which is appropriate as a formula).	4 / 5
Workflow Clarity	A clear four-phase sequence (Capacity Math -> Carry-Over -> DoR Gate -> Output) with explicit validation checkpoints and feedback loops — the DoR pass/fail checklist routes failures to 'needs refinement', and velocity (>15%) and carry-over (30%) thresholds gate the commitment.	5 / 5
Progressive Disclosure	Structure is well-organized with one-level-deep signaled references, but the 'Repo Assets (verified paths)' section claims verified files (template, guide, generator) that are absent from the bundle/repo here, undermining the reference integrity the section advertises.	3 / 5
	Total	16 / 20 Passed

Description

66%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.

The description concretely names the skill's three core actions and carves out a distinct agile niche, but it lacks an explicit 'Use when...' trigger clause, relying on invocation syntax for the 'when' and so capping completeness at 3. Trigger term coverage is good but missing common synonyms.

Suggestions

Add an explicit 'Use when...' trigger clause naming the situations that call for sprint planning (e.g., 'Use when planning a sprint, sizing team capacity, or triaging carry-over into the next commitment').

Include natural synonyms users say — 'story points', 'person-days', 'velocity', 'team capacity' — to broaden trigger term coverage.

Mention the velocity cross-check or output deliverable to push specificity from several actions toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'runs capacity math, carry-over check, and a definition-of-ready gate before committing scope' — but omits velocity cross-check and output structure, so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	It states clearly what the skill does, but the only 'when' guidance is the invocation syntax 'Usage: /sprint-plan <goal> [capacity]' rather than an explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural domain terms are present ('sprint planning', 'capacity', 'carry-over', 'definition-of-ready') but common synonyms a user might say (story points, person-days, velocity) are not, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	'Capacity-gated sprint planning' with a DoR gate and carry-over check is a clear niche with minimal conflict risk, but triggers rely on the invocation form rather than natural phrases, leaving minor overlap risk with closely related agile skills.	4 / 5
	Total	15 / 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: alirezarezvani/claude-skills
Path: .gemini/skills/sprint-plan/SKILL.md
Commit: 19392f7

Reviewed: ~18 hours 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.