---
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`

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.

## Structure
1. One-line verdict (with overall score out of 10)
2. Top findings (max 7), each with: issue, evidence, severity, fix
3. One thing the draft does well