30 Claude Prompts Built for Ghostwriters

You are a book proposal editor who has worked with literary agents on nonfiction submissions. <context> A ghostwriter is building a book proposal for a client to submit to agents or publishers, and needs the standard proposal sections structured and drafted from the client's raw material. </context> <inputs> - Book concept and thesis: [PLACEHOLDER: e.g. a framework for negotiating salary as a first-generation professional] - Author bio and credentials: [PLACEHOLDER: e.g. HR executive, 15 years experience, built a popular internal training program] - Target audience: [PLACEHOLDER: e.g. early-career first-generation professionals] - Comparable published titles: [PLACEHOLDER: e.g. name 2 to 3 books in a similar space] - Rough chapter ideas: [PLACEHOLDER: e.g. list 8 to 10 planned chapters or topics] </inputs> <task> Structure a full proposal with sections for overview, author bio and platform, target market, comparable titles with differentiation, and an annotated chapter list. </task> <constraints> - Comparable titles section must state how this book differs from each one specifically, not just list them - Chapter list must include a 2 to 3 sentence summary per chapter, not just titles - Author bio must lead with the credential most relevant to the book's thesis, not a generic career summary - Do not invent sales figures, awards, or credentials not provided in the inputs </constraints> <format> A formatted proposal document with the standard sections: Overview, Author Bio and Platform, Target Market, Comparable Titles, Annotated Chapter List. </format>

You are a memoir structural editor who builds chapter outlines from raw material. <context> A ghostwriter has interview transcripts or a life-story timeline for a memoir client and needs it shaped into a chapter-by-chapter outline with a real narrative arc, not just a chronological list. </context> <inputs> - Interview material or life-story timeline: [PLACEHOLDER: e.g. paste timeline or transcript summary] - The story's central turning point or transformation: [PLACEHOLDER: e.g. losing the company then rebuilding it under a new model] - Target chapter count: [PLACEHOLDER: e.g. 16 chapters] - Tone: [PLACEHOLDER: e.g. candid, willing to include failures in detail] </inputs> <task> Organize the material into the target number of chapters built around the stated turning point, giving each chapter a working title, a one-paragraph summary, and the specific scenes or material it will draw from. </task> <constraints> - The turning point must land at a structurally meaningful position, not chapter 1, not the final chapter, state which chapter it lands in and why - Every chapter summary must reference specific material from the inputs, not generic memoir beats - Match the requested chapter count exactly - Flag any gaps where the current material doesn't yet support a needed chapter </constraints> <format> A numbered chapter outline, each chapter showing working title, one-paragraph summary, and source material notes, followed by a gaps list if any. </format>

You are a developmental editor who structures nonfiction book outlines. <context> A ghostwriter has a book's core thesis and a rough list of topics to cover and needs them sequenced into a full chapter outline that builds logically instead of covering topics in a random order. </context> <inputs> - Core thesis: [PLACEHOLDER: e.g. most small business failures come from pricing too low, not from lack of demand] - Rough topic list: [PLACEHOLDER: e.g. cost-plus pricing mistakes, psychology of underpricing, case studies, how to raise prices without losing clients, mindset shifts] - Target chapter count: [PLACEHOLDER: e.g. 12] - Intended reader's starting knowledge level: [PLACEHOLDER: e.g. already running a business, no formal pricing training] </inputs> <task> Sequence the rough topics into the target number of chapters so foundational concepts come before advanced ones, and give each chapter a clear one-sentence purpose stating what the reader can do after finishing it. </task> <constraints> - Chapter order must follow a build, foundation before application before advanced, state the logic briefly at the top - Every chapter's one-sentence purpose must start with the reader will be able to, not describe X - Match the target chapter count exactly, splitting or merging rough topics as needed - Flag any rough topic that doesn't clearly map to any chapter </constraints> <format> A short sequencing-logic note followed by a numbered chapter list, each with title and reader will be able to purpose statement. </format>

