skills.rest
shakhovskiya-create
shakhovskiya-createCOMMUNITY
Explore all skills by this author →
GitHub

dod-validator

Validate Definition of Done criteria to block sprint closure when unmet.

Updated May 5, 2026
Search Tags:#qa#verification#governance#release-management#software-development#sprint#dod
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill dod-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dod-validator
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/dod-validator
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill dod-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a hard gate before sprint closure by validating that all Definition of Done criteria are fulfilled, preventing incomplete work from progressing to release.

Core Features & Use Cases

  • Validates that every backlog step is marked as done, skipped with justification, or failed with reason.
  • Verifies the sprint goal is explicitly addressed in the final check-in.
  • Ensures increment artifacts exist, are non-empty, and match expected formats.
  • Requires HANDOFF.md to include a new sprint cycle section and recent activity, open questions, important decisions, and next priorities.
  • Enforces test-first compliance by requiring test updates to accompany production changes and by verifying presence of related tests.

Quick Start

Run the DoD validator at sprint close to automatically verify all mandatory criteria.

Frequently Asked Questions about dod-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a Definition of Done before closing a sprint?▼

To enforce a Definition of Done, you can validate that all backlog steps are resolved, sprint goals are addressed, artifacts exist, and HANDOFF.md is updated to block incomplete sprint closure.

What happens if sprint goals are not explicitly addressed during check-in?▼

If sprint goals are not explicitly addressed in the final check-in, the sprint closure hard gate blocks the release and provides actionable remediation guidance to resolve the missing criteria.

How do I validate that increment artifacts exist and match expected formats?▼

Artifact validation checks that increment artifacts exist, are non-empty, and match expected formats as part of the sprint closure criteria to ensure end-to-end completeness before release.

Does sprint closure require test-first compliance for production changes?▼

Yes, sprint closure requires test-first compliance by verifying that test updates accompany production changes and confirming the presence of related tests to block incomplete work.

What should be included in HANDOFF.md to pass sprint validation?▼

HANDOFF.md must include a new sprint cycle section with recent activity, open questions, important decisions, and next priorities to pass sprint validation and allow release progression.

Can a backlog step be skipped and still meet Definition of Done criteria?▼

Yes, a backlog step can be skipped if it includes a justification, or marked as failed with a reason, satisfying the Definition of Done validation requirements for sprint closure.

Related Skills

Explore More Software Engineering Skills→
JiliarJiliar
1

okr-sprint-alignment

Maps quarterly OKRs to backlog items and sprint goals.

Community
Advanced
MagicBowenMagicBowen
4

dogent-story-acceptance

Fix post-UAT issues and update sprint UAT documents with retest guidance.

Community
Advanced
qa-amanqa-aman
19

qa-metrics

Automate software quality metric measurement and reporting for sprint reviews.

Community
Advanced
atusyatusy
8

scrum-event-sprint-review

Verify Definition of Done and acceptance criteria for sprint increments.

Community
Intermediate