# Definition Of Done Enforcer

> definition-of-done-enforcer

- Skill: `45ck/definition-of-done-enforcer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/definition-of-done-enforcer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/definition-of-done-enforcer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/definition-of-done-enforcer

---

# definition-of-done-enforcer

## Purpose
Evaluate whether backlog items or sprint outputs meet an explicit, requirement-aware definition of done.

## Trigger this skill when
- The team is working in iterations, sprints, or short delivery cycles.
- Backlog items, sprint outcomes, or team process signals need structured review.
- You need clearer delivery discipline instead of vague “be more agile” advice.

## Expected inputs
- item or sprint output
- definition of done
- test/doc/review evidence
- deployment context
- known exceptions

## Deliverables
- done/not-done assessment
- failed criteria list
- waiver notes
- evidence summary
- next actions

## Operating procedure
1. Clarify the delivery context, scope, and timebox.
2. Separate what is known from what is assumed or missing.
3. Produce the skill-specific artifact or review output.
4. Surface coordination, quality, sequencing, or blocker risks explicitly.
5. Recommend the next best handoff instead of trying to solve the whole lifecycle at once.

## Quality gates
- The output is specific to the current iteration context.
- Risks, ambiguity, and dependencies are visible.
- Advice is actionable within a real team workflow.
- The result does not confuse commitment with aspiration.

## Handoff targets
- iteration-outcome-reviewer
- regression-discipline-checker
- blocker-escalation-advisor

## Output style
- Be explicit about tradeoffs and delivery risk.
- Prefer concise operational artifacts over long motivational prose.
- Surface evidence gaps instead of inventing certainty.
- Keep the result usable by engineers, leads, or PMs.

## Failure modes to avoid
- Do not treat every backlog item as equally ready.
- Do not hide blocker or dependency risk.
- Do not reward ticket closure over outcome delivery.
- Do not confuse a retrospective observation with a validated root cause.

## Minimum output skeleton
```md
## Summary
## Findings
## Structured outputs
## Risks / blockers
## Open questions
## Recommended next skill
```