subagent-delegation

# Subagent Delegation Use this skill when the user explicitly asks to delegate work to another coding agent, use a named subagent, get a second opinion, compare approaches, or run a subagent-like workflow. Do not use subagents silently. Tell the user when another subagent is being used. ## Core commands Use only these commands for normal delegation: ```bash devspace agents ls devspace agents run <profile-or-provider-or-id> "<prompt>" devspace agents show <id> ``` `ls` shows existing subagent sessions for the current workspace. DevSpace scopes it automatically from the shell environment injected by the workspace tool. `run <profile> "<prompt>"` starts a new configured profile and prints a DevSpace agent id. `run <provider> "<prompt>"` starts a raw built-in provider when no configured profile is needed. Built-in providers are listed by `open_workspace`. `run <id> "<prompt>"` sends a follow-up to an existing agent. `show <id>` prints status and the latest response. If the agent is still running, `show` waits briefly. If there is still no final response, call `show` again later. Do not run provider CLIs such as `codex`, `claude`, `opencode`, `pi`, `cursor-agent`, or `copilot` directly unless you are explicitly debugging DevSpace agent integration. ## Choosing a profile Choose profiles from the compact subagent profile catalog returned by `open_workspace`. Use the profile name with `devspace agents run`. If no profile fits and delegation is still appropriate, use a bu...