skills.rest
beelabstudio
beelabstudioOFFICIAL
Explore all skills by this author →
GitHub

cto

Guides architecture decisions, ADR approval, and technology strategy for SaaS engineering teams.

Updated Mar 14, 2026
Search Tags:#adr#tech debt#architecture decisions#build vs buy#technology strategy#cto#engineering governance
One-click install
npx skills add https://github.com/beelabstudio/ai --skill cto-beelabstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cto
Source: https://github.com/beelabstudio/ai/tree/main/skills/c-level/cto
Command: npx skills add https://github.com/beelabstudio/ai --skill cto-beelabstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often lack a consistent framework for making high-stakes technology decisions, leading to uncontrolled tech debt, unreviewed architecture changes, and poor build-vs-buy choices. This Skill provides a Chief Technology Officer perspective that governs architecture decisions, stack evaluation, and engineering quality standards. ## Core Features & Use Cases - Architecture Governance: Reviews and approves Architecture Decision Records (ADRs) with a structured approval gate covering problem, alternatives, consequences, and stakeholders. - Decision Frameworks: Applies a build vs. buy matrix and explicit tech debt rules defining when shortcuts are acceptable and when they are never acceptable (security, multi-tenant isolation, billing paths). - Skill Orchestration: Routes specialist questions to the right domain skills such as software-architect, devops-engineer, dba, or qa-engineer based on context. - Use Case: When deciding whether to build an in-house feature flag system or adopt a vendor solution, the Skill produces a structured technical decision document with options compared, a recommendation, ADR requirements, and tech debt risk assessment. ## Quick Start Ask the CTO skill to evaluate whether we should build or buy a feature flag system for our multi-tenant SaaS platform and produce an ADR-ready recommendation.

Frequently Asked Questions about cto

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

FAQPage Schema
How do I decide between building or buying infrastructure components?▼

Use the build vs. buy matrix: build only when the component is a core differentiator or required for regulatory data residency. Buy or use OSS for commodity infrastructure, and evaluate vendor lock-in exit strategy before committing.

What should an Architecture Decision Record include?▼

Every ADR must answer four questions: what problem it solves, what alternatives were considered, what the positive and negative consequences are, and who is affected and who approved. No significant architectural change should ship without a merged ADR.

When is technical debt acceptable in a SaaS product?▼

Tech debt is acceptable when the feature sits behind a feature flag, refactoring is scheduled within two sprints and documented in the PR, and it avoids billing, auth, and GDPR-sensitive data paths. It is never acceptable when it creates security vulnerabilities or breaks multi-tenant isolation.

Does this skill write code or implementation details?▼

No, the CTO skill operates at the decision and governance level, not implementation. It delegates coding, CI/CD, database, and testing work to specialist skills like software-engineer, devops-engineer, dba, and qa-engineer.

How does the skill handle security and compliance decisions?▼

It owns the technical implementation of GDPR requirements, approves security-impacting changes such as auth flows and data access patterns, and coordinates with the CISO skill on risk posture. Security vulnerabilities always block tech debt acceptance.

Related Skills

Explore More Software Engineering Skills→
EpiphyticEpiphytic
7

roadmap-management

Plan and prioritize product roadmaps using RICE, MoSCoW, and ICE frameworks.

Official
Intermediate
clonable-edenclonable-eden
15

unix-architect

Review proposals and PRs against UNIX principles to generate Architecture Decision Records.

Community
Advanced
normcrandallnormcrandall
1

Quality Assurance

Validates implemented software stories with tests, code review, and quality gate assessment.

Community
Basic
jstoobzjstoobz
2

feature-orchestrator

Orchestrate Jira ticket delivery by planning, delegating to agents, and supervising checkpoints.

Community
Advanced