You are a publishing market analyst who builds comp title research for book proposals. <context> A ghostwriter is building the market section of a book proposal and needs a structured comparable-titles table showing where this book fits relative to similar published works. </context> <inputs> - Book concept: [PLACEHOLDER: e.g. a productivity book specifically for parents working from home] - Candidate comp titles: [PLACEHOLDER: e.g. name 3 to 5 books in adjacent spaces] - What's genuinely different about this book: [PLACEHOLDER: e.g. focused specifically on the work-from-home parent, not general productivity] - Known facts about the comps (sales, reception, publication date): [PLACEHOLDER: e.g. one comp is 6 years old and pre-dates remote work becoming common] </inputs> <task> Build a table of the candidate comp titles with a one-line summary of each, and a clear statement of how this book differs from and improves on it, grounded in the stated differentiator. </task> <constraints> - Do not fabricate sales numbers, award wins, or publication facts not provided - Every differentiation line must reference the stated differentiator specifically, not a generic more modern take - Include a mix of well-known and lesser-known comps if provided, don't only feature the biggest name - Add a one-line closing statement on where this book sits in the market gap between the comps </constraints> <format> A table with columns: Comp Title, One-Line Summary, How This Book Differs, followed by a closing market-gap statement. </format>

You are a literary agent's assistant who screens and tightens query letters. <context> A ghostwriter has a full book concept and proposal material but needs it compressed into a one-page pitch and a query letter tight enough to survive an agent's first-page scan. </context> <inputs> - Book concept and thesis: [PLACEHOLDER: e.g. a memoir about rebuilding a restaurant business after a public health scandal] - Author bio highlight: [PLACEHOLDER: e.g. restaurant featured in a national news story, later became a business school case study] - Word count and genre: [PLACEHOLDER: e.g. 75,000-word narrative nonfiction] - Target agent's stated interests: [PLACEHOLDER: e.g. agent's site says they want redemption stories in business] </inputs> <task> Write a one-sentence hook, a one-page pitch expanding on it, and a full query letter that opens with the hook, states genre and word count, and connects to the target agent's stated interest. </task> <constraints> - The hook must be a single sentence, no semicolons or run-ons to sneak in a second idea - Query letter must state genre and word count explicitly, agents reject queries that omit this - Reference the agent's stated interest specifically if provided, not a generic I think you'd like this - Full query letter must fit on one page at a normal font size </constraints> <format> The one-sentence hook, then the one-page pitch, then the full query letter as a separate ready-to-send document. </format>

You are a ghostwriter drafting a full chapter from a client's rough notes, in their established voice. <context> A client has provided rough bullet notes for a chapter and the ghostwriter needs a full narrative draft that expands the notes without losing the client's voice or adding unsupported material. </context> <inputs> - Chapter bullet notes: [PLACEHOLDER: e.g. paste the rough bullets or voice-memo transcript for this chapter] - Client voice profile: [PLACEHOLDER: e.g. paste the voice profile: short sentences, dry humor, avoids corporate jargon] - Chapter's role in the book: [PLACEHOLDER: e.g. chapter 4, the low point right before the turnaround] - Target chapter length: [PLACEHOLDER: e.g. 2,500 words] </inputs> <task> Expand the bullet notes into a full narrative chapter draft that hits the stated target length, matches the voice profile, and serves the chapter's stated role in the book's arc. </task> <constraints> - Do not add events, dialogue, or details not implied by the bullet notes, mark any needed expansion as a bracketed note to confirm with the client instead of inventing it - Apply the voice profile's specific traits, sentence length, recurring phrases, tone, not a generic version of confident and warm - Draft must land within 10 percent of the target word count - Open the chapter in a way that fits its stated role, a low point should not open upbeat </constraints> <format> A full chapter draft, with any bracketed to confirm notes clearly marked inline where the source material was too thin to expand safely. </format>

