# Scope Handoffs

> Use when creating handoff documentation for branched conversations in stay-on-target focused mode

- Skill: `tomevault-io/scope-handoffs` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/scope-handoffs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/scope-handoffs/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/scope-handoffs

---


# Scope Handoffs

## Overview

Create handoff documentation when a conversation branches to a new topic.

## When to Use

When user selects option (C) "Note for later" during scope drift detection.

## Handoff Document Structure

```markdown
# Handoff: [Topic]

**Created:** [Date]
**From conversation:** [Brief description of original work]

## Summary

[2-3 sentences: What was happening, why we're branching]

## Original Context

- **Approach being used:** [What we were doing]
- **Key files:** [Files involved]
- **Decisions made:** [Important choices]

## New Direction

- **Topic:** [What the new exploration is about]
- **Why considered:** [What prompted this]
- **Questions to explore:** [Open questions]

## Relevant Context

[Any code snippets, decisions, or findings that would help the new conversation]
```

## Location

1. Check CLAUDE.md for `## Handoffs` section with Location
2. If not configured, use `.handoffs/` in project root
3. Ensure directory is gitignored

## Process

1. Ask 1-2 clarifying questions about the new direction
2. Write handoff doc based on conversation context + answers
3. Report: "Handoff saved to [path]. Ready to continue on [original task]."

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/technicalpickles) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-12 -->