implementlisted

Implement the work described by the user in the spec or tickets. Use /tdd where possible, at pre-agreed seams. Run typechecking regularly, single test files regularly, and the full test suite once at the end. Once done and green, commit your work to the current branch and push it, then record the implementation below. What follows routes that exact candidate to `/code-review` — review the head you committed, never an uncommitted worktree. ## Record the implementation Producing a candidate is a durable workflow transition, and this skill owns it. Record it so the next session — human or agent — reads the same answer you did. `/tdd`, `/codebase-design`, `/domain-modeling` and any documentation lookup run *inside* this transition: they hand their evidence back here and record nothing of their own. **Only record once the candidate head is durable.** A head that exists in one worktree is not something a later reviewer can read, so, in order: 1. Finish the implementation and run the project's automated validation — typecheck, the tests covering the change, and the full suite once. A red loop is not a candidate. 2. Commit the work, then push the branch so the exact head is durable (`git rev-parse HEAD` is the candidate head; `git push` makes it readable). 3. Post one short evidence comment on the ticket — what this transition changed and which head it produced (`gh issue comment <ticket-issue> --body "..."`), naming the candidate head SHA explicitly. The successo