← Compound WritingCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Compound Writing
Snapshot Sep 30, 2026 · 23:16 UTC · version 2.4.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Revise prose at the sentence and word level while preserving voice, meaning, source accuracy, and useful weirdness. Use when the structure is stable and the user asks for a line edit, polish, tightening pass, or usable rewrite.",
"included_files": [],
"name": "cw-line-edit",
"skill_md_contents": "---\nname: cw-line-edit\ndescription: Revise prose at the sentence and word level while preserving voice, meaning, source accuracy, and useful weirdness. Use when the structure is stable and the user asks for a line edit, polish, tightening pass, or usable rewrite.\n---\n\n# Line Edit\n\n## Purpose\n\nA deep, rigorous pass for sentence- and word-level issues. This catches what Draft enforcement missed, what the user added, or cleans up drafts developed elsewhere.\n\nRead `../../references/context-contract.md` and load the relevant writer, project, publication, and platform voice sources before editing.\n\n## Entry Points\n\nThis skill can be invoked:\n1. After completing a developmental edit\n2. Directly by the user with any draft\n\n## What to Check\n\nApply a thorough review for:\n\n### Sentence Mechanics\n- Vary sentence length\n- Active voice (flag passive constructions)\n- Concrete nouns and verbs\n- Front-load sentences with important information\n\n### Things to Avoid\n- Hedge words (\"perhaps,\" \"maybe,\" \"somewhat,\" \"might\")\n- Correlatives and negative parallelisms (\"not X, but Y\")\n- Throat-clearing (delayed starts, excessive setup)\n- Echo statements (saying the same thing multiple ways)\n- Weasel words (\"some people say,\" \"studies show\" without citation)\n- Empty intensifiers (\"very,\" \"really,\" \"extremely\")\n- Cliché metaphors\n- Hyperbolic or overblown claims\n- Inflated language\n- Technical, business, or academic jargon\n\n### AI Tells\nRun `cw-ai-check` in its required order. When source material or earlier human drafts are available, scan for structural overcompletion before running the full lexicon. Flag and fix:\n- Stock openers (\"In today's fast-paced world...\")\n- AI-scent vocabulary (delve, leverage, utilize, pivotal, crucial)\n- Formal transitions (moreover, furthermore, additionally)\n- Vague authority claims (\"Studies show...\" without citation)\n- Formulaic closers (\"In conclusion...\")\n- Structural patterns (\"No X. No Y. Just Z.\")\n- All patterns in the ai-check lexicon\n\n### Voice Alignment\nCheck the prose against the active writer and project voice sources. Do not make a sentence cleaner by erasing intent, humor, rhythm, priors, or a distinctive aside.\n\n### Meaning And Provenance\n- Preserve the scope and certainty of factual claims.\n- Do not sever citations or source attribution from the claims they support.\n- Mark unsupported or model-added claims instead of smoothing them into authority.\n\n## Output\n\n### Part 1: Revised Draft\n\nDeliver the full draft with all fixes applied. Present it ready-to-use.\n\n### Part 2: Summary of Changes\n\nAfter the revised draft, summarize material changes in order of appearance. Do not bury the usable copy beneath a diagnostic preamble.\n\n```\n---\n\n## Changes Made\n\n1. **Sentence:** \"[Original sentence]\"\n **Problem:** [What was wrong]\n **Suggested Fix:** [What was changed]\n\n2. **Sentence:** \"[Original sentence]\"\n **Problem:** [What was wrong]\n **Suggested Fix:** [What was changed]\n\n[Continue for all changes...]\n```\n\n## Reverting Changes\n\nAfter presenting the summary, note: \"Let me know if you want to revert any of these.\"\n\nWriter can revert by:\n- **Number:** \"Revert #3 and #7\"\n- **Natural language:** \"Put back the original for the one about hedging\"\n\nSystem handles either format.\n\n## Transition\n\nWhen writer is satisfied, offer to move to **Final Pass**: \"Ready for a final pass before publishing?\"\n\n## Lessons\n\n[Skill-specific lessons will be added here as they're captured]\n"
}SHA-256 of public snapshot: 16f1d99ef46a1030e2712771311e366ab3522f1f8008f8aaa25429a772e71cbe