Skill

orchestration-execution

Wave-based parallel execution and teammate health monitoring for multi-agent orchestration. Use when coordinating agent waves, spawning teammates, checking health states, or a teammate appears stalled or blocked.

From agent-orchestrator
Install
1
Run in your terminal
$
npx claudepluginhub l3digitalnet/claude-code-plugins --plugin agent-orchestrator
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Orchestration — Wave Execution and Health Monitoring

Wave Execution Model

Wave 1 → Spawn all independent teammates in parallel
          ↓ Monitor status files for completion signals
Wave 2 → Spawn dependent teammates; include summaries from predecessor handoffs
          ↓ ...
Wave N → Final integration

Between waves, the lead:

  1. Reads all status files and compaction events
  2. Validates handoff compliance (handoff file exists for completed teammates)
  3. Checks for file-ownership violations
  4. Writes lead handoff and evaluates compaction need

Health States

StateSignalResponse
HealthyStatus file shows workingNo action
CompleteStatus shows doneCheck if next wave unblocked
BlockedStatus shows blockedRead notes, resolve, message
StalledNo status file or staleMessage → read handoff → respawn
Quality concernDone but handoff suspiciousSpawn review subagent

Max 2 retries per teammate. Then escalate to user.

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.5k
Stats
Parent Repo Stars3
Parent Repo Forks0
Last CommitFeb 19, 2026