subagent-dispatch

Craft precise subagent prompts with isolated context and explicit return formats.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zcawood-mie/agentz --skill subagent-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-dispatch
Source: https://github.com/zcawood-mie/agentz/tree/main/skills/subagent-dispatch
Command: npx skills add https://github.com/zcawood-mie/agentz --skill subagent-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegating work to subagents while keeping scope clear and ensuring each subagent receives only the necessary goal and context.

Core Features & Use Cases

  • Precise subagent prompts: Define exact operations, required identifiers, and expected return formats for subagent calls.
  • Context isolation: Ensure subagents do not access prior conversations or hidden knowledge unless explicitly provided.
  • Orchestration patterns: Coordinate goals and values between orchestrators and subagents to achieve a task.

Quick Start

Craft a focused subagent prompt and invoke runSubagent with the target repository and clear return expectations.

Frequently Asked Questions about subagent-dispatch

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

FAQPage Schema
How do I orchestrate subagents to keep scope clear and isolate context?

To orchestrate subagents with context isolation, craft precise prompts via runSubagent that define explicit goals, context, and priorities, ensuring subagents receive no prior conversation history. This approach guarantees predictable results and prevents hidden knowledge from affecting operations.

What should a subagent prompt include to avoid prompt injection?

A subagent prompt should include clear operations, required identifiers, expected return formats, and relevant context to avoid prompt injection. Providing only explicit goals and priorities without prior conversation history ensures predictable results.

How does runSubagent delegation work for complex task orchestration?

RunSubagent delegation works by coordinating goals and values between orchestrators and subagents. You invoke runSubagent with a target repository, defining exact operations and return expectations to achieve a task without exposing hidden knowledge.

Can I use subagent dispatch without prior conversation history?

Yes, subagent dispatch explicitly requires context isolation, ensuring subagents do not access prior conversations or hidden knowledge unless explicitly provided. You provide only the explicit goal, context, and priorities for predictable results.

What is the best way to structure prompts for subagent calls?

The best way to structure subagent prompts is to define clear operations, required identifiers, and expected return formats. Explicitly provide the goal, context, and priorities to ensure predictable results and avoid prompt injection.

Why do my subagents return unpredictable results during orchestration?

Subagents return unpredictable results when prompts lack clear operations, identifiers, return formats, or when prior conversation history leaks into the call. Ensure context isolation by providing only explicit goals and relevant context.