ZenStory AI

Practical guide · 实用指南

From one premise to a complete short story: promise, pressure, choice and payoff

只有一个梗，怎样写成完整短篇：开篇承诺、递进与结尾兑现

Source checked 2026-09-12 · 源码核对日期

A premise gives a short story a starting pressure, not a complete plot. 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 one option, not a requirement. Oh Story’s short-writing workflow separates design from drafting and uses a lightweight section plan rather than a long-novel chapter blueprint. The four-part framing here is an editorial aid, not a new mandatory schema. The original repair-shop example closes a relationship decision without pretending that one conversation solves a family’s entire history.

一个梗给了短篇起始压力，却还不是完整情节。先决定读者想得到什么回答、什么阻力让答案不能轻易出现、主角必须作什么选择，以及哪种可见变化能兑现这个问题，再留下通向结尾所必需的场景。反转是一种办法，不是每篇必需。Oh Story 的短篇流程把设计与正文分开，使用轻量小节大纲，而不是长篇的完整章节蓝图。这里的四步框架是编辑建议，不是新增强制字段。原创修补店示例会收束一次关系中的选择，但不假装一场谈话就能解决一家人的全部历史。

Oh StorySource on GitHub

Before you start · 开始之前

Steps · 操作步骤

  1. Turn the premise into a question the ending can answer Name the protagonist’s immediate want and why getting it matters now. In the example, the issue is not whether a sleeve can be repaired, but 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.
  2. 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, not only a villain, catastrophe or new secret. The bundled method emphasizes a single core fulcrum; the particular limits in the example are author choices.
  3. 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 is not escalation unless it exposes a different cost or closes an option. The workflow’s section plan records concrete actions and causal links; it does not require a minimum number of plot points per section or extra obstacles just 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.
  4. 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; do not end with an explanation that does all the work. Without a twist, make the promised change substantial enough to carry the ending.
  5. 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.
  6. 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 instead of accepting defaults accidentally. The documented 8,000–20,000 range is a Chinese web-fiction workflow default, not a definition of all short stories; first person is also a default that an explicit viewpoint can override.
  7. Read the opening and ending together Check whether the ending answers the question the opening made important, and whether the middle earned that answer. Do not confuse an unresolved life with an unresolved central story: the jacket may still need sewing, but the agreed deadline, price and right to refuse are no longer unspoken. If feedback proposes a different story, use the review-to-revision decision guide before rewriting everything.
  1. 把梗改成结尾能够回答的问题 明确主角眼下想要什么、为什么偏偏现在重要。示例的问题不是袖口能不能补，而是许禾能否在离开前，拒绝又一次没有说出口的免费加急承诺。结尾因此有了具体任务。若梗概同时打开五个互不相关的谜，就需要另定篇幅与范围。
  2. 只选一个核心压力，并限定它的范围 让人物、地点和时间窗口适合这篇的体量。问主角沿用惯常办法后，什么会变得更难。压力可以来自互相竞争的责任或紧张关系，不必总靠反派、灾难或新秘密。随包方法强调单一核心支点；示例中具体的人数与时限是作者选择。
  3. 让每一节改变处境 对每个小节追问：什么导致行动、谁实际做了什么、结果怎样改变下一步选择？请求重复一次，并不自动构成升级，除非暴露新的代价或关掉一个选项。流程的小节大纲记录具体行动与因果，不要求每节最低几个情节点，也不支持为凑长度硬加阻碍。 如果场景主要靠谈话推进，人物对白指南展示不同请求、想保护的东西与让步如何带来变化。
  4. 先试结尾，再扩写中段 先说结尾能让读者看到什么。一次决定、付出的代价、改变的关系或得到兑现的后果，都可能形成收束。若使用反转，应为误判提供依据，并在揭示后留出行动空间，不把全部工作丢给一段解释。不用反转时，也要让承诺的变化足够实在，撑得起结尾。
  5. 删掉属于另一篇故事的支线 详细童年史、第二条恋爱线、每件道具背后的秘密都可能有趣，却也会争夺同一个核心问题的篇幅。保留能改变行动、代价或结尾理解的内容。如果必需因果链放不进指定长度，先给取舍建议，不悄悄把短篇扩成连载开头。
  6. 先确认设计，再生成正文 设计阶段产出 设定.md 与 小节大纲.md；正文.md 属于后续写作。明确只做构思时，可以停在正文前。把视角、篇幅范围与节数写出来，不无意中接受默认值。文档的 8000–20000 字是中文网文工作流默认范围，不是所有短篇的定义；第一人称也只是可被明确视角要求覆盖的默认。
  7. 把开头和结尾放在一起读 看结尾是否回答了开头强调的问题，中段是否让这个答案来得有依据。人物的一生尚未解决，不等于核心故事没有收束：衣服可以还没补完，但交付时间、价格和拒绝权已不再含糊。如果审稿意见实际上要求换一篇故事，先按审稿到改稿决策指南作取舍，再决定怎么改。

