maestro:conduct

Orchestrate mission execution by decomposing tasks, dispatching sub-agents, and synthesizing results.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-conduct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro:conduct
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.claude/skills/maestro%253Aconduct
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-conduct

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you coordinate complex software work by decomposing missions or ad-hoc tasks into sub-agent assignments while you oversee planning, execution monitoring, and synthesis.

Core Features & Use Cases

  • Mission execution orchestration: Loads mission/milestone state, prompts agents for pending features, dispatches with independence checks, monitors replies, and performs milestone gates.
  • Ad-hoc decomposition orchestration: Restates the work, captures acceptance criteria, decomposes into 2–7 verifiable tasks, verifies independence, dispatches agents, and synthesizes outcomes.
  • Structured, guardrailed delegation: Enforces hard rules like no implementation code, task definitions before dispatch, verified independence for parallelism, and readable integrated synthesis for you.

Quick Start

Use maestro:conduct when you want to delegate a milestone or task breakdown to sub-agents and stay in the driver seat by overseeing planning and synthesis.

Frequently Asked Questions about maestro:conduct

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

FAQPage Schema
How do I orchestrate multi-agent task decomposition without writing code?

Agent orchestration without coding is achieved by using a conductor to plan, decompose missions into verifiable subtasks, dispatch to sub-agents, and synthesize results while you maintain control. You oversee planning and monitor execution without implementing code yourself.

What is human-in-the-loop workflow control for mission execution?

Human-in-the-loop workflow control means the conductor dispatches sub-agents for task execution but enforces strict delegation guardrails, requiring task-definition gating and milestone gates so you maintain safety and approve progress throughout the mission.

How do I verify task independence for parallel agent dispatch?

Verifying task independence for parallel dispatch requires checking that decomposed subtasks have no dependencies before sending them to sub-agents. The conductor applies independence verification to ensure safe parallel execution and prevent conflicts during mission execution.

How do I decompose ad-hoc tasks into verifiable subtasks for agents?

Ad-hoc task decomposition involves restating the work, capturing acceptance criteria, and breaking the scope into 2 to 7 verifiable tasks. The conductor then dispatches agents for these independent tasks and synthesizes the outcomes into a readable result.

What are the limitations of using a conductor for agent delegation?

A limitation of conductor-based agent delegation is that it requires strict guardrails, including no forwarding of raw agent output and explicit handling of ambiguous scope. You must define tasks before dispatch and verify independence, preventing unstructured or unmonitored execution.