Menu
Codex-native Agent Teams orchestration using file mailboxes and `vc teams` commands for create/send/status/prune workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Ultimate autonomous execution engine. Plan โ Execute โ Test โ Never Stop Until Done. Use when the user wants hands-off completion with no questions, automatic recovery from any failure, and proven results.
Intelligent skill routing with automatic selection, composition, and fallback. Use when the user doesn't specify a skill, says "just do it", or wants the AI to decide the best approach.
Short alias for vc-phase-loop. Use when the user invokes "vcf:" (or explicitly "use vcf:") and wants maximum hands-off completion.
Short, explicit alias for vc-router. Use only when the user explicitly invokes `use vcg:` and wants the shortest reliable router command.
Replace with description of the skill and when Claude should use it.
| name | vc-agent-teams |
| description | Codex-native Agent Teams orchestration using file mailboxes and `vc teams` commands for create/send/status/prune workflows. |
| metadata | {"short-description":"Codex-native team lifecycle + mailbox protocol."} |
Use this skill when the task needs multi-agent coordination in Codex with explicit team lifecycle control.
This skill maps Claude-style team concepts into Codex-native operations:
~/.vc/teamsUse the vc teams command group:
vc teams create --name my-project --description "research + implementation"
vc teams add-member --team my-project --name researcher --agent-type researcher
vc teams add-member --team my-project --name implementer --agent-type coder
vc teams send --team my-project --type message --from team-lead --recipient researcher --content "Analyze architecture"
vc teams send --team my-project --type broadcast --from team-lead --content "Status update"
vc teams status --team my-project
vc teams watch --team my-project --interval-ms 500 --max-iterations 5
vc teams read --team my-project --agent researcher --unread
vc teams await --team my-project --agent team-lead --request-id <id> --timeout-ms 15000 --json
vc teams prune --team my-project --days 7
vc teams delete --name my-project --force true
~/.vc/teams/{team-name}/
โโโ config.json
โโโ inboxes/
โ โโโ team-lead.json
โ โโโ researcher.json
โ โโโ implementer.json
โโโ tasks/
vc teams send --type ... supports:
messagebroadcastshutdown_requestshutdown_responseshutdown_approvedshutdown_rejectedplan_approval_requestplan_approval_responseFor request/response safety:
shutdown_request and plan_approval_request generate requestId automatically if omitted.shutdown_response and plan_approval_response require both --request-id and --approve <true|false>.--force true).