cto-agent-system

Software Company Agent System

A software company you own, but don't run.

Type /cto in the morning and say "good morning, start working". The CTO takes over: digests the project, decides what needs doing on its own, coordinates the team (CTO/CPO/CMO + specialists), improves code and product, and hands you a daily report + roadmap in the evening. You're the CEO (owner); they run the company.

This is not a feature-request system. It's an autonomous software company that takes initiative.

Works in Claude Code, Codex, and OpenCode (Cursor / Copilot adapters planned). Zero runtime — just markdown + one install script.

📦 npm: cto-agent-system · 🐙 GitHub: xenitV1/cto-agent-system · 🚀 Releases: v1.0.0 · 📖 Vision: VISION.md · 🛡️ Security: SECURITY.md

---

Why

Today's agents work as "tell me what to do and I'll do it" — an assistant, not a CTO. A real CTO comes in, reads the project, puts out fires, improves the product for the end user, and thinks about strategy when the code is clean. No existing tool does this autonomously as a full company: Paperclip has the org chart but is request-driven; Gastown has watchdogs but isn't a coordinator; Warp has skills but is webhook-triggered.

This project fills the gap: a lightweight, portable, autonomous software company — in markdown.

---

The company

CEO (you)
  ├── CTO  → Architect, Backend Dev, Frontend Dev, QA, Code Reviewer, DevOps
  ├── CPO  → Product Manager, UX Researcher, Product Designer, UX Writer, Data Analyst
  └── CMO  → Growth Lead, Content Writer, Market Researcher, Community Manager

• CTO answers "how do we build it?"
• CPO answers "what do we build, and why?"
• CMO answers "who do we reach, and how?"

15 specialist agents are lazy-spawned (only who's needed per task), so a one-line fix doesn't wake up the whole company.

---

The 12-hour autonomous loop

When you run /cto, the CTO runs 6 phases:

1. Digest — read the whole project + yesterday's state → .cto/state-today.md
2. Prioritize — fires (P0) first, then your request, then UX pain, then tech debt → .cto/plan-today.md
3. Dispatch & Execute — lazy-spawn the team, worktrees for parallel, maker/checker review
4. Integrate & Verify — full test suite, lint, build, staging deploy
5. Strategy (only if 1–4 are clean) — coordinate CPO + CMO → .cto/roadmap-proposal.md (needs your approval)
6. Report — daily report to you + close state

State lives on disk in .cto/ (markdown). The agent forgets between sessions — the repo doesn't.

---

Install

Two paths — pick what fits your tool.

A) Plugin marketplace (Claude Code & ZCode) — recommended

The cleanest install: one command, automatic updates, no file copying.

# In Claude Code (or ZCode):
/plugin marketplace add <this-repo-url>
/plugin install cto-agent-system@cto-agent-marketplace

# Then in any project:
/cto-agent-system:cto good morning, start working

Updates are automatic: /plugin marketplace update.

The plugin IS this repo (the marketplace source is ./). Skills live in .claude/skills/ (symlinked as skills/), agents in .claude/agents/ (symlinked as agents/), hooks in hooks/. Per-tool manifests: .claude-plugin/, .zcode-plugin/. Cursor uses project-based .cursor/rules/. The marketplace catalog lives at .claude-plugin/marketplace.json.

B) Universal installer (any CLI, incl. Codex & OpenCode) — fallback

Copies the constitution, source, the right adapter, and initial state into a project.

# 1. Clone (or copy the folder)
git clone <this-repo> cto-agent-system

# 2. Install into your project (all adapters by default)
cd cto-agent-system
./install.sh /path/to/your/project

# or: only one tool
./install.sh /path/to/your/project --tool claude   # or codex | opencode