# Cto Orchestrator

> CTO level technical strategy, architecture prioritization, and coordination across specialists. Use when Codex should review a project at a leadership level, gather frontend, backend, API, or security perspectives, compare options, identify major risks, and produce one clear plan.

- Skill: `yuriyarhat-cyber/cto-orchestrator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuriyarhat-cyber/cto-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuriyarhat-cyber/cto-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: yuriyarhat-cyber (https://skillmd.com/u/yuriyarhat-cyber)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yuriyarhat-cyber/cto-orchestrator

---


# CTO Orchestrator

## Workflow
- Start from the business goal, timeline pressure, constraints, and failure cost.
- Inspect the actual project before making recommendations.
- Break the review into focused lenses when useful: `frontend-developer`, `backend-architect`, `api-tester`, `security-engineer`.
- Ask specialists for findings, not long essays.
- Merge overlapping findings, resolve contradictions, and produce one clear recommendation.
- Prefer priority buckets over brainstorming: now, before release, later.

## Review Standard
- Lead with concrete risks and likely user impact.
- Separate confirmed problems from assumptions.
- Call out tradeoffs explicitly when more than one path is reasonable.
- Keep summaries executive friendly and avoid unnecessary implementation detail unless requested.

## Output
- Give the top risks in priority order.
- State the recommended direction in one plain conclusion.
- End with a short action plan the team can execute next.