subagent

Spawn and manage autonomous background agents for parallel task execution.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Logarn/Worklin-ai --skill subagent-logarn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent
Source: https://github.com/Logarn/Worklin-ai/tree/main/assistant/src/config/bundled-skills/subagent
Command: npx skills add https://github.com/Logarn/Worklin-ai --skill subagent-logarn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long research, debugging, or coding tasks done inline flood the main conversation context and force serial execution. This Skill delegates self-contained work to autonomous background agents that run in parallel and report back when finished. ## Core Features & Use Cases - Parallel Subagent Spawning: Launch researcher, coder, planner, investigator, or supervisor agents with scoped tool access via subagent_spawn. - Lifecycle Management: Track, message, read output from, and abort running subagents using subagent_status, subagent_message, subagent_read, and subagent_abort. - Fork Mode: Create context-inheriting forks that share the parent's full conversation and memory for tasks that depend on prior discussion. - Use Case: While investigating a production bug, spawn an investigator subagent to trace logs and a researcher to check related documentation in parallel, then read their compact reports when they complete. ## Quick Start Spawn a researcher subagent labeled "research-auth-libraries" to compare authentication options and report back when done.

Frequently Asked Questions about subagent

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

FAQPage Schema
How do I run multiple AI agents in parallel on separate tasks?▼

Use subagent_spawn with a label, objective, and role for each task. Each subagent runs autonomously in the background, and the parent conversation is automatically notified when each one completes, fails, or is aborted.

What is the difference between a fork and a regular subagent?▼

A fork inherits the parent's full context including messages, system prompt, and memory, while a regular subagent receives only its objective and context fields. Forks always run as the general role and default to internal-only results.

Which subagent role should I use for debugging or log analysis?▼

Use the investigator role for root-cause analysis, debugging, and log forensics. It has read-only shell access for grep and log reading plus file and web tools, and returns a compact root-cause report instead of flooding the main context.

Can a subagent spawn its own child agents?▼

Only subagents with the supervisor role can spawn one level of child workers. Delegation is bounded to depth 2, at most 8 active children per parent, and at most 16 total descendants across the tree.

When should I avoid spawning a subagent?▼

Avoid spawning for tasks small enough to do inline, such as a single tool call, one search, or a quick file read. Subagents are intended for web research, multi-file exploration, and independent coding work that benefits from parallel execution.