2:11 task walkthrough
Follow one useful task, then try it with your own material.
New: actual Ruthless Editor run. 2:36 with captions, review decisions and written steps. Watch the actual app demo →
Step 1
Begin by deciding what needs editing. If the problem is story structure, missing motivation, or the order of events, use Dev Edit to build a revision plan first. Ruthless Editor is the browser app for reviewing proposed line edits and assembling changes you accept. This walkthrough uses prepared fictional material in actual workspace references, so you can learn the decisions without exposing a private manuscript.
Step 2
Import a chapter or supported manuscript file and check the extracted text before analysis. Describe the intended meaning, point of view, tense, and voice. Add phrases or repetitions that should be protected. Keep an unchanged source copy. Scanned PDFs need text extraction before this workflow, and imported text should not be treated as a promise to preserve the original page layout.
Step 3
Open one proposal and read its original passage in context. The source check helps locate the text the suggestion is about. It does not establish that the model's editorial judgment is right. Ask what the passage is doing for the scene, what the proposed replacement changes, and whether a deliberate voice choice is being mistaken for a mistake.
Step 4
Compare the replacement with the original. Accept it when it serves the book, reject it when it does not, or revise the wording before accepting. Work in manageable groups and reread the surrounding sentences. The goal is an edited chapter you can account for, rather than a collection of smoother lines that quietly change character, meaning, or continuity.
Step 5
After deciding on the proposals, review the assembled text against your source. Look for missing material, shifted meaning, repeated new phrasing, and changes to names or intentional wording. Use the workspace's decision and recovery controls when you need to reconsider a change. Keep notes about unresolved story problems instead of forcing a sentence-level tool to solve them.
Step 6
Export the draft containing your accepted edits and keep the original alongside it. Save a portable project backup before changing browsers or devices. For a reusable workflow inside an AI assistant, compare Chapter-by-Chapter Edit or Final Fiction Edit instead. Those are downloadable skills, with their own setup. Your completion check is simple: the chapter still means what you intended, and you can trace the edits you chose.