CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sprint-plan

New or updated sprint plan from the current milestone, completed work, and available capacity.

Quality

72%

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 ./.claude/skills/sprint-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable, well-sequenced operational skill: exact commands, verbatim prompts, complete templates, and explicit gates with feedback loops. Its main weaknesses are repetition of the review-mode policy across multiple phases and inlining of long reference-worthy material in a single large body.

DimensionReasoningScore

Conciseness

The body is dense project-specific instruction with no explanations of concepts Claude already knows, but the review-mode resolution chain is restated in four places (top block, Phase 0, Phase 4, and a full paragraph in Phase 6) and the "Never write a review mode" passage runs long, so it could be tightened.

3 / 5

Actionability

Guidance is fully executable: exact Glob/Grep patterns ("Glob production/epics/**/story-*.md"), verbatim AskUserQuestion prompts with enumerated options, complete markdown and YAML templates, and exact write-ask wording covering the common cases.

5 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced with explicit validation checkpoints (director gates with UNREALISTIC/CONCERNS handling, BLOCKED verdicts, QA-plan gate, separate write approval) and feedback loops that revise and re-present the plan before writing.

5 / 5

Progressive Disclosure

References to .claude/docs/* are one level deep, clearly signaled, and scoped with explicit routing guidance ("the spawned agent reads its own gate file; do not read it in the parent session"), but the ~400-line body inlines long templates and the goal-prerequisites procedure that could live in separate files.

4 / 5

Total

17

/

20

Passed

Description

53%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 identifies a distinct niche (sprint planning) and its key inputs, but is held back by a missing "when to use" clause and thin keyword coverage beyond the single "sprint plan" term family. It reads as a terse artifact definition rather than a trigger-ready capability statement.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create, update, or check a sprint plan, plan the next sprint, or review sprint progress and capacity."

Broaden natural keyword coverage with synonyms users actually say: "sprint planning", "plan a sprint", "sprint status", "backlog", "velocity", "carryover".

State the concrete actions more fully: generating the sprint plan markdown and sprint-status.yaml, running producer feasibility and QA-plan gates, and reporting status.

DimensionReasoningScore

Specificity

"New or updated sprint plan from the current milestone, completed work, and available capacity" names the domain and its concrete inputs but states only 1-2 actions (produce a new or updated plan), matching the anchor for domain-plus-limited-actions rather than the several-specific-actions anchor.

3 / 5

Completeness

The "what" is clear (creates new or updated sprint plans), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"sprint plan" is the primary natural term and "milestone", "completed work", "available capacity" add relevance, but common variations like "sprint planning", "plan the next sprint", or "backlog" are missing, fitting the some-relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

"Sprint plan" carves out a clear niche with distinct triggers that users would naturally say; only minor overlap risk with closely related general planning or roadmap skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/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.