Owner Stefan CoetzeeUpdated 2026-10-14

Open source · MIT license · latest release v0.2.0, 2026-10-14

CTO powersuit

Claude Code agent skills by Stefan Coetzee, one module per CTO function

The CTO powersuit is a set of agent skills, one module per CTO function from the deploy gate to the hand-over, that one person uses to run a company's whole engineering platform.

The answer first. The CTO powersuit is an open-source set of Claude Code agent skills by Stefan Coetzee, published on machinebehavior.io and at github.com/uncovertechtalent/cto-powersuit. It ships as one Claude Code plugin marketplace with 18 plugins: 15 modules for the functions of a CTO and 3 knowledge infrastructure plugins. The skills also install with the skills CLI, for Claude Code and other agents. The license is MIT.

A team installs the plugins it needs and runs them on generic defaults. Each skill also reads a private overlay when one exists: the team's own data for that module, such as rubrics, past decisions, and incident history, kept outside the repository.

Install the latest release

The latest release is v0.2.0, tagged on 2026-10-14. The commands below pin it. The repository is the only source of the project: install it only with these owner-qualified commands or from a clone of the repository.

claude plugin marketplace add uncovertechtalent/cto-powersuit#v0.2.0
claude plugin install sdlc@cto-powersuit

Install each plugin you need by its name from the tiles below, as <plugin>@cto-powersuit, and restart Claude Code after installing. Inside Claude Code the same commands work as /plugin marketplace add and /plugin install. With the skills CLI:

npx skills add uncovertechtalent/cto-powersuit#v0.2.0

The skills CLI copies the skill folders only. Skills that copy templates, the hooks, and the MCP server need the plugin install. Without #v0.2.0, both installers follow the main branch. On an existing repository, start with /sdlc:sdlc-audit: it needs no other module and names the module that fills each gap. To move a pin or roll back, see Versions and rollback in the README at v0.2.0.

Modules

One plugin per function of a CTO, grouped by the area of the job. Each module has its skills, the templates it copies into a repository, and a gate check with a pass fixture and a fail fixture. Each tile opens the plugin's page, and its link goes to the page on this site where the module runs in public.

Direction

Where the company stands, and the big technical decisions.

  1. fit

    The entry assessment: runs the sdlc audit and recommends which modules to fit and in which order. Its repo clinic audits a public repository at its owner's request.

    Running on this siteInside

  2. decisions

    RFCs, architecture decision records, and a review of the decision log, with a gate check that every record has a status, an owner, and a date.

    Running on this siteDecision log

Delivery

How code gets from an idea to production.

  1. sdlc

    The software delivery lifecycle: an audit for repositories built without one, tickets, change review for agent-written code, a local CI run before each push, test strategy, and release with rollback.

    Running on this siteBoard

  2. gate

    A deploy gate: rules with pass and fail fixtures, run records, findings that close only on a passing rerun, and a workflow whose deploy job waits for the gate.

    Running on this siteConformity gate

  3. docs

    A docs tree where every page has an owner and review dates, runbooks, a sweep for stale pages, and a static docs build.

    Running on this siteDocs health

Operations

Keeping it running, and seeing what it does.

  1. reliability

    Availability targets, SLOs and error budgets, incidents and postmortems, a static status page, and an on-call policy.

    Running on this siteStatus

  2. observability

    Alloy, Prometheus, Loki, Grafana, and Alertmanager with docker compose, dashboards as code, and alert routes.

    Running on this siteMission Control

Money

What the platform costs, and where the money goes.

  1. finops

    A cost baseline from invoices and billing exports, showback, unit costs, a SaaS stack audit, and a FOCUS export, with a gate check that every cost figure carries a period and a source.

    Running on this siteFinOps space

Security and risk

Protecting systems and data, staying compliant, testing for failure.

  1. security

    Supply chain, secrets, and access for a repository and its agents: actions pinned by commit SHA with an owner allowlist, a vulnerability scan and an SBOM, provenance checks for skills and MCP servers, a pre-push hook for private terms, and a quarantine for third-party text.

    Running on this siteGate runs

  2. compliance

    A control map to ISO 27001, TISAX, NIS2, and the GDPR by clause and article number, an AI Act triage, and a legal baseline for a website.

    Running on this siteStandards space

  3. red-team

    Pressure tests for a team's AI features: scripted multi-turn runs in a world with a known right answer, graded on the decision the system took.

    Running on this siteRed team

AI

Running AI in the company, and being found by AI.

  1. ai-ops

    Operations for a team's coding agents: a shared harness with narrow permissions, agent spend metered per API request with a budget alert, an audit trail of tool calls, and a coordinator pattern with state in files.

    Running on this siteAgent sessions

  2. aieo

    Visibility in AI search: llms.txt, structured data, answer probes, and predictions hashed before a page goes live.

    Running on this siteAIEO

People

Hiring the team, and handing the work over.

  1. hiring

    An interview loop, rubrics with anchored levels, debriefs with evidence before votes, and the profile of the person who takes over the platform.

    Running on this siteNo public page yet

  2. handover

    Hand the platform to its owner: training per module, exit criteria, and a test plan that shows the owner runs the platform from the docs alone.

    Running on this siteFounder tour

Knowledge infrastructure

Three plugins for the knowledge layer that agents work from. They are the optional parts of the ai-ops module.

  1. vestige

    An output filter you calibrate to yourself from your own transcripts. Hooks scan every reply and every Markdown file Claude writes.

    Running on this siteConformity gate

  2. vault

    A plain-Markdown vault with hybrid keyword and semantic search, served to Claude as an MCP server, with skills to seed it and to atomize documents into it.

    Running on this siteSRE Handbook space

  3. stance

    Stance filters: professional-b2, good-chad, receipts, poles, and mode-leak.

    Running on this siteResearch space

The plugin list, the lines, and the plugin pages follow release v0.2.0 of 2026-10-14: 18 plugins with 74 skills and 22 gate checks. Each plugin page links its source at that release. Changes on the main branch since the release are in the changelog under Unreleased.

Repository, releases, and changes

Three ways to use it

  1. Run it yourself. Your team installs the modules from the repository and runs them on its own.
  2. Call for help. When your team gets stuck, Stefan Coetzee does an assessment or the install.
  3. Hire Stefan Coetzee as your fractional CTO. He runs the powersuit for your company, with his own research and data in a private overlay on top of the open modules.

For the second and the third way: Stefan Coetzee: your next CTO, with the engagement shapes and what a first quarter delivers.

The powersuit in use

Inside, on this site, is the platform behind machinebehavior.io, which Stefan Coetzee runs with AI agent sessions and the CTO powersuit. Most modules link to their page there in the tables above. A five-minute walk through it is the founder tour.

The term

Stefan Coetzee named the CTO powersuit on machinebehavior.io on 11 October 2026. Whether answer engines name him for the term is a public test with a prediction hashed before the term went on the page: the CTO powersuit experiment.

Stefan Coetzee, 2026 The receipts are the argument.