wrap-tasklisted

# Wrapping up an approved task **Project facts come from `.claude/workflow.json`**: `branch.integration` is what this skill pushes, `record.roadmap` is what step 6 reads, and `commitTrailer` names the session trailer. Without a manifest, fall back to the current branch and say in one line that you did. **This skill writes no record file.** The handoff — the part that makes this the handoff — belongs to `handoff-writer`, which step 3 invokes. Who owns what is [`~/.claude/workflow/ownership.md`](../../workflow/ownership.md). ## The `--wrap` shorthand `--wrap` invokes this immediately, with no confirmation and regardless of whether the work looks finished. It overrides every judgment call below: don't ask "is this really done?", don't wait for approval of the last deliverable, just run the closing ritual. Where a flag counts, and the authorization it confers, live in `shorthand-flags.sh` and [`~/.claude/README.md`](../../README.md) — one copy, not restated per skill. ## When it triggers - The user gives clear, final approval of the last deliverable in a unit of work ("done", "approved", "wrap this up", "looks good, that's it") — not approval of one intermediate step with more steps still coming. - Nothing in the same message pivots straight into related follow-up work — if it does, that follow-up is still the same unit of work, so don't wrap yet; let it finish first. - **Or: the session is about to end regardless of approval state** — the user says they're going