coordinator-response-mode

Selects the appropriate response mode for routed agent tasks based on complexity.

5.1k|530|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill coordinator-response-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinator-response-mode
Source: https://github.com/github/gh-aw/tree/main/.squad/templates/skills/coordinator-response-mode
Command: npx skills add https://github.com/github/gh-aw --skill coordinator-response-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After routing decides which agent handles a task, a coordinator still needs to decide how much ceremony that task deserves. This Skill provides the complete decision table for choosing between Direct, Lightweight, Standard, and Full response modes, preventing both over-engineering simple requests and under-serving complex ones.

Core Features & Use Cases

  • Four-tier decision table: Maps task complexity (status checks, single-file edits, normal tasks, multi-agent work) to Direct, Lightweight, Standard, or Full modes with target latency for each.
  • Exemplar prompts per mode: Concrete example requests showing when to answer directly, spawn one lightweight agent, run full ceremony, or fan out in parallel.
  • Lightweight spawn template: A ready-to-use minimal agent spawn prompt that skips charter, history, and decisions reads for fast scoped tasks.
  • Upgrade rules: Explicit guidance to bias toward higher tiers when uncertain and never downgrade mid-task.
  • Use Case: A user asks "fix the typo in README" — the coordinator loads this skill, classifies it as Lightweight, and spawns a single agent with the minimal template instead of full ceremony.

Quick Start

Load this skill after routing a task to an agent and use its decision table to pick the right response mode for the request.

Frequently Asked Questions about coordinator-response-mode

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

FAQPage Schema
How do I choose between Direct, Lightweight, Standard, and Full response modes?

Match task complexity to the mode table: Direct for status checks answerable from context, Lightweight for single-file edits or simple queries, Standard for normal single-agent tasks needing full context, and Full for multi-agent work touching 3+ concerns.

When should a coordinator answer directly without spawning an agent?

Use Direct mode for factual questions the coordinator already knows, such as current branch, team membership, prior decisions, or quick command results like test counts. No agent spawn is needed, targeting roughly 2-3 seconds.

What is the Lightweight spawn template used for?

The Lightweight template spawns one agent with a minimal prompt that skips charter, history, and decisions reads. It suits small scoped edits and follow-ups, and uses agent_type explore for read-only queries.

Can I downgrade from Standard to Lightweight mode mid-task?

No, the upgrade rules explicitly forbid downgrading mid-task. If you started Standard, finish Standard; upgrades are allowed when a Lightweight task turns out to need history or decisions context.

What happens when I am uncertain between two response modes?

Bias toward upgrading: choose Lightweight over Direct, and Standard over Lightweight when uncertain. The skill recommends going one tier higher rather than risking under-serving the task.