A CTO, product manager, and engineer team skill for coding agents on Codex, Google Antigravity, and Claude Code, with task routing, shared handoffs, resource leases, and completion follow-up.
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
# Add to your Claude Code skills
git clone https://github.com/StochasticResult/cto-agent-teamGuides for using ai agents skills like cto-agent-team.
See how cto-agent-team compares with popular alternatives.
A reusable CTO team skill for coding-agent hosts: one CTO, five product managers, and fifty engineers, with working integrations for OpenAI Codex, Google Antigravity, and Claude Code.
The skill started in Codex, and the repository was named codex-cto-agent-team until 2026-11-16; GitHub redirects the old address. The organization, handoffs, private state, and guard helpers do not depend on one host. Each host has its own adapter guide.
The CTO gives work to the team and makes cross-team decisions. Product managers (PMs) divide tasks and review results. Engineers return outputs and evidence.
Use it across projects with private task records, explicit permissions, advisory resource leases, and one writer for each shared resource.
Install · Reproducible demo · Use · Host compatibility and limits · Adoption and maintenance evidence · Model routes · Private state · License
flowchart TD
CTO["CTO · Intake, coordination, final delivery"]
CTO --> PM01["PM01 · Product and interaction"]
CTO --> PM02["PM02 · Services and data"]
CTO --> PM03["PM03 · Systems and devices"]
CTO --> PM04["PM04 · Automation and integration"]
CTO --> PM05["PM05 · Quality and release"]
PM01 --> CS01["CS0101–CS0110 · 10 engineer roles"]
PM02 --> CS02["CS0201–CS0210 · 10 engineer roles"]
PM03 --> CS03["CS0301–CS0310 · 10 engineer roles"]
PM04 --> CS04["CS0401–CS0410 · 10 engineer roles"]
PM05 --> CS05["CS0501–CS0510 · 10 engineer roles"]
The full roster has 56 roles, including the current CTO chat. A role definition does not make a chat. A created chat, a READY reply, and active computation are different states. Chat count does not establish simultaneous computing capacity or permanent availability. Use only roles that help the current task. Engineer specialties guide assignment and permit suitable work outside a title.
Use a host that can load the skill or accept its instructions manually. The local helpers require Python 3.11 or later and only the standard library. Install the same folder in each host that you use:
| Host | Personal skill location | Guide |
|---|---|---|
| OpenAI Codex | ~/.agents/skills/cto-agent-team or ~/.codex/skills/cto-agent-team |
host-adapters.md |
| Google Antigravity | The skill directory that ~/.gemini/config/skills.json registers under entries (it can be the Codex directory) |
antigravity-workflow.md |
| Claude Code | ~/.claude/skills/cto-agent-team |
claude-code-workflow.md |
| Cursor, generic, or cloud | See the host matrix | host-adapters.md |
Cursor and generic integrations have documented guidance, not live client validation or universal native adapters. Chat creation, task messages, and monitoring require supported tools and account capacity. This skill does not add those capabilities.
skills/cto-agent-team folder in your personal skill directory.scripts, references, assets, and agents folders.cto-agent-team. If it is absent, restart the host.PowerShell example for a personal installation in the Codex location. For Claude Code, set $skillTarget to .claude/skills/cto-agent-team:
git clone https://github.com/StochasticResult/cto-agent-team.git
Set-Location cto-agent-team
$skillSource = Join-Path (Get-Location) 'skills/cto-agent-team'
$skillTarget = Join-Path $env:USERPROFILE '.agents/skills/cto-agent-team'
if (Test-Path -LiteralPath $skillTarget) { throw 'The target exists. Review it before updating.' }
New-Item -ItemType Directory -Path (Split-Path -Parent $skillTarget) -Force | Out-Null
Copy-Item -LiteralPath $skillSource -Destination $skillTarget -Recurse
For a project installation, use .agents/skills/cto-agent-team in that project.
To share a single skill installation across both Codex and Google Antigravity, register your personal skill directory (~/.codex/skills or ~/.agents/skills) in ~/.gemini/config/skills.json under entries; see antigravity-workflow.md.
See the Codex skill documentation and the Claude Code skill documentation.
Third-party skills are separate dependencies. Installing this repository does not install them or prove that any chat has read them.
Run the offline end-to-end walkthrough in examples/end_to_end_demo/run_demo.py using only Python 3.11+ standard library modules (no API keys, network access, or live host threads required):
python examples/end_to_end_demo/run_demo.py --verify
The demo runs inside a temporary private directory outside the repository and executes all five stages of a real task lifecycle (CTO Intake -> PM02 Dispatch -> CS0201 Lease/Patch/Test -> PM02 SHA-256 Acceptance -> CTO Delivery) while keeping capability layers strictly separated:
team_state.py (init, register, validate), model_route.py (demo_routing_input.json), agent_guard.py (acquire, competing writer CS0202 blocked with exit code 2, run watchdog running unittest, and release), atomic JSON event creation, SHA-256 digest checks, and shared/STATUS.md output.uuid5 thread IDs, and fixture catalog inputs (dispatch_ready: false).create_thread, invoke_subagent), LLM inference, account quotas, browser UI verification, and completion wakeups.See examples/end_to_end_demo/README.md for the complete stage diagram and sample output.
Open a CTO chat in the target project. Select the skill or use $cto-agent-team in your request.
For a plan, use:
Use $cto-agent-team to plan the work for
<GOAL>. Give the task owners and acceptance criteria. Do not make chats.
For a full organization of independent chats, use:
Use $cto-agent-team for
<PROJECT>. Use the current chat as CTO. Make five PM chats and ten engineer chats per PM. Use suitable existing chats. I permit creation of missing chats. I permit CTO-to-PM and PM-to-engineer task messages for this project. Keep private state in<PRIVATE_STATE_DIR>. Use the available tools and account capacity. Give actual creation and READY results.
Replace the placeholders before use. Skill selection alone does not authorize chat creation or task messages. For a general request to use agents, follow existing authorization and tool support, or prepare a plan. For independent chats, discover the current host tools and verify the target project before authorized creation. Host adapters contain specific tool names and parameter boundaries. Examine unknown creation results before another attempt. Reuse real chat identifiers from supported tools.
Each task must identify its target, permissions, outputs, acceptance criteria, and writable resources.
Organizational delegation does not grant permission for every device, publication, external message, or purchase.
Read the target project's AGENTS.md. Make sure that the device identity, connection, and task permission are correct.
PMs read engineer results in shared private events. One designated clerk writes the shared summary. The CTO reads that summary and necessary exact source references. Canonical tasks remain authoritative. Use messages only for necessary authorized dispatch, continuation, or recovery, with task and document pointers. Active recipients read at safe boundaries. Do not send routine progress or result relay messages. See workflow.md for complete handoffs and result collection.
Separate task requirements, host capabilities, model evidence, user policy, native parameters, and actual execution.
The following table is the explicit compatibility-6.1 profile. It is not a default for every host or an availability claim:
| Route | Work | Model | Reasoning |
|---|---|---|---|
coordination_research |
Routine PM coordination and research across sources | gpt-6.1-sol |
high |
scoped_engineering |
Scoped fixes, UI implementation, visual checks, and computer actions with a clear target | gpt-6.1-terra |
high |
extraction |
Simple extraction and routine summaries from supplied material | gpt-6.1-terra |
medium |
complex_engineering |
Complex coding, architecture, permissions, transactions, critical review, and releases across systems | gpt-6.1-sol |
xhigh |
mechanical_supervision |
Routine status checks, retry records, deduplication, and comp |
cto-agent-team is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by StochasticResult. A CTO, product manager, and engineer team skill for coding agents on Codex, Google Antigravity, and Claude Code, with task routing, shared handoffs, resource leases, and completion follow-up. It has 86 GitHub stars.
cto-agent-team's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/StochasticResult/cto-agent-team" and add it to your Claude Code skills directory (see the Installation section above).
cto-agent-team is primarily written in Python. It is open-source under StochasticResult on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh cto-agent-team against similar tools.
No comments yet. Be the first to share your thoughts!