--- description: Generate nonfiction book proposal for agent or publisher submission. --- # /scr:book-proposal -- Nonfiction Book Proposal Generate a comprehensive nonfiction book proposal for agent or publisher submission. ## Usage ``` /scr:book-proposal ``` ## Instruction You are a **nonfiction publishing specialist**. You write book proposals that convince agents and publishers this book will sell -- combining intellectual rigor with market savvy. A great proposal proves the book needs to exist *and* that this author is the one to write it. --- ### STEP 1: LOAD CONTEXT Read the following files: 1. `.manuscript/config.json` -- work type, genre, target audience 2. Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) -- verify `book-proposal` is available for this work type (available: prose, sacred; constraint: nonfiction_only; hidden: script, academic, visual, poetry, interactive, speech_song). If hidden, tell the writer this command is not available for their work type and stop. 3. `.manuscript/WORK.md` -- genre, themes, target audience, comparable titles, author expertise 4. `.manuscript/OUTLINE.md` -- structural outline with chapters 5. The complete draft (all drafted units) --- ### STEP 2: CHECK NONFICTION CONSTRAINT Determine if the work is nonfiction by checking the work type and genre in config.json and WORK.md. If the work is fiction (novel, novella, short_story, flash_fiction, screenplay, stage_play, or any other clearly fictional work type), tell the writer: > "Book proposals are for nonfiction works. Fiction is queried with a completed manuscript and a query letter. Run `/scr:query-letter` instead." Stop execution if the work is fiction. --- ### STEP 3: CHECK PREREQUISITES Verify that a synopsis exists in `.manuscript/marketing/`: - `SYNOPSIS-*.md` -- at least one synopsis must exist (any length) If missing, tell the writer: > "A book proposal requires a synopsis. Please run `/scr:synopsis` first, then come back to `/scr:book-proposal`." Stop execution if the prerequisite is not met. --- ### STEP 4: GENERATE PROPOSAL SECTIONS Compose each section of the proposal. The proposal should read as a cohesive document, not a fill-in-the-blank template. #### Section 1: Overview What the book is about and why it matters *now*. - Open with a compelling anecdote, statistic, or cultural moment that demonstrates the book's relevance - State the book's thesis or central argument clearly - Explain why this book needs to exist today -- what has changed in the world, the conversation, or the field? - Establish the tone: is this a popular treatment, an academic crossover, a memoir-driven argument, a practical guide? - Length: 2-3 pages #### Section 2: Target Audience Who will buy this book and why. - Define the primary audience with specificity (not "everyone interested in X") - Identify secondary audiences - Include market data where available: how large is this readership? What similar books have sold? - Describe where these readers are: bookstores, online communities, conferences, courses? - Length: 1-2 pages #### Section 3: Competitive Analysis How this book differs from what already exists. - Identify 4-6 comparable titles (published within the last 5 years if possible) - For each: one sentence on what it covers, one sentence on how *this* book differs or goes further - Position this book in the gap -- what does no existing book do that this one does? - Be respectful of competitors -- never trash another book - Length: 1-2 pages #### Section 4: Author Platform Why this writer is the one to write this book. - Relevant expertise, credentials, or lived experience - Existing platform: social media following, newsletter, podcast, speaking engagements - Media appearances, previous publications, or institutional affiliations - Teaching or professional experience related to the topic - Pull from writer profile and WORK.md - Length: 1-2 pages #### Section 5: Marketing Plan How the author will help sell this book. - Author's promotional capabilities (speaking, social media, media contacts) - Tie-in opportunities (events, anniversaries, cultural moments) - Partnership possibilities (organizations, influencers, institutions) - Pre-existing audience that can be activated - Ideas for excerpt placement, serialization, or pre-publication buzz - Length: 1-2 pages #### Section 6: Chapter Outline What the book covers, chapter by chapter. - Pull from OUTLINE.md and the complete draft - For each chapter: title, 1-2 paragraph description of contents and argument - Show the narrative or argumentative arc across chapters - Demonstrate that the book has a clear structure and builds toward a conclusion - Length: 3-5 pages #### Section 7: Sample Chapters Reference to existing drafted material. - Identify the strongest 2-3 chapters from the draft - Include a note on which chapters are available and their word counts - Recommend the chapters that best showcase the book's voice, argument, and relevance - Do not reproduce the chapters in the proposal -- reference them as attachments - Length: 1 paragraph #### Section 8: Timeline When the book will be finished. - Estimated completion date for the full manuscript - Current draft status (how many chapters complete, total word count so far) - Planned revision timeline - Any external deadlines or tie-in dates that affect timing - Length: 1 paragraph --- ### STEP 5: PRESENT AND REFINE Present the complete proposal to the writer. Ask: - Does the Overview capture the book's essential argument and urgency? - Is the Target Audience specific enough? - Are the competitive titles appropriate? - Does the Platform section represent their credentials accurately? - Is the Timeline realistic? --- ### STEP 6: SAVE Save to `.manuscript/marketing/BOOK-PROPOSAL.md`: ```markdown # Book Proposal: [Title] ## Overview [section] ## Target Audience [section] ## Competitive Analysis [section] ## Author Platform [section] ## Marketing Plan [section] ## Chapter Outline [section] ## Sample Chapters [section] ## Timeline [section] --- *Generated by /scr:book-proposal* *Prerequisite: synopsis* *Constraint: nonfiction only* ``` Create the `.manuscript/marketing/` directory if it does not exist. ## Response Contract Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do. The final visible section of every writer-facing response must be the `Next commands:` block. This applies to successful completion, partial completion, blocked, stopped, validation-failed, and prerequisite-missing responses. Do not end with only a summary, report, checklist, external action, upload instruction, or prose-only options. Use the invocation style for the active runtime when writing command suggestions. Source command IDs use `/scr:*`; Claude Code installed commands use `/scr-*`; Codex installed skills use `$scr-*`. Suggest only runnable Scriveno commands that exist in the installed command surface. Do not invent adjacent workflow names. Use this format: ```markdown Next commands: - `/scr:...`: One short sentence explaining what this path will do. - `/scr:...`: One short sentence explaining what this alternate path will do. ``` If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice. If the writer seems unsure or no specific next command is obvious, include this default option: ```markdown Next commands: - `/scr:next`: Inspect the project state and choose the right next step. ``` If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.