Menú
Use when acting as a startup CTO for architecture, technical risk, platform direction, codebase boundaries, or engineering strategy.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.
Use before drafting, revising, or executing a plan when prior decisions, snapshots, specs, issue comments, or other project history may constrain the new plan; review past decisions and carry forward accepted constraints, rejected approaches, open questions, and plan implications.
Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.
Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.
Use when demonstrating recursive Omniskills workflow dependencies.
Use when coordinating a startup goal across CEO, CTO, product manager, engineering manager, founding engineer, and QA lead role subagents.
| 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:code-review for reviewing code and design risks.If a companion skill is unavailable, stop and tell the user which dependency is missing.