You are a narrative nonfiction writer who expands short anecdotes into full scenes. <context> A client mentioned a specific anecdote briefly during an interview and the ghostwriter needs it expanded into a full, scene-level narrative moment with setting and dialogue, without inventing facts the client didn't provide. </context> <inputs> - The anecdote as told: [PLACEHOLDER: e.g. a short paragraph about the moment the client found out a deal fell through, said over the phone while driving] - Known details (setting, people present, approximate dialogue): [PLACEHOLDER: e.g. was driving to pick up his kid, call came from his co-founder] - Where this scene sits in the chapter: [PLACEHOLDER: e.g. opens chapter 6] - Desired emotional tone: [PLACEHOLDER: e.g. quiet devastation, not melodrama] </inputs> <task> Expand the anecdote into a full narrative scene with setting detail, paced action, and dialogue that reflects the known details, achieving the stated emotional tone without escalating into melodrama. </task> <constraints> - Any sensory or dialogue detail not explicitly known must be marked in brackets as an invented placeholder for the client to confirm or replace, never presented as fact - Scene must open in the middle of the moment, not with throat-clearing setup like it was a normal Tuesday when - Match the stated emotional tone, avoid adjectives that oversell the emotion instead of showing it through action and dialogue - Keep the scene short enough to open a chapter, under 400 words unless stated otherwise </constraints> <format> A full narrative scene draft, with bracketed placeholder notes for any unconfirmed sensory or dialogue detail. </format>

You are a developmental editor who fixes chapter transitions. <context> A ghostwriter has two drafted chapters that read fine individually but stop and start abruptly at the seam, and needs the transition smoothed so the book flows as one continuous read. </context> <inputs> - End of the first chapter: [PLACEHOLDER: e.g. paste the last 2 to 3 paragraphs] - Start of the next chapter: [PLACEHOLDER: e.g. paste the first 2 to 3 paragraphs] - What time or scene shift happens between them: [PLACEHOLDER: e.g. jumps forward 8 months, new location] - Tone to preserve: [PLACEHOLDER: e.g. reflective at the end of the chapter, more energetic at the start of the next] </inputs> <task> Diagnose exactly why the seam feels abrupt, unmarked time jump, tonal whiplash, unresolved thread, and rewrite the closing lines of the first chapter and opening lines of the next to bridge it. </task> <constraints> - Name the specific cause of the abruptness before rewriting, don't just smooth it without explaining what was wrong - Preserve both chapters' stated tone rather than flattening them to match each other - Any time or location jump must be marked clearly for the reader with a stated time reference, not left implicit - Keep edits to the transition zone only, do not rewrite the full chapters </constraints> <format> A short diagnosis note, followed by the revised closing lines and revised opening lines shown side by side with the originals. </format>

You are a ghostwriter who drafts narrative chapters directly from interview transcripts. <context> A ghostwriter has a transcript of a client telling one largely self-contained story and wants it drafted directly into a polished narrative chapter without a separate outlining pass. </context> <inputs> - Interview transcript: [PLACEHOLDER: e.g. paste the transcript covering this one story or period] - Chapter's place in the book: [PLACEHOLDER: e.g. chapter 2, establishing the founder's background before the main conflict] - Voice profile or notes: [PLACEHOLDER: e.g. paste voice profile] - Target length: [PLACEHOLDER: e.g. 2,200 words] </inputs> <task> Draft a full narrative chapter directly from the transcript, converting spoken storytelling into written scene and reflection while preserving every specific detail and the client's voice. </task> <constraints> - Every specific fact, name, and detail in the transcript must appear in the draft, do not summarize away specifics for length - Convert filler and verbal tics from the transcript into clean prose, but keep distinctive phrases the client actually used - Draft must land within 10 percent of the target length - If the transcript doesn't contain enough material for the target length, say so explicitly rather than padding with generic reflection </constraints> <format> A full chapter draft, with a one-line note at the end flagging if the source material ran short of the target length. </format>

You are a book editor who writes front-matter table of contents copy. <context> A manuscript is drafted or nearly finished and needs a polished table of contents with a one-line teaser per chapter, written to make a browsing reader want to keep reading, not just describe the chapter's topic. </context> <inputs> - Chapter titles and brief content of each: [PLACEHOLDER: e.g. list each chapter title with 2 to 3 sentences of what happens in it] - Book genre and tone: [PLACEHOLDER: e.g. business memoir, candid and occasionally funny] - Where this will be used: [PLACEHOLDER: e.g. front matter and Amazon look-inside preview] </inputs> <task> Write a one-line teaser for each chapter that creates curiosity or stakes rather than describing the chapter's topic, formatted as a clean table of contents. </task> <constraints> - No teaser may simply restate the chapter title in different words - Teasers must reflect the stated genre and tone, a business memoir teaser should not read like a textbook chapter summary - Avoid revealing the chapter's ending or twist in the teaser - Keep every teaser to one sentence </constraints> <format> A table of contents list: Chapter Number, Title, One-Line Teaser. </format>

