implementlisted

# Implement Implement the work the user named. A passing command or commit is not enough: use `/delivery-proof` to prove the ticket at the level its criteria require. If that companion skill is not installed, apply the evidence checklist and closure rules in this skill directly; proof requirements never become optional. Verify `/tdd`, `/code-review`, `/delivery-proof`, and `/grilling` are installed before starting. Name any missing companion. Do not claim that a missing nested review or proof phase ran; use the embedded fallback only where this skill defines one. ## Process 1. **Pin the starting state.** Record the starting commit, branch, staged and unstaged changes, and in-scope untracked files. Treat pre-existing work as user-owned and keep it distinct from this ticket. 2. **Establish the execution contract.** When the source is a ticket, read its complete spec, decisions, blockers, comments, and original criteria; verify the spec is ready, the ticket is open, and every start blocker is satisfied; then claim it through the configured tracker and re-read it for concurrent changes before editing. A direct conversation request may proceed without a tracker artifact only when it clearly fits one session, contains no unresolved consequential choice, and its behavior and proof can be enumerated without invention. Write a compact in-turn execution contract with stable `AC-*` criteria and `OBL-*` items before editing. Otherwise route through `/to-spec` and `/to-tickets`. 3. **