cto-advisor

Guide CTO-level decisions on tech debt, rewrites, and build vs. buy.

Updated Aug 23, 2026

Search Tags:#architecture #decision making #strategy #tech debt #team scaling #cto

Ready to run

npx skills add https://github.com/sharkitect-solutions/sharkitect-claude-toolkit --skill cto-advisor-sharkitect-solutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cto-advisor
Source: https://github.com/sharkitect-solutions/sharkitect-claude-toolkit/tree/main/skills/cto-advisor
Command: npx skills add https://github.com/sharkitect-solutions/sharkitect-claude-toolkit --skill cto-advisor-sharkitect-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance on critical CTO-level decisions, helping navigate complex challenges in technology strategy, team management, and operational efficiency.

Core Features & Use Cases

Strategic Decision Support: Offers frameworks for prioritizing tech debt, deciding between rewrites and refactors, and evaluating build vs. buy options.
Team & Architecture Guidance: Advises on scaling engineering teams, establishing architecture governance, and optimizing reliability vs. velocity trade-offs.
Use Case: A CTO needs to decide whether to invest in refactoring a legacy system or undertaking a full rewrite. This Skill provides a structured framework to analyze the situation and make an informed decision.

Quick Start

Use the cto-advisor skill to help decide between a rewrite versus a refactor.

Frequently Asked Questions about cto-advisor

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

FAQPage Schema

How do I decide between a rewrite versus a refactor for a legacy system?▼

A rewrite versus refactor decision requires analyzing technical debt prioritization and reliability versus velocity trade-offs. This Skill provides a structured framework to evaluate your legacy system and make an informed strategic decision.

What is the best way to prioritize technical debt across multiple engineering teams?▼

Prioritizing technical debt requires high-level strategic planning for technology leadership. You can use frameworks designed for tech debt prioritization to balance organizational decision-making with engineering team scaling and architecture governance.

How do I evaluate build vs. buy options for new architecture components?▼

Evaluating build vs. buy options involves using specific frameworks to assess vendor lock-in and architecture governance. This strategic guidance helps technology leadership navigate complex vendor decisions while optimizing operational efficiency.

Can I use this framework for engineering team scaling and architecture governance?▼

Yes, this framework provides strategic guidance for engineering team scaling and establishing architecture governance. It focuses on high-level organizational decision-making to help CTOs balance growth and stability.

When should I not use a full rewrite to address technical debt?▼

You should avoid a full rewrite when tech debt prioritization frameworks indicate that a refactor better balances reliability versus velocity trade-offs. Analyzing these trade-offs ensures you maintain operational efficiency without halting development.