delegation

Inject shared protocols and enforce file-writing constraints in delegation prompts.

453|34|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/josstei/maestro-gemini --skill delegation-josstei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation
Source: https://github.com/josstei/maestro-gemini/tree/main/skills/delegation
Command: npx skills add https://github.com/josstei/maestro-gemini --skill delegation-josstei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegation prompts for subagents during orchestration execution require consistent structure and safety measures to ensure high-quality, trustworthy results.

Core Features & Use Cases

  • Protocol Injection: Prepend the shared agent base protocol and filesystem safety protocol to every delegation prompt to enforce standard pre-work and formatting.
  • Context Chain & Downstream Handoff: Assemble phase-context and downstream-context data from session state to maintain continuity across phases.
  • Settings & Enforcement: Read agent frontmatter to apply defaults, enforce tool usage restrictions, and guarantee non-overlapping file ownership in parallel executions.
  • Handoff & Validation: Provide mandatory Task Report and Downstream Context sections to support downstream handoffs and hook validations.

Quick Start

Provide a sample delegation prompt for the current phase that injects protocols, includes downstream context, and enforces tool and file-writing rules.

Frequently Asked Questions about delegation

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

FAQPage Schema
How do I enforce consistent pre-work steps and filesystem safety in subagent delegation prompts?

Subagent delegation prompts enforce filesystem safety and pre-work steps by injecting shared base protocols and filesystem safety blocks directly into the prompt structure before execution begins.

What is the best way to maintain context continuity across orchestration phases for subagents?

Context continuity across orchestration phases is maintained by assembling phase-context and downstream-context data from session state, producing structured Task Reports for seamless downstream handoffs.

Can I prevent overlapping file ownership when running parallel subagent executions?

Parallel subagent executions prevent overlapping file ownership by reading agent frontmatter to apply defaults and enforcing strict, non-overlapping file-writing constraints across concurrent tasks.

How do subagent delegation protocols handle tool usage restrictions during orchestration?

Subagent delegation protocols handle tool usage restrictions by reading agent frontmatter defaults and enforcing strict tool usage constraints throughout the orchestration execution lifecycle.

Does subagent delegation support hook validations for downstream handoffs?

Subagent delegation supports hook validations by providing mandatory Task Report and Downstream Context sections that ensure structured data is available for downstream validation processing.

When do I need structured downstream context for subagent orchestration?

Structured downstream context is needed during multi-phase orchestration when subsequent subagents require phase dependencies and prior execution results to continue processing reliably.