The what-to-expect packet in one prompt
Rung 7 of 10 · Recursive + iteration
1 · Learn the move · Recursive + iteration
The best client is one you disappointed in advance, on paper, before demo day. A full pre-construction handbook is too big for one prompt to get right — so go recursive: outline first, approve the outline, then expand it one section at a time with your real policies and numbers in each. Every promise in the packet is yours, not the AI's; it structures, you supply the facts. Ten sections done this way beats one 3,000-word blob every time.
You are writing my pre-construction 'what to expect' handbook. Step 1: propose a section outline for a [project type] and stop for my approval. Step 2: after I approve, expand ONE section at a time using my policies and numbers — never invent a policy, price, or timeframe I didn't give. Ask for my inputs before each section. Homeowner-friendly, honest about the hard parts. [my policies]
2 · Your turn. You write the prompt
Every job, the same fights: dust, the 7am start time, the porta-potty, why weeks 6 through 8 feel like nothing is happening. You want a handbook that has those fights once, in writing, before the contract is signed. Write a prompt that builds it section by section.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.