One Complaint Can Point to Different Layers

Oh Story’s writing references separate material and audience, plot design, and prose delivery. This does not require overturning a book’s positioning on every pass. It reminds the author that smoother sentences may leave the reason readers disengage untouched.

ObservationFirst place to investigate
The core promise and intended reader remain unclearPositioning and the central premise
Actions are clear but unconvincingMotive, conditions, choice and result
Cause and effect work but the process is hard to followScene delivery, information order and sentences

Replace “boring” with a specific reading failure: an unknown goal, no meaningful obstacle, or the same action repeated three times. Locate the symptom before changing an entire book’s direction in response to one comment.

Original Case: Why Agree After Refusing?

Established premise: Xu Yun wants to borrow a school hall for a performance. Its caretaker worries about rubbish after rehearsals. They have no prior personal relationship.

Problem draft

“No. Someone needs it tomorrow morning,” the caretaker said. Xu Yun smiled. “We really need it.” Moved by her sincerity, he agreed.

The sentences are understandable. The missing step concerns cleanup and next-morning availability. Replacing “sincerity” with a facial expression resolves neither condition.

If the author wants permission granted, first approve an outline change: Xu Yun offers cleanup and same-night return, and the caretaker decides within his established authority. A promise cannot grant authority he lacks. Alternatively, retain the refusal and send Xu Yun elsewhere. These are author-selected plot changes, not automatic consequences of polishing.

Set the Events Before Polishing Their Delivery

Suppose the author chooses a cleanup-and-return proposal and confirms that the caretaker can approve it. Order this revision as follows:

  1. Set the conditions in the outline. Specify the offer, why it is acceptable and the limits of permission.
  2. Deliver the decision in the scene. Show proposal and response rather than skipping negotiation with “moved.” Permission does not mean the performance has succeeded.
  3. Polish repetition afterward. Cut repeated pleas and explanations while preserving the conditions that change the answer.
  4. Check neighboring passages. Later preparations can depend on the booking, but cannot treat it as a week’s unrestricted use.

If the events already work and only the plea repeats, a local expression edit is enough. Diagnosis identifies necessary changes; it does not mandate rewriting an outline before touching any sentence.

Keep One Bounded Revision List

This manual revision list can be filled from author notes or review findings. It is not a new skill data format.

ItemRecord
Main problemLocation, quotation and reader effect
CauseDirection, event design or expression; note missing evidence
DecisionChosen repair, authorized scope and protected facts
AcceptanceWhich condition now works and what later passages need checking

Address problems blocking understanding or major causality before optional style changes. Attractive prose does not prove sound plot, and sound plot does not require every author to share a style.

End the pass when the selected problem is resolved, event boundaries remain intact and neighboring passages introduce no new break. Keep deferred suggestions on the list rather than rewriting indefinitely. Use later revision checks when changed facts affect multiple chapters.

Write the Chosen Hall Repair as a Complete Scene

Continue the refusal example. Suppose the author chooses permission, confirms the caretaker's existing authority, and approves these conditions: enter at six, audience leaves at 7:45, cleanup and return by eight, with another group already booked for the following morning. This original revised passage shows event repair followed by expression work; it is not a model-run report.

“Someone needs it tomorrow morning. We can't leave the cleanup to them,” the caretaker said.

“Only six to eight tonight,” Xu Yun said. “Everyone leaves by 7:45. We'll clear the stage and beneath the chairs, then put the chairs inside the marked lines. You can inspect before eight and take the key back.”

He checked the free slot. “Tonight only. Return it by eight. This doesn't include tomorrow.”

“Agreed.” Xu noted the times and accepted the key.

At 7:55 the chairs were back inside the lines. Checking the final row, the caretaker pointed to a paper cup by a chair leg. Xu picked it up and took it with the other rubbish to the sorting bins outside. He checked the spot again, took back the key and locked the door.

The offer addresses the reasons for refusal. Actual permission precedes receiving the key. Inspection, removing the missed cup and returning the key establish this limited result, without proving a successful show, unrestricted future access or a personal bond. Adapt times to the manuscript; precise minutes cannot replace a feasible cleanup plan.

LayerWhat this pass changes
Event designThe author chooses permission with existing authority, cleanup and return conditions; refusal remains a separate possible route.
Scene deliveryShow proposal, limited approval, key receipt, later inspection and return.
ExpressionCombine repeated pleas while preserving conditions; invent no private friendship or emotional explanation.
Later dependenciesTonight's use has ended and the key is back; another booking needs permission, rather than treating this as a week's access.

A later “She finally had a venue” can remain when it means tonight. “They could rehearse every night that weekend” needs correction or a genuinely new permission. Polishing its excitement first would leave the nonexistent entitlement intact.

Fix the author's chosen events, place the candidate in neighboring prose and reread against the initial problem. This example checks particular conditions and return; it does not require every borrowing or request scene to dramatize a familiar process in full. Irrelevant steps can still be summarized.

FAQ

Must every revision begin with a full-book review?

No. Start with the affected passage and necessary context. Expand when evidence points to broader structural or continuity problems. Unread chapters have not been reviewed.

Do it with the skill

Use /story-review solo, or $story-review solo in Codex, to review the specified scope and locate the problem with quotations. Use story-long-write chapter revision for approved event changes and story-deslop for expression. This is an author’s work plan, not an automatic full-book rewrite mode.

Read the method: Diagnose plot and prose separately · Separate style from facts · Review scope, evidence and author reports · Single-reviewer report format · Chapter revision scope and joins

About Oh StoryThe story-review skill on GitHub

All guides