Optional: another tool

Save before transferring

Read and validate the active task in your work-team folder. The fictional example below illustrates the same format. Keep its revision, status, and next action only in the header. Its Handoff section names artifacts, evidence, blockers, and restart guidance.

## Handoff

Read the header for current state and next action. No artifact exists yet.
When an artifact is saved, record its path and verified work here, plus blockers
and how a new session should continue from the header and saved evidence.

Selected files

• AGENTS.md and POLICY.md
• CLAUDE.md when using the Claude Code bridge
• CONTEXT-INDEX.md and tasks/meeting-times.md
• tasks/TASK-FORMAT.md when editing the task header
• roles/research.md and skills/compare-options/SKILL.md
• The saved recommendation artifact, if present
• Validator and proof record if needed for the checks

For your work team, select its active task, role, indexed inputs and artifact instead of these fictional example paths. All paths resolve from the selected folder root. Keep the same relative paths in a returned packet. Do not upload an entire account folder or old chat history.

Receive and return

Have the receiver report actual file access, loaded files, saved evidence, and exact next action. In a chat-only route, download or copy returned files, save them locally, and read them back. A generated answer is not a local save.

Keep one writer. Compare the canonical revision before accepting changes. Preserve a stale return as a proposal for reconciliation. An expected-revision check does not lock anything.

Scope the result

Record source and receiver product/version, direction, file paths, observed operation, date, and limitations. A successful A-to-B transfer does not prove B-to-A. Advanced manifests and concurrency belong in the Guide 2 outline.