wrap-up

name	wrap-up
description	Wrap-up, implementation summary, or final handoff. Use after build/test/review to report results and close todowrite/HANDOFF/PROGRESS only when applicable.

Wrap-up

Required final summary template

## Summary
- <what was done>

## Files changed
- `<path>` — <purpose of change>

## Commands run
- `<command>` — <result and what it proved>

## State updates
- Live tracker: `todowrite` completed / not used / skipped — <why>
- Durable handoff: `.agents/HANDOFF.md` updated / not needed / skipped — <why>
- Heavy-task progress: `.agents/PROGRESS.md` updated / not needed / skipped — <why>
- Optional roadmap/decisions: updated / not present / skipped — <why>
- Task state: <path/url/status updated> / none matched / skipped — <why>
- Review evidence: `<artifact paths consumed/created and unresolved #F<n> refs>` / valid Level 0/1 exemption — <why>

## Failures or remaining risks
- <failure/risk or `None`>

## Follow-ups
- <optional next action or `None`>

## Confidence
- low / medium / high

Mention if docs/memory/durable progress/task/commit/PR were skipped or require explicit user request.

Before the final user-facing response, close or revise active todowrite items. Update .agents/HANDOFF.md only for boundary/incomplete work. Update .agents/PROGRESS.md only when heavy-task criteria applied and the repo/session already uses it.

For Level 2+ implementation, report the final code-review artifact. For Level 3+, also report the plan-review artifact; report specialist artifacts when delegated. Do not duplicate findings: cite <artifact-path>#F<n> and its disposition. A Level 0 or genuinely tiny Level 1 exemption must be stated explicitly.

Clock-out rules

• For implementation work, require build/test/review results before final handoff.
• A task is not complete unless verification evidence is reported.
• When a repo harness exists, record final state in todowrite or the existing primary tracker and explain if skipped. Do not create .agents/PROGRESS.md for routine completed tasks.
• When memory/task state conflicts with repo state, list the mismatch as a risk; do not create extra state files just to reconcile it.
• Do not commit, push, or create PRs unless the user explicitly requested it.

Durable handoffs

Use .agents/HANDOFF.md with templates/HANDOFF.md only for durable boundaries: paused work, blockers, user approval/manual testing, transfer to another agent/user, or incomplete session end. For routine completed tasks, the final user response is enough unless the Orchestrator asks for the file.

Durable handoffs should include current status, owner, phase/subtask, completed work, files changed, verification, open blockers/risks/follow-ups, resume instructions, and relevant state-file status.