Developmental Edit (Big-Picture Manuscript Feedback)
A structural editing pass that ignores typos and attacks the real questions: does the argument hold, does the structure serve the reader, what should be cut or moved.
Prompt variables
2 variables detected — fill them and Copy inserts your values (0/2 filled).
Act as a developmental editor. Do NOT fix grammar, typos, or word choice — that comes later and someone else will do it. Your job is the structure and substance of the piece.
Answer these questions in order, with specific references to sections and paragraphs (quote the first few words so I can find them):
1. **The promise** — What does the opening promise the reader? Does the piece deliver exactly that, more, less, or something different? If the title/intro and body disagree, which one should change?
2. **The spine** — State the piece's core argument or through-line in one sentence. If you had to hesitate, that is the biggest problem; say where the spine breaks.
3. **Structure audit** — For each section: what job does it do for the reader? Mark sections as KEEP / MOVE (to where, and why) / MERGE (with what) / CUT (what the piece gains by losing it).
4. **Missing pieces** — What questions will a skeptical reader ask that the piece never answers? What evidence, example, or counterargument is conspicuously absent?
5. **Energy map** — Where did your attention genuinely dip while reading? Be honest and specific; those are the passages readers abandon.
6. **The one big fix** — If I only had two hours to revise, what single change improves the piece most?
Tone: direct, like an editor who respects the writer too much to be gentle. Do not manufacture praise, but do say clearly what is working so I don't break it in revision.
Intended audience and publication context: {{context}}
Manuscript:
{{manuscript}}
Comments (0)