Agent skill · product strategy · alirezarezvani
cto-advisor
CTO decisions: tech debt, architecture direction, scaling the engineering team, technology evaluation, DORA metrics. Use whenever the user asks whether to rewrite, how to grow the eng team or which tech to bet on.
Why this skill is useful
Adds executable scripts for assessing technical debt and modeling team scaling that are not commonly found in public resources.
What it needs
Requires python installed locally. About 7k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
CTO Advisor Technical leadership frameworks for architecture, engineering teams, technology strategy, and technical decision-making. Keywords CTO, chief technology officer, tech debt, technical debt, architecture, engineering metrics, DORA, team scaling, technology evaluation, build vs buy, cloud migration, platform engineering, AI/ML strategy, system design, incident response, engineering culture Quick Start Core Responsibilities 1. Technology Strategy Align technology investments with business priorities. Strategy components: Technology vision (3-year: where the platform is going) Architecture roadmap (what to build, refactor, or replace) Innovation budget (10-20% of engineering capacity for experimentation) Build vs buy decisions (default: buy unless it's your core IP) Technical debt strategy (management, not elimination) See references/technologyevaluationframework.md for the full evaluation framework. 2. Engineering Team Leadership Scale the engineering org's productivity — not individual output. Scaling engineering: Hire for the next stage, not the current one Every 3x in team size requires a reorg Manager:IC ratio: 5-8 direct reports optimal Senior:junior ratio: at least 1:2 (invert and you'll drown in mentoring) Culture: Blameless post-mortems (incidents are system failures, not people failures) Documentation as a first-class citizen Code review as mentoring, not gatekeeping On-call that's sustainable (not heroic) See references/engineeringmetrics.md for DORA metrics and the engineering health dashboard. 3. Architecture Governance Create the framework for making good decisions — not making every decision yourself. Architecture Decision Records (ADRs): Every significant decision gets documented: context, options, decision, consequences Decisions are discoverable (not buried in Slack) Decisions can be superseded (not permanent) See references/architecturedecisionrecords.md for ADR templates and the decision review process. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/cto-advisor--caa3d9