autosearch:delegate-subtask

Define auditable execution contracts for delegated subtasks with budgets and schemas.

40|6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/0xmariowu/Autosearch --skill autosearch-delegate-subtask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autosearch:delegate-subtask
Source: https://github.com/0xmariowu/Autosearch/tree/main/autosearch/skills/meta/delegate-subtask
Command: npx skills add https://github.com/0xmariowu/Autosearch --skill autosearch-delegate-subtask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegate-subtask provides a precise execution contract for decomposed tasks, enabling auditable, bounded, and reusable subtask executions.

Core Features & Use Cases

  • Define input/output schemas for subtasks to ensure consistent handoffs
  • Enforce budgets, stop conditions, and traceable progress for each subtask
  • Enable parallelization of subquestions while maintaining auditability and accountability

Quick Start

Provide a concrete subtask description and budget, and let the system generate an auditable execution contract.

Frequently Asked Questions about autosearch:delegate-subtask

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

FAQPage Schema
How do I delegate subtasks to sub-agents with budget constraints?

To delegate subtasks with budget constraints, define an execution contract specifying input/output schemas, budget limits, context seeds, and failure modes to guide bounded, trackable sub-agent execution.

What is an execution contract for parallel subtask execution?

An execution contract for parallel subtask execution is an auditable specification defining input/output schemas, context seeds, and failure modes to ensure bounded, verifiable work across decomposed research tasks.

How do I ensure consistent handoffs when decomposing research tasks into parallel subquestions?

Ensure consistent handoffs by defining input/output schemas within the execution contract, enabling parallelization of subquestions while maintaining auditability and accountability for each sub-agent.

Can I specify failure modes and stop conditions for delegated subtasks?

Yes, you can specify failure modes and stop conditions within the execution contract to enforce budgets and ensure traceable, bounded progress for each delegated subtask.

When do I need to define execution contracts for subtask delegation?

You need execution contracts for subtask delegation when decomposing research tasks into parallel subquestions requiring budgeted, verifiable execution and auditable, trackable sub-agent work.

What is the best way to track sub-agent progress on decomposed research tasks?

The best way to track sub-agent progress is to generate an auditable execution contract that enforces stop conditions, budget constraints, and traceable progress for each parallel subtask.