dor-dod-check

Checks user stories, PRs, sprints, and releases against Definition of Ready and Definition of Done criteria.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/bittlinkm/claude-setup --skill dor-dod-check-bittlinkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dor-dod-check
Source: https://github.com/bittlinkm/claude-setup/tree/main/skills/dor-dod-check
Command: npx skills add https://github.com/bittlinkm/claude-setup --skill dor-dod-check-bittlinkm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often start work on vague stories or close tickets that are not actually shippable. This Skill reviews a user story, PR, sprint, or release against your organization's Definition of Ready and Definition of Done, producing an honest point-by-point checklist instead of a rubber-stamp approval. ## Core Features & Use Cases - DoR Check: Validates a story before sprint commitment across 8 sections covering format, acceptance criteria, technical approach, estimation, tasks, and compliance. - DoD Check: Reviews a story, sprint, or release against quality gates covering code quality, tests, CI, review, documentation, and security. - Honest Verdicts: Marks items ✅, ❌, ❓ (not verifiable from text), or N/A with explanations, and summarizes blockers and items needing human confirmation. - Use Case: Paste a user story before sprint planning and ask "ist die Story ready?" to get a section-by-section DoR assessment flagging the missing estimate and tasks. ## Quick Start Paste your user story or PR description and ask whether it meets the Definition of Ready or Definition of Done.

Frequently Asked Questions about dor-dod-check

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

FAQPage Schema
How do I check if a user story meets the Definition of Ready?

Paste the story text and ask whether it is ready for the sprint. The check evaluates it against 8 DoR sections covering format, acceptance criteria, technical approach, estimation, and tasks, then gives a ready or not-ready verdict with specific gaps.

How do I verify a PR against the Definition of Done?

Provide the PR description or diff and ask if the story can be set to done. The check reviews acceptance criteria, code quality, tests, review status, and documentation, marking items it cannot verify from text as not checkable rather than assuming they pass.

What is the difference between Definition of Ready and Definition of Done?

Definition of Ready applies before work starts, ensuring a story is clear, estimated, and actionable. Definition of Done applies before closing work, ensuring it is tested, reviewed, documented, and shippable. The skill asks which check you want if it is ambiguous.

Can the DoD check verify CI status or code review approval?

No, system-state items like green CI pipelines, completed reviews, or merged branches cannot be verified from pasted text alone. These are marked as not verifiable with guidance on what a human needs to confirm, avoiding false passes.

Does the DoR check require compliance documentation for every story?

No, the compliance and security section only applies when relevant, such as stories touching personal data, authentication, or external interfaces. A trivial UI change can legitimately skip it, and the check explains why rather than silently omitting it.