gps-denied-desktop/_docs/00_templates/definition_of_done.md

Definition of Done (DoD)

A feature/task is considered DONE when all applicable items are completed.

---

Code Complete

• All acceptance criteria from the spec are implemented
• Code compiles/builds without errors
• No new linting errors or warnings
• Code follows project coding standards and conventions
• No hardcoded values (use configuration/environment variables)
• Error handling implemented per project standards

---

Testing Complete

• Unit tests written for new code
• Unit tests pass locally
• Integration tests written (if applicable)
• Integration tests pass
• Code coverage meets minimum threshold (75%)
• Manual testing performed for UI changes

---

Code Review Complete

• Pull request created with proper description
• PR linked to Jira ticket
• At least one approval from reviewer
• All review comments addressed
• No merge conflicts

---

Documentation Complete

• Code comments for complex logic (if needed)
• API documentation updated (if endpoints changed)
• README updated (if setup/usage changed)
• CHANGELOG updated with changes

---

CI/CD Complete

• All CI pipeline stages pass
• Security scan passes (no critical/high vulnerabilities)
• Build artifacts generated successfully

---

Deployment Ready

• Database migrations tested (if applicable)
• Configuration changes documented
• Feature flags configured (if applicable)
• Rollback plan identified

---

Communication Complete

• Jira ticket moved to Done
• Stakeholders notified of completion (if required)
• Any blockers or follow-up items documented

---

Quick Reference

Category	Must Have	Nice to Have
Code	Builds, No lint errors	Optimized
Tests	Unit + Integration pass	E2E tests
Coverage	>= 75%	>= 85%
Review	1 approval	2 approvals
Docs	CHANGELOG	Full API docs

---

Exceptions

If any DoD item cannot be completed, document:

1. Which item is incomplete
2. Reason for exception
3. Plan to address (with timeline)
4. Approval from tech lead