writing-critique

Critique: diagnose a draft and report ranked findings without rewriting — the editorial letter. Use when a piece is finished, stuck, or 'something is off' and the user wants an honest review, feedback

SKILL.md

GitHub

Critique

Read-only. Report what is wrong, where, and what to fix first. The most common failure in critique is starting to fix before finishing the diagnosis — a fix at the top of the hierarchy erases findings below it, so find top-down before anyone touches anything.

  1. Read once whole. No notes on the first read; get the whole experience. Then state the spine — the one-sentence claim (nonfiction) or story engine (fiction) — or no spine found. A reader who cannot state it was not given one.
  2. Work the rubric as passes, in order — spine → structure → scene / paragraph → sentence → evidence (nonfiction) or embodiment (fiction). Early passes dominate: a scene that reads badly may be a structure problem wearing a sentence's clothes. Fiction pieces run references/rubric-fiction.md; essays and arguments run references/rubric-nonfiction.md. Run every test in each pass before moving on.
  3. For each finding, give four things: the location (quote the sentence or name the scene — no location, no finding), the named pattern, the reader cost (what a real reader feels or loses), and a severity: blocking (the piece fails without the fix), major, minor.
  4. Rank the three changes that would most improve the piece, biggest first, and say why each outranks the rest. If the piece is sound, say so and name its weakest point honestly — false balance helps no one.
  5. Do not rewrite, do not pad. A finding the reader will not feel is noise, not thoroughness. Report nothing you couldn't defend with a quote.

Handoffs when the user is ready to act: writing-revise for substance, writing-edit for sentences, writing-verify when the blocking findings are factual.