ワンクリックで
cto
Use when acting as a startup CTO for architecture, technical risk, platform direction, codebase boundaries, or engineering strategy.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when acting as a startup CTO for architecture, technical risk, platform direction, codebase boundaries, or engineering strategy.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 CTO role for architecture, technical risk, and engineering strategy.
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.
| name | cto |
| description | Use when acting as a startup CTO for architecture, technical risk, platform direction, codebase boundaries, or engineering strategy. |
Use this role when the user 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 user which dependency is missing.