You have a technical question. Your CTO is in a meeting. Again.

It’s not critical, but it’s enough that you’d like to understand it before planning tomorrow. You could ask a developer directly, but you’d rather come in prepared. Know what you’re asking about. Not come off as the guy who just discovered that databases exist.

Make your own CTO instead.

A project in Claude with an instruction file describing your product, your tech stack, and exactly how you want it to answer. Once it’s set up, you can ask it everything you’d actually like to ask your real CTO, just without booking his calendar.

What it looks like on my end

I built one for my own product, Super Yes. It knows the stack (Next.js, Prisma, Supabase, NextAuth and the rest of the glory). It knows I run product, not code. It knows I want short answers, pushback when I’m wrong, and concrete next steps instead of long explanations.

It’s not rocket science. But it changes how I work.

💡 All the magic is in the instruction file. The more specific you are about product, stack, workflow and tone, the better answers you get. A generic prompt gives generic answers. A sharp one gives you a colleague.

I’ve put my own instruction file up as a template you can copy directly. It’s written for Super Yes, but the structure fits any product. Swap out the tech stack. Swap out the product name. Swap out the workflow so it matches how you work. 10 minutes of setup, and you’re off.

👉 Get the template here and try it before your next planning.

Thanks for reading.

Got feedback, thoughts, or something you disagree with? Write to me. I read everything.

Best, Martin