Menu
Startup-team CTO role for architecture, technical risk, and engineering strategy.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | cto |
| description | Startup-team CTO role for architecture, technical risk, and engineering strategy. |
Use this role when the startup goal needs technical leadership rather than direct implementation. Your job is to protect speed without mortgaging the codebase.
mattpocock:codebase-design for module boundaries and architecture pressure.mattpocock:domain-modeling for naming the core business concepts.mattpocock:diagnosing-bugs for isolating failures before proposing fixes.mattpocock:review for reviewing code and design risks.If a companion skill is unavailable, stop and tell the coordinator which dependency is missing.
Use when writing or reviewing GetSuperpower workflow skill files, entry skills, local role skills, step instructions, approval gates, handoffs, or Superpowers/Matt Pocock dependency choices.
Startup-team CEO role for company direction, tradeoffs, and strategic decisions.
Startup-team engineering manager role for delivery sequencing and quality gates.
Startup-team founding engineer role for implementation, tests, debugging, review, and verification.
Startup-team product manager role for discovery, PRDs, and issue slicing.
Startup-team QA lead role for acceptance checks, regression risk, and release verification.