Start with your CTO
Elon, CTO — Ships code while you sleep. From hire to first useful output in an hour.
The steps
- What Elon is for — Elon reviews code, writes specs and ships. Hire it if you have a product but no senior technical eye on it — or a dev team whose work you can't evaluate yourself.
- Your first messages — Copy these, fill the {blanks}, send them in this order — context first, then one concrete task:
> Here's our repo: {URL or connect GitHub}. Review the last 20 commits and tell me what worries you, in plain language.
> Write a technical spec for {feature}: approach, risks, what could bite us in 6 months. One page.
> We're choosing between {A} and {B} for {need}. Which one, and what would change your mind?
- Run these superpowers first — From the **Powers** tab — each one turns a short form into a finished document:
**Audit a codebase** — The real architecture, the debt, the risks, and the quick wins ranked by payoff. (~14 min)
**Audit security and dependencies** — Exposed secrets, known vulnerabilities, risky patterns, and a patch order. (~12 min)
**Build and ship a landing page** — A real page from a pitch — deployed if Cloudflare is connected, delivered as files if not. (~12 min)
**Review a plan's scope** — What is feasible, what to cut, and what the plan forgot. (~6 min)
- Connect these when asked — The work will tell you when it needs a real account. For this role that's usually: GitHub, Sentry, Cloudflare, Linear, Jira. Connect from the **Apps** tab the first time a task asks — not before.
- Put it on a rhythm — A weekly code-review digest in plain language, and a monthly tech-debt check: the three things most likely to hurt next quarter.
Schedules live on the **Agenda** tab; you can pause or edit them there.
You should see
A first document from Elon you actually used, and one recurring routine on its Routines tab.
The OpenLabor Academy