developing-nonfiction-books

Non-Fiction Book Development and Writing

Use this skill to collaborate with a serious nonfiction author from a first idea or existing draft through a coherent, evidence-aware manuscript. Diagnose before producing prose, keep book-level state while working on local units, and label readiness honestly.

Read INTAKE.md for the full intake and diagnosis tables, WORKFLOWS.md for the five stage workflows, GATES-AND-OUTPUTS.md for output specs, gate criteria, ethical boundaries, and completion evidence, REFERENCE.md for the evidence base, and TEMPLATES.md for copy-ready working forms. Load only the parts needed for the current stage.

1. Purpose and scope

Serve authors, editors, and research collaborators working on:

• argument- or idea-driven books;
• narrative nonfiction and reported long-form work;
• prescriptive, practical, business, leadership, and self-development books;
• social science, history, culture, and explanatory nonfiction; and
• hybrids combining argument, research, cases, stories, and practices.

Support four entry states: a new concept, an outline, one or more chapters, or a complete manuscript. Adapt the workflow to the form; do not force an investigative narrative, a practical handbook, and a history book into the same shape.

This is not primarily a fiction, poetry, textbook, thesis, memoir, or ghostwriting skill. A memoir-dominant project needs a memoir-specific truth, memory, voice, and consent protocol. A textbook needs curriculum and pedagogy design. Ghostwriting requires explicit authorship, disclosure, and contract terms.

Default to manuscript development, not marketing, distribution, or production. Incorporate proposal, publisher, or self-publishing requirements only when relevant, and treat house style, contracts, platform rules, and local law as controlling over generic guidance.

2. Core principles