AI Guides › Claude Mastery

Claude As A Drafting Partner, Not A Ghostwriter

By Nigel Guy · 3 min read

Ask for a first draft, get something fluent and complete, and the temptation is to treat it as finished rather than as a first attempt — tweak a word here, fix a typo there, send it. That's not drafting with Claude, that's outsourcing the writing to it and doing light copyediting afterwards. The output can be genuinely good and still not represent a single judgement call that was actually yours.

The mechanism

1. Bring the point of view before you ask for the draft, not after. What's the actual argument, the specific thing you want the reader to take away, the position you're willing to be disagreed with on. A draft written without this just picks a plausible-sounding default, and defaults tend to be safe rather than actually yours.
2. Read the first draft for what it argues, not how it reads. It's easy to evaluate fluency — does it sound good — and skip evaluating substance — is this actually what you think. The first is much easier to judge and much less important.
3. Change at least one substantive thing, every time. Not a word swap — a structural choice, a piece of emphasis, an example, a cut. If nothing about the substance changed between what Claude gave you and what you sent, ask honestly whether the thinking was actually yours or borrowed wholesale.
4. Push back on the parts that sound too smooth. Fluent, confident prose can paper over a claim that doesn't actually hold up, or a transition that skips a step in the logic. The politeness of good sentences makes weak arguments easier to miss, not harder.
5. Keep the final judgement calls — the close, the ask, the number — as ones you made, not ones you accepted. Use Claude to generate the options and stress-test the reasoning; make the actual call yourself, especially on anything with your name on it.

What to skip

Skip asking for a draft "in my exact voice, ready to send" as the goal — that framing optimises for you doing nothing, which is the opposite of what a drafting partnership is for. And skip treating heavy editing as a sign the tool failed; a draft that needs substantial reshaping isn't a bad draft, it's doing its job of giving you something concrete to react to, which is often faster than starting from a blank page yourself.

Guardrails

• Anything published, sent, or signed under your name is your responsibility regardless of how much of it Claude drafted — "Claude wrote it" isn't a defence for a factual error or a position you didn't actually hold.
• This is about maintaining your own judgement in the work, not about how much of the literal text you personally typed — a heavily Claude-drafted piece you've genuinely reasoned through is more "yours" than a lightly-edited one you never really engaged with.
• Where authorship disclosure matters — academic work, some publications, some client agreements — check what's actually required rather than assuming a personal comfort level is the same as a policy requirement.

All 751 AI guides · JulieMango plans from £17/mo