Agent skill
scope-handoffs
Use when creating handoff documentation for branched conversations in stay-on-target focused mode
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/scope-handoffs
SKILL.md
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
# 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
- Check CLAUDE.md for
## Handoffssection with Location - If not configured, use
.handoffs/in project root - Ensure directory is gitignored
Process
- Ask 1-2 clarifying questions about the new direction
- Write handoff doc based on conversation context + answers
- Report: "Handoff saved to [path]. Ready to continue on [original task]."
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?