cto-cyclelisted

Use when building any new feature, change, or fix in ANY project that you want done properly — invoked by saying "use the cto-cycle", "run the CTO cycle", "build X with the CTO", or "/cto-cycle". Project-agnostic: it first orients on the current repo (CLAUDE.md, rules, plan docs, stack) and then runs a disciplined loop — investigate the scope, interview the user to kill assumptions, write an implementation plan, have the CTO sub-agent review and score it (0–100), debate to consensus, then implement phase-by-phase with a CTO review after each phase — advancing autonomously without waiting between phases. Supports an optional external deep-audit reviewer and optional email summaries.
diax7/cto-cycle · ★ 0 · AI & Automation · score 75

Install: claude install-skill diax7/cto-cycle

# The CTO Cycle How a feature or fix ships: a developer (you) and a CTO (a sub-agent) work together, with the user involved as little as possible. **You implement; the CTO reviews, scores, and manages quality.** The goal is work that is correct and well-built *for this project at its stage* — right enough the first time, without gold-plating. This skill is **project-agnostic.** It carries the *loop*; the *standards* come from whatever project you're in. This is a **flexible playbook, not a rigid script.** Scale every stage to the task: a one-line tweak collapses most of it; a multi-screen feature uses all of it. Skip what doesn't apply. **The user's explicit instructions always override this skill.** ## 0 — Orient on the project (do this first, every run) Before scoping anything, learn the project so you and the CTO judge by *its* rules: - **`CLAUDE.md`** (root + any nested) — the project's constitution; its declared non-negotiables are hard rules. - **`.claude/rules/`, `docs/`** — design system, ADRs/`DECISIONS.md`, specs, active plan. - **The stack manifest** — `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` / etc. — language, frameworks, and the scripts that prove "green" (build, lint, types, test), plus the package manager. - **Conventions in code** — the UI primitives / shared modules / state layer / data layer you should **reuse or extend** instead of building new. The CTO agent re-orients on its own too, but you set the direction here. If the