cto

Govern architecture decisions and engineering standards with decision criteria and documentation.

105|16|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jordanhubbard/loom --skill cto-jordanhubbard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cto
Source: https://github.com/jordanhubbard/loom/tree/main/personas/default/cto
Command: npx skills add https://github.com/jordanhubbard/loom --skill cto-jordanhubbard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline CTO-level architecture decisions and engineering standards.

Core Features & Use Cases

  • Architecture decision governance: define decision criteria, trade-offs, and documentation.
  • Technical triage & escalation: prioritize and resolve complex engineering problems.
  • Engineering standards: set, enforce, and evolve coding guidelines and design patterns.

Quick Start

Provide your project context and governance goals to initialize the CTO-level architecture review.

Frequently Asked Questions about cto

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

FAQPage Schema
How do I streamline architecture decisions and engineering standards across multiple projects?

Streamlining architecture decisions involves enforcing decision criteria, documenting trade-offs, and maintaining versioned guidelines to ensure consistent, scalable outcomes across projects. This approach guides design, technology selection, and governance.

What is architecture decision governance and how does it work?

Architecture decision governance is the process of defining decision criteria, evaluating trade-offs, and producing documentation for technology selection. It enforces consistent evaluation standards across projects to guide scalable design and engineering outcomes.

How do I set and enforce coding guidelines and design patterns for engineering teams?

Setting and enforcing coding guidelines requires establishing versioned engineering standards that define design patterns and criteria. These standards are evolved over time and applied across projects to ensure consistent, scalable technical implementation and governance.

What is the best way to prioritize and resolve complex engineering problems during technical triage?

Technical triage prioritizes and resolves complex engineering problems by applying structured decision criteria and governance frameworks. This approach uses enforced escalation paths and documentation to guide consistent resolution across projects and engineering teams.

Can I use this approach for engineering management and product leadership, or is it only for senior architects?

This approach applies to product leadership, engineering managers, and senior architects alike. It guides design, technology selection, and governance across projects, ensuring consistent and scalable outcomes regardless of your specific leadership role.

Why do I need versioned guidelines for engineering standards and architecture decisions?

Versioned guidelines are needed to evolve engineering standards and architecture decisions over time while maintaining consistency. They ensure that decision criteria, documentation, and coding guidelines remain scalable and enforceable across changing project contexts.