Dictating a Prompt to Critique Your Own Writing

A spoken method for critiquing your own drafts with evidence and one clear change.

Voiskey Voiskey Team
Voice PromptingChatGPT WorkflowDictating Prompt Critique

Separate the Writer from the Critic

Dictating a Prompt to critique your own writing fails when the writer and the critic share one voice. Start by separating them: say who the draft is for, what it must accomplish, and what the critic should ignore. Then ask the assistant to respond as a reviewer with a specific job, not as a cheerleader. Include the draft and the brief in the same request. The critic should not rewrite the whole piece; it should identify the two or three places where the draft fails its purpose. This separation is what makes self-critique useful instead of a second draft in disguise.

Write the critique brief before you read the draft again. A brief has four parts: the reader, the purpose, the constraints, and the standard. The reader is who will act on the document. The purpose is the decision or action it must produce. The constraints are length, format, and any fixed language. The standard is the bar the draft must meet. Read the brief aloud, then read the draft aloud. The gap between what the brief asks for and what the draft delivers is your critique agenda, and it is more reliable than a general feeling that something is off.

Give the critic permission to be specific and unpleasant. Ask for the weakest paragraph, the sentence that can be cut without loss, and the claim with the least support. A prompt that asks for gentle feedback usually returns praise with a small suggestion at the end. Say plainly that you want the draft treated as a working document, not as a personal statement. Then set a limit: three problems, ranked by effect on the reader. A ranked list is actionable; a page of observations is not. Keep the critique in writing so you can compare it with your own read.

Decide in advance what you will not change. Some choices are deliberate: a term your audience expects, a structure required by a template, or a story you have decided to tell. List these non-negotiables in the brief so the critique does not spend its energy on them. Ask the critic to flag any place where a deliberate choice genuinely confuses the reader, but not to relitigate taste. This boundary keeps the critique focused on defects you can fix and protects the voice of the draft. Without it, self-critique tends to sand away the parts that make the writing yours.

Name the Standard the Critique Should Apply

Name the standard the critique should apply. Clarity, structure, evidence, and tone are four useful dimensions, and each one needs a test. Clarity: can a reader state the point after one reading? Structure: does each section follow from the one before? Evidence: is every claim supported? Tone: does the register match the reader? Ask the critic to score each dimension and quote the sentence that justifies the score. A standard with tests produces a critique you can act on; a request for general feedback produces a mood report. Keep the four tests in the brief so the score has a basis.

Choose two dimensions to prioritize, not four. A draft that is structurally sound but tonally wrong needs a different critique from one that is well written but unsupported. Say which two matter most for this draft and why. Ask for the other two to be noted briefly but not analyzed. Prioritization is what turns a critique into a plan. When everything is a problem, nothing gets fixed before the deadline. Review the two dimensions after each revision; if the draft has improved, promote the next dimension to the top of the list. Write down why the two were chosen so the next draft can reuse the reasoning.

Define severity levels so the critique is sortable. Use three: blocking, meaning the reader cannot act; material, meaning the reader may misread; and polish, meaning the reader notices but is not misled. Ask for every finding to carry a level and a location. Then sort the findings by level before you read them. This simple structure prevents a comment about a comma from competing with a missing conclusion. It also tells you when to stop: when no blocking or material findings remain, the draft is ready for the audience, even if polish items remain. Say this rule out loud before you start editing, so the finish line is clear.

Ask for the critique to respect the genre. A memo, a proposal, a help article, and a personal essay are judged by different standards. Say the genre and the conventions the reader expects. A proposal needs a clear ask and a reason to approve; a help article needs steps in order and a way to check success. When you ask a critic to apply the wrong convention, the feedback punishes the draft for being what it is. Name the genre in the brief and ask the critic to state the convention it applied at the top of the response. If the convention is wrong for the genre, correct it before acting on any finding.

Ask for Evidence, Not Adjectives

Ask for evidence, not adjectives. Every finding should quote the sentence or name the section, explain the effect on the reader, and propose one fix. A comment such as the introduction is weak is not reviewable; a comment such as the first two paragraphs describe the history before stating the question, so the reader cannot tell why it matters is reviewable. Require the location, the effect, and the fix for each finding. This structure makes the critique slower to produce and much faster to use. It also makes disagreements concrete, because you can argue about a sentence rather than a vibe.

Ask the critic to read as the intended reader, not as a writing teacher. The intended reader has a decision to make and limited time. Ask what they would do after the first paragraph, where they would stop, and what they would ask. These answers reveal problems that grammar checks miss. When the critic slips into rules about style, bring it back to the reader. A sentence that breaks a rule but helps the reader is usually fine; a sentence that follows every rule and buries the point is not. Reader simulation is the most useful lens in self-critique.

Separate what is missing from what is wrong. Missing items include a claim with no evidence, a step with no owner, and a section with no conclusion. Wrong items include contradictions, broken references, and unsupported assertions. Ask for two lists, because they lead to different work: missing items need new material, wrong items need edits. Most critiques mix the two, and the writer then tries to edit their way out of a gap that requires research. Sorting the lists before you start is the fastest way to avoid rewriting the same paragraph three times. Keep the two lists separate in the document so the work stays visible.

