Recursive Decomposition Guidelines

References

Consult these resources as needed:

• ./references/rlm-strategies.md — Detailed decomposition patterns from the RLM paper
• ./references/cost-analysis.md — When to apply recursive vs. direct approaches
• ./references/codebase-analysis.md — Full walkthrough of codebase-wide analysis
• ./references/document-aggregation.md — Multi-document information extraction
• ./references/task-model-summary.md — Task model (enum probe + Composer priority) when using Task subagents
• ../council/references/cursor-task-workflow.md — full Task workflow (enum probe, parallelism, anti-patterns)

Core Principles

CRITICAL: Treat inputs as environmental variables, not immediate context.

Most tasks fail when context is overloaded. Instead of loading entire contexts into the processing window, treat inputs as environmental variables accessible through tools. Decompose problems recursively, process segments independently, and aggregate results programmatically.