rlm-orchestrator

Decompose large-context tasks into partitions and spawn parallel subagents.

47|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/belumume/claude-skills --skill rlm-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlm-orchestrator
Source: https://github.com/belumume/claude-skills/tree/main/rlm-orchestrator
Command: npx skills add https://github.com/belumume/claude-skills --skill rlm-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill orchestrates large-context tasks by decomposing them into independent partitions, spawning parallel subagents, and aggregating results to produce a unified outcome. It addresses context window limitations and complex multi-file or multi-source workloads.

Core Features & Use Cases

  • Partition-centric orchestration: automatically split tasks into independent parts for parallel processing.
  • Parallel subagents: spawn multiple subagents (up to ~10 concurrent) with fresh context, and aggregate their results.
  • Iterative refinement: identify gaps and spawn follow-up batches until completion.
  • Claude Code-only workflow: suitable for environments where child agents cannot spawn in a single step.
  • Use cases: large codebases analysis, multi-document synthesis, research-driven tasks.

Quick Start

Start by describing a large, multipart task and specify partition boundaries, then invoke the orchestrator (e.g., mention RLM or /rlm-orchestrator). Monitor batch results and review aggregated outcomes to guide next steps.

Frequently Asked Questions about rlm-orchestrator

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

FAQPage Schema
How do I analyze large codebases that exceed a single context window?

To analyze large codebases exceeding a single context window, you can partition the task into independent parts and dispatch parallel subagents. This orchestration approach spawns fresh-context agents concurrently and aggregates their structured summaries into a unified outcome.

What is the best way to run parallel subagents for multi-file analysis?

The best way to run parallel subagents for multi-file analysis is using a partition, spawn, and aggregate protocol. It decomposes workloads into independent partitions, executes up to ten concurrent subagents, and aggregates their results iteratively to resolve gaps.

How do I orchestrate subagents to synthesize multiple research documents?

Orchestrate subagents to synthesize research documents by defining partition boundaries for the workload, invoking the orchestrator, and monitoring batch results. The system processes partitions concurrently and returns structured summaries to guide iterative refinement until completion.

Does Claude Code support spawning parallel subagents with fresh context?

Yes, Claude Code supports spawning parallel subagents with fresh context. This workflow is designed specifically for Claude Code tooling environments where child agents cannot be spawned in a single step, enabling concurrent execution and result aggregation.

How does iterative refinement work when orchestrating parallel execution?

Iterative refinement during parallel execution works by identifying gaps in aggregated subagent results and spawning follow-up batches. This cycle repeats until completion, ensuring the unified outcome addresses all partition requirements without context window limitations.

When should I not use parallel subagent orchestration for large tasks?

You should not use parallel subagent orchestration for tasks that cannot be decomposed into independent partitions. The workflow requires Claude Code tooling and relies on partition boundaries, making it unsuitable for single-context tasks or non-decomposable sequential workloads.