definition-of-done

Generate completion checklists with acceptance criteria and quality gates.

2|Updated May 15, 2026

Search Tags:#project management #acceptance criteria #quality gates #scope boundary #done checklist

Ready to run

npx skills add https://github.com/bdbch/ai-dotfiles --skill definition-of-done-bdbch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: definition-of-done
Source: https://github.com/bdbch/ai-dotfiles/tree/main/skills/definition-of-done
Command: npx skills add https://github.com/bdbch/ai-dotfiles --skill definition-of-done-bdbch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The lack of a clear checklist can lead to work stretching indefinitely or shipping prematurely with unknown gaps.

Core Features & Use Cases

Establish Done Criteria: Clearly outline acceptance criteria before starting tasks to determine when work is truly done.
Guides for Acceptance Criteria: Offers multiple formats like Rule-based, Scenario-based, and Checklist formats.
Levels of 'Done': Categorizes tasks, features, milestones, and releases for clarity in completion.
Quality Gates: Provides a list of universal quality gates applicable to all code changes.
Scope Boundaries: Clearly defines what is and isn't in scope to prevent scope creep.
Done Checklist Pattern: Provides a template to outline a comprehensive checklist for every task.

Quick Start

Generate a checklist for a new feature in your project using the "definition-of-done" skill.

Frequently Asked Questions about definition-of-done

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

FAQPage Schema

How do I create a done checklist to prevent scope creep in software projects?▼

A done checklist prevents scope creep by defining explicit scope boundaries and acceptance criteria before starting work. This approach categorizes completion criteria across task, feature, and release levels to ensure work is fully complete with no unknown gaps.

What is the best way to define acceptance criteria for a new software feature?▼

Defining acceptance criteria is best handled using rule-based, scenario-based, or checklist formats. Establishing these criteria before development starts determines exactly when a feature is done and prevents premature shipping.

How do universal quality gates work for code changes?▼

Universal quality gates act as mandatory checkpoints applicable to all code changes. They enforce completion clarity by verifying that predefined acceptance criteria and scope boundary checks are met before any task or release is considered finished.

When do I need to define completion criteria at the release level versus the task level?▼

Release level completion criteria are needed when verifying overarching project milestones, while task level criteria focus on individual work items. Categorizing done criteria across these levels ensures scalable completion clarity for various work stages.

Can I use a checklist-driven approach to manage project scope boundaries?▼

Yes, a checklist-driven approach actively manages project scope boundaries by explicitly defining what is and isn't in scope. This prevents indefinite work stretching and ensures all completion criteria are systematically verified.