Skill

delegation-triggers

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

Guidelines for when to delegate tasks to sub-agents vs handle directly. Use when deciding whether to use Explore, Plan, or other specialized agents for a task.

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets
View in Repository
reference.md
Skill Content

Delegation Triggers

Decision Tree

Is this task...
    │
    ├─ Multi-file, independent units? ─► Parallel Orchestration
    │                                     (see complex-orchestrator)
    │
    ├─ Deep analysis / reasoning? ─────► Advanced General Purpose (Opus)
    │   ⚠️ High cost - use sparingly
    │
    ├─ Exploration / Research? ────────► Explore Agent
    │
    ├─ Planning / Design? ─────────────► Plan Agent
    │
    ├─ Simple & Direct? ───────────────► Execute Directly
    │
    └─ Unclear scope? ─────────────────► Decompose First

Quick Reference

SignalAgentTrigger Phrases
Multi-fileParallel (complex-orchestrator)"all files", "across codebase", "every X"
Deep analysisAdvanced (Opus)"thoroughly", "しっかり", "implications"
Find/UnderstandExplore"where is", "how does", "find all"
Design/ArchitectPlan"how should I", "design", "best approach"
Simple editDirect"fix", "add field", "update text"

3-Question Test

  1. Enough context? → No: Explore first
  2. Multiple approaches? → Yes: Plan first
  3. Touch 3+ unseen files? → Yes: Explore/Plan first

Parallel Execution

Launch in single message for parallel:

Task({ description: "A", ... })
Task({ description: "B", ... })  // runs parallel with A

For dependencies, use waves:

Wave 1: shared dependency
Wave 2: parallel consumers (after Wave 1)

For detailed examples and anti-patterns, see reference.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