CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

milestone-review

Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.

Quality

81%

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

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.

A strongly engineered workflow: concrete grep commands, exact paths, a complete output template, explicit input validation, and user-decision feedback loops around the producer verdict. Its main cost is token weight — the NOT ASSESSED principle is restated many times and the whole output template is inlined in an already long single file.

Suggestions

State the 'absent input → NOT ASSESSED, never zero' rule once in the preamble and reference it per-phase instead of restating it for blocked stories, bugs, and the verdict.

Trim the preamble's hypothetical failure-mode examples ('an asset audit returning COMPLIANT…', '>99% headroom…') to a single line each.

Move the ~80-line Phase 3 report template to a references/ file and keep only the section list inline, slimming SKILL.md toward an overview.

DimensionReasoningScore

Conciseness

The no-data principle is restated repeatedly — "NOT ASSESSED — NO DATA, not zero" appears in the preamble, Phase 1 ("the Blocked table and the blocked story count are NOT ASSESSED — NO DATA, not zero") and Phase 2 ("the bug lines are NOT ASSESSED — NO DATA, not zero"), plus general asides like "Absence of evidence is never evidence of absence" and the extended false-clean-pass examples. This goes beyond anchor 4's 'minor instances of over-explanation' and fits anchor 3: mostly efficient but could be tightened.

3 / 5

Actionability

Guidance is copy-paste ready throughout: full Grep invocations with flags ("Grep pattern=\"^## (Sprint Goal|Capacity|Tasks|Carryover|Risks|Progress|Burndown Assessment|Emerging Risks|Definition of Done)\" glob=\"production/sprints/sprint-*.md\" output_mode=\"content\" -A 12"), exact file paths, a complete output template, and fully scripted AskUserQuestion prompts with labeled [A]/[B]/[C] options. Nothing is left as vague direction, so it meets anchor 5 rather than anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with explicit validation checkpoints — the FOUND/ABSENT input checklist ("If any input required for a section is ABSENT, that section is NOT ASSESSED"), the zero-match escape hatch for legacy sprint reports, and the review-mode check applied "before spawning PR-MILESTONE" — plus feedback loops for error recovery (OFF TRACK/AT RISK branches with user-choice options). This matches anchor 5: explicit validation, feedback loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so everything lives in a ~240-line body. External references are well-signaled and one level deep ("See `.claude/docs/director-gates.md` for the full check pattern"; the gate file is read by the spawned agent, not the parent). Structure is good (anchor 4), but the ~80-line inline report template and the repeated no-data prose make the body heavier than a true overview, short of anchor 5's appropriately-split ideal.

4 / 5

Total

17

/

20

Passed

Description

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

A terse, concrete description that explicitly covers both what it produces and when to use it. It sits just below top marks on trigger-phrase breadth (no 'Use when…' phrasing or synonyms like 'on track') and on action specificity, since it names the deliverables but not the mechanics.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a milestone review, progress check, or a go/no-go decision before a deadline.'

Include natural synonyms users would say — 'on track', 'status report', 'are we going to make the deadline' — to broaden trigger coverage.

Name one or two concrete mechanics (aggregates sprint reports, scans TODO/FIXME markers, checks open bugs) to sharpen the 'what'.

DimensionReasoningScore

Specificity

The description names several concrete capability areas — "completeness, quality metrics, risk, go/no-go recommendation" — which exceeds anchor 3's '1-2 concrete actions', but it stops short of anchor 5's comprehensive coverage: it never says how the review is produced (aggregating sprint reports, scanning TODO/FIXME markers, spawning a producer gate check).

4 / 5

Completeness

Both what ("Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation") and when ("At checkpoints or before a deadline") are explicitly present, matching anchor 4; it falls short of anchor 5 because the 'when' clause is terse and lacks concrete 'Use when the user asks for…' trigger phrasing.

4 / 5

Trigger Term Quality

"Milestone", "progress", "go/no-go", and "At checkpoints or before a deadline" are phrases a user would naturally say when they need this skill, matching anchor 4's 'good keyword coverage; a few natural terms missing' — common variants like 'on track', 'status report', or 'sprint rollup' are absent, keeping it below anchor 5's synonym breadth.

4 / 5

Distinctiveness Conflict Risk

'Milestone' + 'go/no-go recommendation' carves a mostly distinct niche (anchor 4), but the body itself reveals closely related sibling skills (/gate-check, /sprint-plan, sprint reports), so it carries minor overlap risk with a sprint-review or phase-gate request rather than the minimal conflict of anchor 5.

4 / 5

Total

16

/

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/milestone-review/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.