report-progresslisted

# Report progress The developer should be able to tell what happened and what to decide without reading a worker session. A worker returns through the harness's subagent tool and leaves its `.teammate-report.md` in the project root; this skill reads that report with `python3 scripts/tm.py report` and is the developer-facing wrapper over the shared `handoff-report` contract. ## When to use - A task is ready for approval. - A worker is blocked, failed, or the review loop is not converging. - A consequential action — merge, push, publish, deploy, delete, or exposing secrets — needs the developer's approval. - A worker has run past the long-run threshold (about 15 minutes) without returning: one interim status, per `monitor-agents`. - Work completes or is cancelled. ## When not to use - Nothing important changed since the last report. Routine waiting belongs to `monitor-agents`, not a developer report; only crossing the long-run threshold earns the one interim status above. ## Inputs - The persisted task (`python3 scripts/tm.py task show <id>`): goal, criteria, iteration, verdict, and findings. - The shared `handoff-report` contract and `templates/report.md`. - The decision you are asking the developer to make. ## Procedure 1. **Assemble the report** with the `handoff-report` contract, filling `templates/report.md`. Read the persisted task with `python3 scripts/tm.py task show <id>` so the report reflects the recorded goal, criteria, iteration, and rep