# Handoff From Side To Main

> Use when the user asks for "Handoff from Side to Main" or wants to transfer a decision, critique, plan, or course correction from a side chat or side task back to its main task. Produce one concise, self-contained, paste-ready handoff containing only the side conversation's new actionable context.

- Skill: `aditya-ramabadran/handoff-from-side-to-main` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aditya-ramabadran/handoff-from-side-to-main`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aditya-ramabadran/handoff-from-side-to-main/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: aditya-ramabadran (https://skillmd.com/u/aditya-ramabadran)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/aditya-ramabadran/handoff-from-side-to-main

---


# Handoff From Side To Main

Produce one self-contained text block the user can paste into the main task.

The main task already has its own conversation context. Transfer only the new
information developed in this side task that the main task needs to act
correctly.

## Include

- The new decision, critique, discovery, or change of direction.
- The rationale needed to understand why the change matters.
- Relevant constraints, caveats, parameters, paths, identifiers, or exact
  values.
- The concrete action requested from the main task.
- Explicit non-goals or things the main task should avoid, when relevant.

## Output

Return one paste-ready block, usually fenced as plain text.

Use this shape when helpful:

```text
Handoff from side thread:

[Concise summary of what changed and why.]

Key details:
- ...

Requested main-task action:
- ...

Caveats / do-not-do:
- ...
```

For a small handoff, use a shorter block.

## Boundaries

- Be concise, but include enough context for the main task to act without
  seeing this side conversation.
- Treat inherited parent-task context as background, not material that needs
  to be repeated.
- Preserve exact names, paths, commands, branch names, run IDs, parameters,
  and links when they matter.
- Do not include hidden reasoning, chain-of-thought, or irrelevant
  exploration.
- Do not continue implementing in the side task unless the user separately
  asks.
- Do not mutate files, launch jobs, or contact external systems merely because
  the handoff requests those actions. The main task should decide and execute
  them.