CTO Advisor
CTO Advisor provides technical leadership frameworks for engineering teams, architecture decisions, and technology strategy. It helps assess technical debt, scale teams, evaluate build vs buy options, and establish engineering metrics, producing actionable reports and plans.
✨ What it does
- Provides tech debt analyzer script to score severity and prioritize fixes.
- Includes team scaling calculator for modeling growth and costs.
- Offers ADR templates and decision governance framework.
- Defines DORA metrics and engineering health dashboard.
- Guides build vs buy analysis with scoring and 3-year TCO.
- Lists red flags and proactive triggers for engineering issues.
🎯 When to use it
- When assessing technical debt and creating remediation plans.
- When making architecture decisions or evaluating technologies.
- When scaling engineering teams or planning hiring.
- When establishing engineering metrics or reviewing engineering health.
- When deciding whether to build or buy a solution.
🚀 How to use
Trigger by asking for CTO advice, tech debt assessment, architecture review, team scaling, or technology evaluation. Provide context about your engineering situation. Use the provided scripts for analysis. Example prompts:
Assess our technical debt and give a prioritized remediation plan.
Should we build or buy a customer data platform?
📄 Output: Deliverables include tech debt inventory, build vs buy analysis, hiring plan, ADR, or engineering health dashboard.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-advisor/skills/cto-advisor .claude/skills/cto-advisorSkill source: c-level-advisor/skills/cto-advisor/SKILL.md
⚠️ Good to know
Requires access to company context and engineering data; scripts are Python-based and need to be run locally.
❓ FAQ
What is the target tech debt ratio?
The target is less than 25% of engineering capacity spent on maintenance.
What are the DORA metrics targets?
Deployment frequency daily, lead time under 1 day, change failure rate under 5%, and MTTR under 1 hour.
When should an ADR be created?
When a decision affects more than one team, is hard to reverse, or has cost/risk implications greater than one sprint.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.