Definition of Done Skill

Use When

Use when defining observable completion criteria for code, tests, documentation, review, and deployment readiness. Use definition-of-ready for pre-sprint admission and formal-review-gates for lifecycle approvals.

Do not use when a more specific upstream or downstream skill owns the task, or when the required project context has not been prepared.
Do not use this skill to fabricate missing project facts, legal conclusions, test results, approvals, or certification claims.

Artefact	Source or provider	Required?	Missing-input behaviour
Engineering standards; test strategy; documentation obligations; review policy; deployment and rollback controls; applicable compliance gates	Engineering, QA, operations, security, and product owners	Yes	Stop dependent work; name the missing item, owner, and decision impact. A review check remains `not assessed`.
Scope, audience, baseline/version, and accountable decision owner	Requester or project context	Yes	Ask for or record the gap; do not infer authority or scope.