Feature Tasks

Status: Draft
Last updated: YYYY-MM-DD

Keep this checklist aligned with the feature plan increments. Stage tests before implementation, record verification commands beside each task, and prefer bite-sized entries (≤90 minutes). Mark tasks [x] immediately after each one passes verification—do not batch completions. Update the roadmap status when all tasks are done. When referencing requirements, keep feature IDs (F-), non-goal IDs (N-), and scenario IDs (S-<NNN>-) inside the same parentheses immediately after the task title (omit categories that do not apply). When new high- or medium-impact questions arise during execution, add them to docs/specs/4-architecture/open-questions.md instead of informal notes, and treat a task as fully resolved only once the governing spec sections (requirements/NFR/behaviour/telemetry) and, when required, ADRs under ``docs/specs/5-decisions/ reflect the clarified behaviour.

Checklist

• T--01 – (F--01, N--01, S--01).
  Intent: What this task delivers (tests, implementation, docs).
  Verification commands:

  • .php artisan test
  • node --test …
  • make phpstan
    Notes: Link to related spec sections or follow-ups.

• T--02 – .
  Intent: …
  Verification commands: …

Add as many tasks as necessary, keeping stored vs inline, CLI vs REST, and UI increments separate.

Notes / TODOs

Document temporary skips, deferred tests, or environment quirks so the next agent can follow up.