PluginBench
Skill
Official
Pass
Audit score 90

deep-agents-orchestration

langchain-ai/langchain-skills

Orchestrate subagents, plan tasks, and require human approval in Deep Agents

What is deep-agents-orchestration?

Deep Agents Orchestration provides three middleware capabilities for coordinating multi-agent workflows: SubAgentMiddleware for delegating work to specialized agents, TodoListMiddleware for planning and tracking complex tasks, and HumanInTheLoopMiddleware for requiring approval before sensitive operations. Use this skill when building agents that need task delegation, structured planning, or compliance-driven approval workflows.

  • Delegate tasks to specialized subagents with custom tools and system prompts via the task tool
  • Plan and track multi-step operations using write_todos with status tracking (pending, in_progress, completed)
  • Require human approval before executing sensitive operations like database writes or deployments
  • Create custom subagents with isolated contexts and specialized tool sets
  • Configure interrupt points for compliance and high-stakes decision workflows

How to install deep-agents-orchestration

npx skills add https://github.com/langchain-ai/langchain-skills --skill deep-agents-orchestration
Prerequisites
  • Deep Agents framework installed
  • LangChain tools library for custom tool definitions
  • MemorySaver or other checkpointer for HITL and TodoList persistence
Claude Code
Cursor
Windsurf
Cline

How to use deep-agents-orchestration

  1. 1.Create a deep agent with create_deep_agent() - all three middlewares are included by default
  2. 2.For subagents: define custom subagents with name, description, system_prompt, and tools array, then call task(agent='name', instruction='...') from main agent
  3. 3.For TodoList: invoke agent with thread_id in config to enable persistence, agent will automatically call write_todos() to plan multi-step tasks
  4. 4.For HITL: configure interrupt_on dict mapping tool names to True (require approval) or False (skip), and provide a checkpointer like MemorySaver()
  5. 5.Access results: retrieve todos from result.get('todos', []) and handle interrupts by resuming with user decisions

Use cases

Good for
  • Delegating research tasks to a specialized researcher subagent while main agent coordinates
  • Planning a multi-step REST API creation with design, CRUD, auth, and testing phases
  • Requiring human approval before production code deployments or database migrations
  • Isolating complex work in subagents to keep main agent context clean
  • Building compliance workflows where certain operations need explicit human sign-off
Who it's for
  • AI agent developers building multi-agent systems
  • Teams requiring human oversight in automated workflows
  • Developers building task-planning systems with complex dependencies
  • Engineers deploying agents in high-stakes environments (production, compliance)

deep-agents-orchestration FAQ

Do custom subagents inherit skills from the main agent?

No. Custom subagents do not inherit skills from the main agent. You must explicitly pass the skills array to each subagent. The default 'general-purpose' subagent does inherit main agent tools and config.

Are subagents stateful across multiple calls?

No. Subagents are stateless and start fresh each time. Provide complete instructions in a single task() call rather than expecting the subagent to remember previous interactions.

What is required for TodoList persistence?

TodoList state requires a thread_id in the config's configurable dict. Without thread_id, todos are lost after each invocation. Use config={'configurable': {'thread_id': 'session-id'}} when invoking.

When should I use TodoList vs just letting the agent plan naturally?

Use TodoList for complex multi-step tasks or long-running operations. Skip it for simple single-action tasks or quick operations under 3 steps where natural planning is sufficient.

How do I require approval for specific tools in HITL?

Pass interrupt_on dict to create_deep_agent() mapping tool names to True (require approval), False (skip), or a dict with allowed_decisions. Also provide a checkpointer like MemorySaver() for interrupt state.

Full instructions (SKILL.md)

Source of truth, from langchain-ai/langchain-skills.


name: deep-agents-orchestration description: "INVOKE THIS SKILL when using subagents, task planning, or human approval in Deep Agents. Covers SubAgentMiddleware, TodoList for planning, and HITL interrupts."

