name	iteration-handoff
description	Use when continuing work in a new chat, creating or updating iteration Work Status, writing handoff context, resuming an in-progress iteration item, or reducing Codex context/cost while preserving project continuity.

Iteration Handoff

Use this skill to carry project work across chats without relying on long conversation history.

Read the smallest useful set:

Each active iteration document should have a ## Work Status section near the top. Use it as the primary resume point for new chats.

Status values:

When the user asks to continue an iteration in a new chat:

Read the iteration document.
Find ## Work Status.
Continue the in_progress item unless the user named another item.
If several items are in_progress, ask the user which one to continue.
Use cost-control mode: avoid broad audits, avoid whole-log reads, and avoid web unless needed.

Before ending a long chat or switching phase:

Update the relevant Work Status item.
Include the latest run/log id, current error, files touched, tests run, and the next narrow step.
Mark completed items done.
Keep handoff concise; do not paste large logs.

Use with $iteration-workflow for starting/closing/merging iterations.
Use with $discuss-plan-execute for ambiguous refactors.
Use with $data-pipeline-safety-check before risky SQLite or large-data mutations.

name	iteration-handoff
description	Use when continuing work in a new chat, creating or updating iteration Work Status, writing handoff context, resuming an in-progress iteration item, or reducing Codex context/cost while preserving project continuity.