Skip to content

Using fiction Prompts in StoryForge ​

Source and scope

Translation of the original Word asset's Chinese migration. These methods are separate from current product implementation; task variables and boundaries are preserved.

Use each stage through prepare materials → run Prompt → inspect result → choose adoption, rather than one generation deciding everything.

1. Three project parameters ​

  1. Length mode: longform, short fiction, or novella/shorter fiction.
  2. Delivery: complete manuscript, volume-based creation, ongoing serial.
  3. Main genre promise: one primary genre with supporting genres; do not load every rule.

These decide which Prompts, how much context, and which rules do not belong in the work.

2. Stages and workspaces ​

StagePrepare in StoryForgeMain outputBefore adoption
P00 BriefIdeas, length, genre, exclusionsBrief, decisionsFaithful to author goal?
P01 InspirationNotes, references, images, fragmentsIdea cards, combinationsMechanisms retained, fingerprints removed?
P02 PositioningGenre, readers, experiencePromises, differentiationConcrete and fulfillable?
P03 CoreConcepts, characters, world ideasConflict, premise, thematic questionSustained choices/consequences?
P04 ResearchQuestions, rules, fact requirementsBoundaries, conditions, plot effectsFacts separate from assumptions?
P05 WorldCore, geography, institutions, powersCausal chains, texture, limitsAffects choices?
P06 CharactersCore, world pressure, draftsDrives, relationships, arcs, statesBehavioral evidence?
P07 Plot engineGoals, conflict, storylinesEscalation, information, collisionsChoices rather than coincidence?
P08 StructureCore, arcs, endingTurns, climax, payoff routeServes this story?
P09 Length branchesStructure, deliveryVolumes, short compression, serial plansOnly applicable rules enabled?
P10 Chapters/scenesTask, states, foreshadowing, emotionTasks, cards, titlesClear change per scene?
P11 ProsePlans, beats, continuity, styleOpening, continuation, dialogue, action, narrationRespects facts/states?
P12 ContinuityProse and known factsSummary, handoff, diffs, timelineEvidence for every change?
P13 Macro revisionOutline, summaries, prose, factsDiagnosis, priorities, routeDiagnose/confirm before rewrite?
P14 LanguageSelected prose, goal, styleScene/dialogue/viewpoint/pacing editsWithin allowed scope?
P15 ReadersOpening, excerpt, promisesComprehension, gaps, risksSimulation treated as risk, not fact?
P16 PackagingCore, outline, summariesTitles, blurbs, synopsis, tagsAccurate promises/spoiler control?
P17 ManagementPrompt, I/O, adoption, feedbackReview, comparison, testsUpgrade supported by varied cases?

3. Minimum prose context ​

Prioritize material directly related to the chapter:

  1. Chapter task and beats.
  2. Prior ending, handoff, previous plan reconciliation.
  3. Recent summaries and relevant distant prose excerpts.
  4. Present characters, relationships, states, confirmed facts.
  5. Relevant rules, places, items, ability limits.
  6. Foreshadowing/storylines to advance or avoid paying off early.
  7. Time, action order, important item ownership.
  8. Author style and necessary character-language examples.

If excessive, rank by chapter relevance, certainty, impact of mistakes. Do not retain only recent text or indiscriminately send the whole work.

4. Four Prompt types ​

Generation ​

Generate candidates, check structure/facts/format, then let authors adopt. For core, worlds, characters, outlines, prose.

Extraction ​

Every result must trace to prose evidence; list conflicts separately. For summaries, states, items, timeline, foreshadowing.

Diagnosis ​

Default to problems, evidence, impact, repair direction—not direct factual changes. For structure, continuity, reader validation.

Revision ​

Preserve original, specify goal/scope, compare differences, then confirm writeback. For restructuring, scenes, language.

New longform ​

P00 → P02 → P03 → P05/P06/P07 cycle → P08 → P09L → P10/P11/P12 cycle → P13/P14/P15 → P16.

Serial longform ​

Enable P09R within longform. Serial parameters affect rewards, breaks, production rhythm, not character logic, world rules, prose facts.

Short fiction ​

P00 → P01/P03 → P09S → simplified P10 → P11 → P14/P15 → P16.

Existing-prose revision ​

P13 macro diagnosis → P12 continuity audit → P14 targeted revision → P15 reading validation → P16 packaging.

6. Adoption principles ​

  1. Confirmed prose outranks old plans and genre conventions.
  2. Explicit author decisions outrank AI candidates.
  3. Confirm structured results by character, relationship, foreshadowing, timeline, etc.; do not use one free-text blob to modify many areas.
  4. Conflicts, gaps, uncertainty go to review, not automatic facts.
  5. Preserve prior versions before important prose/settings writeback for comparison/reversal.
  6. For multiple worlds/timelines/viewpoints, verify the correct world, time, and character scope.

7. Common mistakes ​

  • Batch chapters before stabilizing the core.
  • Sending all settings, characters, history to every prose call.
  • Concurrent tasks modifying the same character/chapter.
  • Writing diagnosis suggestions as facts.
  • Enabling longform, short, and serial rules together.
  • Checking attractive wording but not causality, continuity, ownership.
  • Revising prose without updating states, timeline, future plans.

8. Completion standard ​

A call is complete only when input scope is clear, format complete, no unauthorized factual changes occurred, conflicts are marked, scope/ownership are correct, the author chose adoption or rejection, and downstream information has been synchronized.

Official StoryForge user documentation