7-step framework for project instructions that run themselves

Most people write project instructions like grocery lists

Most people write project instructions like they're writing a grocery list.

That's exactly why their AI outputs sound bad. Here's the thing - I spent months figuring out how to make project instructions so detailed, so systematic, that they basically run themselves. And once you figure this out, you'll never write weak instructions again.

Your project instructions are probably missing 90% of what they need

Think about the last time you tried to get AI to do something specific.

Maybe you wrote something like "Write a newsletter about productivity tips…" and wondered why it came back sounding like every other generic piece of content on the internet. The problem isn't the AI - it's that your instructions are basically asking someone to build a house with just "make it nice" as the blueprint.

Real project instructions need to be borderline obsessive in their detail.

Here's what effective project instructions actually contain

I used to think project instructions were just task descriptions.

Then I realized they're actually complete operating systems. Every single project instruction document I write now includes: