Verification Checklist
Product verification
Section titled “Product verification”Does the work match the defined intent?
- Does the work satisfy the linked behaviours?
- Does the work support the linked features?
- Does the work match the success criteria?
- Has the work avoided creating new product behaviour without approval?
- Are user-facing changes consistent with the defined intent?
Architecture verification
Section titled “Architecture verification”Does the work respect the defined shape of the system?
- Does the work follow the defined solution strategy?
- Does the work use the expected building blocks?
- Does the work respect the system context and boundaries?
- Does the work use the defined data structures and interfaces?
- Does the runtime behaviour match the defined flow?
- Does the work avoid changing unrelated architecture?
Rules verification
Section titled “Rules verification”Were the project’s rules followed?
- Were applicable cross-cutting rules followed?
- Were relevant decisions followed?
- Were delivery rules followed?
- Were security rules followed?
- Were privacy or data handling rules followed?
- Were logging, monitoring, or error handling rules followed where relevant?
Scope verification
Section titled “Scope verification”Did the work stay inside the slice?
- Is the implementation limited to the slice scope?
- Were out-of-scope items avoided?
- Were only expected files or areas changed?
- If unexpected files changed, was the reason explained?
- Did AI avoid adding unrequested features?
Test verification
Section titled “Test verification”Does the work prove itself?
- Were required automated tests added or updated?
- Do tests cover success paths?
- Do tests cover failure paths?
- Do tests cover validation rules?
- Do tests map back to acceptance criteria?
- Were tests run successfully?
Manual review
Section titled “Manual review”Does the feature actually work?
- Does the feature work as described?
- Are errors handled clearly?
- Is the user experience acceptable for this slice?
- Are edge cases handled or documented?
- Are assumptions listed?
- Are unresolved questions documented?
Documentation verification
Section titled “Documentation verification”Is the project definition still accurate?
- Was the AIDD-17 project definition updated if behaviour changed?
- Were interfaces updated if contracts changed?
- Were decisions recorded if new decisions were made?
- Was the implementation plan updated?
- Were follow-up slices created where needed?
AI output review
Section titled “AI output review”Did AI report what it did?
Check that AI provided:
- summary of changes
- files changed
- tests added or changed
- assumptions made
- unresolved questions
- verification performed