boomerang

Executes self-contained tasks in an isolated forked context and returns a compact summary.

13|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/vedang/dotagents --skill boomerang-vedang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boomerang
Source: https://github.com/vedang/dotagents/tree/main/claude/skills/boomerang
Command: npx skills add https://github.com/vedang/dotagents --skill boomerang-vedang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long autonomous tasks flood the main conversation with intermediate reasoning, tool output, and token weight that the user never needs. This Skill offloads self-contained work to a forked context so the main conversation only receives a compact, structured summary of the outcome. ## Core Features & Use Cases - Isolated Execution: Runs the task in a forked context using a general-purpose agent, keeping intermediate steps out of the main conversation. - Autonomous Operation: Works without asking questions, making reasonable assumptions and documenting them in the summary instead of blocking. - Structured Summary Output: Returns a fixed-format report covering outcome, changed files, verification commands, assumptions, and follow-ups. - Use Case: Delegate a chore like "rename all usages of the old config key across the repo and update the tests" — the forked agent does the edits and the main conversation only sees which files changed and what still needs review or committing. ## Quick Start Ask the agent to run the boomerang skill with a self-contained task such as "boomerang: update all deprecated API calls in the src directory and report what changed".

Frequently Asked Questions about boomerang

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a task in an isolated context without cluttering my conversation?

Invoke the boomerang skill with a self-contained task description. It forks a separate context where a general-purpose agent completes the work, and only a compact summary of the outcome returns to your main conversation.

What kinds of tasks work best with forked autonomous execution?

Self-contained tasks whose intermediate steps do not matter to the ongoing conversation work best, such as bulk renames, dependency updates, or test fixes. Tasks needing user decisions mid-flight are poor fits since the forked agent cannot ask questions.

Does the boomerang skill commit changes it makes?

No, the forked agent explicitly does not commit. It follows global instructions like hygiene and quality gates but leaves committing to the main conversation, listing follow-ups in its summary.

What happens if the forked task cannot be completed?

The agent marks the outcome as partial or blocked in its summary and explains why in one sentence. It also lists assumptions made and follow-ups the main agent or user still needs to handle.

When should I avoid delegating work to a forked context?

Avoid it when the task requires interactive clarification, when you need to observe intermediate reasoning, or when the work is tightly coupled to decisions being made in the main conversation.