story-done

End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/story-done/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.

A highly actionable, well-sequenced multi-phase workflow with strong validation gates and concrete commands. Its weaknesses are verbosity from repeated inline templates/option enumerations and a monolithic structure that does not use bundle files to progressively disclose detail.

Suggestions

Split the bulky inline content — the Story-Type test-evidence table (Phase 3), the completion-report template (Phase 6), and the sprint close-out sequence (Phase 8) — into reference files under references/ linked from the body to improve progressive disclosure and reduce token load.

Consolidate the repeated review-mode (full/lean/solo) dispatch blocks in Phases 4b, 5, and the Phase 1 resolution into a single shared helper or table to cut redundancy.

Tighten verbose enumerated AskUserQuestion option lists into concise one-line option specs to improve conciseness without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is project-specific process rather than general concepts Claude already knows, but at ~450 lines it is heavily padded with repeated review-mode blocks, fully enumerated option lists, and inline report/commit templates that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; it avoids level 1 because it does not explain generic concepts.	2 / 3
Actionability	Provides concrete file paths ('production/session-state/active.md', 'docs/architecture/tr-registry.yaml'), specific Grep/Glob patterns, exact AskUserQuestion prompts with options, full report templates, and ready commit commands — copy-paste ready executable guidance matching the level-3 anchor.	3 / 3
Workflow Clarity	Eight numbered phases are clearly sequenced with explicit validation checkpoints and feedback loops (BLOCKED→fix→retry, '>50% UNTESTED → BLOCKING', sign-off checkbox checks, review-mode branching), matching the 'clear sequence with explicit validation steps' anchor; it is above level 2 because checkpoints are explicit rather than implied.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the skill is one large inline monolith; references to '.claude/docs/director-gates.md' are well signaled but point at a project doc, and content that could be split (test-evidence rules, report/commit templates) is inline, matching the 'some structure but content that should be separate is inline' anchor rather than the level-3 ideal of well-signaled one-level references.	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.

A specific, third-person description that concretely enumerates the skill's actions and carves out a distinct game-dev story-closeout niche. Its main weakness is the absence of an explicit 'Use when…' trigger clause and thinner coverage of natural user phrasings.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when finishing a story implementation, closing out a story, or marking a story Complete at sprint end.'

Include common natural phrasings users would actually say ('mark story done', 'close story', 'close out the sprint') to broaden trigger-term coverage.

Consider naming the story-done trigger verb ('/story-done') in the description to sharpen distinctiveness against sibling skills like /story-readiness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Reads the story file, verifies each acceptance criterion...checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story' — matching the 'multiple specific concrete actions' anchor; it is above level 2 because it goes well beyond naming only a domain and a few actions.	3 / 3
Completeness	It clearly answers 'what' with a full action list, but 'when' is only implied by 'End-of-story completion review' with no explicit 'Use when…' clause or equivalent trigger guidance, which per the rubric caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Contains relevant domain terms ('story', 'completion', 'Complete', 'sprint', 'code review') but misses common natural phrasings a user would say like 'mark done', 'close story', or 'close out the story', matching the 'some relevant keywords but missing common variations' anchor rather than the full coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The combination of 'acceptance criterion', 'GDD/ADR deviations', and 'sprint' defines a clear game-dev story-closeout niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	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/story-done/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.