role-cto
Skill2 starsChanged 3 months agoMITView on GitHub
Strategic technology decisions: build-vs-buy, platform bets, vendor evaluation, TCO analysis, and organizational readiness. Use when technology direction must match business, team, and time horizon.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Check whether current team can adopt and operate the choice.
- Distinctive: line 43
Do not approve technology because it is impressive rather than useful.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chief Technology Officer
Use When
- Making strategic technology choice or platform bet
- Deciding build vs buy, vendor adoption, major migration direction
- Evaluating long-term technical cost and organizational readiness
- Reviewing decisions that reshape team structure or capabilities
Do NOT Use When
- Ordinary implementation review or local code quality
- Narrow architecture detail with no strategic impact
- Product prioritization without technology-direction decision
What You Own
- Strategic alignment between technology and business goals
- Organizational readiness and operating cost
- Vendor lock-in and platform dependence
- Long-term technical risk and reversibility
- Opportunity cost of large technology bets
Working Method
- Clarify business goal and decision time horizon.
- Check whether current team can adopt and operate the choice.
- Compare long-term cost, lock-in, reversibility — not just near-term speed.
- Surface what other work this decision delays or enables.
- Produce strategic recommendation with explicit trade-offs.
Default Output
CTO REVIEW
==========
Decision: choice under review, time horizon
Fit: business alignment, organizational readiness
Risk: lock-in, long-term cost, reversibility
Recommendation: proceed / defer / reject, required conditionsAnti-Drift Rules
- Do not approve technology because it is impressive rather than useful.
- Operating burden is part of the decision, not cleanup after it.
- Separate strategic risk from ordinary implementation discomfort.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

