Why I built Mastery Engine

Mastery Engine is a free tool that builds a study prompt for any topic. You name the subject, pick a depth, and it writes a prompt that maps how the thing works: the main parts, what each part does, how they connect, where people usually go wrong, and a plan to practice. I built it for one reason. I wanted a better way to understand a subject well enough to use it, fix it, or teach it.

A summary is not the same as understanding

When you ask for help learning something, you usually get a summary. A summary is fine if you only need to know what a thing is. It falls apart the moment you need to fix a zipper or read a commercial lease before you sign it. For that you need the parts and how they affect each other.

So the engine is built on a rule I care about more than any other: a list of parts is not mechanics. The interactions are the mechanics.

The removal test

Every major part of a topic gets the same check. Remove it, weaken it, double it, and ask what exactly fails. If you can't say what breaks when a part is gone, you know its name but not its job. That test is written into every prompt the engine builds.

Pick how deep you want to go

Not every topic needs the same effort, so you choose the depth. Scout covers four phases and is meant for a quick look before you decide whether to go further. Immersion covers seven phases for working knowledge. Obsession and Mastery Sprint run all twelve.

The full run starts with what knowing the subject well actually looks like. Then it maps the whole field, including what is settled and what people still argue about. It works through the first principles and the parts, looks at how experienced people really work, and studies how things fail. It ends with a practice plan and a reading list ranked by payoff.

Partial work gets called partial

I wanted the engine to be honest about unfinished work. If a phase comes back incomplete, the result is labelled partial and the missing phase is named. You can send it back to finish that phase instead of accepting a short answer as if it were the whole thing.

Reading is not the finish line

The run ends with drills, a project, and a self-test you can honestly fail. The goal is to know you are getting better through signals you can't fake by reading more. Understanding shows up when you can predict how something will behave in a situation nobody covered, or work out what went wrong from the symptoms alone.

Who it's for

It's for people who need to use what they learn. Maybe you have to maintain something you didn't build, like a furnace or a codebase you inherited. Maybe you're starting a new job or a new field and want the core ideas and the real debates, not just the vocabulary. Or maybe you would simply rather practice than read another overview.

How to use it

Go to mastery.stevepeeleii.com and name your topic. Be specific. "How a heat pump works in cold weather" will get you much further than "heat pumps." Add why you're learning it if you can. Pick a depth, then copy the prompt or download it as a .md file and paste it into Muse or the assistant you already use. The prompt is put together right in your browser. It's free, and copying it asks for your email once.

I built Mastery Engine for the moment when a summary isn't enough. If you have a topic like that, give it a try.

Try Mastery Engine at mastery.stevepeeleii.com