To turn an outline into a draft, prompt one section at a time with a fixed layout: context and notes first, your voice and rules next, and the specific request last, including a word budget and the source material to use. A whole-book request gives you a whole-book mess to untangle.
Below is the layout, the reasons behind its order, a word-budget table for a 30,000 to 50,000-word book, a copy-ready template and a worked example.
What order should the parts of the prompt go in?
Reference material first, rules in the middle, request last. Anthropic's prompting guide advises putting long documents and inputs near the top, above the query and instructions, and reports that placing the query at the end "can improve response quality by up to 30 percent in tests, especially with complex, multidocument inputs". There's independent research behind the caution too: in "Lost in the Middle" (Liu et al., 2023), performance was often highest when relevant information sat at the beginning or end of the input and degraded significantly when it was in the middle, even for models built for long contexts. Models change, so treat this as a default to test, not a law.
| Slot | Contents | Why it goes here |
|---|---|---|
| 1. Book context | Title, reader, promise, outline (short) | Orients the model |
| 2. Source notes | Facts, quotes, examples for this section only | Long material goes high |
| 3. Voice and format rules | 3-6 rules, plus an example if you have one | Applies to the whole task |
| 4. Request | Section name, job, word budget, what to leave out | Last thing the model reads |
Use clear labels or XML-style tags such as <outline> and <notes> so the model can tell your material from your instructions. For how much of this you actually need, see how long a prompt should be.
How do I set a word budget for each section?
Divide the book's target length by chapters, then by sections. This is arithmetic, not a rule about ideal length; pick the target that suits your topic.
| Book target | Chapters | Words per chapter | Sections per chapter | Words per section |
|---|---|---|---|---|
| 30,000 | 10 | 3,000 | 5 | 600 |
| 40,000 | 10 | 4,000 | 5 | 800 |
| 50,000 | 12 | about 4,170 | 5 | about 830 |
| 15,000 (short guide) | 8 | about 1,875 | 3 | about 625 |
Ask for "about 600 words" rather than "exactly 600"; assistants often miss precise counts, so check with a word counter and ask for a trim or expansion if the section is off. In my opinion, sections between 400 and 900 words are easiest to review in one sitting, and that's why the table lands there.
What does the prompt template look like?
Here it is, with slots in brackets.
<book>
Title: [title]
Reader: [who, what they already know]
Promise: [what they'll be able to do]
</book>
<outline>
[chapter titles, one line each; mark where this section sits]
</outline>
<notes>
[only the facts, examples and quotes for THIS section]
</notes>
Rules:
- Voice: [3-4 concrete traits]
- Start with a one-sentence answer, then explain
- Use only the facts in <notes>. If something is missing, write [DATA NEEDED: what]
- Don't repeat points covered in other sections: [list]
Write: Chapter [n], section "[name]". Job: [what this section must achieve]. About [600] words.
The "don't repeat" line matters more than it looks: when you draft sections separately, each call forgets the others, so overlaps creep in. Give a one-line list of what other sections cover. For voice, add a short sample as described in few-shot prompting for consistent chapters.
Worked example: from outline bullet to draft request
A single outline line becomes a complete request in under a minute. This is an example I wrote, not a transcript. Suppose the outline line is "Ch. 3: Pricing your first offer". You expand it:
| Outline line | Expanded request |
|---|---|
| Ch. 3 Pricing your first offer | Section 3.2 "Choosing a starting price". Job: help the reader choose a number and defend it. About 650 words. Use notes: three pricing methods I listed, one client story. Don't cover discounts (section 3.4). End with a five-minute exercise. |
If the request is ambiguous, you can have the assistant ask about it first; how to get AI to ask clarifying questions has wording for that. Draft, read, fix the request, and only then continue to the next section. The staged flow comes from a general technique called prompt chaining, covered in prompt chaining to plan, draft and edit a book.
This is the process that Interactive eBook Builder automates: Agent A Spec Builder writes the Chapter Plan, so the structure exists before anything is drafted, and Agent B Drafter then writes against it. Section Blueprints and Constraint Packs in the Packs Database store the "job" and the rules for a section, so you aren't re-pasting the same layout each time. If you'd rather prompt by hand, the template above does the same job manually.
How do I check a draft against the outline?
Compare the draft to the section's job, not to your gut feeling. A quick audit takes five minutes per section and catches the common failures before they spread:
| Check | How to do it | If it fails |
|---|---|---|
| Did it do the job? | Read the opening and closing paragraphs only; do they match the "job" line? | Rewrite the job line, then redraft |
| Length | Paste into a word counter; accept within roughly 15% of budget | Ask for a trim or an added example, not a full redo |
| Facts | Highlight each number and name; match to your notes | Remove or source it |
| Overlap | Search for key phrases from neighboring sections | Add them to the "don't repeat" list |
| Voice | Read one paragraph aloud | Add or swap an example |
The 15% tolerance is my rule of thumb, not an industry standard. Once the draft passes, a separate pass for clarity, pacing and layout is cleaner than trying to do everything in the first request. That separation is how Interactive eBook Builder divides the labor, with Agent C Polisher taking the finishing pass (clarity, voice, pacing, layout, interactivity, final QA) after the drafter is done.
What mistakes make outline-to-draft prompts fail?
Five issues cause most disappointing drafts.
- Too much at once. One prompt for five chapters yields shallow, repetitive text.
- No source notes. The model fills gaps with generic claims or invented specifics (see how to stop AI making up facts).
- Outline too thin. A three-word bullet gives the model nothing to work with; add the section's job.
- Rules buried in the middle of long pasted notes.
- No review gate. Errors in section 1 propagate if you accept it unread.
If a draft comes out wrong, change the request or notes, not just the wording of your complaint.
Before you hit send
- Does the prompt hold only this section's notes?
- Is the request the last thing in the prompt?
- Does the section have a job, a word budget and a list of what to avoid repeating?
- Have you told it what to do when facts are missing?
- Will you read the draft before moving on?
The takeaway: an outline is a map, not a prompt. Convert each line into a request with a job, a budget and sources, and draft one section at a time.