definition-of-donelisted

# Definition of Done Project-level standards that every completed task must satisfy. Unlike acceptance criteria (which vary per task), DoD is a fixed quality baseline. ## Definition of Done vs. Acceptance Criteria | | Acceptance Criteria | Definition of Done | |---|---|---| | **Scope** | Specific to one task or spec | Applies to every increment | | **Changes** | Different per task | Fixed and unchanging | | **Answers** | "Did we build this correctly?" | "Can we confidently ship this?" | | **Defined By** | During task planning | Project-level standard | | **Example** | "User can reset password" | "Tests pass, no regressions, docs updated" | **Key**: A task is only done when it meets **both** its acceptance criteria **and** the Definition of Done. --- ## Completion Standards Checklist Before declaring a task complete, ensure all items below are satisfied: ### Correctness - [ ] All acceptance criteria are met - [ ] Code runs and behaves as intended (verified at runtime, not just compiled or typechecked) - [ ] New functionality is covered by tests: tests fail without the change, pass with it - [ ] Existing tests still pass (no regressions) - [ ] Edge cases and error paths are handled, not just the happy path ### Quality - [ ] Code clearly expresses intent through naming and structure; no comments needed to understand what it does - [ ] No duplicated business logic - [ ] No dead code, debug output, or commented-out blocks - [ ] Changes are scoped to the task; no unrelat