Skill

complex-orchestrator

Install
1
Install the plugin
$
npx claudepluginhub xmgrex/ccx-arsenal --plugin agent-core

Want just this skill?

Add to a custom plugin, then install with one command.

Description

Orchestrates multi-file tasks by delegating to parallel sub-agents. Use when a task spans multiple files or components and can benefit from parallel execution to save context and time.

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets
View in Repository
examples.md
Skill Content

Parallel Task Orchestrator

Distribute multi-file work across parallel sub-agents to save context and time.

When to Use

Task spans multiple files?
    │
    ├─ Independent? ──────► Full Parallel
    ├─ Some dependencies? ─► Staged Parallel (waves)
    └─ Tightly coupled? ──► Sequential or single agent

4-Step Workflow

1. Decompose

Break into file-scoped units. Identify dependencies.

2. Choose Strategy

  • Full Parallel: All units independent
  • Staged Parallel: Wave 1 (dependencies) → Wave 2 (consumers)
  • Fan-out/Fan-in: Setup → parallel work → integration

3. Delegate in Parallel

Launch multiple Tasks in single message:

Task({ subagent_type: "general-purpose", description: "Edit file A", prompt: "..." })
Task({ subagent_type: "general-purpose", description: "Edit file B", prompt: "..." })

4. Integrate

  • Verify each succeeded
  • Check for conflicts
  • Run integration tests

Sub-agent Prompt Structure

## Scope
File: [path] | Task: [what to do in THIS file only]

## Context
Pattern: [consistent approach across all units]

## Constraints
- Only modify [path]
- Follow existing style

Agent Selection

Sub-taskAgent
Simple editgeneral-purpose
Exploration neededExploregeneral-purpose
Complex logicadvanced-general-purpose

For detailed examples and troubleshooting, see examples.md

Stats
Stars1
Forks0
Last CommitJan 31, 2026
Actions

Similar Skills

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.4k