use-coding-agents
How to use the coding agents installed on this machine (claude, codex, droid, grok, hermes, opencode, copilot, pi) as plain sub-agents in orchestrated workflows: one headless invocation, one prompt in, one result out. Deliberately ignores each CLI's own orchestration features (droid --mission, codex multi_agent, hermes delegation/moa/kanban, grok --agents, opencode personas). The orchestrator is whatever session is running the skill; the CLIs are interchangeable workers. Use when the user asks "which agent should run this", "fan out workers", "run X headless", or when a lifeos skill (overnight, timeboxed-iterating, workgraph, gauntlet, bughunt, dark-factory) needs to launch an agent CLI.
Install
Show step-by-stepHide step-by-step
Open your terminal
- Mac: Press โ Space, type "Terminal", press Enter
- Windows: Press Win R, type "cmd", press Enter
Paste the command above and press Enter
Use the Copy command button, then paste in your terminal (Mac: โV, Windows: Ctrl V).
Restart Claude Code
Close and reopen Claude Code, or start a new session, so it picks up the new skill.
Where it lives
Comments
Related skills
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes