Purpose
A task (ticket) is the atomic unit of work. A good one can be picked up and done without questions: clear what, why, and how to know it's done. A bad one ("fix search") wastes time on back-and-forth and breeds "built the wrong thing".
Template
# <Verb + result> ← e.g. "Add auto-clipping of videos into Shorts"
## Context — why, what pain, for whom. Links.
## Acceptance Criteria — observable, testable, binary; cover an edge/error case.
## Out of scope — what we don't do here.
## Definition of Done — tests green · review · (web) browser pass · merged · docs · neighbors intact.
## Estimate — <story points> · Priority <P1/P2/P3>
Example 1 — feature
# Add export of the personal core to JSON
## Context — users want to move favorites/notes across devices; data is locked in the browser.
## Acceptance Criteria
- [ ] "Export" downloads a .json with favs, notes, collections, backlog.
- [ ] schemaVersion is written for future migration.
- [ ] Import on another device restores data 1:1.
- [ ] Corrupt/incompatible file → clear error, data not wiped.
## Definition of Done — export/import unit tests green · browser pass · review · docs.
## Estimate — 5 · Priority P2
Example 2 — bug
# Fix focus loss when closing the modal on mobile
## Context — on iOS Safari focus isn't returned to the opener, breaking keyboard nav & a11y (3 support tickets).
## Acceptance Criteria
- [ ] On close, focus returns to the element that opened the modal.
- [ ] Reproduced on iOS Safari and Android Chrome — fixed on both.
- [ ] Regression: desktop open/close still works.
## Definition of Done — focus-return test · mobile browser pass · review · merged.
## Estimate — 2 · Priority P1
Quality checklist
- Title is verb + result.
- "Why" is clear (context, pain).
- Criteria observable, testable, binary.
- Edges/errors covered, not just happy path.
- "Out of scope" present.
- DoD explicit; estimate & priority set.
Common mistakes
Noun titles; no "why"; impression-criteria; scope creep; giant task (≥13 → epic, split).