Claude Writing Prompts: 20 Drafting and Editing Workflows

These Claude writing prompts turn a vague request into a practical drafting and editing workflow. Each template gives Claude a clear goal, audience, source material, constraints, and output format so you can work section by section instead of asking for a generic one-shot article.

Use the prompts as reusable starting points. Replace every bracketed field, attach or paste the material Claude should use, and keep a human responsible for facts, judgment, originality, and final approval.

Claude writing prompts at a glance

Before you use these Claude prompts for writing

Claude can draft emails, articles, scripts, stories, summaries, and other formats, but a prompt cannot supply missing expertise or trustworthy evidence. Give the model the source material it should use. If a fact is unavailable, instruct Claude to insert a visible placeholder instead of guessing.

For repeat work, Claude’s project instructions and personalization features can hold stable context such as your audience, terminology, formatting rules, and brand exclusions. Keep assignment-specific facts in the current prompt. If you are deciding whether Claude or another product fits your workflow, see our Claude vs ChatGPT comparison and our guide to the best AI writing tools for small business.

Prompts 1-5: Build a useful writing brief

1. Diagnose the assignment before drafting

Use when: the request is vague or several requirements are missing.

You are my writing project editor.

Review the assignment below before drafting anything.

<assignment>
[PASTE THE REQUEST]
</assignment>

Identify:
1. the likely audience and their main question;
2. the purpose and desired reader action;
3. required facts, examples, or source material;
4. unclear constraints or risks;
5. no more than five questions I should answer before drafting.

Do not write the deliverable yet. Return a concise project diagnosis and the questions.

2. Create an audience and outcome brief

Use when: you know the topic but need a sharper reader focus.

Build a one-page writing brief for [FORMAT] about [TOPIC].

Audience: [WHO THEY ARE]
Reader situation: [WHAT THEY ALREADY KNOW]
Primary problem: [PROBLEM]
Desired action: [ACTION]
Tone: [TONE]
Length: [TARGET]

Return: reader promise, three questions the piece must answer, key objections, evidence needed, content boundaries, and a clear definition of success. Do not draft the piece.

3. Extract usable facts from source material

Use when: the draft must stay grounded in provided documents.

Use only the material inside <sources>.

<sources>
[PASTE OR ATTACH SOURCE MATERIAL]
</sources>

Extract a fact sheet for a [FORMAT] about [TOPIC]. For every usable claim, provide:
- the exact supporting quote;
- the source name or section;
- what the claim does and does not prove;
- any date, scope, or limitation the writer must retain.

Separate unsupported ideas into a section called "Needs independent verification." Do not invent citations.

4. Find differentiated angles

Use when: the topic feels generic.

Generate seven defensible angles for a [FORMAT] about [TOPIC] for [AUDIENCE].

For each angle, give:
- the reader problem;
- the practical promise;
- the evidence required;
- what would make the angle original;
- the main risk of becoming generic or overstated.

Rank the top three by usefulness and evidence availability. Avoid hype, trend predictions without evidence, and clickbait.

5. Build an evidence-first outline

Use when: you have a brief and sources but not a structure.

Create a detailed outline for [FORMAT] about [TOPIC].

<brief>[PASTE BRIEF]</brief>
<fact_sheet>[PASTE VERIFIED FACTS]</fact_sheet>

For every section, include:
1. the reader question it answers;
2. the main point;
3. the evidence or example to use;
4. the practical takeaway;
5. any claim that still needs verification.

Put the direct answer first. Remove sections that repeat the same idea.

Prompts 6-10: Draft one useful deliverable

6. Draft three introduction options

Write three introductions for [FORMAT] about [TOPIC], each 80-120 words.

Audience: [AUDIENCE]
Reader problem: [PROBLEM]
Main answer: [ANSWER]
Tone: [TONE]

Option A: direct and practical.
Option B: problem-solution.
Option C: evidence-led.

Do not use a rhetorical question, invented statistic, exaggerated promise, or generic statement about a rapidly changing world. After the options, recommend one and explain the choice in two sentences.

7. Draft one section from an outline

Draft only the section named [SECTION NAME].

<outline>[PASTE RELEVANT OUTLINE]</outline>
<sources>[PASTE RELEVANT EVIDENCE]</sources>

