What problem does it solve? Teams without an explicit, shared Definition of Done let "done" mean different things to different people, causing reopenings, 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: Bump the DoD via semver during retrospectives when recurring defects expose gaps, keeping the checklist aligned with newly automatable gates. - Per-Increment Checklists: Apply the DoD as an AND-logic checklist per increment so partially satisfied items never count as done. - Use Case: A team repeatedly reopens stories because "done" was declared with red test suites. Use this Skill to write a DoD binding every increment to green api/ui/E2E suites, OpenAPI compliance, and approved review, then track it in each work package's progress log. ## Quick Start Ask the assistant to draft a versioned Definition of Done for the team based on the project's actual CI gates and test suites.
