wrap-up

Wrap Up

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool.

The user must leave now. Convert everything in flight — the session's own work and any subagents' — into either secured completed work or a decision-complete handoff, without losing progress. Optimize for wall-clock time over polish: target roughly five minutes end to end. When present, use $ARGUMENTS as the user's deadline or departure note. A stated deadline overrides the default budget.

In a single-agent session, skip Worker Wind-Down and apply the same rules to the session's own in-progress work.

Freeze

Immediately and before anything else:

• Launch no new subagents, waves, or scopes. Reclassify queued or not-yet-started work as remaining work for the handoff.
• Stop your own expansion into new files or subsystems. Finish only the edit currently mid-flight so no file is left syntactically broken or half-rewritten.
• Start no new long-running validation. Record unverified claims as unverified instead of proving them.

Worker Wind-Down

Enumerate active subagents with the host's agent listing, then message every messageable worker — in Claude Code through SendMessage, in Codex CLI through the native subagent messaging tool — with a wrap-up order. Send all messages in one turn as parallel calls:

• Finish the smallest safe unit: complete the current edit, leave no file half-written, start nothing new.
• Skip remaining validation; report what ran and what was skipped instead.
• Reply with exactly these named fields: status (completed, partial, or not-started), summary, changed files listing only files actually touched, verification listing commands run with outcomes plus checks skipped, remaining work, and risks/blockers.

Give messageable workers a soft deadline of two to three minutes, or less when the user's stated deadline demands it. The deadline limits how long this skill waits. It is never permission to cancel a worker. When any worker remains active at the deadline, leave its agent, subprocess runner, and watcher running under their existing timeouts. Never use a stop, interrupt, kill, or termination action merely because wrap-up was invoked, the worker is silent, or it has no message channel.