coordinator-response-mode

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

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill coordinator-response-mode-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinator-response-mode
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/coordinator-response-mode
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill coordinator-response-mode-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After routing decides which agent handles a task, coordinators still need 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 to Direct (coordinator answers instantly), Lightweight (minimal single-agent spawn), Standard (full single-agent ceremony), or Full (multi-agent parallel fan-out) modes with target latency ranges. - Exemplar Prompts per Mode: Concrete example requests for each tier, from status checks answered directly to multi-agent "Team" requests touching 3+ domains. - Lightweight Spawn Template: A ready-to-use minimal agent spawn template that skips charter, history, and decisions reads, plus an explore-agent variant for read-only queries. - Upgrade Rules: Explicit bias-toward-upgrading guidance, including the rule to 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 one agent with the minimal template instead of the full ceremony. ## Quick Start Load this skill after routing has identified the agent, then use the decision table to pick the response mode for the user's 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 the mode to task complexity using the decision table: Direct for status checks the coordinator already knows, Lightweight for single-file edits or simple queries, Standard for normal single-agent work, and Full for multi-agent tasks touching 3+ concerns.

What is the difference between routing and response mode selection?

Routing determines WHO handles the work by selecting the agent, while response mode selection determines HOW they handle it by choosing the ceremony level. Response mode selection happens after routing has identified the agent.

When should I use the Lightweight spawn template?

Use it for single-file edits, small fixes, follow-ups, and simple scoped read-only queries. It skips charter, history, and decisions reads, targeting roughly 8-12 seconds instead of the full Standard ceremony.

Can I downgrade a response mode mid-task?

No, the rules explicitly prohibit downgrading mid-task. If you started in Standard mode, finish in Standard mode; upgrades are allowed when a task turns out to need more context than expected.

What agent type should I use for read-only queries?

Use agent_type "explore" for read-only queries in Lightweight mode. It runs on a fast Haiku model with a minimal prompt containing only the question, team root, and current datetime.