Prerequisites for a chapter batch

Several chapters suit a project with existing prose, current character state and executable outlines. Plan an idea first; import a loose manuscript before treating chat memory as history.

Check the first unwritten chapter. Do not generate another Chapter Seven if it already exists. An outline saying only “finds the truth” needs action and causality before a batch can consume it.

This page concerns one batch; long-term character and clue maintenance has a separate guide.

Separate batch goal from chapter jobs

In this original story, Lin Cen organizes an outdoor community film. Chapter Six established venue consent. This batch must make the screening arrangement workable, not claim the audience has already watched it.

ChapterJob and resultCarryover
7Check equipment and time; borrowed screen too wideCurrent plan does not fit
8Compare resizing and moving; lender agrees and hands over narrower screenObject available; trial still needed
9Trial at venue; responsible host confirms picture and start timePlan works; public event remains later

This manual plan is not the native chapter-outline format. Each row needs scenes, choices, resistance and space; it does not replace executable outlines. Mark unreleased secrets explicitly rather than spoiling them for speed.

Carry actual results forward in order

Before Chapter Eight, carry the actual Chapter Seven result: knowing the screen does not fit is not having a replacement. If Eight gains only verbal consent without handover, Nine cannot begin with the new screen installed unless that step is supplied or remains an obstacle.

The pinned Oh Story workflow drafts sequentially and commits state after each chapter, with a three-chapter per-turn ceiling. That is a tool workflow, not every writer’s daily quota. Split longer requests into later batches rather than generating conflicting results in parallel. Manual writers can borrow the principle of checking what actually happened before continuing.

Record relevant selected venue, held equipment and known changes. Unaccepted plans are not completed state.

Review accumulated results at batch end

Do the three chapters move Lin from venue consent to a tested arrangement? Does each consume the previous result instead of repeating screen dimensions? Whose credit, resources and knowledge change? Has a new mystery displaced an old promise?

Check repeated titles, clues, character state and unconsumed outline items. Length matters to delivery, but extra words do not replace the missing trial or response.

Leave an accurate next-batch entry: public screening not started, equipment handed over and tested, host confirmed the time. A candidate plan must not become a successful event in the summary.

A bounded request and common repairs

Ask $story-long-write to draft Chapters 7–9 in the established outline order. Keep Chapter Six’s consent, require handover before possession, end Nine at the trial rather than the public event, report actual and missing results, and stop after the batch. Missing outlines should be reported, not replaced with a new ending.

Replace numbers and facts with your project. The three-row example is not a formal outline. Say “discussion only, no prose” if that is the task.

ProblemRepair
Several chapters repeat one preparationMerge repetition; plan the next real change
Unwritten step treated as completeSupply it or revise the next entry state
Summary exposes future secretsUse current reader knowledge
Duplicate titles or old character stateReconcile with existing prose before continuing

Allow room for revision and rest. A smaller batch preserves judgment better than padding a quota.

FAQ

Is requesting ten chapters at once more efficient?

It depends on the workflow and outline readiness. The pinned version caps a turn at three chapters and splits longer ranges. Preserve causality, reveal boundaries and state rather than equating fewer checks with efficiency.

Do it with the skill

Use $story-long-write for the specified batch in outline order. Confirm range and shared goal, carry actual previous results forward, preserve reveal limits, update relevant changes and review accumulated payoffs and gaps before stopping.

Read the method: Chapter batching, sequential drafting and batch review · Scene expansion, causality and useful change

About Oh StoryThe story-long-write skill on GitHub

All guides