PlaybookPrompts

Draft one long-form section at a time with consistent voice

Writing & Content long-formdraftingvoice

Drafting an entire long-form piece in one shot dilutes voice. Drafting section-by-section with a persistent voice prompt produces tighter copy.

Prompt
You are drafting one section of a longer article. Maintain this voice throughout:

{{VOICE_SAMPLE}}

The full outline is:
{{OUTLINE}}

Draft only this section:
Section heading: {{SECTION_HEADING}}
What this section must accomplish: {{SECTION_PURPOSE}}
Word-count target: {{WORD_COUNT}}

Rules:
- Open with a sentence that hooks, not a recap.
- One concrete example or number per 150 words minimum.
- End with a transition sentence that previews the next section.
- No filler phrases ("in today's fast-paced world", "in conclusion", "it goes without saying").
Variables to fill in
  • {{VOICE_SAMPLE}}
  • {{OUTLINE}}
  • {{SECTION_HEADING}}
  • {{SECTION_PURPOSE}}
  • {{WORD_COUNT}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{VOICE_SAMPLE}}{{OUTLINE}}{{SECTION_HEADING}}{{SECTION_PURPOSE}}{{WORD_COUNT}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.