cto-advisor

Analyzes technical debt, plans engineering team scaling, and provides architecture decision frameworks.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill cto-advisor-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto-advisor
Source: https://github.com/Tgoldi/claude-skills/tree/main/cto-advisor
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill cto-advisor-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Engineering leaders lack structured frameworks for assessing technical debt, planning team growth, evaluating technologies, and tracking engineering performance, leading to ad-hoc decisions and misaligned strategy. ## Core Features & Use Cases - Technical Debt Analysis: Run the tech debt analyzer script to score systems across architecture, code quality, infrastructure, security, and performance, then receive prioritized remediation plans with effort estimates. - Team Scaling Calculator: Generate hiring plans, role distributions, budget projections, and organizational structures based on current headcount and growth targets. - Decision Frameworks: Apply ADR templates, technology evaluation matrices, and DORA metrics dashboards for architecture governance and vendor selection. - Use Case: A CTO preparing for a board meeting uses the skill to quantify technical debt, model a 25-to-75 engineer scaling plan with budget projections, and present DORA metrics trends. ## Quick Start Ask the assistant to analyze technical debt for your system or calculate an engineering team scaling plan for your target headcount.

Frequently Asked Questions about cto-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess technical debt in a legacy system?

Run the tech_debt_analyzer.py script with scores for architecture, code quality, infrastructure, security, and performance indicators. It produces a weighted debt score, risk assessment, prioritized action items, and sprint-level effort estimates.

How to plan engineering team scaling and hiring?

Use the team_scaling_calculator.py script with your current headcount, role distribution, and target headcount. It generates a quarterly hiring timeline, role priorities, budget projections including salary and recruiting costs, and organizational structure recommendations.

What are DORA metrics and what targets should engineering teams hit?

DORA metrics measure deployment frequency, lead time for changes, mean time to recovery, and change failure rate. Elite teams deploy multiple times daily with under one hour lead time, under one hour MTTR, and below 15% change failure rate.

When should I write an Architecture Decision Record?

Write an ADR when a decision has significant impact, multiple options were seriously considered, the decision is hard to reverse, or you repeatedly explain the same choice. The references include a template covering context, options, decision outcome, and consequences.

How do I evaluate build vs buy for a technology decision?

Follow the technology evaluation framework: gather requirements, research 3-5 candidates, run a 2-4 week proof of concept, and score options on technical (40%), business (30%), and operational (30%) criteria. Build only for core differentiators with unique requirements.

What are the limitations of the team scaling calculator?

The calculator uses fixed role ratios and US/EU/APAC salary bands, so results are estimates rather than precise plans. It caps onboarding at 25% growth per quarter and does not account for domain-specific hiring constraints or market salary fluctuations.