How to Turn an Idea into a Complete Short Story
Oh Story · Updated 2026-09-29
A premise gives a short story its starting pressure; the plot still has to be built. Decide what the reader should want answered, what prevents an easy answer, what the protagonist must choose and what observable change will settle that question. Then build only the scenes needed to earn that ending. A twist is optional. Oh Story’s short-writing workflow separates design from drafting and plans with a section outline that is lighter than a long-novel chapter blueprint. The four-part framing here is an editorial thinking aid; the design files still follow the skill’s bundled format. The original repair-shop example closes one relationship decision and leaves the family’s longer history where it is. The opening, negotiation and ending excerpts below show that choice on the page: a failed hint becomes stated terms, a deposit and a departure, while the jacket still waits to be mended at her new home and older family hurts remain.
Method fromstory-short-write6 method files
Before you start
- A premise and material you own or are authorized to use. State the intended emotional experience, viewpoint, length range and what the story must not do. “Relief mixed with lingering discomfort after setting a boundary” is more useful than “make it moving.”
- Separate approved facts from open design choices. A new character, hidden motive or unusual rule is a design choice for you to approve. If this continues an existing story, bring its relevant facts so the work picks up from what already exists.
- For the example command, install Oh Story in a supported agent host and open the intended writing folder. The example uses Claude Code slash syntax and runs in the agent host where you installed Oh Story; ZenStory Workbench and DSH installation are separate layers, explained in agent skills for writers.
Steps
- Turn the premise into a question the ending can answer Name the protagonist’s immediate want and why getting it matters now. On the surface the example is about mending a sleeve; the real question is whether Xu He can refuse another unspoken promise of free, urgent labor before leaving town. This gives the ending a specific job. A premise that opens five unrelated mysteries will require a different scope.
- Choose one central pressure and its limit Keep the cast, place and time window small enough for the intended story. Ask what gets harder when the protagonist tries their usual response. Pressure can come from competing obligations or a strained relationship as well as from a villain, catastrophe or new secret. The bundled method emphasizes a single core fulcrum; the particular limits in the example are author choices.
- Make each section change the situation For each proposed section, ask: what causes the action, what does someone actually do, and what result changes the next choice? A repeated request escalates only when it exposes a different cost or closes an option. The workflow’s section plan records concrete actions and causal links; a section can carry one plot point or several, and it is complete once it delivers its change, even when it is short, so leave out obstacles added only to fill space. When the scene turns on a conversation, the character-dialogue guide shows how different requests, protected concerns and concessions create that change.
- Test the ending before expanding the middle Describe what the reader will be able to observe at the end. A decision, paid cost, changed relationship or fulfilled consequence can provide closure. If you use a twist, plant the basis for the mistaken interpretation and leave room for action after the reveal, so consequences carry the ending and explanation stays brief. Without a twist, make the promised change substantial enough to carry the ending.
- Cut branches that belong to another story An elaborate childhood account, a second romantic plot or a secret behind every prop may each be interesting but compete with the chosen question. Keep an element when it changes an action, a cost or the reader’s interpretation of the ending. If the essential chain will not fit the requested length, propose a tradeoff; do not quietly inflate a short story into the opening of a serial.
- Agree on the design, then draft The design stage produces 设定.md and 小节大纲.md; 正文.md belongs to drafting. A request for conception only can stop before prose. State the intended viewpoint, length range and section count so you don’t inherit defaults by accident. The documented 8,000–20,000-character range is this Chinese web-fiction workflow’s default when no length is given; first person is likewise a default that an explicit viewpoint overrides.
- Read the opening and ending together Check whether the ending answers the question the opening made important, and whether the middle earned that answer. A life can stay unresolved while the central story closes: the jacket may still need sewing, and the agreed deadline, price and right to refuse are now spoken aloud. If feedback proposes a different story, use the review-to-revision decision guide before rewriting everything.
Example
Example
ORIGINAL PLANNING EXAMPLE: an editorial plan and excerpts written for this guide.
Working title: The Last Repair Ticket Premise: On the day she closes her repair shop and moves away, Xu He must quote her mother a real price and deadline and turn down another free rush job. Reader promise: relief mixed with lingering discomfort when a familiar obligation becomes a choice both people can see. Approved facts: the moving van arrives at 17:00; the sewing machine is already packed; her mother's work jacket needs a cuff alteration. The machine is moving with her, and she can finish this one repair at her new home in time to dispatch it on Wednesday. Xu He has previously repaired family clothes without charging but never clearly distinguished a gift from an obligation. Her mother is alive, is not hiding a dramatic secret, and is allowed to decline the offer. Do not make either woman a caricature. Central question: can Xu He turn an assumed free rush job into a paid repair with a deadline she can keep, then leave?
Six-section plan for this story, recording actions and changed conditions: 1. Her mother lays the jacket over the price list and asks for “just two stitches before you go.” Xu He now has to answer a request she usually accepts without discussion. 2. Xu He says she is leaving soon. Her mother puts down the lunch she brought and waits, hearing it as a delay. Hinting has not changed the assumed agreement. 3. Xu He notices an old family repair ticket with the price left blank. She recognizes that she has helped keep the terms invisible; a list of past grievances would not fix today's agreement. 4. She writes a price and a Wednesday dispatch date on a new ticket. She will take the jacket only on those terms, not finish it before the van arrives. Her mother may take it elsewhere. The cost is the uncomfortable possibility of refusal, and that is cost enough. 5. Her mother asks whether she really needs a ticket too. Xu He keeps the offer and the right to refuse intact. After a pause, her mother pays the agreed deposit. Neither makes a speech claiming that all past hurt is healed. 6. Her mother puts the receipt in her wallet and asks, “Wednesday?” Xu He confirms and carries the packed machine to the van. She does not add a promise to finish that night. The repair is still pending; the central agreement is settled.
What we leave out: a terminal-illness reveal, a hostile neighbor, a surprise inheritance and a second romance. None is needed to make this decision costly or visible.
From the plan to prose: three separate editorial excerpts These are three original first-person samples from Xu He's viewpoint, written for this guide and taken from moments in sections 1–2, 3–5 and 6. The development between them belongs to the full draft, which covers all six sections at 3,500–5,000 Chinese characters.
Opening sample — the hint does not settle the terms: Mother laid her work jacket over the price list. “Just two stitches before you go.” “The moving van comes at five,” I said. “The machine's already packed.” She set down the lunch she had brought and pulled up a chair. “Have something to eat first. Then do it.” The price list was still under the jacket. I did not reach for the jacket.
Negotiation sample — a visible offer, then an actual choice: The price space on the old family repair ticket was still empty. I turned to a new ticket, filled in the price, then wrote “Dispatch Wednesday” and set it beside the jacket. “I need a ticket too?” Mother asked. “I'll do this one after I move. I'll send it on Wednesday.” I pointed to the price. “If you don't want it on those terms, you can take it somewhere else.” Mother said nothing. I left the price on the ticket; the jacket stayed on the table. After a while she paid the agreed deposit.
Ending sample — keep the agreement when leaving: Mother put the receipt into her wallet. Before closing it, she asked, “Wednesday?” “I’ll send it Wednesday.” She closed the wallet. I took the work jacket and the packed machine with me and got into the van.
What earns the quiet ending: - In the opening, “I'm leaving” meets “eat first, then do it”: the old assumption survives the hint. The clothes cover the price list, and even an uncovered list would leave the terms unspoken. Xu He has to say what she is offering. - The blank price on the old ticket matters between opening and negotiation. It connects today's discomfort to terms Xu He herself has left unstated; the tension grows from her own habit, and her mother's motives are left for the reader to see. Write that bridge so the receipt at the end has something to carry. - The negotiation keeps price, Wednesday dispatch and refusal on the table at the same time. While the mother stays silent, she has not yet agreed; in this plan, paying the deposit is her acceptance. Why she accepts, whether she is pleased and whether the relationship is mended for good all remain off the page. - The ending repeats the date with a changed function: it is now the agreed commitment, with nothing left to guess. Wednesday is the dispatch date. The clothes and machine leave with Xu He; the alteration remains work she will do after unpacking at her new home.
A warmer-sounding line can undo this chosen ending: Adding “Never mind, I'll do it free tonight” would restore the very rush-and-price assumption this plan chose to change. A free repair for family can make a good ending too. That is a different choice, and it needs its own planned payoff; a sweet extra line slipped into this ending cannot supply it. Likewise, if the author has the mother refuse, plan the consequences of that refusal and cut the payment scene.
Beyond these excerpts, the middle still needs writing: The final draft still has to connect the old ticket, the explicit offer, the possibility of refusal and acceptance at this story's chosen pace. Let section lengths follow their content, and let the conversation itself lead the mother to pay, with no added crisis. Retain the six approved section responsibilities; if the plan itself needs fewer sections, revise the plan first, then draft. A quiet ending is earned by the preceding choices; earlier scenes can rise and fall.
Suggested request in an installed Claude Code workflow: /story-short-write Plan this original family slice-of-life short story in first person, from Xu He's viewpoint. Intended Chinese prose length: 3,500–5,000 characters, across six sections. Those numbers are this project's own choices. Use the approved facts, central question and ending above; mark any further invention as a proposed choice. Preserve an unhurried voice, uneasy warmth and the mother's right to refuse. Do not add a hidden illness, a villain or a final shock twist. This turn is conception only. In [the selected story directory], create only 设定.md and 小节大纲.md following the bundled design format. Do not create 正文.md or edit another story. Identify any scope or causal gap instead of padding the outline. Stop after the design and list the files created.
After deciding any open choices and reading the design, explicitly request drafting from the approved plan. The short story is complete only once the prose is drafted.
Once those two design files are approved, make the full-draft handoff explicit: /story-short-write The design in [the approved story directory] is approved. Draft the complete Chinese story into 正文.md, in Xu He's first person, keeping the agreed 3,500–5,000-character range and all six planned sections. Follow the workflow's section batches; do not return only opening/ending excerpts or treat them as the whole manuscript. Keep the price offer, the right to refuse, the agreed deposit, Wednesday dispatch and departure with the packed machine. The repair itself remains unfinished at the ending. Preserve the unhurried voice and uneasy warmth without adding an illness, villain or shock reveal. Do not silently change the approved design to meet length. If the constraints conflict, report the specific conflict before changing them. If 正文.md already exists, report that before overwriting it. Stop after the requested story and report the written file and any unresolved gaps; do not start another story. [Replace the directory, facts, voice and length with your own approved design.]
The samples on this page are editorial illustrations. Per the documentation, the writing phase delivers one 正文.md file that covers every planned section; confirm completion by checking that file.
Expected files
- After a conception-only pass: 设定.md and 小节大纲.md with an agreed central pressure, planned changes and ending. The bundled outline has its own fields; the six summaries above illustrate creative decisions, and the files still follow that format.
- After a separately requested drafting pass: story prose in 正文.md, following the approved sections and delivery parameters. Beyond the opening, negotiation and ending samples on this page, the full draft must also cover the approved development between them.
- An explicit list of unresolved design choices or necessary tradeoffs. A quiet ending can be strong, and a twist has to be earned; judge both by what this story promised and showed.
Check the result
- Can you state the opening question and point to the final action that answers it? If the ending only introduces the next mystery, decide whether you are actually planning a serial opening.
- Does each middle section change information, an available choice, a relationship or a cost? Remove repetitions that change none of these, and keep necessary emotional development written out as full scenes.
- Keep approved viewpoint, length and scope separate from the tool’s defaults. A finished design and a passed structural check settle the structure; once the prose is drafted, read it yourself to judge its quality.
Sources
- Single core fulcrum, opening/ending and viewpoint precedence
- Separate design and drafting phases
- Framework and the two design files
- Concrete causal actions without padding
- Examples where a twist is not required
- A reveal needs prior mistaken decisions and later consequences
- Explicit or default delivery range and planned section count
- Prose output and explicit delivery parameters
- Section batches, full-story scope and no silent section collapse