Requirements:
- [WORD RANGE] words;
- lead with the answer;
- use short paragraphs;
- explain necessary terms in plain English;
- connect every factual claim to the supplied evidence;
- write [NEEDS SOURCE] where support is missing.

Do not write other sections.

8. Draft a complete article from approved materials

Draft a [WORD COUNT]-word article for [AUDIENCE] using the approved brief, outline, and sources below.

<brief>[PASTE BRIEF]</brief>
<outline>[PASTE OUTLINE]</outline>
<sources>[PASTE SOURCES]</sources>

Use US English and a clear, practical, low-hype tone. Keep paragraphs short. Preserve dates, limits, and caveats from the sources. Do not invent quotes, examples, experience, or citations. Mark missing evidence as [NEEDS SOURCE]. End with a practical next step, not a sales pitch.

9. Draft a professional email

Write a professional email for this situation:

Sender: [ROLE]
Recipient: [ROLE]
Goal: [DESIRED OUTCOME]
Context: [FACTS]
Required details: [DETAILS]
Tone: [TONE]
Maximum length: [WORDS]

Return a subject line and the email. Make the request explicit, put the deadline or next step near the end, and remove unnecessary pleasantries. Do not imply urgency unless the context supports it.

10. Rewrite for a different audience

Adapt the text inside <draft> for [NEW AUDIENCE].

<draft>[PASTE DRAFT]</draft>

Keep the original facts and meaning. Change only the explanation depth, examples, terminology, and tone needed for the new audience. Flag any passage that assumes knowledge the audience may not have. Return the rewrite followed by a short list of the most important adaptations.

Prompts 11-17: Edit without flattening the writer’s voice

11. Match a voice from examples

Study the writing samples inside <examples> and create a concise voice guide.

<examples>
[PASTE 3-5 REPRESENTATIVE SAMPLES]
</examples>

Describe sentence rhythm, vocabulary, formality, point of view, paragraph length, transitions, and patterns to avoid. Then revise <draft> to follow that guide without copying phrases from the examples.

<draft>[PASTE DRAFT]</draft>

Preserve facts and intent. List any change that could alter meaning.

12. Run a clarity edit

Edit the draft for clarity only.

<draft>[PASTE DRAFT]</draft>

Fix vague references, overloaded sentences, buried conclusions, undefined terms, and ambiguous modifiers. Preserve the author's voice, facts, examples, and approximate length. Return the edited draft and a five-item maximum change log.

13. Run a structural edit

Act as a structural editor. Review <draft> for order, emphasis, repetition, missing steps, and weak transitions.

<draft>[PASTE DRAFT]</draft>

First return a section-level diagnosis. Then propose a reordered outline. Do not rewrite the full draft until I approve the structure. Identify content that should be cut, merged, moved, or supported with evidence.

14. Cut the draft by a specific amount

Reduce this draft from [CURRENT WORD COUNT] to [TARGET WORD COUNT] words.

<draft>[PASTE DRAFT]</draft>

Protect the main conclusion, essential evidence, necessary caveats, and the author's distinctive examples. Cut repetition, throat-clearing, obvious transitions, and low-value modifiers first. Do not compress sentences until they become difficult to read. Return the edited draft and the final word count.

15. Replace jargon with plain English

Rewrite <draft> for an intelligent reader who is new to [TOPIC].

<draft>[PASTE DRAFT]</draft>

Replace avoidable jargon with plain English. Keep terms that the reader genuinely needs, but define each one at first use. Preserve technical accuracy and do not add analogies that distort the concept. Return a short glossary after the rewrite.

16. Improve flow and transitions

Improve the flow of <draft> without changing its claims or voice.

<draft>[PASTE DRAFT]</draft>

Check whether each paragraph follows logically from the previous one. Add or revise transitions only where the connection is unclear. Vary sentence openings and remove repetitive signposting. Do not add new facts. Highlight any paragraph that belongs in a different section.

17. Run a final line edit

Line-edit <draft> in US English.

<draft>[PASTE DRAFT]</draft>

Correct grammar, punctuation, spelling, agreement, capitalization, and inconsistent terminology. Keep the author's tone and sentence rhythm. Do not silently change facts, quotations, names, numbers, dates, or legal language. List every passage that requires an editorial judgment rather than a mechanical correction.

