Sign in Start free

Know When to Kill a Draft

Sunk cost keeps bad drafts alive, and the usual outcome is publishing something mediocre to justify the hours already spent. Every published weak page also has a cost after publication: it competes with your stronger pages, it dilutes topical focus, and someone will have to maintain it. Killing drafts needs to be a normal, cheap decision made against stated criteria rather than a judgment about the writer.

CATEGORY
Content production
FORMAT
kill-a-draft.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when a draft has been through two or more rounds of edits and still is not right.

The skill file

kill-a-draft.md 
---
name: kill-a-draft
description: Use when a draft has been through two or more rounds of edits and still is not right.
---

# Know When to Kill a Draft

Sunk cost keeps bad drafts alive, and the usual outcome is publishing something mediocre to justify the hours already spent. Every published weak page also has a cost after publication: it competes with your stronger pages, it dilutes topical focus, and someone will have to maintain it. Killing drafts needs to be a normal, cheap decision made against stated criteria rather than a judgment about the writer.

## What you need first

- the original brief and its stated purpose
- the current draft and its edit history
- the SERP for the intended query as it stands today

## Method

1. Ask what question this page answers better than anything currently ranking. If the honest answer is "the same, but written by us", stop here - that page has no route to visibility.
2. Check whether the topic was ever winnable. If page one is entirely major brands, forums or tools, no amount of editing changes the format mismatch.
3. Count the rounds. Beyond two substantive edit rounds, the problem is nearly always the brief or the topic, not the prose, so a third round of line edits will not save it.
4. Separate salvage from rescue: extract the two or three genuinely good paragraphs into a notes file for use elsewhere, then kill the rest. Most dead drafts contain something reusable.
5. Consider merging into an existing page. Material too thin to stand alone often strengthens a page that already ranks, and this is usually the highest-value outcome.
6. Record the reason for killing it in one line and feed it back into briefing. Drafts die for repeating reasons, and unrecorded reasons produce the same dead draft again.

## What this produces

A documented kill, merge or salvage decision with the reusable material extracted and the cause logged.

## Where this goes wrong

- Publishing anyway because the work is paid for, adding a page you will later pay again to prune
- Blaming the writer when the brief never contained anything proprietary to write about
- Killing the draft without extracting the good sections or logging the reason, so the effort is lost twice

---

From the QuQi skill library - https://www.quqi.io/skills/kill-a-draft
Free to download · no account, no email

What you need first

  • the original brief and its stated purpose
  • the current draft and its edit history
  • the SERP for the intended query as it stands today

Method

  1. 01 Ask what question this page answers better than anything currently ranking. If the honest answer is "the same, but written by us", stop here - that page has no route to visibility.
  2. 02 Check whether the topic was ever winnable. If page one is entirely major brands, forums or tools, no amount of editing changes the format mismatch.
  3. 03 Count the rounds. Beyond two substantive edit rounds, the problem is nearly always the brief or the topic, not the prose, so a third round of line edits will not save it.
  4. 04 Separate salvage from rescue: extract the two or three genuinely good paragraphs into a notes file for use elsewhere, then kill the rest. Most dead drafts contain something reusable.
  5. 05 Consider merging into an existing page. Material too thin to stand alone often strengthens a page that already ranks, and this is usually the highest-value outcome.
  6. 06 Record the reason for killing it in one line and feed it back into briefing. Drafts die for repeating reasons, and unrecorded reasons produce the same dead draft again.

What this produces

A documented kill, merge or salvage decision with the reusable material extracted and the cause logged.

Where this goes wrong

  • Publishing anyway because the work is paid for, adding a page you will later pay again to prune
  • Blaming the writer when the brief never contained anything proprietary to write about
  • Killing the draft without extracting the good sections or logging the reason, so the effort is lost twice

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/kill-a-draft/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When do I kill a draft rather than commission another round of edits?

After two substantive edit rounds have not fixed it. Beyond that the problem is nearly always the brief or the topic rather than the prose, so a third round of line edits changes nothing. The alternative most teams reach for, publishing anyway to justify the spend, adds a weak page that competes with your stronger ones and needs maintaining.

What do I need in front of me to make the call?

The original brief and its stated purpose, the draft with its edit history, and today's SERP for the intended query. Without the brief you cannot tell whether the writer missed it or it never contained anything proprietary, and that distinction decides whether you rebrief or drop the topic. Without the current SERP you re-argue a topic that was never winnable.

What do I end up with, and which outcome is usually best?

A recorded kill, merge or salvage decision with the reusable paragraphs extracted into a notes file. The merge outcome is normally the most valuable, because material too thin to stand alone often strengthens a page that already ranks. The one-line reason is what pays later: drafts die for repeating causes, and unlogged causes produce the same dead draft again.

What is the mistake that costs me here?

Killing the draft without extracting the good sections or logging the cause, so the effort is lost twice and the next brief repeats the fault. Blaming the writer is the other one, and it is expensive because it sends you hiring instead of fixing a brief that contained nothing only your organization could supply.

More in Content production

Write a Brief That Survives a Writer

Use when you are commissioning a page and cannot personally rewrite it if the draft comes back g...

Edit an AI Draft Into Something Publishable

Use when you have a model-generated draft that reads fine sentence by sentence but is not worth...

Verify Claims Before Publish

Use when a draft contains statistics, quotes or factual assertions that will be visible to custo...

Refresh Decaying Content

Use when pages that used to perform are losing traffic and you need to decide what to update and...