<overview> Deep Agents include three orchestration capabilities:
  1. SubAgentMiddleware: Delegate work via task tool to specialized agents
  2. TodoListMiddleware: Plan and track tasks via write_todos tool
  3. HumanInTheLoopMiddleware: Require approval before sensitive operations

All three are automatically included in create_deep_agent(). </overview>


Subagents (Task Delegation)

<when-to-use-subagents>
Use Subagents WhenUse Main Agent When
Task needs specialized toolsGeneral-purpose tools sufficient
Want to isolate complex workSingle-step operation
Need clean context for main agentContext bloat acceptable
</when-to-use-subagents> <how-subagents-work> Main agent has `task` tool -> creates fresh subagent -> subagent executes autonomously -> returns final report.

Default subagent: "general-purpose" - automatically available with same tools/config as main agent. </how-subagents-work>

<ex-custom-subagents> <python> Create a custom "researcher" subagent with specialized tools for academic paper search.
from deepagents import create_deep_agent
from langchain.tools import tool

@tool
def search_papers(query: str) -> str:
    """Search academic papers."""
    return f"Found 10 papers about {query}"

agent = create_deep_agent(
    subagents=[
        {
            "name": "researcher",
            "description": "Conduct web research and compile findings",
            "system_prompt": "Search thoroughly, return concise summary",
            "tools": [search_papers],
        }
    ]
)

# Main agent delegates: task(agent="researcher", instruction="Research AI trends")
</python> <typescript> Create a custom "researcher" subagent with specialized tools for academic paper search.
import { createDeepAgent } from "deepagents";
import { tool } from "@langchain/core/tools";
import { z } from "zod";

const searchPapers = tool(
  async ({ query }) => `Found 10 papers about ${query}`,
  { name: "search_papers", description: "Search papers", schema: z.object({ query: z.string() }) }
);

const agent = await createDeepAgent({
  subagents: [
    {
      name: "researcher",
      description: "Conduct web research and compile findings",
      systemPrompt: "Search thoroughly, return concise summary",
      tools: [searchPapers],
    }
  ]
});

// Main agent delegates: task(agent="researcher", instruction="Research AI trends")
</typescript> </ex-custom-subagents> <ex-subagent-with-hitl> <python> Configure a subagent with HITL approval for sensitive operations.
from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver

agent = create_deep_agent(
    subagents=[
        {
            "name": "code-deployer",
            "description": "Deploy code to production",
            "system_prompt": "You deploy code after tests pass.",
            "tools": [run_tests, deploy_to_prod],
            "interrupt_on": {"deploy_to_prod": True},  # Require approval
        }
    ],
    checkpointer=MemorySaver()  # Required for interrupts
)
</python> </ex-subagent-with-hitl> <fix-subagents-are-stateless> <python> Subagents are stateless - provide complete instructions in a single call.
# WRONG: Subagents don't remember previous calls
# task(agent='research', instruction='Find data')
# task(agent='research', instruction='What did you find?')  # Starts fresh!

# CORRECT: Complete instructions upfront
# task(agent='research', instruction='Find data on AI, save to /research/, return summary')
</python> <typescript> Subagents are stateless - provide complete instructions in a single call.
// WRONG: Subagents don't remember previous calls
// task research: Find data
// task research: What did you find?  // Starts fresh!

// CORRECT: Complete instructions upfront
// task research: Find data on AI, save to /research/, return summary
</typescript> </fix-subagents-are-stateless> <fix-custom-subagents-dont-inherit-skills> <python> Custom subagents don't inherit skills from the main agent.
# WRONG: Custom subagent won't have main agent's skills
agent = create_deep_agent(
    skills=["/main-skills/"],
    subagents=[{"name": "helper", ...}]  # No skills inherited
)

# CORRECT: Provide skills explicitly (general-purpose subagent DOES inherit)
agent = create_deep_agent(
    skills=["/main-skills/"],
    subagents=[{"name": "helper", "skills": ["/helper-skills/"], ...}]
)
</python> </fix-custom-subagents-dont-inherit-skills>

TodoList (Task Planning)