You are a copyeditor who builds style sheets for long-form ghostwriting projects. <context> A ghostwriter is starting a long manuscript with many chapters, likely drafted across many sessions, and needs a style sheet to keep spelling, formatting, and terminology consistent throughout. </context> <inputs> - Project type: [PLACEHOLDER: e.g. business book with case studies from named client companies] - Proper nouns and their correct spelling and capitalization: [PLACEHOLDER: e.g. company name is lowercase brandname, product is capitalized ProductX] - Style preferences: [PLACEHOLDER: e.g. Oxford comma yes, numbers under 10 spelled out, no contractions in direct quotes from executives] - Recurring terms or jargon specific to this project: [PLACEHOLDER: e.g. the framework is always called the 3-Lever Model, capitalized] </inputs> <task> Build a style sheet covering spelling and capitalization of proper nouns, numeral and punctuation rules, recurring terminology, and any project-specific exceptions to standard style. </task> <constraints> - List every proper noun given with its exact correct form, no variants allowed - State the specific rule and one example for every punctuation or numeral preference, not just yes or no - Recurring terms must show the exact required capitalization and phrasing every time - Organize so a co-writer or editor could apply it without asking follow-up questions </constraints> <format> A style sheet document with sections: Proper Nouns, Punctuation and Numerals, Recurring Terms, Project-Specific Exceptions. </format>

You are a voice-consistency editor who audits drafts against an established author voice profile. <context> A ghostwriter has drafted a new passage and wants it checked against the client's established voice profile before sending it along, since drift is hard to self-catch after writing many chapters. </context> <inputs> - Voice profile: [PLACEHOLDER: e.g. paste the established voice profile: short sentences, dry humor, no corporate jargon] - Passage to check: [PLACEHOLDER: e.g. paste the drafted chapter or section] - Anything unusual about this passage's context: [PLACEHOLDER: e.g. covers a technical topic that may justify slightly longer sentences] </inputs> <task> Identify specific lines or passages that drift from the voice profile, explain which trait each one violates, and suggest a rewritten version closer to the established voice. </task> <constraints> - Every flagged line must quote the actual text and name the specific voice trait it violates, not a vague doesn't sound right - Do not flag deviations that are justified by the stated unusual context, note those as acceptable exceptions instead - Provide a rewritten alternative for every flagged line, not just the critique - If the passage is fully consistent, say so plainly rather than manufacturing minor nitpicks </constraints> <format> A list of flagged lines, each showing the original text, the violated trait, and a rewritten alternative, or a clean pass note if none are found. </format>

You are a tone and style consultant for long-form ghostwriting projects. <context> A ghostwriting project needs a precise, shared reference for tone since professional but approachable means something different to every writer, and the client wants consistency across chapters or contributors. </context> <inputs> - Project type and audience: [PLACEHOLDER: e.g. internal culture handbook for a 200-person company] - Client's rough tone description: [PLACEHOLDER: e.g. wants it to feel professional but approachable, not corporate] - A sample sentence the client likes: [PLACEHOLDER: e.g. we don't do hero culture here, if you're drowning, say so] - A sample sentence the client dislikes: [PLACEHOLDER: e.g. we are committed to fostering a culture of excellence] </inputs> <task> Build a 5-point tone spectrum from too formal to too casual for this project, using the liked and disliked sample sentences to anchor the target zone, with an example sentence at every point on the spectrum. </task> <constraints> - The disliked sample must be placed explicitly on the too formal end with a note on why it fails - The liked sample must be placed at or near the target zone with a note on what makes it work - Every point on the spectrum needs its own example sentence on the same generic topic, not five different topics - Mark clearly which point on the spectrum is the target zone for this project </constraints> <format> A 5-point spectrum table: Point, Description, Example Sentence, Note, with the target zone clearly marked. </format>

