Name: testland/definition-of-done
Rating: 75.2 (1 reviews)
Author: testland

testland/definition-of-done

The team's Definition of Done (DoD), both halves of the lifecycle: authoring and auditing. Explains the Scrum Guide's DoD definition ("a formal description of the state of the Increment when it meets the quality measures required for the product"), proposes a starter DoD with the 7-10 lines most teams need (code reviewed, unit tests, docs, AC met, deployed to staging, smoke passed, no a11y regressions, telemetry wired), emits a per-PR checklist a reviewer enforces, and audits work against an existing DoD line by line with repository evidence (review records, diffs, CI runs, coverage reports), tagging every line met, not met, or unverifiable - never passing a line on self-attestation. Use when the team doesn't have a DoD, wants to revise theirs, or is about to mark a story or PR done and nobody has checked the work against the committed checklist.

Quality

94%

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

Quality

Content

92%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 high-quality body that balances authoring and auditing halves with executable commands, real evidence standards, explicit validation feedback loops, and a well-placed reference for the worked example. Only minor tightening of audit prose would improve conciseness further.

Suggestions

Tighten the prose paragraphs in the 'Auditing adherence' section (e.g. the two Scrum-Guide framing paragraphs) — the tables already carry the load and some narration restates them.

Consider moving the full line-pattern-to-evidence mapping table into the worked-example reference if the spine ever grows, to keep the overview leaner.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's intelligence (no explaining what Scrum, CI, or coverage are); the evidence-mapping and three-states tables earn their tokens, though some prose around the audit section could be tightened.	4 / 5
Actionability	Provides concrete executable commands throughout — `gh pr view --json reviews,reviewDecision`, `git diff --name-only`, LCOV `LF:`/`LH:` parsing, the axe `violations` array — plus copy-paste-ready starter DoD and PR template, covering the common cases.	5 / 5
Workflow Clarity	The audit half is a clearly sequenced process (pin revision/window → split atomic lines → handle conditionals → map patterns to evidence → assign states → verdict) with explicit validation checkpoints and feedback loops ('self-attestation is not evidence', 'a green CI run for a different SHA proves nothing', unverifiable blocks until a named human supplies evidence).	5 / 5
Progressive Disclosure	Well-organized overview in SKILL.md with a single clearly-signaled one-level-deep reference to the real file references/adherence-worked-example.md ('A full stage-2 audit worked end to end is in [references/adherence-worked-example.md]'), keeping the bulk worked example out of the spine.	5 / 5
	Total	19 / 20 Passed

Description

92%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 strong, specific description that names both lifecycle halves and concrete artifacts, with an explicit 'Use when' trigger clause and third-person voice. Minor room to densify natural trigger synonyms, but it clearly answers what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'proposes a starter DoD with the 7-10 lines most teams need', 'emits a per-PR checklist a reviewer enforces', and 'audits work against an existing DoD line by line with repository evidence (review records, diffs, CI runs, coverage reports), tagging every line met, not met, or unverifiable' — with no meaningful coverage gaps.	5 / 5
Completeness	Explicitly answers both 'what' ('both halves of the lifecycle: authoring and auditing' with enumerated actions) and 'when' ('Use when the team doesn't have a DoD, wants to revise theirs, or is about to mark a story or PR done and nobody has checked the work against the committed checklist').	5 / 5
Trigger Term Quality	Includes natural user phrases ('Definition of Done', 'DoD', 'mark a story or PR done', 'doesn't have a DoD', 'wants to revise theirs') with synonyms, but leans on scenario framings rather than a dense list of natural trigger terms, leaving a few common variations implicit.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Definition of Done authoring plus repository-evidence auditing — with distinct triggers unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Reviewed

19 days ago

Table of Contents

Discovery Implementation Validation