divide-and-conquer

Decompose complex tasks into independent parallel agents with conflict checks.

5|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/build000r/skills --skill divide-and-conquer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: divide-and-conquer
Source: https://github.com/build000r/skills/tree/main/divide-and-conquer
Command: npx skills add https://github.com/build000r/skills --skill divide-and-conquer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose complex tasks into independent, parallel sub-agents with no overlapping concerns, race conditions, or inter-agent dependencies. Use BEFORE spawning Task agents when the work involves multiple files, domains, or concerns that could be parallelized. Triggers on: planning multi-agent work, "split this into agents", "parallelize this", "divide and conquer", or when about to launch 2+ Task agents for a complex task. Also use when a task feels too large for a single agent but the right decomposition isn't obvious.

Core Features & Use Cases

  • Formalized process to identify boundaries and ensure independence between agents.
  • Guidance on safe split patterns and conflict checks to prevent write collisions.
  • Practical workflow for launching parallel agents with minimal coordination.

Quick Start

Outline a 2- to 5-agent decomposition for a given complex task, assign each agent a distinct concern, and specify their write boundaries to ensure conflict-free parallel execution.

Frequently Asked Questions about divide-and-conquer

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

FAQPage Schema
How do I split a complex software project into parallel agents without write conflicts?

To split tasks into parallel agents without write conflicts, you must identify clear boundaries for each sub-agent and specify distinct write boundaries. This conflict-free decomposition prevents overlapping writes and race conditions during multi-agent orchestration.

What is the best way to parallelize a large task into independent sub-agents?

The best way to parallelize a large task is to outline a 2- to 5-agent decomposition, assign each agent a distinct concern, and enforce independence by avoiding inter-agent dependencies before launching the workflow.

When should I use multi-agent orchestration for task decomposition?

Use multi-agent orchestration when a task feels too large for a single agent or involves multiple files and domains. It is triggered when planning to launch 2 or more Task agents for complex, scalable task distribution.

How do I prevent race conditions when launching parallel sub-agents?

Prevent race conditions in parallel sub-agents by applying a formal conflict-check and launch protocol. This protocol guides safe split patterns to avoid overlapping writes and ensures conflict-free parallel execution.

Can I use divide and conquer planning for data analysis and research tasks?

Yes, you can use divide and conquer planning for data analysis and research tasks. The orchestration applies to planning multi-agent workflows across diverse domains, enabling scalable task distribution beyond software projects.

What are the limitations of dividing tasks into parallel agents?

A limitation of dividing tasks into parallel agents is the requirement for strict independence. If the work cannot be separated into distinct concerns with non-overlapping write boundaries, the decomposition will fail due to inter-agent dependencies.