definition-of-done

Generate mandatory Definition of Done checklists for tasks, phases, and deliveries.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill definition-of-done-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: definition-of-done
Source: https://github.com/mahg-es/araya/tree/main/skills/definition-of-done
Command: npx skills add https://github.com/mahg-es/araya --skill definition-of-done-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Definition of Done ensures every unit of work has explicit, verifiable completion criteria, eliminating ambiguity and rework.

Core Features & Use Cases

  • Task DoD: Criteria for individual tasks including coding standards, tests, and reviews.
  • Phase DoD: Criteria for SDLC phases (design, development, testing, security, validation).
  • Delivery DoD: Criteria for feature deliveries and handoffs.

Quick Start

Define and verify the DoD for a given task or phase before work begins.

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 in project management?

A definition of done (DoD) checklist is a mandatory set of verifiable completion criteria for tasks, phases, or deliveries. It eliminates ambiguity and rework by explicitly defining what constitutes a finished unit of work before development begins.

How do I create definition of done criteria for SDLC phases?

You can generate definition of done criteria for SDLC phases by applying phase-level DoD templates. These templates enforce specific verification criteria for design, development, testing, security, and validation phases before a phase is considered complete.

Can I use DoD templates for both individual tasks and feature deliveries?

Yes, DoD templates support task-level, phase-level, and delivery-level verification. Task DoD covers coding standards and reviews, while Delivery DoD handles criteria for feature deliveries and handoffs across your SDLC workflow.

Does definition of done verification support storing evidence artifacts?

Yes, the definition of done verification workflow supports storing evidence artifacts. It allows product owners and project managers to specify acceptance criteria and formally verify completion in real work scenarios while retaining proof of compliance.

What is the best way to enforce acceptance criteria in software development?

The best way to enforce acceptance criteria is to define and verify the DoD for a given task or phase before work begins. Generating mandatory checklists ensures every unit of work has explicit, verifiable completion criteria to prevent rework.

When should I not use a formal definition of done verification workflow?

A formal definition of done verification workflow should be avoided for highly exploratory or ad-hoc work where rigid completion criteria may stifle iteration. It is designed for structured SDLC workflows requiring explicit, verifiable acceptance criteria and evidence artifacts.