<when-to-use-todolist>
Use TodoList WhenSkip TodoList When
Complex multi-step tasksSimple single-action tasks
Long-running operationsQuick operations (< 3 steps)
</when-to-use-todolist> <todolist-tool>
write_todos(todos: list[dict]) -> None

Each todo item has:

  • content: Description of the task
  • status: One of "pending", "in_progress", "completed" </todolist-tool>
<ex-todolist-usage> <python> Invoke an agent that automatically creates a todo list for a multi-step task.
from deepagents import create_deep_agent

agent = create_deep_agent()  # TodoListMiddleware included by default

result = agent.invoke({
    "messages": [{"role": "user", "content": "Create a REST API: design models, implement CRUD, add auth, write tests"}]
}, config={"configurable": {"thread_id": "session-1"}})

# Agent's planning via write_todos:
# [
#   {"content": "Design data models", "status": "in_progress"},
#   {"content": "Implement CRUD endpoints", "status": "pending"},
#   {"content": "Add authentication", "status": "pending"},
#   {"content": "Write tests", "status": "pending"}
# ]
</python> <typescript> Invoke an agent that automatically creates a todo list for a multi-step task.
import { createDeepAgent } from "deepagents";

const agent = await createDeepAgent();  // TodoListMiddleware included

const result = await agent.invoke({
  messages: [{ role: "user", content: "Create a REST API: design models, implement CRUD, add auth, write tests" }]
}, { configurable: { thread_id: "session-1" } });
</typescript> </ex-todolist-usage> <ex-access-todo-state> <python> Access the todo list from the agent's final state after invocation.
result = agent.invoke({...}, config={"configurable": {"thread_id": "session-1"}})

# Access todo list from final state
todos = result.get("todos", [])
for todo in todos:
    print(f"[{todo['status']}] {todo['content']}")
</python> </ex-access-todo-state> <fix-todolist-requires-thread-id> <python> Todo list state requires a thread_id for persistence across invocations.
# WRONG: Fresh state each time without thread_id
agent.invoke({"messages": [...]})

# CORRECT: Use thread_id
config = {"configurable": {"thread_id": "user-session"}}
agent.invoke({"messages": [...]}, config=config)  # Todos preserved
</python> </fix-todolist-requires-thread-id>

Human-in-the-Loop (Approval Workflows)

<when-to-use-hitl>
Use HITL WhenSkip HITL When
High-stakes operations (DB writes, deployments)Read-only operations
Compliance requires human oversightFully automated workflows
</when-to-use-hitl> <ex-hitl-setup> <python> Configure which tools require human approval before execution.
from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver

agent = create_deep_agent(
    interrupt_on={
        "write_file": True,  # All decisions allowed
        "execute_sql": {"allowed_decisions": ["approve", "reject"]},
        "read_file": False,  # No interrupts
    },
    checkpointer=MemorySaver()  # REQUIRED for interrupts
)
</python> <typescript> Configure which tools require human approval before execution.
import { createDeepAgent } from "deepagents";
import { MemorySaver } from "@langchain/langgraph";

const agent = await createDeepAgent({
  interruptOn: {
    write_file: true,
    execute_sql: { allowedDecisions: ["approve", "reject"] },
    read_file: false,
  },
  checkpointer: new MemorySaver()  // REQUIRED
});
</typescript> </ex-hitl-setup> <ex-approval-workflow> <python> Complete workflow: trigger an interrupt, check state, approve action, and resume execution.
from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver
from langgraph.types import Command

agent = create_deep_agent(
    interrupt_on={"write_file": True},
    checkpointer=MemorySaver()
)

config = {"configurable": {"thread_id": "session-1"}}

# Step 1: Agent proposes write_file - execution pauses
result = agent.invoke({
    "messages": [{"role": "user", "content": "Write config to /prod.yaml"}]
}, config=config)

# Step 2: Check for interrupts
state = agent.get_state(config)
if state.next:
    print(f"Pending action")

# Step 3: Approve and resume
result = agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)
</python> <typescript> Complete workflow: trigger an interrupt, check state, approve action, and resume execution.
import { createDeepAgent } from "deepagents";
import { MemorySaver, Command } from "@langchain/langgraph";

