Interactive eBook BuilderInteractive eBook Builder
$59 · unlimited access, unlimited eBooksGet it for $59

· By · 10 min read

Prompt Engineering Frameworks Explained

promptsaiwritingebook

A prompt engineering framework is a checklist of parts to include in a brief—such as role, task, context, examples, constraints and output format—so you do not forget a decision the model would otherwise guess. You do not need a trademarked acronym to do this well. OpenAI’s prompt engineering guide already organizes a developer message into identity, instructions, examples and context. Anthropic’s prompting best practices group the work into clear instructions, useful context, examples, XML structure, a role, and careful handling of long documents. Google’s prompt design strategies walk through clear instructions, constraints, response format, zero-shot versus few-shot examples, added context, and breaking complex work into components.

For eBook and workbook projects, Interactive eBook Builder is a $59 one-time Notion AI template with Spec Builder, Drafter, Polisher and SEO BOT already set up, so those parts can live in a working book workflow instead of in a checklist you rebuild for every chat. Notion AI access and usage are separate from the purchase. The examples below are teaching prompts written for this article, not paid Builder prompts and not recorded model outputs.

Start with the official structures

If you want a framework with a clear source, start here. These are not complete copies of the vendor pages; they are the parts that transfer cleanly to writing a book.

OpenAI’s four-part developer message:

Anthropic’s practical set:

Google’s design set:

Any of those three will carry an eBook chapter if you fill them in with real decisions. A framework fails when you treat the headings as decoration and leave the parts vague.

What about RTF, CO-STAR, CRISPE and RISEN?

Writers and course materials often teach short mnemonic checklists. They can be handy. They are not official methods from OpenAI, Anthropic or Google, and they are not the subject of the papers cited elsewhere in this series. Use them as memory aids. Do not attribute them to those labs, and do not assume a finished acronym produces a better book.

Here is a cautious reading of four common ones, described as checklists rather than as proven systems:

ChecklistParts people usually includeUseful forEasy to misuse
RTFRole, Task, FormatA short request when you already have the notes elsewhereLeaving out source material and limits
CO-STARContext, Objective, Style, Tone, Audience, ResponseMatching voice and audience on a pageFilling Style and Tone with adjectives and skipping notes
CRISPECapacity/role, Insight, Statement, Personality, ExperimentExploring tone while you iterateTreating “Experiment” as a substitute for a testable requirement
RISENRole, Instructions, Steps, End goal, NarrowingMulti-step planning or exercisesWriting steps the model does not need, or narrowing after the fact

If a checklist helps you remember a missing part, keep it. If you are only renaming “write a good chapter” as an Objective or an End goal, it is not doing any work. Notice, too, that all four overlap with the official structures: a role, a task, some context, a format, and often a constraint. You are not choosing a different science of prompting. You are choosing a reminder.

A worked eBook example, filled two ways

Suppose you are writing a short eBook for new freelance designers, and you need a chapter section on stating a revision limit in the kickoff email.

Filled as OpenAI-style identity, instructions, examples and context:

Identity
You are helping the author of a short, practical eBook for new freelance
designers. Use plain, calm language.

Instructions
- Stay inside the supplied notes.
- If a number or rule is missing, write "Need from me" instead of inventing it.
- Do not add legal or income claims.
- Return a 250 to 350-word teaching section, then a one-line email sentence
  with a blank for the revision limit.

Context
- The reader says yes to extra revisions because they are afraid of seeming
  difficult.
- No default number of revisions has been chosen.

Request
Draft the teaching section and the email sentence.

Filled as CO-STAR, for comparison:

Context: A short eBook for new freelance designers. This section sits in
the chapter on revision limits. The reader says yes to extra work because
they are afraid of seeming difficult. No default number has been chosen.

Objective: Help the reader put a revision limit in the kickoff email.

Style: Plain teaching prose, then one reusable sentence.

Tone: Calm and practical, not inspirational.

Audience: First-time freelance designers reading in short sessions.

Response: 250 to 350 words, then one email sentence with a blank for the
number. Stay inside the notes. Flag missing facts as "Need from me."

Both briefs can be good if the notes and the output test are present. The second one spends more words on style and tone, which helps only if those words are specific. “Not inspirational” is more useful than “engaging.” “A blank for the number” is more useful than “a professional email.” If you dropped the notes from either version, the framework would not save the prompt.

How to choose a framework without collecting them

Use this rule: pick the smallest checklist that would have prevented your last miss.

Then stop adding frameworks. A second mnemonic on top of a working brief is how cargo-cult prompting starts: the headings are complete, the decisions are not, and the result is still generic. Our article on prompt engineering mistakes to avoid covers that failure in more detail.

When a brief is stable, turn it into a reusable prompt template rather than memorizing a new acronym for each chapter.

How this shows up in a book-building system

Spec Builder, Drafter and Polisher are, in effect, a framework split across stages: plan the work, draft from the plan, then refine it against the same rules. The value is not the labels. The value is that each stage has a job, a place for notes, and an output you can inspect. SEO BOT can later publish supporting articles to the Auto-Blogger blog, each linking back to your eBook, site and brand, which is also a structured job rather than a one-off “write some SEO.” You can keep the supplied, editable setup or adapt the audience, voice and activities. Review still belongs to you.

If you are doing this in a chat tool, you can copy one official structure into a standing brief and ignore the rest until a real miss tells you which part to add.

What a framework cannot do

A framework will not choose your reader, invent notes you did not supply, or tell you whether a chapter is true. It will not settle a disagreement between vendor guides, such as whether to include examples by default. And it will not make a vague line more precise just because you placed it under a heading called Objective or End goal.

The honest use is narrower: when you sit down to write a brief, the framework asks you a set of questions you have already decided matter. If you cannot fill a part, either go find the missing decision or drop the part. Empty headings are how a checklist becomes a costume for the same vague prompt you started with.

If you are writing an eBook about your own subject, the framework belongs in your working notes. The reader’s chapter should still start with the answer they came for, not with an explanation of RTF or CO-STAR.

FAQ

Which prompt engineering framework is best?

There is no official winner. The official vendor structures are the ones you can cite and test. The mnemonic checklists are optional reminders. The best framework is the one that makes you include the parts your last draft was missing, and that still leaves you a result you can inspect.

Do I need to use the same framework in ChatGPT, Claude and Gemini?

No. You can keep one brief and adjust only what a vendor’s current documentation tells you to adjust, such as where to put long context or whether to include examples by default. The parts—reader, job, notes, format, limits—travel. The acronyms do not have to.

Can a framework replace examples?

No. If the miss is about shape or voice, you still need a sample, as the few-shot guidance from OpenAI, Anthropic and Google describes. A heading called “Response” or “Format” is not the same thing as an example of the page you want.

Should I publish a framework as part of my eBook?

Only if the book is actually about prompting, and only if you describe the checklist honestly—as a memory aid or as a vendor structure, not as a proven method it is not. For other niches, the framework should stay in your working notes, not in the reader’s chapter.

Before you hit send

Ship niche eBooks with agents already built.

Get the Interactive eBook Builder for $59