subagent-response

Return structured status summaries with identifiers and issues to parent agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagents often perform tool calls and intermediate work that the parent agent cannot see; this Skill ensures the subagent communicates only the essential, structured results the parent needs to continue decision-making.

Core Features & Use Cases

  • Status-first reporting: Requires a clear status token (success / failure / partial) up front so the parent agent can immediately assess outcome.
  • Structured result payload: Mandates entries for what was done, key data (IDs, URLs, counts, samples), and any issues or anomalies.
  • Terse factual summaries: Eliminates narrative, tool traces, and unsolicited advice so the parent receives only actionable facts.
  • Use Case: A subagent that created a PR, ran tests, or queried a database returns a single concise summary the parent can parse to decide next steps.

Quick Start

Summarize the completed subtask with a leading status, a brief "what was done" line, all relevant identifiers or links, and any issues or warnings.

Frequently Asked Questions about subagent-response

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

FAQPage Schema
How do I format a subagent response so the parent agent gets actionable results?▼

To format a subagent response, lead with a status token (success, failure, or partial), then provide a brief line of what was done, all relevant identifiers or URLs, and any issues or warnings so the parent agent can proceed without intermediate context.

What should a subagent return summary include after executing queries or tool calls?▼

A subagent return summary should include a clear status token, a concise description of what was done, key data like IDs or URLs, and any issues or anomalies, eliminating narrative and tool traces for immediate parent agent parsing.

Why does my parent agent fail to parse subagent work outcomes correctly?▼

Parent agents fail to parse subagent outcomes when summaries contain narrative, tool traces, or unsolicited advice instead of structured facts, making it necessary to use a status-first reporting format with essential identifiers.

Can I use a structured reporting format for subagents that create pull requests or run tests?▼

Yes, you can use a structured subagent reporting format for tasks like creating pull requests or running tests, which requires returning a single concise summary with status, actions taken, key identifiers, and issues for parent agent decision-making.

When do I need a status-first reporting format for subagent communication?▼

You need a status-first reporting format when a subordinate agent must report outcomes to a parent agent after executing tools, queries, or changes, ensuring the parent can immediately assess the outcome as success, failure, or partial.