# Tasks for SPEC-000

Status legend: [ ] pending, [x] done

Tasks follow TDD ordering: a failing-test task precedes the implementation task it covers (see `.devfoundry/rules/general.md`).

- [ ] Task 1: <description> — files: <file list>
- [ ] Task 2 (test, red): Write failing test(s) for <behavior> — files: <test file list> — completed: <YYYY-MM-DD HH:MM>
- [ ] Task 3 (implementation, green): Implement <behavior> until Task 2's test(s) pass — files: <file list> — completed: <YYYY-MM-DD HH:MM>
- [ ] Task 4: <description> — files: <file list>

## Notes
- Add dependency order notes here if tasks must be done in sequence.
- For legacy stacks without a test harness, replace "test, red" tasks with "write manual verification step" tasks, authored before the implementation task they verify.
- Record a `completed: <timestamp>` note on every test/verification and implementation task when it is checked off. The QA Verifier uses these to confirm the test's timestamp precedes its paired implementation's (per `.devfoundry/skills/regression-check.md`).