Definition of Done Checklist

A starter checklist your team can adapt and enforce. Use it as the universal bar every ticket must meet before it counts as shipped.

Download .md
# Definition of Done — {{ TEAM_NAME }}

Every ticket must satisfy every item below before it is considered done. Without exception.

## Code

- [ ] Implementation complete
- [ ] Edge cases handled (or explicitly out-of-scope and documented)
- [ ] No commented-out code
- [ ] No `TODO` / `FIXME` left without an issue link
- [ ] Lint and typecheck pass

## Tests

- [ ] Unit tests added or updated
- [ ] Integration tests added or updated where the change touches a workflow
- [ ] All tests pass on CI

## Review

- [ ] At least one review approval
- [ ] All review comments addressed or filed as follow-ups
- [ ] Reviewer ran the change locally if it's a UI change

## Deploy

- [ ] Merged to main
- [ ] Deployed to staging (or production behind a feature flag)
- [ ] Smoke-tested by the author after deploy

## Observability

- [ ] Telemetry / logging added for any new user-facing flow
- [ ] Errors raise to Sentry (or equivalent)
- [ ] Feature flag killswitch documented if applicable

## Documentation

- [ ] User-facing change → public docs updated
- [ ] Internal change → README / runbook updated
- [ ] Acceptance criteria from the ticket all met

---

Glossary: https://sprintflint.com/glossary/definition-of-done

Definition of Done — {{ TEAM_NAME }}

Every ticket must satisfy every item below before it is considered done. Without exception.

Code

  • Implementation complete
  • Edge cases handled (or explicitly out-of-scope and documented)
  • No commented-out code
  • No TODO / FIXME left without an issue link
  • Lint and typecheck pass

Tests

  • Unit tests added or updated
  • Integration tests added or updated where the change touches a workflow
  • All tests pass on CI

Review

  • At least one review approval
  • All review comments addressed or filed as follow-ups
  • Reviewer ran the change locally if it’s a UI change

Deploy

  • Merged to main
  • Deployed to staging (or production behind a feature flag)
  • Smoke-tested by the author after deploy

Observability

  • Telemetry / logging added for any new user-facing flow
  • Errors raise to Sentry (or equivalent)
  • Feature flag killswitch documented if applicable

Documentation

  • User-facing change → public docs updated
  • Internal change → README / runbook updated
  • Acceptance criteria from the ticket all met

Glossary: https://sprintflint.com/glossary/definition-of-done

Stop filling in templates.

SprintFlint runs the sprint for you — capacity, velocity, retros, burndown — with no template to keep up to date.