developmental-edit
/developmental-edit
Gives big-picture feedback on a draft as a prioritized edit letter about its point, structure, gaps, cuts, and where readers get lost, without line edits. Use when someone asks for "feedback on my draft", "a structural edit", "what's not working", "is this any good", or has a full draft of an essay, personal statement, article, report, chapter, or story and wants to know what to fix first.
- Author
- scratchpad-sh ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Gives big-picture feedback on a draft as a prioritized edit letter about its point, structure, gaps, cuts, and where readers get lost, without line edits. Use when someone asks for "feedback on my draft", "a structural edit", "what's not working", "is this any good", or has a full draft of an essay, personal statement, article, report, chapter, or story and wants to know what to fix first.
Triggers from the description
Original author description
Gives big-picture feedback on a draft as a prioritized edit letter about its point, structure, gaps, cuts, and where readers get lost, without line edits. Use when someone asks for "feedback on my draft", "a structural edit", "what's not working", "is this any good", or has a full draft of an essay, personal statement, article, report, chapter, or story and wants to know what to fix first.
How it works
- When to use it
- What to ask for
- How to do it
- The format
- Example
- Pitfalls
- Saving the draft
SKILL.md preview
---
name: developmental-edit
description: Gives big-picture feedback on a draft as a prioritized edit letter about its point, structure, gaps, cuts, and where readers get lost, without line edits. Use when someone asks for "feedback on my draft", "a structural edit", "what's not working", "is this any good", or has a full draft of an essay, personal statement, article, report, chapter, or story and wants to know what to fix first.
---
# Developmental edit
A developmental edit looks at a draft the way a reader experiences it: as a
whole. It asks whether the piece knows what it is saying, whether the parts
come in an order that builds, what the reader needs and does not get, and what
the writer included because they love it rather than because the piece needs
it. Book and magazine editors deliver this as an edit letter, and that form is
worth keeping: a letter forces the editor to rank problems and explain them,
instead of scattering a hundred comments of equal weight through the margins.
This skill does not touch the sentences: line edits on a draft whose structure
is about to change are wasted work. The writer decides what to take; the
letter's job is to make the most important problems impossible to miss.
## When to use it
- A complete first or second draft of an essay, article, report, chapter,
grant proposal, or short story.
- The writer senses something is wrong but cannot name it.
- Before investing in polish, to check the piece is the right piece.
For sentence-level cuts, use `tighten-prose`; for errors, `proofread`. To
build structure before a draft exists, use `outline-first`. For fiction scenes
specifically, `fiction-scene` and `dialogue-polish` go deeper.
## What to ask for
- **The draft**, all of it. Partial drafts get partial verdicts; say so.
- **What the writer intends**: the point, the reader, and where it will be
published or submitted. Default: infer them from the draft, and state your
inference, because a mismatch between intent and draft is often the main
finding.
- **What worries them**, if anything. Step 9 answers it by name.
- **Any length limit** (a word count for an application or a journal). Under
a limit, every fix that adds material must say what to cut to pay for it.
## How to do it
1. **Read the whole draft without stopping to fix anything.** Note where your
attention drifted, where you were confused, where you were moved or
convinced, and where you wanted something that did not come.
2. **State the point back.** In one sentence, write what the draft is saying
as a reader would take it. Compare it with the writer's intent. If they
differ, or you cannot write the sentence, that is finding number one.
3. **Map the structure.** List each section or major paragraph with what it
does (sets up, argues, illustrates, digresses, repeats). This "reverse
outline" shows sections that repeat, sections in the wrong order, and
sections doing nothing.
4. **Check the reader's path.** Where does a reader need background they do
not have? Where does a claim arrive before its support? Where is the
reader's obvious objection unanswered? Where does the piece lose momentum?
5. **Find what is missing.** Evidence for the central claim, an example that
makes an abstraction concrete, a stake (why this matters), a turn or
payoff, an ending that does something.
6. **Find what to cut.** Material that is true and interesting but not about
this piece. Say it kindly and plainly; this is usually the writer's
favorite part.
7. **Note what works.** Specifically, so the writer keeps it through revision:
"The scene in the parking lot is the heart of this; build toward it."
8. **Rank.** Sort every issue into three tiers: must fix (the piece does not
work without it), should fix (it would be noticeably better), and consider
(taste). Most letters have one to three must-fixes. If you have eight, you
have not found the root problem yet. If you have none, say so and leave
the section out rather than promoting a should-fix to fill it.
9. **Write the letter.** Lead with the overall read, then the ranked issues,
each with where it shows up, why it matters to a reader, and one or two
possible fixes (as options, not orders). Answer the writer's stated worry
by name, in the overall read or under the issue it belongs to. End with a
suggested revision order.
10. **Never rewrite the draft or add content.** You may quote the draft to
point at something. You may suggest the kind of material that is missing
("a specific case would help here"), but not invent it.
## The format
```markdown
# Edit letter: [Title of draft]
**What I think it's saying:** [One sentence]
**What you said you intend:** [One sentence, or "not stated"]
**Overall:** [Two or three sentences: the big read, what works, the main issue]
## What's working
- [Specific strength, with where it is]
## Must fix
1. **[Issue in a few words]**
[Where it shows up. Why it matters to the reader. Possible fixes.]
## Should fix
2. **[Issue]**
[...]
## Consider
- [Smaller, taste-level suggestion]
## Structure as it stands
1. [Section]: [what it does]
2. [Section]: [what it does]
## Suggested revision order
1. [First change, because others depend on it]
2. [...]
```
## Example
Input: a 1,800-word essay draft titled "Why I quit running", which spends its
first 1,000 words on the writer's marathon training, then 300 on an injury,
then 500 on discovering they enjoy swimming more. Identity comes up only in
the last 200 words, around the line "I forgot to count" during a first lap in
the pool. The writer says it is about "letting go of an identity".
```markdown
# Edit letter: Why I quit running
**What I think it's saying:** I got injured and found I like swimming better.
**What you said you intend:** an essay about letting go of an identity.
**Overall:** The writing is vivid and the swimming section is the best thing
here. But the identity question, which is your real subject, barely appears;
most of the essay is training log.
## What's working
- The paragraph about the first lap in the pool, where you "forgot to count".
That is the essay's turn, and the only place identity is felt, not stated.
## Must fix
1. **The real subject arrives too late.**
Identity appears in the last 200 words. Readers spend 1,000 words thinking
this is a running essay. Options: open with the moment you realized you no
longer called yourself a runner; or cut training to two scenes that show
how much the identity meant.
## Should fix
2. **The injury is summarized, not felt.**
It is the hinge of the piece but gets one paragraph of facts. A scene here
(the moment you knew) would carry the loss the essay is about.
## Consider
- The title promises a reason. "Forgetting to count" might suit the essay you
are actually writing.
## Structure as it stands
1. Marathon training (1,000 words): sets up the running identity, at length.
2. The injury (300 words): the hinge, told as summary.
3. Swimming (500 words): the turn, and the only place identity is felt.
## Suggested revision order
1. Decide the opening (it sets what the training section must do).
2. Cut training to what serves identity.
3. Expand the injury into a scene.
```
## Pitfalls
- **Line editing.** Word-choice comments pull attention from the structure.
- **Equal weight to everything.** A list of twenty notes leaves the writer to
rank them. Rank them yourself.
- **Prescribing one fix.** Offer options. The writer knows things about the
material you do not.
- **Only problems.** Writers revise toward what you tell them is working.
Name it specifically.
- **Reviewing the piece you would write.** Judge it against what the writer is
trying to do, and flag a mismatch only when the draft does not achieve it.
- **Inventing content in suggestions.** "Add the statistic about X" assumes
a fact. Say "evidence for this claim would help" instead.
## Saving the draft
If a notes app is connected (for example the Scratchpad connector, or any notes
tool you can call), offer to save the draft there as a new note with a clear,
searchable title, or to add it to an existing note the person names. Otherwise,
give the whole draft as one Markdown block that pastes cleanly into any notes
app. Saving the edit letter beside the draft lets the next revision be checked
against it.
Versions
The database has no other skills named developmental-edit.
Database snapshot: 13.11.2026 · package version d8f8987bcaba (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100personal-essay
Helps write a personal essay from real memories by finding the subject under the story, balancing scene and reflection, and finding an ending that lands. Use when someone wants to "write about something that happened to me", is drafting a personal essay, memoir piece, or college… - 100editor
Use when a task needs the judgment of a manuscript or content editor — diagnosing structural problems in a draft, writing a developmental edit letter, running a line-edit or copyedit pass, deciding what to cut to hit a word-count target, or triaging conflicting author feedback. - 90statement-of-purpose
Use when the user mentions an SOP, statement of purpose, personal statement, grad-school application essay, grad school essay, admissions essay, motivation letter or letter of intent (treated identically), research statement for a graduate application, an MBA or business-school… - 100long-form-editor
Edit a long draft in three passes: developmental (argument and structure), line (paragraph and sentence clarity) and copy (consistency and errors), with a prioritised change list and an edited version. Use when a student, writer or professional has an essay, article, report,…