hand-offlisted

# Hand-off Delegate a defined scope of work to a fresh Claude Code subagent, with full context preserved across the boundary. Each handoff is recorded as a folder at `<project-root>/.handoffs/<feature>/` containing `input.md` (the brief) and `output.md` (the result). In git projects, `baseline.txt` is also captured to enable recovery if the subagent fails to write `output.md`. All files persist on disk as an audit trail. ## When to use Trigger this skill when: - The user types `/hand-off` (literal slash-command style) - The user asks to "hand off", "delegate to a subagent", "spin this off", "fork this", or "pass this to a fresh agent" - The user signals context exhaustion and wants a chunk of work moved to its own session ("I'm running out of context, let me spin this off") ## Workflow ### 1. Identify the scope (and clarify if unclear) Before writing anything, determine: - **What is being handed off?** The specific task or set of tasks the subagent must complete. - **What context does the subagent need?** Relevant files, decisions already made, constraints, and the current state of the workspace. If either is unclear, **stop and ask the user** before proceeding. Do not guess. Examples of useful clarifying questions: - "Is the handoff just task X, or should it also include the follow-up Y we discussed?" - "Should the subagent see the work we did on `<file>`, or start fresh?" - "What does 'done' look like for this handoff?" - "Any constraints I should pass along — fil