Writing & Editing
Get Structural Feedback on a Draft
Reviews a draft like a developmental editor: is the argument clear, ordered and supported? Gives ranked feedback without rewriting it.
- Customizable fields
- 6 fields
Writing & Editing
Sorts scattered notes into an article outline with a clear argument, a logical order and a list of what is still missing.
Designed for general-purpose AI assistantsPublished November 2026
Fill in the fields and the prompt updates. What you type stays in this page and is never saved or sent.
I have rough notes for an article. Help me find the argument in them and organize it into an outline. Do not write the article.
Working topic: {{topic}}
Audience and what they already know: {{audience}}
What I want the reader to think or do afterwards: {{reader outcome}}
Format and approximate length: essay, 1,200 words
My notes, in the order I wrote them:
{{notes}}
Do this:
1. State the central point you can find in my notes, in one sentence, and tell me how confident you are that it is what I meant. If you see two or more possible arguments, list them and ask me to choose before continuing.
2. Group the notes into themes. Show which of my notes belong to which theme by quoting a few words from each.
3. Propose an outline with a working title, an opening that establishes why the reader should care, the sections in a logical order, and an ending that delivers the reader outcome. Under each section write one line on its purpose and list which of my notes feed it.
4. Notes I did not use, with a short reason for each. They may be off topic, repeated or save-for-later.
5. Gaps: places where the argument needs an example, evidence, a definition, a counterargument or a transition that my notes do not provide. Ask me for them as questions.
6. The weakest link in the argument as it stands, and how I might strengthen it.
Rules: do not add claims, facts or examples that are not in my notes. If a section needs one, mark it [needed] and say what kind. Preserve my wording for key phrases where it is better than a generic one.4 required fields are empty and will stay as a {{placeholder}} in the copied text.
Illustrative only. Real answers depend on your input and the assistant you use.
Central point (confidence: medium): Small teams adopt too many tools because each tool solves a real problem, and the cost only shows up as coordination overhead. I also see a second possible argument: "choose tools by switching cost". Which did you mean? Themes: tool sprawl (notes 1, 4, 9), hidden coordination cost (notes 2, 6: "meetings about the meetings"), how to decide (notes 3, 7, 8). Outline Title (working): The Hidden Cost of Every New Tool 1. Opening: the team that added a tool a month (note 1). Purpose: make the reader recognize the problem. 2. Why each tool seems fine alone (notes 4, 9). 3. Where the cost actually shows up (notes 2, 6). [needed: one concrete example with real numbers] 4. A simple test before adding a tool (notes 3, 7). 5. Ending: what to ask on Monday. Not used: note 5 (pricing of one vendor; off topic), note 10 (a quote, save for later). Gaps: What is the strongest argument for adding tools anyway? Weakest link: Section 3 asserts cost without evidence.
Choosing the argument is the hard part of writing, and it is the part assistants usually skip. This prompt makes the question explicit.
Keep the "not used" list. Many good articles started as notes that did not fit the first one.
If you disagree with the outline, say what is wrong with it and not just "try again". Specific objections lead to much better revisions.
Writing & Editing
Reviews a draft like a developmental editor: is the argument clear, ordered and supported? Gives ranked feedback without rewriting it.
Writing & Editing
Condenses a long report or proposal into a one-page executive summary that leads with the decision needed and the evidence for it.
Writing & Editing
Explains a technical idea to a specific non-expert audience using one analogy, plain terms and an honest note on where the analogy breaks.