skills.rest
zzafergok
zzafergokCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cto-advisor

Advise engineering leadership on technology strategy, technical debt, and organizational design.

1|Updated Aug 7, 2025
Search Tags:#technical debt#engineering metrics#CTO#technology strategy#vendor evaluation#engineering leadership#team design
One-click install
npx skills add https://github.com/zzafergok/arktos --skill cto-advisor-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cto-advisor
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/cto-advisor
Command: npx skills add https://github.com/zzafergok/arktos --skill cto-advisor-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering leaders face high-stakes decisions about technology investments, technical debt, team structure, and vendor selection without a structured framework to connect technical choices to business outcomes, delivery capacity, and operational risk. ## Core Features & Use Cases - Technology Strategy: Translate product and business goals into capability needs, compare build/buy/partner/defer options, and sequence investments with measurable decision points. - Technical Debt Portfolio: Build an evidence-backed debt inventory evaluated by customer impact, incident risk, delivery drag, and cost of delay, then recommend targeted remediation rather than blanket cleanup. - Team and Operating Model: Align ownership boundaries with product and platform boundaries while reviewing cognitive load, decision latency, on-call burden, and cross-team dependencies. - Use Case: A CTO at a growth-stage startup needs to decide whether to migrate to a new cloud vendor. The Skill frames the decision around functional fit, integration cost, data portability, exit cost, and roadmap alignment, then produces a recommendation with assumptions, risks, leading indicators, and a review date. ## Quick Start Ask the advisor to evaluate whether your engineering organization should build or buy a specific platform capability given your team size and funding horizon.

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 across engineering teams?▼

Create an evidence-backed inventory and evaluate each debt item by customer impact, incident risk, delivery drag, security exposure, and cost of delay. Recommend a portfolio approach: prevent new debt, contain critical risk, retire high-cost debt, and explicitly tolerate low-impact debt.

How to make a build vs buy decision for platform tooling?▼

Evaluate functional fit, integration cost, security and compliance, data portability, service reliability, pricing sensitivity, exit cost, and roadmap alignment. Compare total cost of ownership and reversibility across build, buy, partner, and defer options before committing.

What engineering metrics should a CTO track?▼

Use metrics to answer an operating question, not to rank individuals. Combine delivery flow, reliability, quality, security, customer outcomes, and team health, and define each metric's data source, cadence, owner, expected behavior, and gaming risk.

When should I use this advisor instead of an architecture review?▼

Use this advisor for executive-level decisions about strategy, organization, investment, and risk. For a specific system architecture decision requiring deeper technical analysis, use a senior software architect skill instead.

What are the limitations of executive technology advisory?▼

Strategic recommendations are proportionate to available evidence and depend on accurate inputs about company stage, constraints, and vendor facts. Current vendor claims should be verified independently, and implementation details require separate technical analysis.

Related Skills

Explore More Software Engineering Skills→
anyreachaianyreachai
1

maturity-assessment

Analyze SOPs and company background to benchmark operational maturity in a React dashboard.

Official
Advanced
mariasebarespersonamariasebarespersona

autoplan

Automate three-phase governance reviews of plans with structured decision logging.

Community
Advanced
zhangzhang-111-izhangzhang-111-i
2

stress-test

Stress-test business assumptions by modeling downside scenarios and calculating sensitivity.

Community
Advanced
PeterHddPeterHdd
10

engineering-senior-developer

Guide software architecture, technical planning, and production-safe rollout strategies.

Community
Advanced