You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. ---
  2. title: 'Enhanced Dev Story Definition of Done Checklist'
  3. validation-target: 'Story markdown ({{story_path}})'
  4. validation-criticality: 'HIGHEST'
  5. required-inputs:
  6. - 'Story markdown file with enhanced Dev Notes containing comprehensive implementation context'
  7. - 'Completed Tasks/Subtasks section with all items marked [x]'
  8. - 'Updated File List section with all changed files'
  9. - 'Updated Dev Agent Record with implementation notes'
  10. optional-inputs:
  11. - 'Test results output'
  12. - 'CI logs'
  13. - 'Linting reports'
  14. validation-rules:
  15. - 'Only permitted story sections modified: Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, Status'
  16. - 'All implementation requirements from story Dev Notes must be satisfied'
  17. - 'Definition of Done checklist must pass completely'
  18. - 'Enhanced story context must contain sufficient technical guidance'
  19. ---
  20. # 🎯 Enhanced Definition of Done Checklist
  21. **Critical validation:** Story is truly ready for review only when ALL items below are satisfied
  22. ## 📋 Context & Requirements Validation
  23. - [ ] **Story Context Completeness:** Dev Notes contains ALL necessary technical requirements, architecture patterns, and implementation guidance
  24. - [ ] **Architecture Compliance:** Implementation follows all architectural requirements specified in Dev Notes
  25. - [ ] **Technical Specifications:** All technical specifications (libraries, frameworks, versions) from Dev Notes are implemented correctly
  26. - [ ] **Previous Story Learnings:** Previous story insights incorporated (if applicable) and build upon appropriately
  27. ## ✅ Implementation Completion
  28. - [ ] **All Tasks Complete:** Every task and subtask marked complete with [x]
  29. - [ ] **Acceptance Criteria Satisfaction:** Implementation satisfies EVERY Acceptance Criterion in the story
  30. - [ ] **No Ambiguous Implementation:** Clear, unambiguous implementation that meets story requirements
  31. - [ ] **Edge Cases Handled:** Error conditions and edge cases appropriately addressed
  32. - [ ] **Dependencies Within Scope:** Only uses dependencies specified in story or project-context.md
  33. ## 🧪 Testing & Quality Assurance
  34. - [ ] **Unit Tests:** Unit tests added/updated for ALL core functionality introduced/changed by this story
  35. - [ ] **Integration Tests:** Integration tests added/updated for component interactions when story requirements demand them
  36. - [ ] **End-to-End Tests:** End-to-end tests created for critical user flows when story requirements specify them
  37. - [ ] **Test Coverage:** Tests cover acceptance criteria and edge cases from story Dev Notes
  38. - [ ] **Regression Prevention:** ALL existing tests pass (no regressions introduced)
  39. - [ ] **Code Quality:** Linting and static checks pass when configured in project
  40. - [ ] **Test Framework Compliance:** Tests use project's testing frameworks and patterns from Dev Notes
  41. ## 📝 Documentation & Tracking
  42. - [ ] **File List Complete:** File List includes EVERY new, modified, or deleted file (paths relative to repo root)
  43. - [ ] **Dev Agent Record Updated:** Contains relevant Implementation Notes and/or Debug Log for this work
  44. - [ ] **Change Log Updated:** Change Log includes clear summary of what changed and why
  45. - [ ] **Review Follow-ups:** All review follow-up tasks (marked [AI-Review]) completed and corresponding review items marked resolved (if applicable)
  46. - [ ] **Story Structure Compliance:** Only permitted sections of story file were modified
  47. ## 🔚 Final Status Verification
  48. - [ ] **Story Status Updated:** Story Status set to "review"
  49. - [ ] **Sprint Status Updated:** Sprint status updated to "review" (when sprint tracking is used)
  50. - [ ] **Quality Gates Passed:** All quality checks and validations completed successfully
  51. - [ ] **No HALT Conditions:** No blocking issues or incomplete work remaining
  52. - [ ] **User Communication Ready:** Implementation summary prepared for user review
  53. ## 🎯 Final Validation Output
  54. ```
  55. Definition of Done: {{PASS/FAIL}}
  56. ✅ **Story Ready for Review:** {{story_key}}
  57. 📊 **Completion Score:** {{completed_items}}/{{total_items}} items passed
  58. 🔍 **Quality Gates:** {{quality_gates_status}}
  59. 📋 **Test Results:** {{test_results_summary}}
  60. 📝 **Documentation:** {{documentation_status}}
  61. ```
  62. **If FAIL:** List specific failures and required actions before story can be marked Ready for Review
  63. **If PASS:** Story is fully ready for code review and production consideration