The brief your AI coding tool actually needs. Answer a few questions about what you want built, and get a spec clear enough that Claude, Cursor, Manus or Lovable can follow it without guessing.
Try: "Job requests come in by email and someone retypes them into a spreadsheet" or "I want to stop writing quotes by hand"
Most specs are written for people to read. This one is structured so an AI coding tool can follow it without filling the gaps with guesses.
AI builds rarely stall on code. They stall because nobody wrote down what a right answer is. This asks you that before anything else.
Bad data, edge cases, the thing nobody thought about, and who looks after it in month six. The parts a demo never shows you.
Describe what you want built, or the process that's eating your week. Plain words are fine.
They get specific on purpose. The awkward ones are the ones that stop your build going sideways later.
Sent to your email, ready to paste straight into Claude, Cursor, Manus or whatever you build with.
Get a spec your AI tool can actually follow.