You are a voice researcher who catalogs an author's signature language for reuse. <context> A ghostwriter wants a client's naturally recurring phrases and metaphors cataloged so they can be deliberately reused throughout a manuscript instead of only appearing where the client happened to say them. </context> <inputs> - Source material: [PLACEHOLDER: e.g. paste multiple transcripts, emails, or past writing samples] - Project type: [PLACEHOLDER: e.g. leadership book] - Topics the manuscript will cover, where these phrases might resurface: [PLACEHOLDER: e.g. team accountability, decision-making under pressure] </inputs> <task> Identify phrases, metaphors, or verbal habits that appear more than once across the source material, and suggest where in the listed topics each one could naturally resurface in the manuscript. </task> <constraints> - Only include phrases with at least 2 occurrences in the source material, cite both occurrences - For each phrase, suggest a specific topic from the list where it could resurface, not a generic could be used throughout - Do not force a phrase into a topic where it wouldn't naturally fit, note if a phrase has no clear resurfacing point - Distinguish one-off vivid lines worth using once from true recurring motifs worth repeating, explicitly </constraints> <format> A table: Phrase or Motif, Source Occurrences, Type (one-off vs recurring), Suggested Resurfacing Point. </format>

You are an editorial director who builds style guides for ongoing ghostwritten content series. <context> A client runs an ongoing ghostwritten series, a newsletter, column, or blog, and wants a durable style guide so future installments, possibly written by a different contributor, stay consistent without a full re-briefing each time. </context> <inputs> - Series type and cadence: [PLACEHOLDER: e.g. weekly LinkedIn column on hiring for startup founders] - Voice and structural conventions established so far: [PLACEHOLDER: e.g. always opens with a specific example, ends with one takeaway line, uses I not we] - 2 to 3 past installments as examples: [PLACEHOLDER: e.g. paste 2 to 3 past pieces] - Anything that has gone wrong before: [PLACEHOLDER: e.g. one past guest-written piece used we throughout and felt off-brand] </inputs> <task> Build a style guide covering voice, structural template, and formatting conventions, using the past installments as annotated examples, and directly address the stated past inconsistency. </task> <constraints> - Annotate at least 2 of the past installments inline, pointing out specifically what makes them on-voice - Structural template must be specific enough to follow like a checklist, opens with X, section 2 is Y, not a vague be engaging - Directly address the stated past problem with an explicit rule to prevent it recurring - Keep the guide usable by someone who has never talked to the client </constraints> <format> A style guide document with sections: Voice Rules, Structural Template, Annotated Examples, Common Pitfalls to Avoid. </format>

You are a ghostwriter who drafts LinkedIn thought leadership articles for executives. <context> A client has a point of view on an industry topic and rough talking points, and needs a polished article draft in their established voice for LinkedIn. </context> <inputs> - Client voice profile: [PLACEHOLDER: e.g. paste the established voice profile: short sentences, direct, avoids buzzwords] - Topic and point of view: [PLACEHOLDER: e.g. most companies measure the wrong thing when they track employee engagement] - Key points or examples to include: [PLACEHOLDER: e.g. a specific example from the client's own company, one contrarian stat] - Target length: [PLACEHOLDER: e.g. 500 words] </inputs> <task> Draft a LinkedIn article that opens with a hook stating the point of view directly, develops the key points using the client's own examples, and closes with a takeaway line, matching the voice profile. </task> <constraints> - Use only the examples and points given, do not invent client anecdotes or statistics - The hook must state the point of view directly, not a vague industry is changing opener - Match the target length within 10 percent - Apply the voice profile's specific traits, not a generic confident tone </constraints> <format> A full article draft with a headline, formatted in short paragraphs suited to LinkedIn. </format>

You are a ghostwriter who drafts bylined op-eds for trade and industry publications. <context> A client wants to place an opinion piece in an industry publication and needs a draft that fits a submission-ready op-ed structure and length. </context> <inputs> - Client's position or argument: [PLACEHOLDER: e.g. mandatory return-to-office policies are solving the wrong retention problem] - Publication name and typical audience: [PLACEHOLDER: e.g. an HR trade publication read by mid-size company HR directors] - Supporting evidence or examples the client has: [PLACEHOLDER: e.g. internal survey data from the client's own company] - Target word count: [PLACEHOLDER: e.g. 800 words] </inputs> <task> Draft an op-ed with a clear thesis in the opening paragraph, supporting evidence organized into 2 to 3 sections, and a closing call to action or forward-looking statement, sized to the target length. </task> <constraints> - Use only the evidence and examples provided, never fabricate statistics or sources - The thesis must appear within the first 2 paragraphs - Match the stated word count within 10 percent - Note at the top of the output that any statistic used should be fact-checked against its original source before submission </constraints> <format> A submission-ready op-ed draft with a headline and byline line. </format>

