---
name: nests-handoff
description: Use when continuing work through Nests, handling a nests.sh link, avoiding agent cold starts, or preparing a handoff between Codex, Claude Code, OpenCode, or another coding harness.
---

# Nests Handoff Skill

Nests is a repo-scoped memory handoff layer. It captures snapshots with compiled
context, handoffs, diffs, observed events, and artifacts so another agent can
continue without a cold start.

## Startup

1. Run `nests status`.
2. If Nests reports a discovered or stale remote, run `nests pull`.
3. Run `nests context --for codex`, `nests context --for claude`, or
   `nests context --for agent`.
4. Continue from the handoff, but verify claims against observed evidence.

Do not infer that no Nest exists just because `.nests/` is absent. Absence
means discovery should run.

## While Working

- Use `nests report "<text>"` for meaningful claims.
- Use `nests artifact add <path>` for important files or outputs.
- Keep claims separate from evidence.
- Run normal project verification before claiming completion.

## Handoff

Before ending work or sending another agent in:

```bash
nests snapshot -m "<what changed and what remains>"
nests share
```

If the work should be continued elsewhere:

```bash
nests share
```

## Evidence Model

Treat these as claims:

- reports
- handoff notes
- agent summaries

Treat these as evidence:

- git diffs
- file state
- command output
- hook events
- registered artifacts

When claims and evidence conflict, trust evidence and report the discrepancy.