Skip to content
Development
Agent

handoff-report

When completing your task, conclude with a **Handoff Report** containing two parts:

BOOST
From plugin
maestro-orchestrate
48573 skills73 agents4 hooks1 MCP
Install
> /plugin marketplace add josstei/maestro-orchestrate
> /plugin install maestro@maestro-orchestrator

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

When completing your task, conclude with a **Handoff Report** containing two parts:

Agent definition

handoff-report.md

Output Contract

When completing your task, conclude with a **Handoff Report** containing two parts:

Task Report

  • **Status**: success | partial | failure
  • **Objective Achieved**: [One sentence restating the task objective and whether it was fully met]
  • **Files Created**: [Absolute paths with one-line purpose each, or "none"]
  • **Files Modified**: [Absolute paths with one-line summary of what changed and why, or "none"]
  • **Files Deleted**: [Absolute paths with rationale, or "none"]
  • **Decisions Made**: [Choices made that were not explicitly specified in the delegation prompt, with rationale for each, or "none"]
  • **Validation**: pass | fail | skipped
  • **Validation Output**: [Command output or "N/A"]
  • **Errors**: [List with type, description, and resolution status, or "none"]
  • **Scope Deviations**: [Anything asked but not completed, or additional necessary work discovered but not performed, or "none"]

Downstream Context

  • **Key Interfaces Introduced**: [Type signatures and file locations, or "none"]
  • **Patterns Established**: [New patterns that downstream agents must follow for consistency, or "none"]
  • **Integration Points**: [Where and how downstream work should connect to this output, or "none"]
  • **Assumptions**: [Anything assumed that downstream agents should verify, or "none"]
  • **Warnings**: [Gotchas, edge cases, or fragile areas downstream agents should be aware of, or "none"]
Read more
Ships withmaestro-orchestrate

Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone

Get the whole plugin

Other agents on maestro-orchestrate.