cto-advisor

Provide structured decision frameworks for startup CTO technical choices.

5|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ceoimperiumprojects/imperium-brain --skill cto-advisor-ceoimperiumprojects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto-advisor
Source: https://github.com/ceoimperiumprojects/imperium-brain/tree/main/skills/cto-advisor
Command: npx skills add https://github.com/ceoimperiumprojects/imperium-brain --skill cto-advisor-ceoimperiumprojects

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Startup CTOs often face high-stakes technical decisions with limited resources, leading to over-engineering, wasted engineering time, and misalignment between technical choices and business goals. This Skill eliminates guesswork by providing proven, stage-aligned frameworks for every core CTO responsibility.

Core Features & Use Cases

  • Architecture & System Design: Decision trees for monolith vs microservices, database selection guides, and ADR templates to document technical choices.
  • Tech Stack Evaluation: Weighted scoring frameworks and pre-vetted default stacks for pre-seed to growth-stage startups to avoid resume-driven development.
  • Build vs Buy Analysis: Structured matrices to prioritize engineering resources on core product differentiators instead of commodity tools.
  • Tech Debt Management: Prioritization frameworks, the 20% rule, and refactoring strategies to maintain code quality without sacrificing feature velocity.
  • Team Scaling Guidance: Stage-specific hiring plans, team structure blueprints, and engineering culture best practices to build high-performing teams.
  • Security & Metrics: Stage-aligned security roadmaps and a CTO metrics dashboard to track engineering health, velocity, and cost efficiency.
  • Use Case: A seed-stage CTO can use this Skill to select a default tech stack, evaluate whether to build or buy an authentication system, plan their first 5 engineering hires, and set up basic monitoring without over-engineering.

Quick Start

Ask the cto-advisor skill to evaluate whether your seed-stage startup should build a custom notification system or purchase a third-party tool, and receive a prioritized recommendation with clear tradeoffs.

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 building or buying a software component for my startup?

Use a structured build versus buy analysis matrix to evaluate whether building a custom component or purchasing a third-party tool best prioritizes your engineering resources on core product differentiators. This framework clarifies tradeoffs to prevent wasted engineering time on commodity tools.

What is the best way to manage technical debt without sacrificing feature velocity?

Technical debt management requires prioritization frameworks and the 20% rule to balance code refactoring with feature velocity. This approach provides structured strategies to maintain code quality while ensuring your engineering team continues shipping product capabilities.

How do I select a tech stack for a pre-seed to growth-stage startup?

Tech stack selection for startups uses weighted scoring frameworks and pre-vetted default stacks to avoid resume-driven development. These stage-aligned recommendations balance technical excellence with business constraints and resource limitations.

How do I plan engineering team scaling and structure my first technical hires?

Engineering team scaling relies on stage-specific hiring plans, team structure blueprints, and culture best practices. These frameworks guide your first 5 engineering hires to build high-performing teams aligned with your startup's growth stage.

When do I need to transition from a monolith to microservices architecture?

Architecture design decision trees for monolith versus microservices help determine when to transition based on your startup's scaling stage. These frameworks prevent over-engineering by aligning system design choices with current business constraints.

What metrics should a startup CTO track to measure engineering health?

A CTO metrics dashboard tracks engineering health, velocity, and cost efficiency to monitor team performance. These stage-aligned metrics ensure technical choices remain aligned with business goals and resource limitations.