---
name: draft-roast
description: Roasts a piece of writing (email, Slack post, doc, one-pager, landing page) by measuring it with scripts and critiquing it for buried ledes, buzzwords, vague claims, long sentences, and missing asks. Use when the user asks to review, critique, roast, tighten, or sanity-check a draft before sending it. Do NOT use for writing a new draft from scratch, translation, or grammar-only proofreading.
allowed-tools: Bash(cat:*), Bash(wc:*), Bash(grep:*), Bash(tr:*), Bash(awk:*), Bash(sort:*), Bash(uniq:*), Bash(head:*)
---

# Draft Roast

## Context
Draft: !`cat draft.md 2>/dev/null || echo "no draft.md in this folder"`
Word count: !`cat draft.md 2>/dev/null | wc -w`
Opening lines: !`grep -v '^[[:space:]]*$' draft.md 2>/dev/null | head -2`
Longest sentences: !`cat draft.md 2>/dev/null | tr '\n' ' ' | tr '.?\041' '\n\n\n' | awk 'NF {print NF " words:" $0}' | sort -rn | head -3`
Buzzwords: !`grep -oiwE 'leverag(e|ed|ing)|seamless(ly)?|robust|synerg(y|ies)|cutting-edge|best-in-class|game-changer|revolutioniz(e|es|ing)|empower(s|ing)?|unlock(s|ing)?|streamlin(e|ed|es)|holistic|paradigm' draft.md 2>/dev/null | tr 'A-Z' 'a-z' | sort | uniq -c | sort -rn`
Hedge words: !`grep -oiwE 'just|really|very|actually|basically|quite|truly|potentially' draft.md 2>/dev/null | tr 'A-Z' 'a-z' | sort | uniq -c | sort -rn`
Passive voice: !`grep -oiwE '(is|are|was|were|be|been|being) [a-z]+ed' draft.md 2>/dev/null | head -20`
Longest paragraphs: !`awk 'BEGIN{RS=""} {print "paragraph " NR ": " NF " words"}' draft.md 2>/dev/null | sort -t: -k2 -rn | head -3`
Links: !`grep -nE 'https?://|\]\(' draft.md 2>/dev/null || echo "none found"`

If any script returns no output, skip that signal and note "no data available." Do not guess.

If the lines above show raw commands instead of output, you can't run scripts here. Ask the user to paste the draft, then do the counting yourself.

## Constraints
- Never be vague. Quote the exact sentence as evidence.
- Every finding must include: what's wrong, evidence, severity, fix (a rewritten line, not advice)
- Never rewrite the whole draft. Fix the worst lines only.
- Never flag grammar or spelling nits unless they change the meaning
- Maximum 7 findings, ordered by severity
- Only make findings backed by the text or the script output. Never invent facts about the product, the company, or the reader.
- Prioritize by what costs the reader most: a buried ask beats a stray buzzword

## Workflow
Work through these phases in order. Do not skip phases.
1. Read the script output. Summarize length, the opening, and the worst offenders.
2. Categorize findings by type (buried lede, missing ask, vague claim, jargon, length, tone). Score severity. Run self-assessment. Drop or flag weak findings.
3. Write the fixes. Run constraints checklist. Present final assessment.

## Self-Assessment
Rate each finding before presenting:
- Evidence quality (1-10): Is this backed by a quote or script output, or by inference?
- Severity accuracy (1-10): Will this hurt the reader, or is it just a style preference?
- Actionability (1-10): Could the author paste your fix in right now?

If any finding scores below 6 on evidence quality, drop it or flag as "needs investigation."
Show the scores for each finding so the reader can see your reasoning.

## Structure
1. One-line verdict (with overall score out of 10)
2. Top findings (max 7), each with: issue, evidence, severity, fix
3. Confidence summary (how many findings were high-confidence vs flagged)
4. One thing the draft does well