Work Todo

---
description: Work through every remaining (unchecked) task in TODO.md — implement, commit, move it to todo-history.md under today's date, and attach UI proof
---

## Goal

Drive the project's root `TODO.md` to completion. Pick up every remaining (unchecked) task, implement it for real, commit it on its own, move it out of `TODO.md` into `todo-history.md` (grouped under today's date), and attach UI proof when the change is visible in the app. Repeat until no unchecked tasks remain in `TODO.md`.

Completed tasks never stay in `TODO.md` as `- [x]`; the finished log lives in `todo-history.md`, one dated block per day.

If `$ARGUMENTS` is non-empty, scope the run to only the task(s) it describes (by number, by quoted text, or "just the next one"). Otherwise, work the whole remaining list top to bottom.

## Preflight

1. Run `git status --porcelain`. If the working tree is **not** clean, stop and report — do not start on top of uncommitted work. Ask the user to commit, stash, or discard first.
2. Read root `TODO.md`. Collect the unchecked tasks — lines starting with `- [ ]`. If there are none, report "TODO.md is already complete" and stop.
3. Restate the list of remaining tasks back to the user as a numbered plan before starting, so they can redirect you. Then begin.

## Per-task loop

For **each** unchecked task, in order, do the following completely before moving to the next:

1. **Understand it.** The task text is usually in Spanish and may reference a mockup file (e.g. `post-conversation-mockup.html`, `landing-full-mockup.html`) — read the referenced file when one is named. Match the existing pattern in the codebase first (see the project `CLAUDE.md`): shared schemas before backend before frontend, shadcn components, React Query, i18n keys in both `en.json` and `es.json`, named exports, kebab-case files.

2. **Implement it for real.** No stubs, no TODO comments left behind. Add backend + shared + frontend pieces as the task requires. Write unit tests when you add a feature, per the testing rules in `CLAUDE.md`.

3. **Verify it compiles and passes checks.** From the repo root run `pnpm lint`, `pnpm typecheck`, and `pnpm test`, and fix anything that fails before committing. The husky `pre-commit` hook (`.husky/pre-commit`) already runs these three on `main` and will **abort the commit** if they fail — but run them yourself first so a failure surfaces here instead of blowing up the commit step mid-loop. Never commit red.

4. **Run the review loop.** Before committing, run the `review-loop` skill on this task's pending changes — it iteratively runs `/review-changes` (auditing the changes against `CLAUDE.md` conventions and flagging leftover complexity), applies the recommendations, and re-reviews until the report comes back clean. Address every finding it surfaces. If the review loop changed code, re-run the checks from step 3. Only proceed once the review is clean **and** lint/typecheck/test are green again.

5. **Capture UI proof when it applies.** If the change is visible in the running app (a page, form, layout, redirect, badge, etc.), capture a screenshot:
   - Use the `feature-checker` agent (it drives the running app at `http://localhost:5174` with Playwright) to exercise the changed feature and save screenshots under `screenshots/` in the repo root.
   - Name the file after the task, e.g. `screenshots/<short-task-slug>.png`. Capture before/after or multiple states when the task implies them (light/dark, en/es, empty/filled), mirroring the existing TODO entries.
   - If the task is **not** user-visible (pure backend, config, types, refactor), skip the screenshot — note "no UI proof (backend/internal change)" in the history entry (step 6) instead.

6. **Move the task into the dated history log.** Do **not** mark it done in place — instead move it out of `TODO.md` and into `todo-history.md`:
   - **Remove** the task's line from `TODO.md`, including any indented continuation lines that belong to the same task block.
   - Get today's date with `date +%F` (format `YYYY-MM-DD`).
   - In root `todo-history.md`, ensure there's a `## <today's date>` heading for the current day. If the file's last date heading isn't today's, add a new `## <today's date>` heading at the **end** of the file; otherwise reuse the existing one. All tasks finished on the same day live under that single date heading.
   - **Append** the task under today's heading as a `- [x]` entry with a concise summary in the existing house style — a short `—` dash clause describing the change, then `Proof: \`screenshots/<file>.png\`` (with parenthetical state labels) when a screenshot exists. One entry per task, matching the one-line style of the surrounding `todo-history.md` entries.

7. **Commit just this task.** Stage everything for this task — the code, the tests, the updated `TODO.md` (task line removed), the updated `todo-history.md` (task appended under today's date), and the screenshots — and make a single commit. Write a clear message summarizing the task (in English), and end it with the required trailer:

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

One task = one commit. Do not batch multiple tasks into one commit. Commit on the current branch — `main` is fine; do **not** create a feature branch. The husky pre-commit hook re-runs lint/typecheck/test on `main`; if the commit is rejected, fix the reported failure and retry the commit rather than bypassing the hook (never use `--no-verify`).

8. **Report and continue.** Print a one-line summary of the finished task (what changed, commit hash, proof path) and move to the next unchecked task.

## Finishing

When `TODO.md` has no remaining open tasks, stop and give the user a summary: the tasks completed (now logged in `todo-history.md` under today's date), one commit per task (list the hashes), and the screenshots produced. Do not push unless the user asks.

## Rules

- **One task, one commit** — always in this order: implement