subagents-management

Managing subagents across Claude Code, Codex CLI, and OpenCode involves updating the correct user/project instruction locations and AGENTS.md conventions. This skill automates creating, listing, moving, and editing agent definitions while ensuring correct YAML frontmatter schema usage.

Deleting a subagent definition safely requires explicit user confirmation before the operation executes. This skill enforces operational safety guardrails to prevent accidental loss of agent definitions, pausing all deletion tasks until you explicitly approve the removal.

Creating a read-only subagent for reviewing code requires defining specific tools, model parameters, and permissions in the YAML frontmatter. This skill handles subagent lifecycle management by generating the correct configuration files for your desired agent scope and permissions.

Yes, subagent configuration supports moving agents between user and project scopes. This skill updates the correct instruction locations for each platform, ensuring persistent agent behaviors are maintained when relocating definitions across Claude Code and Codex CLI environments.

YAML frontmatter is required when configuring specialized agents to define their tools, model, and permissions. This skill ensures correct YAML frontmatter and schema usage, applying the necessary metadata for persistent agent behaviors across different instruction layouts.

Yes, you can list all available subagents before generating new ones. This skill supports listing operations via provided scripts, allowing you to review existing agent definitions in the project scope before creating new specialized configurations.