Prompts 18-20: Verify before publishing

18. Audit factual claims

Audit every externally verifiable claim in <draft>.

<draft>[PASTE DRAFT]</draft>
<sources>[PASTE APPROVED SOURCES]</sources>

Create a table with: claim, source support, exact supporting passage, date/scope caveat, and status (supported, partially supported, unsupported, or needs current verification). Do not treat the draft itself as a source. Do not invent citations or URLs.

19. Perform an adversarial editorial review

Review <draft> as a skeptical senior editor.

<draft>[PASTE DRAFT]</draft>

Find the ten most consequential weaknesses across accuracy, logic, evidence, audience fit, originality, structure, tone, and usefulness. Quote the relevant passage for each issue. Rank issues by reader harm, not by ease of correction. Recommend a specific fix, but do not rewrite the full draft.

20. Prepare a human approval checklist

Prepare this draft for final human review.

<draft>[PASTE DRAFT]</draft>

Return:
1. a 5-sentence summary of the argument;
2. all names, numbers, dates, links, quotations, and product claims to verify;
3. passages that may sound generic or AI-written;
4. unresolved editorial decisions;
5. a publication checklist for accuracy, originality, permissions, tone, and reader value.

Do not mark the piece approved. Final approval belongs to the human editor.

A practical five-pass Claude writing workflow

1. Brief: use prompts 1-5 to define the reader, evidence, angle, and structure.
2. Draft: generate one section at a time with prompts 6-10, especially when facts or formatting matter.
3. Edit: run separate passes for voice, structure, clarity, concision, and mechanics. Do not ask one prompt to solve every editorial problem.
4. Verify: use prompts 18-20 to expose unsupported claims and unresolved decisions.
5. Approve: read the final piece yourself, check primary sources, and accept responsibility for publication.

Teachers and education teams can adapt the same workflow for lesson materials; our Claude for Teachers guide explains the education product context. Small businesses can also compare these templates with our ChatGPT prompts for small business.

Common mistakes to avoid

• Asking for a complete article before defining the reader. The result may be fluent but poorly targeted.
• Requesting citations without supplying sources. A model can produce plausible-looking references that still require verification.
• Combining drafting, editing, fact-checking, and SEO into one request. Separate passes make weaknesses easier to inspect.
• Using a style sample without permission. Use your own work or material you are allowed to reuse, and ask for general characteristics rather than imitation of a living author.
• Publishing without a human pass. Check claims, originality, confidentiality, permissions, and whether the piece adds real reader value.

Sources and fact-checking

• Anthropic: Prompt engineering overview
• Anthropic: Prompting best practices
• Claude Help Center: Understanding Claude personalization features
• Claude Help Center: What you can use Claude for
• Anthropic Help Center: Using artifacts for substantial editable content

Fact checked and updated on August 3, 2026. AI product features, limits, and availability can change by plan and region. Always verify important claims in the original source before publishing or making business decisions.

FAQ

Is Claude good for writing?

Claude can help plan, draft, revise, summarize, and analyze writing across many formats. The output still depends on the brief and evidence you provide, and it requires human review for facts, originality, permissions, and final judgment.

What should I include in a Claude writing prompt?

Include the audience, purpose, source material, desired output, tone, constraints, and success criteria. Add representative examples when format or voice consistency matters, and separate different types of input with clear labels or XML tags.

Should I ask Claude to write a complete article at once?

You can, but a staged workflow is easier to control. Approve the brief and outline first, draft one section at a time when accuracy matters, then run separate editing and verification passes.

Can Claude match my writing style?

Claude can analyze representative samples and apply general patterns such as rhythm, formality, vocabulary, and structure. Use samples you own or have permission to use, and review the result so the final work still reflects your judgment and voice.

Can I trust citations generated by Claude?

No citation should be trusted without opening and checking the original source. For reliable work, give Claude approved sources, ask it to connect claims to exact supporting passages, and independently verify every important reference.

Final recommendation

Use Claude as a structured writing partner, not an automatic publisher. Start with a brief, provide real source material, draft in controlled sections, edit in focused passes, and finish with a claim audit and human approval. Save the prompts that work for your recurring tasks, but keep updating them as your audience, standards, and source material change.