home / skills / shaul1991 / shaul-agents-plugin / executive-cto

executive-cto skill

safe

This skill defines and communicates the technology strategy, architecture decisions, and R&D leadership to align teams and drive results.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill executive-cto

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

551 B

---
name: executive-cto
description: Executive CTO Agent. 기술 전략, 아키텍처 결정, R&D 리더십을 담당합니다.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch
---

# Executive CTO Agent

## 역할
기술 비전과 전략을 수립하고 기술 조직을 리드합니다.

## 담당 업무
- 기술 로드맵 수립
- 아키텍처 결정
- R&D 리더십
- 기술 거버넌스

## 트리거 키워드
기술 전략, 아키텍처, 기술 비전, 기술 로드맵

## 산출물 위치
- 기술 전략: `docs/tech-strategy/`

Overview

This skill acts as an Executive CTO agent that defines technology vision, drives architecture decisions, and leads R&D and technical governance. It provides clear strategic outputs like roadmaps, architecture reviews, and governance recommendations. The agent is designed to support executive-level technical planning and operational oversight.

How this skill works

The agent inspects current product and platform constraints, existing architecture artifacts, and organizational capabilities to propose a strategic technology roadmap. It synthesizes tradeoffs across scalability, cost, time-to-market, and risk to recommend architecture decisions and governance patterns. Outputs are organized into deliverables such as a technology strategy folder, architecture decision records, and R&D priorities for engineering leadership.

When to use it

When defining or revising long-term technology strategy
Before making major architecture or platform changes
When prioritizing R&D investments across projects
To create governance, compliance, or risk mitigation patterns
When aligning engineering org structure with product goals

Best practices

Start with clear business objectives to align technical priorities
Use architecture decision records (ADRs) for transparent, versioned decisions
Balance short-term delivery needs with long-term platform health
Incorporate measurable success criteria and review cycles for the roadmap
Engage cross-functional stakeholders early to validate assumptions

Example use cases

Create a 12–18 month technology roadmap aligned to product milestones and staffing
Evaluate migration options (monolith→microservices or cloud provider changes) with pros/cons and cost estimates
Define platform-level standards: observability, security baseline, CI/CD patterns
Prioritize R&D experiments and define success metrics for proof-of-concept work
Establish governance rules and approval flows for third-party services and large infra changes

FAQ

What deliverables does the agent produce?

It produces a technology strategy dossier, architecture decision records, prioritized R&D backlog, and governance guidance; strategy documents are typically organized under a tech-strategy folder.

How does it balance short-term vs long-term needs?

It maps work into time horizons with explicit tradeoffs, recommends quick wins that enable longer-term investments, and ties each recommendation to measurable outcomes and risk assessments.