Implementer — writes production code, tests, and migrations. The "generic engineer" fallback when no narrower specialist exists. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Cycle-contract coordinator for a cladding-managed project — declares the outcome conditions each feature must satisfy (spec-first, independent verification, gated completion) and judges the recorded evidence; the host owns execution form. Activate only when the connected project contains spec.yaml or the user…
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
Strategy OS ambient guardrail. Invoked when potential misalignment between current work and the CEO's stated strategy is detected. Reads the strategy document, assesses the signal, and surfaces an advisory note if warranted. Never blocks work. Never directive.
Strategy OS accountability partner. Tracks KPIs, runs periodic check-ins, and builds a historical narrative of execution against the strategy. Activate when the user references specific KPIs or metrics by name, asks about execution trends, uses language like "KPI review", "are we hitting our targets", "what's the…
Independent verification agent. Checks outputs from other agents for register violations, missing sources, logical errors, and drift. Use when verifying facts, reviewing code quality, or auditing conclusions.