Recently Written · git

ai-config

One canonical AI agent config (rules, skills, MCP servers) rendered into Claude Code, Codex, Copilot CLI and Antigravity by acsync

git clone https://github.com/equwal/ai-config

Log | Files | Refs


skills/impactful-writing/references/revision-frameworks.md (13564 bytes)

1 # Revision Frameworks and Editing Science
2 
3 Research-backed processes for transforming drafts into impactful content.
4 
5 ## Contents
6 - The Four-Level Editing System
7 - Revision Strategy Research
8 - The Conciseness Pass
9 - Active Voice Conversion
10 - Before/After Case Studies
11 - Self-Editing Techniques
12 - Common Revision Mistakes
13 
14 ## The Four-Level Editing System
15 
16 ### Overview
17 
18 Professional editors work through four distinct levels, never mixing concerns:
19 
20 | Level | Focus | Time Investment |
21 |-------|-------|-----------------|
22 | 1. Developmental | Structure, content, argument | 30-50% |
23 | 2. Line | Style, clarity, flow | 25-35% |
24 | 3. Copy | Grammar, consistency, facts | 20-30% |
25 | 4. Proofreading | Typos, formatting | 10-15% |
26 
27 **Critical principle**: Work through levels sequentially. Fixing typos before addressing structure wastes time.
28 
29 ### Level 1: Developmental Editing
30 
31 **Focus**: Big-picture organization, narrative flow, argument structure
32 
33 **Questions to ask:**
34 - What is the core message? (Write it in one sentence)
35 - Does every section advance this message?
36 - Is information in logical order?
37 - Are there gaps in logic or evidence?
38 
39 **Technique**: Reverse outline
40 - After drafting, outline what you wrote
41 - Each paragraph = one bullet
42 - Gaps and redundancies become visible
43 
44 ### Level 2: Line Editing
45 
46 **Focus**: Sentence-level improvements, paragraph flow, voice consistency
47 
48 **Questions to ask:**
49 - Is this the clearest way to say this?
50 - Can I say this in fewer words?
51 - Does each paragraph have one clear focus?
52 - Are transitions smooth?
53 
54 **Technique**: Read aloud
55 - Unclear passages trip your tongue
56 - Run-on sentences make you gasp for breath
57 - Awkward phrasing becomes obvious
58 
59 ### Level 3: Copyediting
60 
61 **Focus**: Grammar, punctuation, style guide adherence, fact-checking
62 
63 **Questions to ask:**
64 - Is this grammatically correct?
65 - Is it consistent with prior usage?
66 - Are facts and citations accurate?
67 
68 **Technique**: Separate passes for different concerns
69 - One pass for punctuation
70 - One pass for consistency
71 - One pass for facts
72 
73 ### Level 4: Proofreading
74 
75 **Focus**: Typos, formatting, layout issues
76 
77 **Questions to ask:**
78 - Are there any remaining errors?
79 - Is formatting consistent?
80 - Do all links work?
81 
82 **Technique**: Read backwards
83 - Forces focus on individual words
84 - Prevents brain from "filling in" expected text
85 - Catches typos the eye normally skips
86 
87 ## Revision Strategy Research
88 
89 ### Graham & Perin Meta-Analysis (2007)
90 
91 Analysis of 123 studies with 154 effect sizes:
92 
93 | Intervention | Effect Size |
94 |--------------|-------------|
95 | Strategy instruction | 0.82 (highest) |
96 | Sentence combining | 0.50 |
97 | Process writing | 0.32 |
98 | Grammar instruction | -0.32 (negative) |
99 
100 **Key insight**: Teaching explicit revision strategies has nearly triple the impact of teaching grammar rules.
101 
102 ### What "Strategy Instruction" Means
103 
104 The most effective approach combines:
105 1. **Cognitive strategies**: Planning, organizing, self-regulation
106 2. **Metacognitive strategies**: Self-assessment, reflection
107 3. **Procedural knowledge**: Specific techniques to apply
108 
109 **Implication**: Having a revision process matters more than knowing grammar rules.
110 
111 ### Timing Research
112 
113 Studies show separating drafting from editing improves quality:
114 - Self-assessment before and after revision improves both self-efficacy and writing
115 - 24-hour gap between drafting and editing recommended (cognitive refresh)
116 - "Kill your darlings" easier with time distance
117 
118 ## The Conciseness Pass
119 
120 ### Scott Hotaling's Framework (Limnology and Oceanography Letters, 2020)
121 
122 Three types of filler that reduce conciseness:
123 
124 **1. Qualifiers (adverbs)**
125 - Examples: quickly, extremely, frequently, very, really
126 - Impact: Often add zero information
127 - Fix: Remove entirely in most cases
128 
129 **2. Prepositional phrase chains**
130 - Examples: "in this case," "among other things," "on the other hand"
131 - Impact: Make sentences jumbled and unclear
132 - Fix: Replace multi-word phrases with single words
133 
134 **3. Overused transitions**
135 - Examples: however, meanwhile, thus, furthermore
136 - Impact: Create verbal clutter when overused
137 - Fix: Remove extraneous transitions, combine sentences
138 
139 ### Common Wordy Phrases
140 
141 | Wordy | Concise | Words Saved |
142 |-------|---------|-------------|
143 | due to the fact that | because | 4 |
144 | in order to | to | 2 |
145 | at this point in time | now | 4 |
146 | in the event that | if | 3 |
147 | with regard to | about | 2 |
148 | for the purpose of | to | 3 |
149 | in spite of the fact that | although | 5 |
150 | it is important to note that | (delete entirely) | 6 |
151 | the reason why is that | because | 3 |
152 | until such time as | until | 3 |
153 
154 ### Unnecessary Lead-Ins
155 
156 | Cut This | Keep This |
157 |----------|-----------|
158 | "It is worth noting that the data shows..." | "The data shows..." |
159 | "In terms of the findings, we see that..." | "We found..." |
160 | "As far as the analysis is concerned..." | "The analysis..." |
161 | "With respect to the issue of..." | (State the issue directly) |
162 
163 ### Word Simplification
164 
165 | Complex | Simple | Syllables Saved |
166 |---------|--------|-----------------|
167 | utilize | use | 2 |
168 | commence | start | 1 |
169 | terminate | end | 2 |
170 | demonstrate | show | 2 |
171 | facilitate | help | 3 |
172 | subsequently | later | 2 |
173 | approximately | about | 3 |
174 | endeavor | try | 2 |
175 | ascertain | find out | 1 |
176 | implement | do, use | 2 |
177 
178 ### Compound Effect
179 
180 Small edits compound across documents:
181 - 8,000-word document
182 - 50 phrase simplifications (average 3 words each)
183 - 150 words saved
184 - 10-30% length reduction possible
185 
186 ## Active Voice Conversion
187 
188 ### Identification
189 
190 Passive voice pattern: form of "to be" + past participle
191 
192 | Passive Indicator | Example |
193 |-------------------|---------|
194 | is/was + past participle | "was written" |
195 | are/were + past participle | "were found" |
196 | has/have been + past participle | "has been completed" |
197 | will be + past participle | "will be reviewed" |
198 
199 ### Conversion Process
200 
201 1. Identify the true actor (who/what performs the action)
202 2. Make the actor the subject
203 3. Use active verb form
204 
205 **Examples:**
206 
207 | Passive | Active |
208 |---------|--------|
209 | The report was written by the team | The team wrote the report |
210 | Errors were found in the code | We found errors in the code |
211 | The meeting was scheduled for 3pm | I scheduled the meeting for 3pm |
212 | A decision was made to proceed | The board decided to proceed |
213 | The feature has been implemented | We implemented the feature |
214 | Concerns were raised about costs | Stakeholders raised concerns about costs |
215 
216 ### When to Keep Passive
217 
218 Keep passive voice only when:
219 - **Actor unknown**: "The window was broken" (no one knows by whom)
220 - **Actor irrelevant**: "The samples were collected" (focus on samples, not collector)
221 - **Object emphasis**: "Three bugs were fixed" (emphasis on bugs)
222 - **Hedging appropriate**: "Mistakes were made" (deliberately vague)
223 
224 **Default**: Convert to active unless specific reason to keep passive.
225 
226 ## Before/After Case Studies
227 
228 ### Case Study 1: Legal Court Form
229 
230 **Original** (complex):
231 - Average comprehension: 61%
232 - Sentence length: 28 words average
233 
234 **Revised** (plain language):
235 - Average comprehension: 81% (+33%)
236 - Sentence length: 16 words average
237 - Length: 40% shorter
238 
239 **Changes made:**
240 - Sentence length reduced from 28 to 16 words
241 - Legal jargon removed: "hereinafter," "aforementioned," "pursuant to"
242 - Active voice throughout
243 - Clear headings and white space
244 - Steps listed numerically
245 
246 ### Case Study 2: Judicial Opinion
247 
248 **Original:**
249 > The plaintiff commenced an action in this Court seeking declaratory relief with respect to the issue of whether or not the defendant insurance company has an obligation under the applicable policy provisions to provide coverage for the injuries sustained by the plaintiff in the accident which is the subject matter of this litigation.
250 
251 (51 words, one sentence)
252 
253 **Revised:**
254 > Robert Wills was injured when someone fired shots toward his car, causing him to swerve into a tree. He filed a declaratory-judgment action to determine whether State Farm had to pay him uninsured-motorist benefits.
255 
256 (35 words, two sentences)
257 
258 **Results:**
259 - 61% of lawyers preferred revised version
260 - Rated 7/10 vs 6/10
261 
262 ### Case Study 3: Technical Documentation
263 
264 **Before:**
265 > In order to facilitate the implementation of the authentication functionality, it will be necessary for developers to utilize the OAuth2 library which has been provided in the dependencies folder, ensuring that the appropriate configuration parameters have been set in accordance with the specifications outlined in the configuration documentation.
266 
267 (53 words)
268 
269 **After:**
270 > To add authentication, use the OAuth2 library in the dependencies folder. Set the configuration parameters as described in config.md.
271 
272 (20 words)
273 
274 **Improvement:**
275 - 62% fewer words
276 - Same information
277 - Clearer action steps
278 
279 ### Case Study 4: Email Communication
280 
281 **Before:**
282 > I am writing to follow up with you regarding the matter we discussed in our previous meeting concerning the upcoming project deliverables. As we discussed, it would be beneficial for us to schedule a time to meet in order to review the current status of the project and to discuss any potential issues that may need to be addressed prior to the deadline.
283 
284 (68 words)
285 
286 **After:**
287 > Can we meet this week to review the project status before the deadline? I want to address any issues early.
288 
289 (20 words)
290 
291 **Improvement:**
292 - 70% fewer words
293 - Clear action requested
294 - Specific timeline
295 
296 ## Self-Editing Techniques
297 
298 ### Technique 1: The "So What?" Test
299 
300 **Application**: After each paragraph, ask "So what?"
301 
302 If you can't answer clearly, the paragraph needs revision.
303 
304 **Example:**
305 > "The system uses a microservices architecture."
306 
307 So what?
308 
309 > "The system uses a microservices architecture, so you can update individual components without redeploying everything."
310 
311 ### Technique 2: One Idea Per Sentence
312 
313 **Application**: If sentence contains "and," "but," or "however," consider splitting.
314 
315 **Before:**
316 > "The API is fast and reliable but requires authentication and uses rate limiting."
317 
318 **After:**
319 > "The API is fast and reliable. It requires authentication and uses rate limiting."
320 
321 ### Technique 3: Front-Load Subject and Verb
322 
323 **Application**: First 7-8 words should contain subject and main verb.
324 
325 **Before:**
326 > "In order to understand the implications of the proposed changes to the system architecture, developers need to review the documentation."
327 
328 **After:**
329 > "Developers need to review the documentation to understand the proposed changes."
330 
331 ### Technique 4: The Grandmother Test
332 
333 **Application**: Would a non-expert understand the main point?
334 
335 If not, simplify until they would.
336 
337 ### Technique 5: The Cut Test
338 
339 **Application**: For each sentence, ask "Can I remove this without losing meaning?"
340 
341 If yes, remove it.
342 
343 ### Technique 6: Kill Your Darlings
344 
345 **Application**: Identify your favorite phrases. Evaluate them critically.
346 
347 Writers overvalue their clever phrasing (overconfidence bias). Favorite phrases often serve the writer's ego, not the reader's understanding.
348 
349 ### Technique 7: Convert Nominalizations
350 
351 **Application**: Change noun phrases back to verbs.
352 
353 | Nominalization | Verb Form |
354 |----------------|-----------|
355 | made an investigation into | investigated |
356 | reached a conclusion about | concluded |
357 | gave consideration to | considered |
358 | performed an analysis of | analyzed |
359 | made a decision to | decided to |
360 
361 ### Technique 8: The 24-Hour Rule
362 
363 **Application**: Wait 24 hours between drafting and editing.
364 
365 Cognitive refresh reveals:
366 - Unclear passages you thought were clear
367 - Redundancies you missed
368 - Missing transitions you assumed were there
369 
370 ## Common Revision Mistakes
371 
372 ### Mistake 1: Editing While Drafting
373 
374 **Problem**: Interrupts creative flow, wastes time on text you'll delete
375 **Fix**: Draft first, edit later (separate sessions)
376 
377 ### Mistake 2: Starting with Grammar
378 
379 **Problem**: You'll fix sentences you later delete
380 **Fix**: Work developmental → line → copy → proof
381 
382 ### Mistake 3: Over-Reliance on Tools
383 
384 **Problem**: Tools don't understand context or meaning
385 **Fix**: Use tools for detection, not decision-making
386 
387 ### Mistake 4: Accepting All Suggestions
388 
389 **Problem**: Not every "issue" is actually a problem
390 **Fix**: Evaluate each suggestion against context and purpose
391 
392 ### Mistake 5: Ignoring Reader Feedback
393 
394 **Problem**: Authors can't see their own blind spots
395 **Fix**: Seek external feedback; it correlates with improvement
396 
397 ### Mistake 6: Single-Pass Revision
398 
399 **Problem**: Different issues require different attention
400 **Fix**: Multiple passes, each with focused purpose
401 
402 ## Quantified Improvement Targets
403 
404 **Based on research synthesis, effective revision should achieve:**
405 
406 | Metric | Target |
407 |--------|--------|
408 | Word reduction | 10-30% from first to final draft |
409 | Average sentence length | 15-20 words |
410 | Maximum sentence length | 25 words |
411 | Passive voice | <10% of sentences |
412 | Adverbs (qualifiers) | Reduce by 50-70% |
413 | Multi-syllable words | Reduce by 20-30% where possible |
414 | Readability (Flesch) | 60-70 for general audience |
415 
416 ## Revision Workflow Summary
417 
418 ### Phase 1: Macro (30-40% of time)
419 - Structure and organization
420 - Core message clarity
421 - Information hierarchy
422 
423 ### Phase 2: Clarity (25-35% of time)
424 - Sentence simplification
425 - Active voice conversion
426 - Jargon elimination
427 
428 ### Phase 3: Conciseness (15-20% of time)
429 - Word elimination
430 - Phrase simplification
431 - Redundancy removal
432 
433 ### Phase 4: Polish (10-15% of time)
434 - Grammar and punctuation
435 - Consistency check
436 - Final proofreading