definition-of-done

Verify that a feature or story meets its Definition of Done criteria.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill definition-of-done-haabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: definition-of-done
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/definition-of-done
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill definition-of-done-haabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable, checklist-driven approach to verify that a feature or story satisfies all Definition of Done criteria before it is marked complete.

Core Features & Use Cases

  • Ensures coverage across functionality, quality, testing, documentation, and deployment aspects.
  • Provides a structured framework for reviews, testing, and traceability to acceptance criteria.
  • Use Case: A product team uses this skill to validate readiness, reducing rework and miscommunication.

Quick Start

Verify that a feature or story meets Definition of Done criteria before marking it complete.

Frequently Asked Questions about definition-of-done

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

FAQPage Schema
What is a definition of done checklist for agile stories?

A definition of done checklist verifies that a feature or story meets acceptance criteria across functionality, quality, testing, documentation, and deployment domains before being marked complete. It enforces consistent DoD standards through traceable criteria and documented evidence.

How do I verify acceptance criteria before marking a story complete?

To verify acceptance criteria, apply a structured checklist-driven approach to validate feature readiness across functionality, quality, testing, documentation, and deployment. This ensures traceable criteria and documented evidence satisfy the definition of done before completion.

How do I enforce a consistent definition of done across product teams?

You can enforce a consistent definition of done by applying a repeatable, checklist-driven framework that requires traceable criteria and documented evidence across functionality, quality, testing, documentation, and deployment domains for every story.

Does definition of done verification cover quality assurance and deployment?

Yes, definition of done verification covers quality assurance and deployment domains. It applies a structured checklist across functionality, quality, testing, documentation, and deployment to validate readiness and ensure all acceptance criteria are met.

Why use a structured checklist for definition of done validation?

Use a structured checklist for definition of done validation to reduce rework and miscommunication. It provides a repeatable approach to verify feature readiness, ensuring traceable criteria and documented evidence satisfy all required domains before completion.