agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-cto/SKILL.md

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.

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
  1. Distinctive:

    Check whether current team can adopt and operate the choice.

    line 27
  2. Distinctive:

    Do not approve technology because it is impressive rather than useful.

    line 43

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Clarify business goal and decision time horizon.
  2. Check whether current team can adopt and operate the choice.
  3. Compare long-term cost, lock-in, reversibility — not just near-term speed.
  4. Surface what other work this decision delays or enables.
  5. 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 conditions

Anti-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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.