sprint-plan

Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.

Quality

72%

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

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 body is highly actionable and clearly sequenced with strong validation checkpoints and feedback loops, but carries redundancy in the review-mode explanation and keeps large templates inline rather than progressively disclosing them.

Suggestions

Remove the duplicate review-mode explanation in Phase 6 — consolidate to a single canonical description referenced from Phase 0.

Consider moving the full sprint-plan, status-report, and sprint-status.yaml templates into a references file (e.g. references/templates.md) and linking from the body, since no bundle files currently exist.

Tighten the gate-spawning prose in Phase 4 by referencing the shared pattern in .claude/docs/director-gates.md instead of restating verdict handling inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete templates and no padding with concepts Claude already knows, but the review-mode explanation is duplicated (Phase 0 and Phase 6) and some gate-spawning prose could be tightened.	2 / 3
Actionability	Provides complete, copy-paste-ready markdown and yaml templates with all fields, exact file paths, specific tool calls (Glob, Task, AskUserQuestion), and full AskUserQuestion prompts with option text.	3 / 3
Workflow Clarity	Six clearly sequenced phases with explicit validation checkpoints (feasibility gate verdict handling, "Do NOT write yet" gating), feedback loops (revise and re-present before write), and a Definition of Done checklist.	3 / 3
Progressive Disclosure	Well-organized into headed phases with a one-level signaled reference (.claude/docs/director-gates.md), but no bundle files exist and large templates plus gate-pattern detail are kept fully inline rather than split out.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 occupies a clear, distinct niche, but it omits explicit "when to use" trigger guidance and offers limited natural trigger-term variations.

Suggestions

Append a 'Use when ...' clause with natural triggers, e.g. 'Use when planning the next sprint, replanning an in-progress sprint, or when the user asks for a sprint status report.'

Add natural phrasing variations users might say, such as 'sprint planning', 'plan my sprint', or 'sprint goals'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Generates a new sprint plan", "updates an existing one", "Pulls context from production documents and design backlogs" — each tied to specific inputs (milestone, completed work, capacity).	3 / 3
Completeness	Clearly answers what the skill does but provides no explicit "when to use" trigger guidance, capping completeness at 2 per the missing-trigger guideline.	2 / 3
Trigger Term Quality	Contains relevant natural terms ("sprint plan", "milestone", "design backlogs") but lacks common phrasing variations and explicit trigger phrasing users would naturally say.	2 / 3
Distinctiveness Conflict Risk	Sprint planning against milestones and design backlogs is a well-scoped niche unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 984023d

Reviewed: 3 days 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.