review-worklisted

# Review work Completion is not correctness, and you own the work you delegated. This skill coordinates review — who reviews, what verdict is recorded, and what happens when the work fails. The review method itself (evidence, findings, severity, verdict rules) is shared with every other reviewer, so apply `review-change` instead of re-deriving it here. ## When to use - A worker has returned and its result must be checked against the acceptance criteria. - `review_policy` in `team-mate.toml` requires review, or the change is important or risky enough that the implementer should not judge it alone. - Rework came back and needs another pass. ## When not to use - The task is still running: see `monitor-agents`. - You only need the review method (findings, severity, verdict): that is `review-change`. ## Inputs - The returned task from the ledger (`python3 scripts/tm.py task show <id>`): its goal, acceptance criteria, and iteration. - The worker's fresh output — `report`, `diff`, and the project's own check commands (from `load-project-context`). - `review_policy` from `team-mate.toml`, and the `review-change` method the reviewer applies. ## Procedure 1. **Assemble the review inputs.** Read the persisted task with `python3 scripts/tm.py task show <id>` for the goal, criteria, and iteration, then collect the worker's current output so the reviewer has fresh material: ```bash python3 scripts/tm.py report "<name>" python3 scripts/tm.py diff --cwd "