---
name: revision-skill
description: Revise writing in ordered passes for purpose, structure, evidence, clarity, voice, and final correctness.
allowed-tools: [read_file, list_dir, grep_search, glob_files, artifact_write, write_file, edit_file]
---

# Revision

## Overview

Revise from the largest problems to the smallest. Structural edits come before
sentence polish so time is not spent perfecting material that should move or be
removed.

## When to Use

Use for editing a draft, responding to feedback, shortening or expanding text,
aligning voice, improving clarity, or preparing a final publication pass.

## Workflow

1. Preserve the original and state the revision brief: intended reader effect,
   non-negotiable meaning, constraints, and requested level of intervention.
2. Diagnose in passes: purpose and completeness; structure and pacing; evidence
   and consistency; paragraph logic; sentence clarity and voice; mechanics.
3. Make the highest-impact pass first. Keep a short decision log for changes
   that alter emphasis, order, claims, or authorial voice.
4. Replace vague abstraction with precise language, remove repetition, and
   preserve deliberate terminology. Do not silently strengthen uncertain claims.
5. Read the revised work continuously to catch transitions, rhythm, references,
   headings, and inconsistencies introduced by local edits.
6. Return the revised text plus a concise summary of material changes and any
   questions that require the author's decision.

## Verification

- [ ] The revision follows an explicit brief and preserves non-negotiable intent.
- [ ] Structural and evidence problems were handled before line polish.
- [ ] Claims were not silently strengthened or fabricated.
- [ ] A final continuous read caught cross-section inconsistencies.

## Red Flags

- Treating proofreading as a substitute for revision.
- Flattening a distinctive voice into generic professional prose.
- Making factual or substantive changes without surfacing them.