cto-review

Reviews documents and proposals through a CTO lens focused on platform strategy and shipping velocity.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill cto-review-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto-review
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/cto-review
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill cto-review-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering proposals and technical plans often lack scrutiny on platform thinking, iteration speed, and execution ownership. This Skill simulates feedback from an experienced CTO so documents get stress-tested on architecture, mobile-first design, and ship-readiness before reaching real leadership. ## Core Features & Use Cases - Platform & Architecture Review: Probes API surfaces, data models, latency budgets, and whether a proposal builds platform primitives or just features. - Execution & Shipping Critique: Challenges scope with two-week v1 cycles, single-owner accountability, metrics gates, and rollback plans. - Structured Verdict Output: Delivers prioritized feedback (critical to nice-to-have) ending with a clear Ship it / Revise / Rethink verdict and 2-3 actionable next steps. - Use Case: Before sending a microservices migration proposal to your VP of Engineering, run it through this review to surface missing performance budgets, cross-team dependency risks, and an over-scoped v1. ## Quick Start Ask the assistant to review your attached architecture proposal using the cto-review skill and return a prioritized critique with a ship verdict.

Frequently Asked Questions about cto-review

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

FAQPage Schema
How do I get CTO-level feedback on an architecture proposal?

Submit your proposal document and invoke the cto-review skill. It applies a structured checklist covering platform thinking, performance budgets, mobile UX, and shipping plans, then returns prioritized feedback with a clear verdict.

What types of documents can this skill review?

It reviews platform architecture proposals, build-vs-buy analyses, engineering team structure plans, technical roadmaps, sprint plans, and mobile-first product proposals. It is not suited for pure business strategy or individual code craft feedback.

When should I use cto-review instead of a general document review?

Use it when the core question is whether something will scale and ship fast under real engineering leadership scrutiny. For document clarity and writing quality, a general writing review fits better; cto-review focuses on org execution and platform strategy.

What output format does the review produce?

Feedback is organized by priority from critical to nice-to-have, written in a direct, demo-oriented CTO voice. It ends with a verdict of Ship it, Revise and resubmit, or Rethink the approach, plus 2-3 actionable next steps with aggressive timelines.

What are common reasons a proposal fails this review?

Proposals get pushed back when they lack a working prototype, think in features instead of platforms, plan multi-quarter work without milestones, require multiple teams for v1, treat mobile as an afterthought, or omit success metrics and performance budgets.