Ask for the strongest counterargument to your main point. A critique that only finds weaknesses in prose misses the larger risk. Say the main claim and ask what a skeptical reader would say against it, with the evidence they would cite. Then decide whether the draft answers that objection. If it does not, add a sentence or a section. This question is uncomfortable and it is the one most likely to improve the argument rather than the style. Keep the counterargument in the critique notes so you can check whether the revision actually addresses it. If the objection still stands, either answer it or narrow the claim.

Apply One Change at a Time

Voiskey keeps the critique and the draft in the same place. Open the document, press the shortcut, and speak the critique brief and the questions you want answered. The polished text lands at the insertion point, so the critique sits next to the passage it concerns. Then read the draft aloud and dictate your own notes as you go. Because filler words and false starts are removed, the notes read like a review rather than a transcript. The workflow of speak, polish, type, and edit turns a read-through into a usable list of findings without leaving the document. Keep the brief at the top of the file so the critique has a visible standard.

Apply one change at a time. Pick the highest-severity finding, make the edit, and read the passage aloud again. If the change solves the problem, move to the next finding; if it creates a new problem, revert and try the proposed fix instead. One change per round keeps cause and effect visible. Batch edits hide which one helped and which one introduced a new issue. Record each change beside the finding. When the list is long, fix the blocking items first and schedule the polish for a later pass, or you will run out of time before the argument is sound.

Keep the version before the critique and the version after. Read both aloud and compare the first paragraph and the conclusion, which is where improvement shows fastest. Ask a colleague which version they would act on and why. If the revised version is clearer but flatter, you have edited the life out of it; restore one deliberate choice from the non-negotiables list. A critique should sharpen the draft, not homogenize it. Comparing versions is the only reliable way to see whether the change helped or merely made the text different. If the difference is invisible to a reader, revert the change and save the time.

Set a stop rule before you start. Two rounds of critique and revision are enough for most documents; a third round rarely changes the reader experience. Stop when no blocking or material findings remain, or when the deadline arrives, whichever comes first. Write down the remaining polish items and move on. Endless self-critique is a form of avoidance, and it produces a draft that is careful and late. The goal is a document the reader can act on, not a document that survives every possible objection. A document that answers the reader is finished; a document that answers every imagined critic never is.

Keep a Critique Brief for Recurring Drafts

Save the critique brief as a reusable template: reader, purpose, constraints, non-negotiables, standard, severity levels, and the questions you always ask. Keep it to one page. For each new draft, change the reader and the purpose and keep the rest. A fixed brief makes critiques comparable across documents and stops you from forgetting the counterargument question under deadline. Review it quarterly and remove questions that never produced a change. A small, tested brief is more useful than a comprehensive rubric you never finish. Print the template, keep it beside the draft during the read-through, and date the last revision.

Share the brief with your team and agree on the severity labels. The team plan offers shared vocabulary and workflows, so blocking, material, and polish mean the same thing to everyone. Store one annotated example that shows each level. When reviewers disagree, compare the example rather than the draft. This reduces the long arguments about whether a comment is important. Ask each reviewer to run the brief once before a review cycle. Shared language makes feedback faster to give and easier to accept, because the levels are not personal. Review the labels after each cycle and tighten any that caused confusion.

Voiskey supports more than one hundred languages and translation, so you can write in one language and ask for a critique in another, or ask for the critique in your first language and apply the changes to the draft yourself. Keep quoted sentences in the original language so the finding points to the exact text. Ask the critic to state which language it is judging, because conventions differ. Review translated findings with a fluent reader before acting on them. A critique in translation is useful for structure and argument; it is less reliable for idiom and rhythm. For a final polish, ask a native reader to review the edited draft.

Download Voiskey for Mac and Windows and run one real draft through the critique brief. Speak the reader, the purpose, and the two dimensions, then read the draft aloud and dictate your notes. Apply the highest-severity finding, keep both versions, and compare them the next morning. Add one question to the brief that you wish you had asked. Two drafts are enough to show whether the brief sharpens your writing or just adds a step. Keep the version that produces changes you would defend in front of the reader. Then run the same brief on a second draft and compare how long the critique takes.

FAQ s

Voiskey is an AI voice typing app. Press a shortcut, speak the reader, purpose, standard, and questions, and the text appears at the insertion point in the app you are using. Filler words, stutters, and self-corrections are removed, so the critique brief arrives as a clean set of instructions.

Yes. Open the draft, press the shortcut, and speak your notes as you read. Voiskey removes filler words, stutters, false starts, and self-corrections, and adapts punctuation and formatting, so the notes land at the insertion point as a readable review rather than a transcript.

Voiskey learns names, jargon, acronyms, and spelling preferences, so character names, product terms, and house style stay consistent across drafts and notes. Say them once as you dictate and the app keeps your spelling. Consistency matters in a critique, because a finding must point to the exact term.

Voiskey supports more than one hundred languages and translation. You can dictate the critique brief in one language and ask for findings in another, keeping quoted sentences in the original. Review the findings with a fluent reader before editing, since translated comments can blur idiom and rhythm.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and dictate a critique of your next draft.

Use it across macOS, Windows, iOS, and Android

Use it across