KMP Delivery Lifecycle: Definition of Ready (DoR) & Definition of Done (DoD)

When to Use This Skill

Use this skill when:

• Evaluating an issue or task ticket before writing code to verify it meets the Definition of Ready (DoR)
• Specifying verifiable acceptance criteria (Given/When/Then) for complex feature initiatives
• Determining whether a task requires UI layout verification, accessibility audits, or performance benchmarks
• Verifying code against the Definition of Done (DoD) before opening or squash-merging a Pull Request
• Opening a PR or filing a bug that changes what users see — Phase 3A.3 before/after evidence is mandatory
• Preventing premature feature sign-off, untested regressions, or unverified multiplatform claims

Do NOT use this skill when:

• Triaging issue hierarchy or avoiding GitHub comment spam (use kmp-github-issue-governance)
• Running static code quality rules or Detekt configuration (use kmp-code-quality)
• Performing ad-hoc profiling without delivery criteria (use kmp-benchmark or kmp-compose-web-performance)

Trigger keywords: definition of ready, definition of done, DoR, DoD, quality gate, delivery lifecycle, acceptance criteria, pr readiness, readiness checklist, done checklist, ui validation, performance gate, open a PR, pull request, gh pr create, before/after screenshots, visual evidence.