cto-advisor
Guide CTO Engineering Strategy
Engineering leaders need consistent ways to assess debt, scale teams, and choose technologies. This skill provides CTO-ready frameworks, calculators, templates, and metrics guidance for structured technical leadership decisions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "cto-advisor" from https://skillstore.io/skills/alirezarezvani-cto-advisor.md and its manifest at https://skillstore.io/api/skills/alirezarezvani-cto-advisor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "cto-advisor". Assess technical debt for a legacy commerce platform with weak tests and manual deployments.
Expected outcome:
- Overall debt level: medium-high, with security and infrastructure as top risks.
- Recommended focus: CI/CD automation, vulnerability scanning, and test coverage gates.
- Suggested capacity: dedicate 25 percent of sprint capacity for two quarters.
Using "cto-advisor". Plan growth from 25 to 75 engineers over four quarters.
Expected outcome:
- Hiring should emphasize engineering managers, tech leads, senior engineers, and DevOps capacity first.
- Main risks are onboarding load, communication overhead, and culture dilution.
- A phased structure with platform, product, infrastructure, and data teams is recommended.
Using "cto-advisor". Create an ADR for choosing Kubernetes over ECS and Nomad.
Expected outcome:
- Decision context: microservices need automated deployment, scaling, and high availability.
- Chosen option: Kubernetes, because of ecosystem maturity and multi-cloud portability.
- Consequences: higher operational complexity, mitigated through managed Kubernetes and training.
Security Audit
SafeAll static findings were adjudicated as false positives caused by Markdown fences, local file references, and leadership terminology. Reviewed scripts perform local calculations and report formatting; no subprocess, network, credential access, or prompt injection evidence was found.
Risk Factors
โ๏ธ External commands (19)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/alirezarezvani-cto-advisor/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/alirezarezvani-cto-advisor?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/alirezarezvani-cto-advisor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alirezarezvani-cto-advisor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/alirezarezvani-cto-advisor.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
alirezarezvani. (2026). cto-advisor security audit report (audit version 6) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/alirezarezvani-cto-advisor/audits/6BibTeX citation
@techreport{alirezarezvani-alirezarezvani-cto-advisor-2026,
author = {alirezarezvani},
title = {cto-advisor security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/alirezarezvani-cto-advisor/audits/6},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cto-advisor security audit report (audit version 6)"
version: "1.0.0"
type: report
authors:
- name: "alirezarezvani"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/alirezarezvani-cto-advisor/audits/6"
identifiers:
- type: other
value: "skillstore:alirezarezvani-cto-advisor:audit:6"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
davila7-cto-advisor
2026-08-21
alirezarezvani-cto-advisor
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan Engineering Growth
Create a hiring sequence, role mix, budget estimate, and team structure for a scaling engineering organization.
Build Metrics Governance
Select DORA, quality, delivery, and team health metrics with safeguards against metric gaming.
Document Architecture Choices
Use ADR templates to compare options, record trade-offs, and communicate decisions to stakeholders.
Try These Prompts
Assess our main application for technical debt. Ask me for architecture, code quality, infrastructure, security, and performance details before recommending priorities.
Create a team scaling plan from our current engineering team to our target headcount. Include role gaps, quarterly hiring, budget risks, and onboarding constraints.
Help me evaluate three technology options for a critical platform decision. Score technical, business, and operational criteria, then summarize trade-offs.
Prepare a CTO operating review covering technical debt, engineering metrics, architecture decisions, hiring risks, vendor strategy, and next-quarter priorities.
Best Practices
- Provide current metrics, team size, business goals, and constraints before asking for recommendations.
- Use the calculators as planning aids, then validate assumptions with finance, HR, and engineering leads.
- Pair every architecture or vendor recommendation with an ADR and a measurable success metric.
Avoid
- Do not use generic salary, velocity, or team ratio assumptions as final operating plans.
- Do not optimize one metric without checking quality, reliability, and team health impacts.
- Do not treat framework output as a substitute for stakeholder alignment and risk review.
Frequently Asked Questions
What does this skill help with?
Can it run calculations?
Does it connect to live engineering tools?
Who should use it?
Can it choose a vendor for me?
Does it work with Claude, Codex, and Claude Code?
Developer Details
Author
alirezarezvaniLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
c1fdca50ff516318f65fed0d7f9e82797c5171dc
Maintenance freshness
7/18/2026
Usage
8 downloads ยท 198 views
File structure
๐ references/
๐ architecture_decision_records.md
๐ technology_evaluation_framework.md
๐ scripts/
๐ team_scaling_calculator.py
๐ SKILL.md