hub-and-spoke

Coordinate a central hub to spawn and manage parallel spokes.

3|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill hub-and-spoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-and-spoke
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/hub-and-spoke
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill hub-and-spoke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrating distributed tasks across multiple workers can introduce complexity, latency, and coordination overhead; hub-and-spoke provides centralized control with parallel execution while remaining scalable.

Core Features & Use Cases

  • Centralized orchestration: A single hub coordinates and distributes work to multiple spokes.
  • Horizontal scalability: Spokes can be added or removed without changing hub logic.
  • Result aggregation: The hub collects, monitors, and summarizes results from all spokes.

Quick Start

Start a hub workflow to distribute work across multiple spokes and collect results.

Frequently Asked Questions about hub-and-spoke

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

FAQPage Schema
How do I coordinate parallel task execution across multiple workers from a central hub?

Centralized orchestration of parallel task execution is achieved by a single hub that spawns and manages multiple spokes running concurrently, dispatching workloads and aggregating the collected results into a final summary.

What is a hub-and-spoke orchestration pattern for distributed workflows?

The hub-and-spoke orchestration pattern uses a single central hub to dispatch, monitor, and coordinate work across multiple distributed spokes, allowing horizontal scaling without changing the hub logic while aggregating summarized results.

How do I set up a multi-repo build with centralized control and parallel execution?

Set up a multi-repo build by initiating a hub workflow that distributes build tasks across multiple spokes for parallel execution, enabling the central hub to collect, monitor, and summarize the distributed build results.

Can I dynamically add or remove workers during distributed workflow orchestration?

Workers can be added or removed during distributed workflow orchestration without changing the hub logic, providing horizontal scalability so the central hub continues monitoring and aggregating results from all active spokes.

What is the best way to aggregate results from multiple parallel workers in an automated workflow?

Aggregating results from multiple parallel workers is best handled by a centralized hub that collects and summarizes outputs from all distributed spokes, providing a single point of monitoring and result aggregation for automated workflows.