Example · 示例

ORIGINAL PLANNING EXAMPLE — written for this guide, not an observed skill run or a complete manuscript.

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 instead of accepting 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 — actions and changed conditions, not a universal six-beat formula:
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 a delay rather than a refusal. 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, not a manufactured emergency.
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.

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 choices for this project, not genre rules. 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. Design files alone are not a finished short story.
原创规划示例——为本指南撰写，不是技能运行记录，也不是完整正文。

暂定篇名：最后一张修补单
核心梗：修补店闭店搬走当天，许禾必须向母亲说出真实价格与交付时间，而不是再次答应免费加急。
读者承诺：熟悉的义务变成双方看得见的选择后，松了一口气，却仍有一点不自在。
已确认事实：搬家车 17:00 到；缝纫机已经打包；母亲的工服需要改袖口。机子会随她搬走，她能在新住处拆箱后完成这一单，赶上约定的周三寄出。许禾过去给家人修衣不收费，却从没说清那是赠送还是义务。母亲在世，没有隐藏的重大秘密，也有权拒绝这次报价。不要把任何一人写成脸谱。
核心问题：许禾能否把默认的免费加急改成一份有价格、能按承诺交付的修补约定，然后离开？

六节规划——动作与处境变化，不是通用六节公式：
1. 母亲把工服压在价目表上，说“你走前，就缝两针”。许禾必须回应一个过去总会直接接受的请求。
2. 许禾说自己马上要走。母亲放下带来的午饭，坐着等，把这句话听成推迟而不是拒绝。暗示没能改变默认约定。
3. 许禾看到一张没写价格的旧家人修补单，意识到自己也一直让条件隐形。罗列旧委屈解决不了今天的约定。
4. 她在新单上写下价格与周三寄出时间。只有按这些条件才接，不在搬家车来前做完；母亲可以拿去别处修。代价是对方可能拒绝时的难堪，不是临时制造一场大事故。
5. 母亲问“给我也要写单？”许禾保留报价，也保留她不修的选择。沉默后，母亲支付约定定金。没有人发表一段“一切旧伤都已治愈”的宣言。
6. 母亲把回执收进钱包，问“周三？”许禾确认后，抱着打包好的机子上车，没有补一句今晚就能修好。修补还没完成，但核心约定已经落定。

本篇不加入：绝症揭露、恶邻、意外遗产或第二条恋爱线。没有这些支线，这次决定仍然有代价，也有可见变化。

在已安装的 Claude Code 工作流中，可以这样请求：
/story-short-write
规划这篇原创亲情日常短篇，采用许禾第一人称。中文正文目标 3500–5000 字，共六节；这些数字是本篇选择，不是题材规则。采用上面的已确认事实、核心问题和结尾；进一步新增的内容标为待选设计。保留不疾不徐的语气、带着不自在的温情，以及母亲拒绝报价的权利。不添加隐藏疾病、反派或终局震惊反转。
本轮只做构思。在 [选定的短篇目录] 中，按随包设计格式只创建 设定.md 与 小节大纲.md；不创建 正文.md，不改其他故事。范围或因果有缺口就指出，不靠填充情节凑大纲。设计完成后停止，列出创建的文件。

决定开放选项并读完设计后，再明确请求按确认的蓝图写正文。只有设计文件，还不算完成一篇短篇。

Expected files · 预期文件

Verify the result · 验证结果与边界

Sources and version notes · 来源与版本说明