Section 2 · tasks.md
tasks.md Structure
Version-controlled task file — grouped by dependency, linked to requirements, with verification steps per task.
Three Pillars
Groups by Dependency
Tasks ordered so dependencies are explicit — foundation before logic before verification.
Group A (Data) → Group B (Logic) → Group C (Tests)Link Back to Requirements
Every task references a REQ-XXX from requirements.md — no orphan work.
Requirement: REQ-002 — Data lifecycleVerification Steps
Each task includes checkbox criteria that define done objectively.
[ ] Message schema validates required fieldsFull Task List — Messaging Example
Design the message data structure
Requirement: REQ-002 — Data lifecycle
Depends on: —
Define message schema: id, senderId, receiverId, body, status, createdAt, deletedAt
Verification
- Schema includes all fields from data lifecycle spec
- Status enum covers: pending, sent, failed, deleted
- Soft-delete sets deletedAt without removing record
Implement the send message function
Requirement: REQ-001 — User roles
Depends on: Task 1
Sender composes and dispatches; message persisted only on confirmed delivery
Verification
- Sender can create a message with receiverId and body
- Message not persisted until delivery confirmed
- Receiver can fetch the message after send
Create error handling for failed messages
Requirement: REQ-003 — Error behaviour
Depends on: Task 2
On send failure, surface retry UI; no orphan records; retry without duplicate
Verification
- Failed send shows user-facing retry option
- No orphan records in database on failure
- Retry succeeds without creating duplicates
Write unit tests for message sending
Requirement: REQ-001, REQ-002, REQ-003
Depends on: Task 3
Test happy path send, soft-delete, failed send + retry
Verification
- Happy path: send → persist → receiver reads
- Soft-delete hides message from sender view
- Failed send triggers retry flow without duplicate
Example — Messaging App Tasks
After clarifying the send-message spec, /create-tasks produces atomic, dependency-ordered tasks linked to requirements.
A — Data Foundation
Task 1: Design the message data structure
Requirement
REQ-002 — Data lifecycle
Depends on
—
Define message schema: id, senderId, receiverId, body, status, createdAt, deletedAt
Verification
templates/tasks.md in the repository.