thread-spawner

Spawn and manage parallel threads on a running claude-threads orchestrator.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hanibalsk/example-claude-threads --skill thread-spawner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thread-spawner
Source: https://github.com/hanibalsk/example-claude-threads/tree/main/.claude/skills/thread-spawner
Command: npx skills add https://github.com/hanibalsk/example-claude-threads --skill thread-spawner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to spawn and coordinate Claude threads against a running claude-threads orchestrator, facilitating parallel task execution and remote control.

Core Features & Use Cases

  • Remote Spawning: Connect to a running orchestrator and spawn new threads with isolated worktrees by default.
  • Template & Context Customization: Use templates and JSON context to tailor each thread.
  • Parallel Execution: Launch multiple threads in parallel to accelerate delivery.

Quick Start

Connect to an orchestrator, then spawn a thread with a template and optional context. Example: ct remote discover; ct remote connect localhost:31337 --token $CT_API_TOKEN; ct spawn epic-7a --template bmad-developer.md --worktree --context '{"epic_id":"7A"}'

Frequently Asked Questions about thread-spawner

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

FAQPage Schema
How do I spawn parallel Claude threads with isolated worktrees?

Spawning parallel threads creates isolated worktree instances on a running claude-threads orchestrator. Connect to the orchestrator with a valid token, then use the spawn command with template and context parameters to launch multiple threads in parallel for concurrent task execution.

What setup do I need to run thread spawning against an orchestrator?

Thread spawning requires a running claude-threads API server, a valid CT_API_TOKEN or runtime token, and remote discovery and connection to the orchestrator endpoint. Templates and JSON context files are optional but enable customized thread configuration.

Can I use thread spawning to coordinate background tasks across Claude Code sessions?

Yes. Thread spawning enables cross-instance coordination, BMAD workflows, and background task execution by spawning epics, stories, or tasks from Claude Code sessions with isolated git worktrees and wait semantics for remote control.

How do templates and context JSON customize spawned threads?

Templates define thread configuration and context JSON provides runtime variables passed to each spawned thread. Together they enable customization of thread behavior, environment setup, and task-specific parameters without modifying the spawn command.

What's the difference between spawning threads locally versus remotely on an orchestrator?

Remote spawning connects to an external orchestrator API for centralized thread management and coordination across multiple Claude Code instances, while local spawning would be limited to single-machine execution. Remote spawning enables parallel delivery and cross-session task delegation.