add-tasks-checklistlisted

# tasks.md Checklist Schema <!-- uses: - skill: add-architecture-discovery - mention: add-feature-specification - mention: /add.plan - command: /add.plan-to-ready - command: /add.wiki --> ## Overview `tasks.md` is the **single source of progress truth** for a feature (or subfeature, in epics). `plan.md` is the frozen spec; `tasks.md` is the developer's activity breakdown that absorbs all tick state — area work, contract validation, TDD evidence, and quality gates. ## When to Use - Generating a new `tasks.md` for a feature or subfeature - Per-area validator ticking sections after implementation - Deciding whether a section/item gets `[x]` or `[!]` - Reading tick state to gate review or delivery - Coordinator merging multi-area validator reports in `/add.plan-to-ready` ## When NOT to Use - Generating `plan.md` (use `/add.plan`, which writes it against the `feature-plan` schema) — `plan.md` carries prose contracts, not ticks - Generating `about.md` (use `add-feature-specification`) - Tick state for hotfixes (hotfixes do not use `tasks.md`) ## Canonical Structure `tasks.md` has **6 sections in this exact order with these exact headings** (validators parse by exact text). The 6th section (`## Validation Gates`) is **conditional** — present only when CLAUDE.md exposes a `validation_gates` block. ```markdown # Tasks: [feature or SF name] ## Metadata | Field | Value | |-------|-------| | Complexity | SIMPLE / STANDARD / COMPLEX | | Total tasks | [N] | | Services | databas