Sub-Agent Orchestrator

Manages the specialized AI agents that form the core of this engineering environment.

Overview

Specialized sub-agents are defined in master templates and then projected into tool-specific configurations. This skill ensures that your Planner, Implementer, Reviewer, and other agents remain consistent and highly capable regardless of the platform they are running on.

Workflow: Syncing Sub-Agents

Use this when you have modified a master template or the global metadata.

1. Run Sync Command:
   bashCopy

   ./scripts/update-subagents.sh --agent=all --system=all --force
   

   • --agent: planner, reviewer, implementer, coordinator, prompt-creator, or all.
   • --system: copilot, opencode, claude, or all.
2. Verify Synchronization:
   bashCopy

   ./scripts/validate-subagents.sh
   

   • This ensures that the content (excluding headers) is identical between different system implementations.

Workflow: Adding a New Sub-Agent

1. Create Master Template: Create templates/subagents/master/<agent-name>.md with the core behavioral instructions.
2. Register in Metadata: Add the agent's entry to templates/subagents/master/METADATA.json.
   • Define name, description, and examples.
   • Specify header_lines for each target system.
3. Initialize Across Systems:
   bashCopy

   ./scripts/update-subagents.sh --agent=<agent-name> --system=all --force
   

Reference: Agent Structure

Resources

scripts/

• update-subagents.sh: The primary engine for projecting master templates into configuration files.
• validate-subagents.sh: A consistency checker that identifies drifts between platforms.
• extract-to-master.sh: (Utility) Used for reverse-syncing if a change was made directly to a target file.

references/

• templates/subagents/master/METADATA.json: The "Source of Truth" for agent names, descriptions, examples, and permission overrides.
• templates/subagents/master/*.md: The master behavioral templates.
• templates/subagents/headers/*.template: Header structures for different tools.