Set up the project brief before generating an ebook
Define topic, audience, pain points, desired outcomes, title direction, and author context before Scribora plans the book.
The brief tells Scribora what the sources are for
The same set of notes can support very different books. A technical handbook for practitioners should not be organised like an executive introduction. The project brief supplies the intended reader and outcome that raw source material cannot infer reliably on its own.
- Topic: the actual domain and boundary of the book.
- Target audience: who should recognise themselves as the reader.
- Pain points: what currently costs that reader time, money, confidence, or progress.
- Desired outcomes: what should be different after they finish the book.
Be specific without writing the outline
Describe the promise and reader; let the Plan phase decide chapter structure from the source evidence. If the brief already dictates ten generic chapter titles, it can anchor the system to a structure that the material does not justify.
Ready to use the workflow?
Start with a real source set. Scribora is most useful when you already have material worth turning into a book.