task-template.md

id	TASK-XX
title	<Short descriptive title>
source	PRD-XX:F-YY | ADR-XX
priority	high | medium | low
created	YYYY-MM-DD
started	YYYY-MM-DD
completed	YYYY-MM-DD
owner	<name/role>

Description

Describe what should be implemented and why this task exists.

Acceptance Criteria

• R1: When , the shall .
• R2: While , the shall .
• R3: If , then the shall .

Implementation Notes

Capture decisions, constraints, and relevant execution details as work progresses.

Verification

• Unit/automated tests updated or created
• Manual verification steps run
• Logs/metrics checked (if relevant)

Dependencies

• Blocking dependency:
• Related task(s):

ADR/PRD Updates

Changes that must be fed back into planning artifacts:

• Update ADR-XX:
• Update PRD-XX:
• Add memory entry in memory/learnings.md or memory/gotchas.md

Follow-Up Tasks

• Optional follow-up task proposal

---

Notes for Template Users

• Keep tasks small enough to complete in one focused implementation cycle.
• If acceptance criteria become ambiguous or non-EARS, pause and rewrite before coding.
• Do not move task to done with unresolved ADR/PRD update checkboxes.