subagents

Delegate parallel AI agent tasks to isolated tmux background subprocesses.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/hschne/pi-stuff --skill subagents-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagents
Source: https://github.com/hschne/pi-stuff/tree/main/skills/subagents
Command: npx skills add https://github.com/hschne/pi-stuff --skill subagents-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, pi, jq, yq.

What problem does it solve?

Manually managing multiple parallel AI agent tasks requires constant context switching, manual session tracking, and waiting for long-running tasks to complete before moving on to other work, which wastes time and reduces productivity.

Core Features & Use Cases

  • Parallel Subagent Execution: Launch multiple isolated Pi subagent instances in background tmux sessions to run tasks concurrently without blocking your main workflow.
  • Template-Based Agent Reuse: Use pre-built agent templates for common tasks like research or code scouting to standardize execution and avoid repeating configuration.
  • Non-Blocking Workflow: Fire off subagent tasks and continue working, then collect results later when they are ready, or block inline only when you need the output immediately.
  • Use Case: For example, you can launch a researcher subagent to compare two software frameworks and a scout subagent to map a new codebase at the same time, then retrieve both results without waiting for either to finish.

Quick Start

Use the subagents skill to launch a background researcher subagent to compare React and Vue frameworks, then collect its final output once it completes.

Frequently Asked Questions about subagents

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

FAQPage Schema
How do I run parallel AI agent tasks without blocking my main workflow?

You can run parallel AI agent tasks without blocking your main workflow by delegating them to isolated background tmux subprocesses. This eliminates manual session management and context switching by handling concurrent execution automatically.

What is the best way to manage concurrent background agents for code analysis and research?

The best way to manage concurrent background agents for code analysis and research is using template-based agent execution with persistent run artifact storage. This standardizes configuration and allows you to retrieve results later without waiting inline.

Do I need tmux and pi CLI to delegate tasks to background subagents?

Yes, you need tmux and the pi CLI to delegate tasks to background subagents. Additionally, jq is required for processing, and yq is optional for handling template-based agent execution configurations.

Can I launch multiple isolated AI agent instances at the same time?

Yes, you can launch multiple isolated AI agent instances at the same time. This approach applies to workflows requiring concurrent execution of independent tasks across separate Pi agent instances running in background tmux sessions.

How does template-based agent reuse work for parallel execution?

Template-based agent reuse for parallel execution works by using pre-built templates for common tasks like research or code scouting. This standardizes execution across multiple isolated background subagents and avoids repeating manual configuration.

Why does manual session tracking reduce productivity during parallel AI workflows?

Manual session tracking reduces productivity during parallel AI workflows because it requires constant context switching and waiting for long-running tasks to complete. Delegating to isolated background subprocesses eliminates this overhead and saves time.