What problem does it solve? Teams without an explicit, shared Definition of Done let 'done' mean different things to different people, causing reopened work, hidden technical debt, and unreliable velocity. This Skill establishes a versioned, verifiable DoD where every item maps to an objective check such as a CI gate, test suite, or review approval. ## Core Features & Use Cases - DoD Authoring: Draft a Definition of Done where each item has an objective verification (pytest exit codes, Jest runs, Playwright E2E, OpenAPI schema drift checks, code review approval). - Versioned Evolution: Evolve the DoD through retrospectives with semver bumps and recorded rationale for each change. - Per-Increment Checklists: Apply the DoD as an AND-logic checklist per increment so partially compliant work is never marked done. - Use Case: A team keeps reopening stories because 'done' was ambiguous. Use this Skill to inventory the project's real CI gates, write a DoD where every item is verifiable with a command, and enforce it on every increment. ## Quick Start Ask the assistant to draft a versioned Definition of Done for the team based on the project's actual CI pipeline, test suites, OpenAPI generation, and code review process.
