delegation-helper

Construct minimal task packages with required files for dev, reviewer, or QA agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cihantas/cao --skill delegation-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-helper
Source: https://github.com/cihantas/cao/tree/main/.claude/skills/delegation-helper
Command: npx skills add https://github.com/cihantas/cao --skill delegation-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates context overload and wasted tokens when delegating work to AI agents, ensuring they receive only the essential information needed to complete tasks effectively.

Core Features & Use Cases

  • Minimal Context Packaging: Construct focused task packages with only relevant files and background
  • Agent Selection Guidance: Choose the right agent (dev, reviewer, qa) for each task type
  • Use Case: When you need to delegate a bug fix to a developer agent, this Skill helps you package just the ticket details and affected files, avoiding the confusion of full conversation history.

Quick Start

Use the delegation-helper skill to create a minimal task package for fixing the login bug in TICK-042.

Frequently Asked Questions about delegation-helper

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

FAQPage Schema
How do I reduce context overhead when delegating development tasks to AI agents?

Minimal context packaging focuses delegation by including only essential files and background needed for the task. This reduces token waste and ensures agents receive focused information rather than full conversation history, improving efficiency for bug fixes, features, or code reviews.

What should I include in a task package when delegating to a developer or QA agent?

A task package requires ticket details, affected files, and concise background using the mandatory Context Package Structure. Include only files relevant to the specific task—bug fix, review, or test—and exclude unrelated tickets or conversation history to keep the scope tight.

Can I delegate ticket-based tasks to multiple agent types with the same context?

No. Agent selection depends on task type: developers handle implementation, reviewers focus on code quality, and QA agents test functionality. Each agent type receives a customized minimal package tailored to their specific role and what they need to complete their part.

Why does full conversation history hurt delegation efficiency?

Full conversation history introduces irrelevant context that consumes tokens without adding value to the delegated task. Delegation-helper enforces context packages that exclude unrelated discussion, ensuring agents process only actionable information needed to implement, review, or test changes.

When should I use task delegation instead of direct agent coordination?

Use delegation when you need to hand off discrete, ticket-based work—like a specific bug fix or code review—and want to avoid overwhelming agents with unnecessary files or background. It's ideal for scaling work across dev, reviewer, and QA roles without context bloat.