george-cto-plugin
Your AI agents need a CTO.
AI coding agents are powerful, but without leadership they produce inconsistent work — skipping tests, pushing to main, hardcoding assumptions, and leaving debt everywhere. This plugin gives your agents a CTO and a development culture.
What's Inside
Structure
skills/dispatch-team-lead/
├── SKILL.md # Dispatch mechanics + gotchas
├── references/team-lead-culture.md # Full Team Lead culture (loaded on dispatch)
└── scripts/dispatch.sh # Helper script for reliable culture injection
🧑💼 George — the CTO Agent
A custom agent (agents/george/) that acts as your CTO. George:
- Reports to the CEO (the user) — you set vision, George executes
- Manages a team of Team Lead agents — delegates complex work, doesn't code directly
- Knows when to dispatch vs handle directly — complex tasks get a Team Lead, casual questions George handles himself
- Reports results honestly — interprets Team Lead output, flags issues, suggests next steps
- Carries the "quality over everything" motto — never rushes past quality gates
📋 Dispatch Team Lead Skill
A skill (skills/dispatch-team-lead/) that George uses to spawn autonomous Team Lead agents via ahpx (Agent Host Protocol). The Team Lead culture lives in references/team-lead-culture.md and is loaded via progressive disclosure at dispatch time. Includes:
- The complete Team Lead identity and development culture
- When to dispatch a Team Lead vs. handling it yourself
- How to dispatch via
ahpx prompt to AHP servers with multi-host fleet support
- How to write good dispatch prompts (what + why, not step-by-step how)
- Session management for observing dispatched agents
- Remote filesystem discovery via
ahpx browse
The Mental Model
CEO (the user)
↓ gives direction
George (custom agent — agents/george/george.agent.md)
↓ uses the skill to dispatch
Team Lead (culture in references/, loaded on demand via skills/dispatch-team-lead/)
↓ dispatched to AHP servers via ahpx, carries the culture
The work gets done
George decides. The skill executes. The Team Lead culture travels with the dispatch.
🔒 Hooks Awareness
Rather than shipping global hooks (every project has its own linter, test runner, and quality gates), the Team Lead culture teaches agents to value and invest in hooks as part of their work:
- Check for existing hooks before starting work on any project
- Respect project hooks as automated quality gates
- Create hooks when they're missing — post-edit lint, session-end tests, pre-commit checks
- Knows hook locations for Copilot CLI (
.github/hooks/), Claude Code (.claude/hooks/), and Codex (.codex/hooks/)
Hooks belong in the project, not in a global plugin. This keeps quality enforcement tailored to each project's ecosystem.
Quick Start
Prerequisites
Install ahpx, the Agent Host Protocol CLI for dispatching agents:
npm install -g @tylerl0706/ahpx
You'll also need at least one AHP server running. Configure servers with ahpx server add. Run ahpx server status to check available servers.
Install as a Claude Code Plugin (recommended)
Install directly from GitHub:
/plugin install george-cto-plugin@george-cto-tools
Or add the marketplace first, then install:
/plugin marketplace add TylerLeonhardt/george-cto-plugin
/plugin install george-cto-plugin@george-cto-tools
Test locally during development:
claude --plugin-dir ./george-cto-plugin
Install as an Open Plugin
If your tool supports the Open Plugin format (.plugin/plugin.json), the plugin is also compatible with that system.
Manual Installation
Clone this repo and reference it from your project:
git clone https://github.com/TylerLeonhardt/george-cto-plugin.git
Copy what you need into your project's .github/ directory:
# Copy the George agent
cp -r george-cto-plugin/agents/george your-project/.github/agents/
# Copy the dispatch skill
cp -r george-cto-plugin/skills/dispatch-team-lead your-project/.github/skills/
How It Works
George acts as your CTO. When you give him a complex task, he uses the dispatch skill to spawn an autonomous Team Lead agent on an AHP server via ahpx. The skill injects the full Team Lead culture into the dispatch prompt — so the spawned agent carries your development values.
# George dispatches to an AHP server
ahpx prompt -n <session-name> --cwd <project-dir> "<culture + task prompt>"
# Or target a specific server in your fleet
ahpx prompt -n <session-name> -s <server-name> --cwd <project-dir> "<culture + task prompt>"
Example:
ahpx prompt -n add-auth --cwd ./my-project \
"You are a Team Lead. Our motto is **quality over everything.** ...