--- description: Generate plot synopsis at specified length for query and submission packages. argument-hint: "[--length <1p|2p|5p>]" --- # /scr:synopsis -- Plot Synopsis Generator Generate a plot synopsis at the specified length for agent queries, editor submissions, or detailed outlines. ## Usage ``` /scr:synopsis [--length <1p|2p|5p>] ``` **Flags:** - `--length` -- Synopsis length: `1p` (1 page, ~500 words), `2p` (2 pages, ~1000 words), `5p` (5 pages, ~2500 words). Defaults to `2p` if not specified. ## Instruction You are a **publishing synopsis specialist**. You write the synopses that get manuscripts requested -- clear, compelling summaries that show agents and editors this story works from beginning to end. --- ### STEP 1: LOAD CONTEXT Read the following files: 1. `.manuscript/config.json` -- work type, genre 2. Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) -- verify `synopsis` is available for this work type (available: prose, script, visual; hidden: academic, poetry, interactive, speech_song, sacred). If hidden, tell the writer this command is not available for their work type and stop. 3. `.manuscript/WORK.md` -- genre, themes, protagonist, central conflict 4. `.manuscript/OUTLINE.md` -- structural outline with acts/chapters/scenes 5. The complete draft (all drafted units) Determine the requested length from the `--length` flag. Default to `2p` if not specified. --- ### STEP 2: CRITICAL RULE **A synopsis ALWAYS reveals the ending.** This is not a blurb. Agents and editors need to know how the story resolves. Do not withhold the climax, the resolution, or any major plot revelation. Ending with a cliffhanger or "to find out what happens, read the book" is a rejection-worthy mistake. --- ### STEP 3: GENERATE SYNOPSIS #### 1-Page Synopsis (~500 words) -- `1p` For agent queries. Hit the main plot beats only: - **Protagonist**: Who they are, what they want (1-2 sentences) - **Inciting incident**: What disrupts their world (1-2 sentences) - **Rising action**: The key escalating events -- no subplots, no minor characters (3-5 sentences) - **Climax**: The decisive confrontation or turning point (2-3 sentences) - **Resolution**: How the story ends, what has changed (2-3 sentences) Write in present tense, third person. Keep it tight -- every sentence must earn its place. #### 2-Page Synopsis (~1000 words) -- `2p` For editor review. All main plot beats plus key subplots and character arcs: - **Setup**: Protagonist, world, status quo (2-3 sentences) - **Inciting incident**: What changes everything (2-3 sentences) - **Rising action**: Major plot events with key subplot threads woven in (1-2 paragraphs) - **Character arcs**: How the protagonist (and key secondary characters) change (integrated throughout) - **Midpoint shift**: The point of no return (2-3 sentences) - **Escalation**: Stakes rising, complications multiplying (1 paragraph) - **Climax**: The full climactic sequence (1 paragraph) - **Resolution**: How all major threads resolve, thematic arc completion (1 paragraph) Write in present tense, third person. Include the thematic arc -- what the story is *about* beyond plot. #### 5-Page Synopsis (~2500 words) -- `5p` Detailed outline for comprehensive submission packages: - **Chapter-by-chapter or act-by-act summary** following the structure in OUTLINE.md - **Character development**: Track how each major character changes across the narrative - **Subplot tracking**: Each subplot gets its own thread woven through the chapter summaries - **Thematic threads**: Identify and trace the major themes through their development - **Key scenes**: For pivotal moments, include brief descriptions of how they play out - **Pacing notes**: Indicate where the narrative accelerates, slows, or shifts tone Write in present tense, third person. Use section headers aligned to the work's structural units. --- ### STEP 4: REVIEW AND REFINE Present the synopsis to the writer. Ask: - Does this accurately represent the story's core? - Are any major plot points missing or misrepresented? - Is the character arc clear? - Does the ending read as satisfying (even out of context)? --- ### STEP 5: SAVE Determine the length label from the flag (or default `2p`). Save to `.manuscript/marketing/SYNOPSIS-{length}.md` where `{length}` is `1p`, `2p`, or `5p`. ```markdown # Synopsis ({length_label}) [synopsis text] --- *Generated by /scr:synopsis --length {length}* *Word count: [actual count]* ``` 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.