subagent-execution

Delegate eligible workflow steps to fresh subagents under controller governance.

25|2|Updated Mar 5, 2026

Search Tags:#workflow #verification #subagents #delegation #governance #execution #hotl

Ready to run

npx skills add https://github.com/yimwoo/hotl-plugin --skill subagent-execution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-execution
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/subagent-execution
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill subagent-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegating eligible steps to fresh subagents while the controller maintains governance, verification, and stop conditions enables scalable execution without sacrificing centralized control.

Core Features & Use Cases

Delegates implementation steps to independent subagents to improve throughput while maintaining a single source of truth in the controller.
Enforces critical invariants: verification stays in the controller; gates and stop conditions remain controller-owned; no nested delegation.
Use Case: When a workflow has multiple independent steps, hand off execution to subagents to parallelize work while the controller supervises results.

Quick Start

Dispatch a fresh subagent to handle a designated step while the controller retains governance and verification.

Frequently Asked Questions about subagent-execution

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

FAQPage Schema

How do I delegate workflow steps to subagents while keeping central governance?▼

Delegate eligible steps sequentially to fresh, isolated subagents while the controller maintains central state management, gate control, and final verification. This approach enables scalable execution without sacrificing centralized control over the workflow.

What is HOTL execution workflow and when do I need subagent delegation?▼

HOTL execution is a governance-backed workflow where independent implementation steps are handed off to isolated workers. You need subagent delegation when a workflow has multiple independent steps and you want to parallelize work while the controller supervises results.

How do I start delegating tasks to subagents in a governed workflow?▼

Dispatch a fresh subagent to handle a designated step while the controller retains governance and verification. The controller coordinates runtime execution, manages state under .hotl/state, and enforces non-nested delegation rules.

Does subagent delegation allow nested task handoff within isolated workers?▼

No, the workflow enforces non-nested delegation. Subagents execute designated steps independently, but critical invariants like verification, gates, and stop conditions remain strictly controller-owned to maintain a single source of truth.

What are the limitations of delegating workflow execution to independent subagents?▼

Subagent delegation requires explicit runtime coordination and central state management under .hotl/state. Verification stays in the controller, gates remain controller-owned, and nested delegation is prohibited to ensure governance-backed execution is maintained.

Can I parallelize work with subagents while maintaining a single source of truth?▼

Yes, delegating implementation steps to independent subagents improves throughput while maintaining a single source of truth in the controller. The controller enforces gate control, stop conditions, and final verification over all delegated results.