Critique a draft
Gives honest, ranked feedback on any draft across purpose, structure, argument, clarity and voice without rewriting it, and ends with the three changes that would matter most.
Useful critique is a diagnosis, not a rewrite. It judges the draft against what it is trying to do for a specific reader, ranks problems by how much they get in the way of that, points to exactly where they are, and explains the effect on the reader so the writer can fix it in their own voice. Unhelpful critique is the opposite: twenty equal-weight comments, line edits on paragraphs that should be cut, vague praise ("flows well"), or a polite verdict that hides the one structural problem that matters.
Critique this draft at depth.
- If the draft is empty, ask for it and stop. If the purpose or reader is vague, state the reading you are assuming in one line under Verdict and continue.
- Read it once as the target reader would, at their speed. Write down in one sentence what that reader would take away. Compare it with the purpose. The gap between the two is usually the most important finding.
- Assess five dimensions, adapting them to the genre:
- Purpose and fit: does it do its job for this reader, at the right length, in the right form?
- Structure: is the main point where this reader needs it; does each section earn its place; is anything missing or in the wrong order?
- Argument and support: are claims specific and backed; are obvious objections or questions left open? For narrative or personal writing, read this as story, stakes and payoff.
- Clarity: are there passages a reader could misread, undefined terms, or overlong sentences?
- Voice and tone: does it sound like a person, at the right register for this reader, consistently?
- For each issue, give: where it is (section, paragraph number or the first few words quoted), what the problem is, its effect on the reader, and the direction of a fix. Describe the fix; do not write the replacement passage.
- Rank every issue: Blocking (it stops the draft doing its job), Major (it weakens it noticeably) or Minor (polish).
- Scope by depth:
- quick: the three to five highest-ranked issues only;
- standard: every Blocking and Major issue, and up to five Minor ones;
- deep: everything in standard, plus paragraph-by-paragraph notes and recurring sentence-level patterns, each with one example quoted from the draft.
- Name two or three specific strengths the writer should keep through revision.
- Be honest. If the draft is not ready, say so plainly; if it is ready, say so and do not manufacture problems to fill the format.
- Separate problems from preferences. If something is a matter of taste, label it as such or leave it out.
- Do not rewrite sentences or paragraphs. Short illustrations of a pattern ("for example, the three sentences starting 'It is…'") are fine.
- Do not correct the facts or the opinion unless something is clearly wrong or unsupported; then flag it as "check".
- Do not comment on grammar or typos unless they would cost the writer credibility with this reader; then group them as one Minor issue.
Verdict
Two or three sentences: what the draft does now, what it needs to do, and its state: ready, close, needs revision, or needs rethinking.
What works
Two or three bullets, each specific and quoted or located.
Issues
A numbered list ordered by rank. Each item: [Blocking | Major | Minor] Dimension: where, then the problem, the effect on the reader, and the direction of the fix in two or three sentences.
Three changes that matter most
Three numbered sentences, each an action the writer can take next, in order of impact. If fewer than three changes are worth making, list only those and say so.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Editing
- level
- Beginner
- made for
- Writer / author, Student, Anyone, personal use, Editor
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install critique-draft --target claude-codenpx skills add hermes-hq/hodios-dist --skill critique-draft -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of EditingEdit a draft for structure
Edits a non-fiction draft at the structural level, covering argument, order, misplaced and missing sections, with a reverse outline and a prioritised revision plan instead of line edits.
edit-for-structureStrengthen the argument in a draft
Revises a proposal, essay or memo to be more persuasive for its reader by sharpening claims, adding prompts for missing evidence and answering objections, without hype.
strengthen-argument-in-draftTighten prose
Tightens prose by cutting filler, redundancy and weak verbs toward a target reduction while keeping the author's voice, meaning and necessary qualifiers, and reports what it cut.
tighten-proseLine-edit prose
Line-edits fiction or non-fiction prose for rhythm, precision, word choice and sentence variety while preserving the author's voice, showing each edit with a brief reason and the habits behind them.
line-edit-proseEditor
Editor who serves the reader and the author's intent, edits at the right level with structure before lines, and explains every change so the author can accept, reject or learn from it.
editorProofread a text
Corrects grammar, spelling, punctuation and consistency errors in the chosen English variety, preserving the author's voice, and lists each change with the rule behind it.
proofread-text