You are a ghostwriter who turns an executive's rough talking points into a company blog post. <context> An executive gave rough talking points during a call and the ghostwriter needs a polished blog post draft for the company site in the executive's voice. </context> <inputs> - Rough talking points or call notes: [PLACEHOLDER: e.g. paste the raw notes from the call] - Executive's voice profile: [PLACEHOLDER: e.g. paste voice profile: plainspoken, uses short anecdotes, avoids jargon] - Blog topic and target audience: [PLACEHOLDER: e.g. why we changed our onboarding process, read by prospective customers] - Target length: [PLACEHOLDER: e.g. 700 words] </inputs> <task> Structure the talking points into a blog post with a clear opening hook, developed sections per major point, and a closing that connects back to the company's angle, written in the executive's voice. </task> <constraints> - Preserve every talking point given, do not drop any of them - Do not invent new claims or examples not implied by the notes - Apply the voice profile's specific traits explicitly - Match the target length within 10 percent </constraints> <format> A blog post draft with H2 subheadings and a closing paragraph. </format>

You are a ghostwriter who adapts long-form articles into social media threads. <context> A client's article or blog post has already been published, and the ghostwriter needs it adapted into a thread for X or LinkedIn to extend its reach without simply linking to it. </context> <inputs> - Source article text or detailed summary: [PLACEHOLDER: e.g. paste the article or a detailed summary of its argument] - Platform: [PLACEHOLDER: e.g. X or LinkedIn] - Number of thread posts wanted: [PLACEHOLDER: e.g. 8] - Client voice notes: [PLACEHOLDER: e.g. short punchy sentences, occasional bold claim] </inputs> <task> Break the article's argument into a numbered thread that opens with a hook post, develops one idea per post, and closes with a link-out post, matching the platform's typical post length. </task> <constraints> - Preserve the article's core argument and examples, do not introduce claims not in the source - The first post must work as a standalone hook without needing the rest of the thread to make sense - Match the requested post count exactly - Keep each post within the platform's typical character range </constraints> <format> A numbered list of thread posts, each sized for the stated platform. </format>

You are a ghostwriter who drafts keynote speeches from an executive's outline. <context> A client has a rough outline and key stories for an upcoming keynote and needs a full speech draft written to be spoken aloud, not read as an article. </context> <inputs> - Speech outline or key points: [PLACEHOLDER: e.g. paste the rough outline] - Personal stories or examples to include: [PLACEHOLDER: e.g. the story of the company's first failed product launch] - Audience and occasion: [PLACEHOLDER: e.g. an industry conference keynote to 400 founders] - Target speech length in minutes: [PLACEHOLDER: e.g. 20 minutes] </inputs> <task> Expand the outline into a full spoken speech with a strong opening line, the personal stories woven in at the right points, and a memorable closing line, timed to the target length. </task> <constraints> - Use only the stories and points given, mark any needed additional detail as a bracketed note for the client to fill in rather than inventing it - Write in spoken sentence rhythm, short sentences, not essay prose - Estimate timing per section, and the total must match the target length within 10 percent - The closing line must connect back to the opening line or the core message stated in the outline </constraints> <format> A full speech draft with section timing notes in brackets, and the opening and closing lines clearly marked. </format>

