spawn

Name: spawn
Availability: InStock
Author: kinnerkarmanish

Launch specialized agents with scoped identity, workspace access, and controlled commands.

Updated Apr 26, 2026

Search Tags:#workflow #agent #runtime #parallel #orchestrator #spawn #subtask

Ready to run

npx skills add https://github.com/kinnerkarmanish/mak --skill spawn-kinnerkarmanish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spawn
Source: https://github.com/kinnerkarmanish/mak/tree/main/library/skills/coordination/spawn
Command: npx skills add https://github.com/kinnerkarmanish/mak --skill spawn-kinnerkarmanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launch specialized agents to perform discrete subtasks with scoped identity, workspace access, and controlled command sets.

Core Features & Use Cases

Create dedicated agent runtime for a subtask with its own identity, scope, and command allowlist.
Enable parallelization by spawning multiple agents for different subtasks.
Support backend runtimes via tmux (visual) or subprocess (headless) for flexibility.

Quick Start

Spawn a new agent to handle a focused subtask with a defined identity, workspace scope, allowed commands, and a chosen backend.

Frequently Asked Questions about spawn

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

FAQPage Schema

How do I run parallel agents for subtasks at scale?▼

To run parallel agents for subtasks, spawn launches specialized agents with scoped identity, workspace access, and controlled command sets. Apply this to parallel task decomposition and isolated subtask execution to manage multiple operations concurrently.

Can I use tmux for visual agent runtimes and subprocess for headless?▼

Yes, you can use tmux for visual agent runtimes and subprocess for headless execution. Spawn supports multi-backend runtime orchestration, allowing you to choose between visual monitoring or background execution based on your workflow requirements.

How do I isolate workspace access and commands for spawned agents?▼

Isolate workspace access and commands by defining a scoped identity and command allowlist for each spawned agent. Spawn applies workspace scoping, identity resolution, and controlled command sets to ensure discrete subtask execution without overlap.

What is the best way to orchestrate multiple subtasks with scoped identity?▼

The best way to orchestrate subtasks with scoped identity is using a dedicated agent runtime. Spawn implements identity resolution, workspace scoping, inbox setup, and heartbeat monitoring to coordinate isolated subtask execution across parallel agents.

Does spawn require dependencies for backend runtime orchestration?▼

No, spawn requires no external dependencies for backend runtime orchestration. It natively implements multi-backend runtime orchestration, supporting both tmux for visual and subprocess for headless execution out of the box.

When should I not use parallel task decomposition for agents?▼

Avoid parallel task decomposition when subtasks require shared mutable workspace state or lack clear boundaries. Spawn relies on workspace scoping and controlled command sets, making it unsuitable for tightly coupled operations requiring direct cross-agent communication.