skills.rest
devmuslim
devmuslimCOMMUNITY
Explore all skills by this author →
GitHub

DoD / DoR / AC — معايير الجودة والجاهزية

Define quality and readiness criteria for software development tasks.

Updated Mar 6, 2026
Search Tags:#quality assurance#acceptance criteria#agile#definition of done#scrum#kanban#definition of ready
One-click install
npx skills add https://github.com/devmuslim/pdm-skills --skill dod-dor-ac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: DoD / DoR / AC — معايير الجودة والجاهزية
Source: https://github.com/devmuslim/pdm-skills/tree/main/team-os/skills/dod-dor-ac
Command: npx skills add https://github.com/devmuslim/pdm-skills --skill dod-dor-ac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the criteria for when a development task is ready to start (Definition of Ready), when it's considered complete (Definition of Done), and precisely what needs to be built (Acceptance Criteria).

Core Features & Use Cases

  • Definition of Ready (DoR): Ensures stories meet essential criteria before Sprint Planning.
  • Definition of Done (DoD): Outlines comprehensive completion standards for developers, QA, and product owners across various stages (Story, Sprint, Release).
  • Acceptance Criteria (AC): Provides a structured template (Given/When/Then) for defining specific, testable requirements.
  • Framework Alignment: Adapts DoR/DoD principles for Scrum, Kanban, and SAFe methodologies.

Quick Start

Use the dod-dor-ac skill to define the acceptance criteria for a new user login feature.

Frequently Asked Questions about DoD / DoR / AC — معايير الجودة والجاهزية

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

FAQPage Schema
What is the difference between Definition of Ready and Definition of Done in agile?▼

Definition of Ready ensures stories meet essential criteria before Sprint Planning, while Definition of Done outlines comprehensive completion standards for developers, QA, and product owners across Story, Sprint, and Release stages.

How do I write acceptance criteria using Given When Then?▼

Acceptance criteria should use the Given/When/Then template to define specific, testable requirements. This structured format standardizes quality gates and enforces clear deliverable expectations for development workflows.

Does this Definition of Done template work for Kanban and SAFe?▼

Yes, the quality and readiness gates adapt DoR and DoD principles for Scrum, Kanban, and SAFe methodologies. Framework alignment provides specific templates and guidelines for each stage of the development lifecycle.

What's the best way to standardize quality gates across a development team?▼

Standardize quality gates by applying consistent DoR, DoD, and acceptance criteria templates. This enforces consistent quality checks and clear deliverable expectations for developers, QA, and product owners.

Why do we need a Definition of Ready before starting sprint planning?▼

A Definition of Ready is needed to ensure stories meet essential criteria before Sprint Planning begins. It standardizes task initiation requirements and prevents incomplete or ambiguous work from entering the sprint.

Related Skills

Explore More Software Engineering Skills→
jikig-aijikig-ai
12

user-story-writer

Decompose feature requirements into INVEST-compliant user stories with acceptance criteria.

Official
Intermediate
v1bh0rv1bh0r

nw-leanux-methodology

Apply LeanUX principles to validate and size backlog items.

Community
Advanced
h4vzzh4vzz
33

Project Management

Create and manage software project plans with task breakdowns and status reports.

Community
Advanced
0xRayAI0xRayAI

lint

Run node-based linting servers to enforce code quality standards.

Official
Intermediate