const agent = await createDeepAgent({
  interruptOn: { write_file: true },
  checkpointer: new MemorySaver()
});

const config = { configurable: { thread_id: "session-1" } };

// Step 1: Agent proposes write_file - execution pauses
let result = await agent.invoke({
  messages: [{ role: "user", content: "Write config to /prod.yaml" }]
}, config);

// Step 2: Check for interrupts
const state = await agent.getState(config);
if (state.next) {
  console.log("Pending action");
}

// Step 3: Approve and resume
result = await agent.invoke(
  new Command({ resume: { decisions: [{ type: "approve" }] } }), config
);
</typescript> </ex-approval-workflow> <ex-reject-with-feedback> <python> Reject a pending action with feedback, prompting the agent to try a different approach.
result = agent.invoke(
    Command(resume={"decisions": [{"type": "reject", "message": "Run tests first"}]}),
    config=config,
)
</python> <typescript> Reject a pending action with feedback, prompting the agent to try a different approach.
const result = await agent.invoke(
  new Command({ resume: { decisions: [{ type: "reject", message: "Run tests first" }] } }),
  config,
);
</typescript> </ex-reject-with-feedback> <ex-edit-before-execution> <python> Edit the proposed action arguments before allowing execution.
result = agent.invoke(
    Command(resume={"decisions": [{
        "type": "edit",
        "edited_action": {
            "name": "execute_sql",
            "args": {"query": "DELETE FROM users WHERE last_login < '2020-01-01' LIMIT 100"},
        },
    }]}),
    config=config,
)
</python> </ex-edit-before-execution> <boundaries> ### What Agents CAN Configure
  • Subagent names, tools, models, system prompts
  • Which tools require approval
  • Allowed decision types per tool
  • TodoList content and structure

What Agents CANNOT Configure

  • Tool names (task, write_todos)
  • HITL protocol (approve/edit/reject structure)
  • Skip checkpointer requirement for interrupts
  • Make subagents stateful (they're ephemeral) </boundaries>
<fix-checkpointer-required> <python> Checkpointer is required when using interrupt_on for HITL workflows.
# WRONG
agent = create_deep_agent(interrupt_on={"write_file": True})

# CORRECT
agent = create_deep_agent(interrupt_on={"write_file": True}, checkpointer=MemorySaver())
</python> <typescript> Checkpointer is required when using interruptOn for HITL workflows.
// WRONG
const agent = await createDeepAgent({ interruptOn: { write_file: true } });

// CORRECT
const agent = await createDeepAgent({ interruptOn: { write_file: true }, checkpointer: new MemorySaver() });
</typescript> </fix-checkpointer-required> <fix-thread-id-required-for-resumption> <python> A consistent thread_id is required to resume interrupted workflows.
# WRONG: Can't resume without thread_id
agent.invoke({"messages": [...]})

# CORRECT
config = {"configurable": {"thread_id": "session-1"}}
agent.invoke({...}, config=config)
# Resume with Command using same config
agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)
</python> <typescript> A consistent thread_id is required to resume interrupted workflows.
// WRONG: Can't resume without thread_id
await agent.invoke({ messages: [...] });

// CORRECT
const config = { configurable: { thread_id: "session-1" } };
await agent.invoke({ messages: [...] }, config);
// Resume with Command using same config
await agent.invoke(new Command({ resume: { decisions: [{ type: "approve" }] } }), config);
</typescript> </fix-thread-id-required-for-resumption> <fix-interrupt-checks-between-invocations> <python> Interrupts happen BETWEEN invoke() calls, not mid-execution.
result = agent.invoke({...}, config=config)       # Step 1: triggers interrupt
if "__interrupt__" in result:                      # Step 2: check for interrupt
    result = agent.invoke(                         # Step 3: resume
        Command(resume={"decisions": [{"type": "approve"}]}),
        config=config,
    )
</python> </fix-interrupt-checks-between-invocations>