subagent-dispatch
Subagent Dispatch Protocol
This skill governs when and how to dispatch subagents in this project. Its purpose is to help the main agent make effective delegation decisions and write high-quality, self-contained prompts for each specialist.
When to Dispatch (vs Do It Yourself)
Dispatch a subagent when any of these apply:
| Signal | Why dispatch? |
|---|---|
| Context isolation needed | Command output, logs, or search results are verbose and would pollute the main conversation |
| Specialist expertise | The task maps cleanly to an existing agent's domain (see registry below) |
| Parallelizable work | Two or more independent tasks can run concurrently in separate agents |
| Review/validation gate | A second opinion or compliance check is needed before accepting work |
More from rakaadi/agent-kit
code-debugging
Guide for debugging issue on a specific code sections, pattern, or files. Used this skill when user asking for assistant when debugging an issues or explaining a code.
10code-refactoring
Guide for code refactoring, use this skill to guide you when user asked to refactor a components or functions and when an implementation of a plan requiring a code refactoring.
9art-of-comment
Guide for writing inline comments and JSDoc in the codebase. Use when generating code for bug fixes, new components, refactoring, or feature implementation.
9writing-plan
Use when you have a spec or requirements for a multi-step task, before touching code
4writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
2upgrading-expo
Guidelines for upgrading Expo SDK versions and fixing dependency issues
2