cto-advisor

Assess technical leadership decisions and engineering risk for CTO-level planning.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill cto-advisor-veloxia-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto-advisor
Source: https://github.com/Veloxia-agency/VELOXIA-WEB/tree/main/.claude/skills/c-level-advisor/skills/cto-advisor
Command: npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill cto-advisor-veloxia-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps engineering leaders turn messy technical choices into clear, prioritized decisions for architecture, team growth, and technology strategy.

Core Features & Use Cases

  • Architecture governance and ADR support for major design decisions.
  • Technical debt assessment and remediation prioritization for legacy systems.
  • Team scaling and engineering health guidance using planning metrics and capacity models.
  • Example: when a product team is debating a rewrite, this Skill helps compare options, document trade-offs, and propose a phased path forward.

Quick Start

Ask the skill to review your architecture, technical debt, or team growth plan and return a prioritized CTO-level recommendation.

Frequently Asked Questions about cto-advisor

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

FAQPage Schema
How do I prioritize technical debt remediation for legacy systems?

Prioritize technical debt remediation by assessing engineering risk and system constraints against business goals. This produces a prioritized recommendation and metric-driven action plan, turning messy legacy choices into clear, phased remediation paths for CTO-level planning.

What is the best way to evaluate architecture trade-offs for a system rewrite?

Evaluating architecture trade-offs requires comparing design options against system constraints and team capacity. This process generates ADR-ready reasoning and prioritized recommendations, helping engineering leaders document major design decisions and propose a phased path forward.

How do I structure team scaling plans using engineering metrics?

Structure team scaling plans by applying planning metrics and capacity models to assess engineering health. Providing structured inputs on team capacity and business goals yields guidance on team growth and metric-driven action plans for CTO-level strategy.

Can I generate ADR-ready documentation for major design decisions?

Yes, you can generate ADR-ready documentation by inputting system constraints and business goals for architecture governance. The process outputs ADR-ready reasoning that documents trade-offs and supports major design decisions for engineering leaders.

How do I assess vendor evaluation risks in technology strategy planning?

Assess vendor evaluation risks by analyzing technical leadership decisions and engineering constraints against business goals. This yields prioritized recommendations and metric-driven action plans, ensuring vendor choices align with your overall technology strategy and system capacity.