Turn AI manuscript feedback into a focused revision plan
Oh Story · Updated 2026-10-15
Sort review comments before you rewrite anything. Connect each criticism to a passage and an established story constraint, then decide what to fix, what needs clarification and what is simply an alternative taste. A useful revision brief names the problem, approved action, facts to preserve, exact chapter or scene and possible effects on later chapters. Oh Story separates story-review findings from the chapter-revision workflow. The decision sheet below is an editorial aid that the author fills in and rules on. For wording alone, use the separate prose-revision guide; for which character or reader knows what, see long-novel continuity. For interchangeable character speech, start with the dialogue example and fix it as a dialogue problem first; consider a whole-book style change only after that. The revised scene below turns the accepted fix (give the protagonist more agency) into dialogue and action while holding three constraints: the seal stays intact, the culprit stays hidden, and an agreement to register stays distinct from a completed registration.
Method fromstory-review3 method files
Before you start
- A manuscript you own or are authorized to edit, its chapter plan and the relevant preceding/following passage. Include the book’s viewpoint, intended reader experience and facts or reveal timing that must stay. List any missing context as an explicit gap for the author to fill.
- The original review comments and passages they refer to. Oh Story reports give a priority, location, evidence, issue and a proposed fix. Evidence is what points a comment at the sentence or story decision that should change.
- The commands below assume an existing long-form Oh Story project open in Claude Code, in the correct writing folder. The chapter-revision commands run inside that long-form project; a short story keeps its own writing workflow, and the decision sheet works for both. For a long-form manuscript not yet in a tracked project, follow the import guide before a project-level revision that requires existing tracking state.
Steps
- Ask what the criticism actually establishes For each finding, keep the location and evidence alongside the proposed fix. “The protagonist is passive” needs the decision they fail to make and the resulting effect; “too slow” needs the scene function that is delayed or duplicated. If two comments disagree, preserve the disagreement and ask which better serves this book. The review workflow lays conflicts out plainly for the author to decide.
- Prioritize damage before stylistic preference The author-facing report groups findings as must fix, suggested fixes or optional changes. Problems that break the main story, motivation, world rules or reader trust come first; substantial chapter problems also need repair before local polish. Resolve a supported contradiction before polishing its sentences. A factual conflict needs resolving whatever the author prefers; an unsupported criticism needs evidence first.
- Choose an action for each comment Use four editorial decisions: accept a specific repair; ask for missing evidence; defer a lower-priority change; or reject a proposed solution that violates the story contract. You can accept the diagnosis and reject its suggested fix. Record why. These decisions sit alongside the report: its severity labels stay as they are, and the manuscript, settings and outline change only when you start an explicit revision.
- Separate a repair from a new story decision If prose contradicts an approved fact, choose the authoritative fact and repair the passage. If the desired change would move a reveal, alter a relationship or replace the chapter outcome, it is a change of direction: settle it with the author and revise the affected plan explicitly before drafting. Do not smuggle it in as “stronger tension.” For a flat but correct blueprint, see outline to chapter. If a short story has no settled central question or ending yet, first clarify its premise-to-payoff plan; the author makes that decision first, and local polishing comes after.
- Bound one revision pass Name the chapter and the scene or paragraph anchors. Specify the accepted items, immutable facts, allowed changes and stopping point. The documented chapter workflow reads adjacent context, backs up the original and distinguishes local edits from whole-chapter rewrites. If the agreed improvement cannot fit that scope, ask for a report of the conflict and a revised plan, and widen the scope only with the author's approval.
- Keep later consequences visible The chapter-revision workflow uses a revision transaction to rebuild the affected chapter record and current continuity views. If you remove a clue that a later chapter still references, list it as a manuscript conflict first; changing who learned something may affect later dialogue. List those passages for the author to decide on, and leave later chapters as they are this pass. Review recommendations and future plot ideas stay out of tracking; tracked facts change only on evidence from the prose.
- Decide whether the repair worked Read the changed scene against the accepted problem: does the protagonist now make the intended choice, is the evidence still present, and does the following scene still follow? Ask for changes made, suggestions not applied and unresolved downstream effects. Judge the pass by whether the selected problem is solved; once it is, stop, and leave the remaining taste-based comments for the author to weigh. Distinguish a changed initiator from a completed task: a request or agreement can repair the interaction while the chapter still owes the actual result, such as registering before a deadline.
Example
Example
ORIGINAL EDITORIAL EXAMPLE, invented for this guide.
Chapter 8: The Transfer Slip Approved facts and outcome constraints: by the end of this scene, Zhou Lan and workshop keeper Yu Heng must both know that the last two digits on a retired machine's exterior plate differ from its transfer slip. She must register the discrepancy before 17:00. She may inspect the exterior only; the machine stays sealed. Both the chapter plan and the already-written chapter 9 depend on that seal remaining intact. The person who changed the record is not identified until chapter 12. Current weakness: Yu notices the mismatch, explains everything and offers to register it; Zhou merely agrees.
Four comments and an author's decision sheet: 1. “Zhou has no consequential action.” ACCEPT THE DIAGNOSIS. Approved repair: she compares the two visible numbers, asks to register the mismatch and insists when Yu proposes waiting. Yu still sees the same evidence. Keep the discrepancy, deadline and sealed machine. 2. “Cut the transfer-slip exchange; it slows the scene.” REJECT THE DELETION, ACCEPT COMPRESSION. Its evidence supports the later investigation. Remove repeated explanation; keep the comparison and registration decision. 3. “Have Zhou break the seal and find the culprit's signature for a stronger ending.” REJECT THIS SOLUTION. It changes the permitted action, chapter 9's premise and chapter 12's reveal. If the author wants that different plot, plan its consequences separately. 4. “Every line should be shorter and sharper.” ASK FOR A SPECIFIC PROBLEM; DEFER THE BLANKET REWRITE. This book uses an unhurried voice. Identify an actual redundant exchange; the overall voice stays.
Put the accepted repair on the page: a bounded trial The passage below is another original editorial example. It supplies wording and small comparison actions for decisions 1 and 2, keeping the facts above. It ends when they agree what to register, before any submission channel, receipt or completion time enters the scene.
Zhou Lan held the transfer slip beside the machine’s exterior plate, read the last two digits on the plate, then traced the corresponding line on the slip to its last two digits. “The last two digits don’t match. Look.” Yu Heng compared the places she indicated. “They don't. Let's wait until we've cleared it up before registering anything.” “The reason still needs checking, but the discrepancy has to be registered before five.” Zhou kept the slip raised. “I'm raising it now. Write down what's on the plate and what's on the slip separately. Leave the seal alone; we're not making a claim about what's inside.” “Just the number mismatch?” “Yes. We can't put down a cause as though we already know it.” “Then let's record the two numbers first.” Zhou turned the slip toward him. “Both of them. Don't choose one as correct yet.”
What the repair changes: - The actions move to Zhou. She compares the evidence, brings it to his attention, asks to register it now and resists waiting for a cause. Yu still sees the same mismatch; she has no new secret expertise or authority. - The deadline now drives a decision in the scene, so the reader no longer hears it explained twice. Keeping the two visible sources separate makes the request precise; the mismatch is recorded as a mismatch, and who changed the record, which number is correct and what is inside the machine all stay open. - Yu's wait proposal creates resistance without turning him into an accomplice. Zhou's move is to narrow what she is asking for; she neither threatens him nor opens the seal. Her longer sentence carries the deadline, request and limit; agency comes from actions that move things forward, and the dialogue can stay calm.
Compress repetition, keep the negotiated distinction: A second speech explaining again that the last two digits differ could go. “Just the number mismatch?” does different work here: it tests the scope of what they will record, and Zhou's answer excludes an unproven cause. Removing that exchange works only if the remaining passage still makes the agreed scope clear. Even after the mismatch has been mentioned, judge each later question by the work it does.
Where the trial stops: Yu has agreed to record the numbers; the excerpt does not show a completed registration. The chapter still owes the before-17:00 requirement. Read the surrounding unchanged passage for its actual completion, or identify the missing beat and choose an additional revision scope. Tick the deadline off only when the registration is actually completed on the page; someone saying “now” leaves it open. This bounded repair addresses the accepted agency problem; check the rest of chapter 8 separately.
One concrete later-chapter check, without inventing later prose: A hypothetical factual narration saying “Yu was the first to notice the mismatch” could conflict with this change of initiator. Flag it and read its context; a character's deliberate lie is a separate case, so judge that line in its own scene, by hand. A later statement that both characters saw the mismatching numbers and the seal stayed intact still fits the approved facts. These check sentences are invented for the example. Keep chapter 12's identity reveal where it belongs. A tracking transaction reflects saved revisions; an untouched later sentence needs its own repair.
If you want to try the wording before a file revision, use an explicitly separate chat request: Using the pasted facts and accepted decisions, draft only the transfer-slip exchange and its comparison actions in this reply. Keep the unhurried voice and both characters' shared evidence. Stop at the agreement about what to register; explain the unresolved deadline obligation. No seal opening, identified culprit, new submission process or claim of completed registration. Do not edit manuscript, outline, tracking or other project files, and do not save this trial as an author preference. [Paste the actual passage, facts and accepted decisions; replace this exercise's names and circumstances with your own.] This trial stays in the chat reply. To apply selected wording to a chapter, set the explicit scope and backup handoff, then use the file-revision command below.
Suggested first request for an installed Claude Code workflow: /story-review solo Review only chapter 8. Read the named chapter plan and relevant passages from chapters 7 and 9 as supporting context, not additional review batches. Identify evidence-backed problems and distinguish a diagnosis from one possible fix. Show missing evidence and disagreements. Deliver the report in this reply; do not edit manuscript, settings, outline, tracking or other project files. Do not infer persistent author preferences from this one request. [Supply the real paths, approved facts and original feedback.]
After choosing the repair: /story-long-write 修改第8章 Only revise the transfer-slip conversation and its local number-comparison actions. Apply decisions 1 and 2 above; do not apply 3 or the blanket rewrite in 4. Preserve the deadline, sealed machine, reveal timing and everything outside this scene. Confirm that scope, back up the original and follow the bundled revision workflow. If a plan conflict prevents the local repair, report it before writing. Report the actual changes and any consequences for chapters 9 onward; do not edit those chapters or start a new one this turn.
Expected files
- A review report with located evidence, priority, actual review mode, missing context and disagreements. The author fills in a separate decision sheet with accepted fixes and protected facts.
- After an explicit revision, the selected chapter changes within the agreed scope, with an original-copy backup and a report of later impacts. The documented workflow updates tracking through its transaction; check the files themselves to confirm the manuscript and state were saved.
- Review modes have different write boundaries. Solo leaves story tracking untouched; batch review can save unresolved findings in .story-review/state.md. Full/lean may maintain tracking through the prescribed transaction when existing prose proves a recorded fact is wrong or missing. This is why the example requests a single-chapter solo report and excludes file edits in the request itself.
- A chat-only trial, if that is what you requested, stays a proposal in the reply, with its stopping point and unresolved obligations stated. Saving the chapter and running the tracking transaction wait for a formal revision.
Check the result
- Check the accepted decisions against the actual changed passage, including material that must remain. Count only the accepted changes as fixes; flag any unrequested plot change, however dramatic the scene now sounds.
- Read each specifically affected later passage. If its premise no longer holds, leave the conflict visible and decide the next revision scope; that unchanged passage needs its own revision even when the tracking view is consistent.
- Review severity measures problems inside the manuscript; judge sales, platform acceptance and publishability separately.
Sources
- Review modes and effective execution
- Evidence, location and severity of findings
- Report synthesis and conflicting recommendations
- Batch-review state kept separate from story tracking
- Tracking-maintenance boundaries and workflow handoff
- Chapter scope, adjacent context and original backup
- Revision transaction and later-chapter impacts
- Blueprint boundaries and changes that need planning
- Current workflow source (2026-10-15)