Continue your unfinished novel with AI: import into Oh Story
Oh Story · Updated 2026-10-15
If you already have 10 to 20 chapters, do not ask an empty chat to continue in the same style. Run Oh Story's story-import: it rebuilds the manuscript as a writing project, keeps the original prose, and generates settings, outlines and continuity records from it. Inferred facts go on a review list, and the manuscript stays the evidence you check them against. Then request the next chapter by name. The harbor-radio example below shows a continuation paying off a decision the last chapter already made. Intentions that never reached the page come from you: put them in the next-chapter plan, and check the new chapter's voice against your last original chapters.
Method fromstory-import5 method files
Before you start
- Back up material you own or may use. Documented direct inputs are one .txt/.md file, a directory of chapter files, or pasted text; convert a .docx, EPUB or PDF manuscript to .txt or .md first.
- Open a supported agent host in the writing workspace. New to skills or hosts? Read Agent skills for writers. Commands below follow Claude Code’s npx skills path; with another host or the marketplace plugin, use the command spelling documented for that setup.
- Identify the last complete chapter. Keep a half-written ending marked as a partial draft so unfinished events do not become established facts. Keep an unaccepted alternate opening outside the import source, and explicitly choose whether to retain it. In the worked example the author excludes it.
Steps
- Choose import when you want to keep writing Use story-import for a continuable project: settings, outlines, normalized prose and tracking. Use story-long-analyze when all you need is a deconstruction library and report. Import also analyzes your manuscript; that analysis is raw material for the rebuilt project, and any external comparison title you set stays a separate reference book. If you only want to learn how a passage works, the fiction-analysis guide walks through an evidence-to-mechanism reading exercise with no import needed.
- Prepare a clean source boundary Use one .txt/.md file, a directory with sortable chapter filenames, or pasted text. Exclude advertisements, author notes and alternate drafts unless they are evidence. State the title, genre, platform, completion status and last complete chapter. Confirm the detected chapter range and long/short classification.
- Set up first, then import For Claude Code’s npx path, run /story-setup in the workspace, refresh the session, then run /story-import and provide the path. Direct import also works. When the project infrastructure is missing, it lets you choose between running setup first and continuing with slower serial analysis. Do not mix this spelling with namespaced marketplace-plugin commands.
- Keep author decisions with the author Confirm continuable project versus analysis only, the last complete chapter, and treatment of a partial ending. If the text has no volume markers, review candidate divisions before volume outlines are finalized. Fields the manuscript cannot support stay [待补充] or go on the continuity-risk list.
- Review history and keep planned events out of it Confirm 正文/ has the expected chapters with unchanged prose, then inspect 设定/角色/, 大纲/ and 追踪/上下文.md. Past events and current locations, possessions, relationships and knowledge need manuscript evidence or an explicit author-confirmed background boundary. Separate that history from an inferred interpretation and from a newly approved next-chapter plan. A future repair, revelation or reconciliation that appears in a planning field stays in the plan until prose shows it happening.
- Do not rewrite old chapters to fill a new template Historical chapter blueprints are reconstructed descriptions of the chapters as written. The import records each chapter’s measured original length, marks hooks, relationship changes and side plots [待补充] when the chapter summaries cannot establish them; it invents nothing to fill the gaps. A [待补充] field records what the import could not confirm from the manuscript, and you decide later whether anything belongs there. Preserve the old prose; make future-facing choices in the next chapter’s plan.
- Restore the unwritten intention before prose An unresolved ending can lead to several defensible stories, and only you know which one you meant to write. State the next chapter’s job, viewpoint, voice and reveal limits, and approve the plan before prose. Also identify what the last chapter has already decided. If it ends with “one more try,” the next chapter carries that attempt and its consequences forward; whether to try is already settled. Leaving together can fulfill a local promise without repairing the receiver, solving the mystery or restoring all trust.
- Name the next chapter and keep one authority From the imported book directory, use /story-long-write 写第21章 (replace 21 with N+1) or a scoped daily request. A bare command only diagnoses the project. Revise an old chapter through its revision route; do not hand-edit derived tracking views. A current project with 追踪/_tracking-state.json normally continues without full re-import. If you expand the imported source range, the documented path is a fresh full import over the whole range. Back up any work added since the first import before rebuilding.
Example
Example
ORIGINAL EDITORIAL EXAMPLE — Harbor Radio An original reading and handoff exercise written for this guide; the editors wrote every request and passage below by hand. It assumes an author-owned, complete chapter 1–20 manuscript. Only the relevant excerpts are shown here; the real import source is the complete manuscript. All /ABS paths are placeholders for real files in your own environment.
Source boundary: /ABS/harbor-radio/complete-chapters.md — accepted chapters 1–20 only. /ABS/harbor-radio/alternatives/ch21-unused.md — an old, unaccepted opening, excluded. The author chooses NOT to retain that alternate opening. No chapter 21 prose file is present in the imported book in this example. If a real project keeps a partial chapter, send a revision/completion request for that existing file.
Accepted chapter 18 promise: “When we stop work this time, I’ll leave with you,” Lin Zhou told Chen Yu.
Chapter 19 evidence and confirmed information boundary: The manuscript shows Lin Zhou finding a red notebook and hiding it in his inside pocket. The reader has seen it. The author confirms that Chen Yu has not learned about it by the end of chapter 20. Who changed the broadcast log remains unresolved for the reader, and this exercise leaves that identity open as well.
Accepted chapter 20 ending, at 20:10 in the old radio room: “At twenty-forty, the causeway closes,” Chen Yu said. She set the torch beside the toolbox. “I can wait another half hour.” Lin Zhou felt the hard corner of the red notebook through his inside pocket. “One more try.” He turned the lamp toward the open receiver.
What the import handoff can preserve: - Both characters are still in the radio room. The receiver has not been repaired. - Lin has the notebook; Chen does not know about it. Reader knowledge stays separate from character knowledge. - Lin has promised to leave with Chen when they stop work; they have not left yet. - He has already committed to one more attempt. The next scene carries that attempt forward; “Will he try?” is already answered. - Chen has stated a time limit. Whether the repair succeeds, when they leave and how the conflicts between them settle all remain open.
A reconstruction mistake — a deliberately authored counterexample: Suppose the imported handoff already reports the following as established history: “The receiver finally worked. Chen Yu opened his red notebook and pointed to the culprit’s name. By morning they had all the answers, and nothing stood between them anymore.” This is wrong as the imported chapter-20 state: the attempt is unfinished, Chen has neither the notebook nor that knowledge, and the next morning is outside the stated cutoff. It also turns a local promise into complete reconciliation. Those events belong in a proposal for the future, outside the history and intention recovered from chapters 1–20.
What the author NOW chooses — a future plan, kept apart from imported history: Chapter 21 is about leaving an unfinished task without abandoning a promise to another person. The extra attempt will fail. Chen prepares her own things but does not pack Lin’s for him. Lin stops, packs the still-unrepaired receiver and leaves with her before her stated deadline. The notebook stays in his pocket; its contents and the person who changed the log are not revealed here. This is one chosen direction; the source leaves room for other valid readings. Do not turn the choice into a romance, permanent trust or an explanation of Chen’s private feelings unless the author separately establishes those things.
Why the intention belongs in the plan: A different author could choose a successful repair and the cost of staying. The accepted chapter 20 alone cannot choose between those futures. Here, the author’s decision governs chapter 21; it must not be backfilled as “the receiver failed and they left” in the imported chapter-20 checkpoint before the new scene has been written.
Suggested import request, after the host setup described above: /story-import Import only /ABS/harbor-radio/complete-chapters.md as a continuable long-form project. Chapters 1–20 are complete; the book is unfinished. Do not import the excluded alternate opening, rewrite old prose, or turn my future chapter-21 decision into past events. Before migration, show the detected chapter range and any candidate volume divisions that require my choice. Leave unsupported reconstruction fields uncertain. Complete the declared import workflow, but do not write chapter 21 in this request.
After reviewing the reconstructed project, make the next-chapter plan explicit: /story-long-write 补纲 Plan chapter 21 only; stop before prose. Keep chapter 20’s “one more try” decision. I approve the unsuccessful attempt, Lin packing the unrepaired receiver himself, and both characters leaving together before Chen’s stated deadline. Do not give Chen the notebook, reveal the person who changed the log or claim a complete reconciliation. Preserve chapters 1–20 and their established events. Treat this as a new plan; the historical record stays as it is. If the reconstructed outline points elsewhere, show the change before applying it.
After that plan is accepted, and no chapter 21 prose file exists: /story-long-write 写第21章 Write only chapter 21 from its approved blueprint, in Lin Zhou’s close third person with restrained dialogue. Carry through the extra attempt and the decision to stop, then show packing and leaving together. Keep the notebook in his pocket and Chen’s knowledge limited. Do not jump to the next morning, finish the repair off-page, or continue to chapter 22. If a chapter-21 file or incompatible project state is present, stop and report it; do not overwrite it. Report the actual changed files when the chapter is finished.
A candidate closing passage — original editorial prose for the last lines of the chapter: Static rose again. Lin Zhou turned the dial back. Chen Yu picked up her raincoat. She left the screwdriver beside his hand. “Still trying?” The notebook’s corner pressed against his ribs. “No. Let’s go.” He put the screwdriver into the box and closed the lid himself. A quarter of an hour remained before the time Chen had named. He lifted the unrepaired receiver and stepped outside with her.
This small ending enacts stopping, packing and leaving together. Whether Chen forgives him, whether they reach home and who changed the log all stay open. In a complete chapter, the attempted repair gets its own scene before this closing excerpt. Only after the approved chapter actually contains these events should the resulting continuity state advance. Judge the voice by reading this passage beside the last original chapters.
Expected files
- 拆文库/{book}/ holds the source backup and reconstruction analysis; you keep writing in the separate {book}/ project described next.
- A long-form project puts preserved prose in 正文/, reconstructed settings in 设定/, outlines in 大纲/, and continuity state in 追踪/.
- Reconstructed blueprints for chapters 1–N describe the imported prose as it stands. A later author-approved blueprint for N+1 describes an intended future. Keep that plan separate from the historical checkpoint until prose establishes the new events.
- 追踪/_tracking-state.json is authoritative. Context, character, foreshadowing and timeline Markdown are generated views; continuation begins after the last complete imported chapter.
- For ongoing chapters after import, use the long-novel continuity example: separate author truth, character/reader knowledge, unresolved promises and future plans before drafting.
Check the result
- Before chapter N+1, compare the final scene, active characters’ locations and knowledge, unresolved promises and reader-visible facts with the manuscript. Correct unsupported inferences or keep them uncertain.
- Read the first continuation beside the last two original chapters for voice, viewpoint, knowledge boundaries and causal handoff. Revise old chapters through the workflow and leave generated tracking files to the tool.
- For the harbor exercise, distinguish an action already chosen from an outcome not yet achieved. The continuation must actually show the attempt and, if that plan is approved, stopping and leaving together; it must not reset the choice, teleport the notebook, reveal its secret to Chen or equate leaving with complete reconciliation.
Sources
- Installation paths, command namespaces and import/continuation order
- Import order, continuable-project choice, supported inputs and author confirmations
- Project skeleton, unchanged prose migration and author-confirmed volume boundaries
- Evidence-limited outline reconstruction and continuity initialization
- Character snapshots, knowledge boundaries, partial drafts and expanded-range imports
- Authoritative tracking state, derived views and manual-edit boundary
- Next-chapter context: prior prose, current state, characters and commitments
- Explicit next-chapter, daily continuation and revision routes
- Reconstructed history, unknown fields and future events kept out of past checkpoints
- Next-chapter intent, approved blueprint and limits on premature outcomes
- Current workflow source (2026-10-15)