Section 3 · Verify
Per-Task Verification & Feature Sign-Off
Verification is the gate between tasks — not optional QA at the end. Every checkbox must pass before advancing.
Two Levels of Verification
Per-task
Task verification checkboxes
Defined in tasks.md for each atomic task. Must pass before the next task unlocks. Run after every implementation.
Feature-level
Acceptance criteria
From user stories in requirements.md. Run once all tasks are verified. Defines feature complete.
Verification Flow
Implement Task N
↓
Run task verification checkboxes
↓
All pass? ──no──→ Fix code → re-verify
│
yes
↓
Mark Task N complete
↓
More tasks? ──yes──→ Task N+1
│
no
↓
Run acceptance criteria from requirements.md
↓
Feature complete ✓Messaging Example — All Task Verifications
Task 1Design the message data structure
- Schema includes all fields from data lifecycle spec
- Status enum covers required states
- Soft-delete sets deletedAt without removing record
Task 2Implement the send message function
- Sender can create a message with receiverId and body
- Message not persisted until delivery confirmed
- Receiver can fetch the message after send
Task 3Create error handling for failed messages
- Failed send shows user-facing retry option
- No orphan records in database on failure
- Retry succeeds without creating duplicates
Task 4Write unit tests for message sending
- Happy path: send → persist → receiver reads
- Soft-delete hides message from sender view
- Failed send triggers retry flow without duplicate
Feature Completion Criteria
- All tasks in tasks.md verified
- All verification checkboxes checked
- All user story acceptance criteria from requirements.md pass
- Implementation matches spec — not retrofitted spec matching code
What does the spec say should happen — not what does the code happen to do. If verification fails, fix the code. Never rewrite the spec to match accidents.