subagent

Define an internal protocol for evo optimization subagents to orchestrate iterative improvements.

7|3|Updated May 4, 2026
One-click install
npx skills add https://github.com/nopperabbo/codebuddy2api --skill subagent-nopperabbo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent
Source: https://github.com/nopperabbo/codebuddy2api/tree/main/opencode-config/skills/evo-subagent
Command: npx skills add https://github.com/nopperabbo/codebuddy2api --skill subagent-nopperabbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the interaction protocol between a coordinating agent and its evo optimization subagents, enabling reproducible experiments and disciplined task delegation.

Core Features & Use Cases

  • Defines a structured brief format and iteration workflow for evo subagents.
  • Reads traces and briefs to guide iterative edits and experiments within the main repository.
  • Ensures host-agnostic operations and safe spawning of subagents within the EVO framework.

Quick Start

Provide a brief that defines objective, parent, boundaries, and pointer traces, then run the orchestrator to spawn the initial subagent worktree.

Frequently Asked Questions about subagent

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

FAQPage Schema
How do I coordinate evo optimization subagents for iterative experiments?▼

You can coordinate evo optimization subagents by defining a structured brief with objectives and pointers, then running the orchestrator to spawn agent worktrees that execute iterative repository edits.

What is an evo subagent orchestration protocol and when do I need it?▼

An evo subagent orchestration protocol standardizes interaction between a coordinating agent and spawned optimization agents, needed when automating reproducible experiments and disciplined task delegation.

How to spawn subagents safely within the evo framework?▼

To spawn subagents safely, provide a brief defining objective, parent, boundaries, and pointer traces, then run the orchestrator which enforces host-agnostic commands and workspace rules.

Does the evo subagent protocol enforce host-agnostic operations for spawned agents?▼

Yes, the evo subagent protocol enforces host-agnostic operations and safe interaction patterns, ensuring spawned agents execute structured experiments without environment-specific dependencies.

What format do briefs need to be in for evo optimization subagents?▼

Briefs for evo optimization subagents must define the objective, parent, boundaries, and pointer traces to guide iterative edits and evaluation results within the main repository.

Can I use evo subagent orchestration without existing evaluation traces?▼

No, the orchestrator reads traces and briefs to guide iterative experiments, so existing evaluation results and pointer traces are required to drive structured improvements.