CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/sprint-plan/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A lean, highly actionable process skill: explicit formulas, thresholds, defaults, and a gated four-phase workflow with real validation checkpoints. Its weakness is navigation — the 'verified' repo-asset paths point outside the skill and no bundle files exist to back them, so the progressive-disclosure structure is partly broken.

Suggestions

Fix the asset paths so they resolve relative to the skill's own directory (e.g., `assets/sprint_planning_template.md`, `references/sprint-planning-guide.md`) and actually ship those files in the skill's bundle, or drop the 'Repo Assets (verified paths)' section.

Show the generator invocation with its expected input/arguments (e.g., an example epic source) rather than a bare `python3 .../user_story_generator.py`.

Trim the redundant Usage block and the duplicated script path in 'Repo Assets' to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is imperative and dense — no padding explaining what a sprint or INVEST is, and it assumes Claude's competence throughout. Minor redundancy keeps it below anchor 5: the Usage section repeats the frontmatter invocation, and the 'Repo Assets (verified paths)' section duplicates the script path already given in Phase 3.

4 / 5

Actionability

Concrete, executable decision rules throughout: focus factor default 0.7, explicit deduction categories, the '>15% over trailing velocity → plan to velocity' rule, the '~30% carry-over → recommend smaller commitment' flag, a five-item DoR checklist, and a defined output structure. The one code command (`python3 product-team/.../user_story_generator.py`) is copy-pasteable but shows no arguments or expected input, a minor gap that fits anchor 4 rather than 5.

4 / 5

Workflow Clarity

Four phases are clearly sequenced (capacity math → carry-over → DoR gate → output) with explicit validation checkpoints: the velocity cross-check in Phase 1, the per-story DoR gate in Phase 3 with a defined failure path ("goes to 'needs refinement', not the sprint"), and the Phase 4 invariant that committed scope sums to ≤ the planning number. The DoR checklist plus recovery path matches anchor 5's validation-with-feedback-loop pattern; this is not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The body is well-sectioned, but every referenced supporting file (sprint_planning_template.md, sprint-planning-guide.md, user_story_generator.py) points into a `product-team/agile-product-owner/...` tree outside the skill, and the skill's own bundle (references/, scripts/, assets/) is empty — none of the paths resolve from the skill's location. Structure exists but the references cannot be followed, which matches anchor 3 rather than 4's 'references mostly clear, minor gaps'.

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 is specific and appropriately concise, with a strong "what" built from three named gates and good domain keywords. Its main weakness is the missing explicit trigger guidance — the Usage line shows how to invoke the command but never states when to use it.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when planning a sprint, committing sprint scope, or when the user mentions sprint capacity, carry-over, or velocity.'

Include common user phrasings/synonyms such as 'iteration planning', 'sprint commitment', or 'backlog grooming' to strengthen trigger coverage.

Consider naming the output artifact (a capacity table plus committed/stretch scope plan) so the 'what' covers the deliverable, not just the process.

DimensionReasoningScore

Specificity

"runs capacity math, carry-over check, and a definition-of-ready gate before committing scope" names three concrete, distinct actions with a clear outcome condition. It sits between anchor 3 (only 1-2 actions) and anchor 5 (comprehensive multi-action coverage with no gaps) — output artifacts and scope-splitting are not mentioned, so 4 fits best.

4 / 5

Completeness

The "what" is explicit and concrete (capacity math, carry-over check, DoR gate before committing scope), but there is no "Use when..." clause or equivalent trigger guidance. "Usage: /sprint-plan <goal> [capacity]" documents invocation syntax, not when the skill should be used, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say — "sprint planning", "capacity", "carry-over", "definition-of-ready", "sprint" — are all present. A few natural variations are missing (e.g., "iteration planning", "sprint commitment", "velocity", "backlog"), which matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Capacity-gated sprint planning" carves a clear niche with distinct triggers, unlikely to fire for unrelated skills. Minor overlap risk remains with adjacent agile skills (story generation, retrospectives, sprint health), matching anchor 4 rather than 5's minimal-conflict niche.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.