definition-of-ready-done

Standardize Definition of Ready and Done across stories, sprints, and releases.

1|Updated Nov 29, 2025

Search Tags:#acceptance-criteria #team-alignment #definition-of-done #agile-governance #definition-of-ready #waivers

Ready to run

npx skills add https://github.com/SSiertsema/claude-code-plugins --skill definition-of-ready-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: definition-of-ready-done
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/definition-of-ready-done/skills/definition-of-ready-done
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill definition-of-ready-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent readiness and delivery gates, leading to rework and misaligned expectations. This skill standardizes DoR and DoD, providing a shared language and a lightweight governance structure.

Core Features & Use Cases

Establish DoR (pre-commit) and DoD (post-build) with per-level scope (story, sprint, release).
Enforce a concise, team-calibrated checklist (8 items max) and a consistent acceptance criteria format (Given-When-Then or checklist).
Provide guidance for exceptions/waivers, living-document governance, and cadence for reviews.
Applicable across product teams to improve predictability and alignment with organizational policies.

Quick Start

Configure your team's DoR/DoD by entering team name, domain, delivery model, current pain, and the required DoD levels.

Frequently Asked Questions about definition-of-ready-done

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

FAQPage Schema

How do I standardize Definition of Ready and Definition of Done across multiple agile teams?▼

You can standardize Definition of Ready and Definition of Done by applying a consistent framework with per-level scopes for stories, sprints, and releases, alongside a living-document governance model for ongoing team alignment.

What is the maximum number of items recommended for a Definition of Ready checklist?▼

The maximum recommended number of items for a Definition of Ready checklist is eight, ensuring the pre-commitment gate remains concise, team-calibrated, and lightweight to enforce across product teams.

How do you format acceptance criteria to align team readiness with delivery gates?▼

You format acceptance criteria using a consistent Given-When-Then structure or a standardized checklist to align team readiness with delivery gates and reduce misaligned expectations.

When should our team use waivers for agile governance exceptions in the DoD?▼

You should use waivers for agile governance exceptions when a delivery gate cannot be met, utilizing official waiver handling to manage deviations while maintaining the integrity of the Definition of Done.

Does this approach support different delivery scopes for Definition of Done?▼

Yes, this approach supports different delivery scopes by establishing a per-level Definition of Done specifically tailored for stories, sprints, and releases to ensure comprehensive agile governance.

What information do I need to configure a team's DoR and DoD framework?▼

To configure your team's DoR and DoD framework, you need to provide the team name, domain, delivery model, current pain points, and the required Definition of Done levels for standardization.