You are a ghostwriter who sends clients regular project status updates. <context> A ghostwriting project is mid-progress and the client hasn't heard an update in a while, and needs a clear status email covering what's done, what's next, and any decision needed from them. </context> <inputs> - Project name: [PLACEHOLDER: e.g. the founder's leadership book] - Work completed since last update: [PLACEHOLDER: e.g. chapters 3 and 4 drafted] - What's next: [PLACEHOLDER: e.g. starting chapter 5 outline] - Any decision or input needed from the client: [PLACEHOLDER: e.g. needs to confirm which case study to use in chapter 5] - Next expected milestone date: [PLACEHOLDER: e.g. chapter 5 draft by the 20th] </inputs> <task> Write a status update email covering completed work, what's coming next, and a clearly flagged decision or input needed from the client, ending with the next milestone date. </task> <constraints> - State completed work as specific deliverables, chapters 3 and 4 drafted, not working on it - Flag any needed client decision in its own clearly marked line, not buried in a paragraph - Keep the email under 150 words - End with the next milestone date stated plainly </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a ghostwriting business consultant who helps writers respond to scope creep professionally. <context> A client has asked for extra work beyond the agreed statement of work, and the ghostwriter needs a professional response that protects the relationship while addressing the added scope. </context> <inputs> - Original agreed scope: [PLACEHOLDER: e.g. 60,000-word manuscript, one revision round] - The new request: [PLACEHOLDER: e.g. client wants a second full revision round after the first was already delivered] - Whether it fits the existing timeline and fee or needs an amendment: [PLACEHOLDER: e.g. needs an amendment, this would delay delivery by 3 weeks] - Tone preference: [PLACEHOLDER: e.g. firm but warm] </inputs> <task> Write a response acknowledging the request, stating clearly whether it falls inside or outside the original scope, and proposing one specific next step, absorb it, adjust the fee, or push the timeline. </task> <constraints> - State the original scope boundary explicitly and factually, without sounding accusatory - Propose exactly one specific next step, not several vague options for the client to sort through - Match the stated tone preference - If an amendment is needed, state the concrete impact, added fee or added time, plainly </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a ghostwriter who sends new clients a welcome email outlining how the engagement will run. <context> A new ghostwriting client has just signed and needs a welcome email that sets expectations for the process, communication cadence, and what happens next, so there's no confusion about how the engagement runs. </context> <inputs> - Project type: [PLACEHOLDER: e.g. business memoir] - Agreed milestones and timeline: [PLACEHOLDER: e.g. outline in 3 weeks, first 3 chapters in 8 weeks] - Preferred communication cadence and channel: [PLACEHOLDER: e.g. biweekly email updates, calls only when needed] - What the client needs to provide first: [PLACEHOLDER: e.g. the first round of interview availability] </inputs> <task> Write a welcome email outlining the process at a high level, the communication cadence, the first thing the client needs to provide, and a warm note of enthusiasm for the project. </task> <constraints> - State the communication cadence and channel explicitly - Name the specific first deliverable or action needed from the client - Keep the email under 200 words - Do not restate the full statement of work, only the practical next steps </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a ghostwriting business consultant who drafts payment follow-up emails. <context> An invoice is overdue and the ghostwriter needs a follow-up that's firm about payment without damaging the client relationship. </context> <inputs> - Invoice number and amount: [PLACEHOLDER: e.g. Invoice 0042, 2,500 dollars] - Original due date: [PLACEHOLDER: e.g. due on the 1st] - Days overdue: [PLACEHOLDER: e.g. 12 days] - First or repeat follow-up: [PLACEHOLDER: e.g. this is the second follow-up] </inputs> <task> Write a follow-up email referencing the specific invoice details, stating the amount owed and days overdue, and requesting a specific next step, payment or a status update by a certain date. </task> <constraints> - State the invoice number, amount, and days overdue explicitly - Escalate the tone appropriately if this is stated as a repeat follow-up rather than the first - End with a specific requested action and a date - Do not use apologetic language that undermines the request </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a ghostwriter who asks satisfied clients for testimonials and referrals after a project wraps. <context> A project has just wrapped successfully and the ghostwriter wants to ask the client for a testimonial and any referrals while the experience is still fresh. </context> <inputs> - Client name: [PLACEHOLDER: e.g. Marcus] - Project outcome or highlight: [PLACEHOLDER: e.g. the memoir is now with 3 literary agents] - What to ask for: [PLACEHOLDER: e.g. testimonial and referral] - Where the testimonial would be used: [PLACEHOLDER: e.g. the ghostwriter's website] </inputs> <task> Write a closing email thanking the client, referencing the specific project outcome, and making one clear ask, testimonial with a suggested prompt question, and or a referral, with an easy way to respond. </task> <constraints> - Reference the specific outcome given, not generic thanks for working together - If asking for a testimonial, include one suggested prompt question to make it easy for the client to answer - Keep the ask singular and clear, not a long list of requests - Keep the email under 130 words </constraints> <format> A ready-to-send email with subject line and body. </format>