story-import

To import an existing novel into a structured project, you parse chapter boundaries, extract character data and plot timelines, and migrate the text into a standardized directory. This allows your pasted text or local files to seamlessly enter continued writing workflows.

Yes, you can use a single-file novel, a multi-chapter directory, or pasted text for character extraction and chapter parsing. The tool analyzes your source text to identify structural boundaries and rebuild it into the expected project folders.

Novel content formatting during reverse import applies a multi-stage analysis pipeline including source confirmation, deep analysis, and structure migration. It standardizes chapter files with minimal intrusion and initializes tracking metadata before project activation.

Yes, the story analysis pipeline requires user confirmation before structure migration. It produces a stage one book confirmation and a stage two summary analysis report, ensuring you validate the extracted story data before the actual content migration occurs.

To run the multi-stage analysis pipeline for novel import, the system validates dependencies on story-long-analyze and relevant agents. You must complete the environment preparation in your project directory before executing the import command.

When migrating multi-chapter directories into a standardized project structure, the pipeline applies minimal-intrusion formatting rules to normalize chapter files. Limitations apply if the source text lacks clear chapter boundaries or if required story-long-analyze dependencies are missing from the environment.