cto

Document architecture decision records and guide cost-aware infrastructure choices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill cto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto
Source: https://github.com/jforksy/claude-skills/tree/main/cto
Command: npx skills add https://github.com/jforksy/claude-skills --skill cto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CTO Co-Pilot acts as a strategic technologist, guiding architecture decisions, infrastructure optimization, and cross-functional engineering coordination to align technology with business goals.

Core Features & Use Cases

  • Strategic technical leadership: help prioritize initiatives, align with product roadmap, and steer architectural choices.
  • Architecture decision support: document ADRs and capture trade-offs for major technical bets.
  • Infrastructure cost awareness: evaluate stack choices, hosting options, and scalability in a cost-conscious way.
  • Use Case: When deciding between a monolith and microservices, map trade-offs and propose a path forward.

Quick Start

Use the CTO Co-Pilot to run the discovery flow and load engineering context, then generate an ADR for the upcoming data pipeline decision.

Frequently Asked Questions about cto

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

FAQPage Schema
How do I document architecture decisions and capture trade-offs for major technical bets?

To document architecture decisions, you can generate Architecture Decision Records (ADRs) that capture trade-offs for major technical bets. This provides a clear rationale and historical context for your engineering team's strategic choices.

What is the best way to decide between a monolith and microservices for my startup?

Deciding between a monolith and microservices requires mapping specific trade-offs to propose a path forward. You should evaluate team coordination, infrastructure costs, and scalability to align the architecture with your business goals.

How do I load project context from engineering data sources to guide team coordination?

You can load project context by running a discovery flow that ingests engineering data sources. This process gathers the necessary technical and project information to guide cross-functional engineering coordination and prioritize initiatives.

Can I use this for strategic technical leadership from MVP to scale?

Yes, this applies across startup contexts from MVP to scale. It supports strategic technical leadership by helping prioritize initiatives, align with the product roadmap, and steer architectural choices as the engineering team grows.