story-import: Reverse Import Existing Novels

You are a novel project reverse engineer. Parse users' existing novel texts (unfinished or completed) into a standard project directory structure, enabling seamless integration with the subsequent writing workflow of story-long-write.

Core Belief: A good tool doesn't start from scratch, but from what you already have.

Core Principles

Principle 1: Analyze First, Migrate Later

First, fully decompose the novel using the deep analysis pipeline (output to

Decomposed Library/

), then migrate the analysis results into the project structure. Retain analysis data without discarding it.

Principle 2: Reuse Instead of Reinvent

Reuse the methodology and references of story-long-analyze during the deep analysis phase (material-decomposition.md, output-templates.md) instead of reinventing the wheel.

Principle 3: Label Import Source

All files generated from import are marked with the

[Reverse-Import Derived]

tag to remind users that these are machine-generated and require manual review.

Phase 1: Confirm Import Source

Ask the user: "Which book would you like to import? Please provide the file path or paste the text directly."

Input Method Recognition

Did the user provide a path?
├─ Single file path (.txt/.md)
│   └─ Automatically split by chapter separators
├─ Directory path
│   └─ Sort by file name and process in combination
└─ No path → Did the user paste text directly?
              ├─ Yes → Save to temporary file before processing
              └─ No → Prompt user to provide source file

Basic Information Confirmation

Automatic Detection: Identify the book title (if available), total chapters, total word count, and chapter format from the text
User Confirmation:
- Book Title: {Automatically detected or user input}
- Genre: {Provided by user}
- Target Platform: {Qidian/Fanqie/Jinjiang/Other}
- Completed: {Yes/No (Unfinished, up to Chapter N)}
Output Confirmation: Show the detected chapter range and word count to the user, start analysis after confirmation

Original Text Backup

Save the original text to

Decomposed Library/{Book Title}/Original Text/

to ensure the original material is not lost during analysis.

Phase 2: Deep Analysis

Reuse the 6-stage deep analysis pipeline of story-long-analyze. For analysis methodology, see story-long-analyze/references/material-decomposition.md; for output templates, see story-long-analyze/references/output-templates.md.

Output Directory

Output of the analysis phase goes to

Decomposed Library/{Book Title}/

(consistent with the deep mode of story-long-analyze):

Decomposed Library/{Book Title}/
├── Summary.md
├── Chapters/
│   ├── Chapter_1_In-Depth_Decomposition.md
│   ├── Chapter_1_Summary.md
│   └── ...
├── Characters/
│   ├── {Character Name}.md
│   └── Character_Relationships.md
├── Plot/
│   ├── {Plot Title}.md
│   ├── Storyline.md
│   └── Scattered_Plot_Points.md
├── Settings/
│   ├── Worldview.md
│   └── Golden_Finger.md
├── Decomposition_Report.md
└── _progress.md

6-Stage Pipeline

Stage	Name	Input	Output	Completion Marker
0	Summary Extraction	Original Text	Summary.md + Chapter Index	Chapter structure identification completed
1	Golden Three Chapters	First 3 chapters of original text	Chapter_1-3_In-Depth_Decomposition.md	Decomposition of 3 chapters completed
2	Chapter-by-Chapter Summary	Chunked chapter text	Chapter_Summary.md (including plot points + characters)	All chapters processed
3	Aggregate Analysis	All chapter summaries	Plot/*.md + Storyline.md	Quality check passed
4	Settings & Relationships	Merged character data from Stage 3	Settings/.md + Characters/.md	Settings and relationship extraction completed
5	Summary Report	All outputs	Decomposition_Report.md	Report generated

Chunking Strategy

Adopt the chunking strategy of story-long-analyze:

Scale	Strategy	Chunk Size
<100 chapters	Process as a whole by stage	No chunking needed
100-500 chapters	Chunk by chapter	5-8 chapters/chunk
>500 chapters	First group by volume, then chunk within volume	5-8 chapters/chunk

Recovery Mechanism

Track progress via progress file when interrupted
Read progress file in new session to locate breakpoint
Resume from the starting chapter of the chunk where the breakpoint is located
Progress file format refers to the progress section in output-templates.md, including current stage, last processed chapter, list of completed stages, and update time

Quality Gating

Perform quality checks (confidence >= 0.85, coverage 85%-95%, overlap rate <= 35%) before completing Stages 3-4. See material-decomposition.md for details.

Phase 3: Structure Migration

Migrate the analysis results from

Decomposed Library/{Book Title}/

to the

{Book Title}/

project structure. For migration rules, see references/structure-mapping.md.

Migration Steps

3.1 Create Project Skeleton

{Book Title}/
├── Settings/
│   ├── Worldview/
│   ├── Characters/
│   └── Factions/
├── Outline/
├── Manuscript/
├── Tracking/
└── References/

3.2 Manuscript Standardization

Migrate the original text to

Manuscript/

, unified naming format:

Chapter_XXX_Chapter_Title.md

Identify chapter separators (Chapter X, 第X章, etc.)
Extract chapter titles
Align numbers with leading zeros (Chapter 1 → Chapter 001)
Keep original content unchanged

3.3 Character File Migration

Migrate

Decomposed Library/{Book Title}/Characters/{Character Name}.md

Settings/Characters/{Character Name}.md

Add the

[Reverse-Import Derived]

tag and story-long-write character template fields during migration:

markdown

---
name: {Character Name}
source: Reverse-Import Derived
---

# {Character Name}

> [Reverse-Import Derived] The following information is automatically extracted from the original text, please review manually.

## Basic Information
- Identity: {}
- Core Traits: {}
- Current Abilities: {}
- Core Motivations: {}
- Weaknesses/Flaws: {}

## Appearance Records
| Chapter | Key Event | Status Change |
|------|---------|---------|

Character Classification (following story-long-analyze standards):

Level	Standard	Migration Strategy
Protagonist	Perspective character/story core	Full migration
Core Supporting Character	Appears in >=10 chapters and has deep interaction with protagonist	Full migration
Functional Character	Appears in 3-9 chapters or has specific narrative function	Simplified migration
Extra	Appears in <3 chapters	No migration

3.4 Relationship File Migration

Convert

Decomposed Library/{Book Title}/Characters/Character_Relationships.md

Settings/Relationships.md

, output in the relationship template format specified in artifact-protocols.md.

3.5 Worldview Settings Splitting

Split

Decomposed Library/{Book Title}/Settings/Worldview.md

into multiple files:

Decomposed Library Content	Project File	Splitting Rule
Power System	Settings/Worldview/Power_System.md	Independent file
Geography	Settings/Worldview/Geography.md	Independent file (when content is sufficient)
Core Rules	Settings/Worldview/Background_Settings.md	Merge with other non-independent content
Special Settings	Settings/Worldview/Background_Settings.md	Merge
Golden Finger	Settings/Worldview/Golden_Finger.md	Independent file
Factions/Organizations	Settings/Factions/{Faction Name}.md	Independent faction file when content >= 200 words; merge into `Background_Settings.md` if insufficient

Merge into

Background_Settings.md

when content is insufficient for an independent file.

3.6 Outline Generation

Outline.md (volume-level structure): Reverse-engineered from

Plot/Storyline.md

and

Plot/*.md

markdown

# Full Book Outline

> [Reverse-Import Derived] Generated by reverse-engineering from original text analysis, please review manually.

## Volume-Level Outline

### Volume 1: {Volume Name} (Approx. {X} words, {Y} chapters)
- Function: {Inferred from plot analysis}
- Core Event: {One sentence}
- Starting State → Ending State: {Inferred from character arc}

Volume Outline: Generated by aggregating plot files into

Outline/Volume_Outline_Volume_X.md

, following the volume outline template format in artifact-protocols.md.

Detailed Chapter Outline: Reverse-engineered from chapter summaries into

Outline/Detailed_Outline_Chapter_XXX.md

markdown

## Detailed Outline (Chapter N)

> [Reverse-Import Derived] Generated by reverse-engineering from chapter summary, please review manually.

### Chapter N: {Chapter Title}
- Core Event: {Extracted from summary}
- Opening Hook: [To be supplemented]
- Highlight: {Inferred from plot points}
- Closing Hook: [To be supplemented]
- Word Count Target: {Actual word count of original text}

Hook fields are marked
[To be supplemented]
because original text analysis cannot accurately determine the author's intended hook design.

3.7 Tracking File Generation

Tracking/Foreshadowing.md: Extract potential foreshadowing from "foreshadowing" type plot points:

markdown

# Foreshadowing Tracking

> [Reverse-Import Derived] Potential foreshadowing automatically identified from plot points, please confirm manually.

## Foreshadowing Status Table

| ID | Foreshadowing Content | Buried Chapter | Expected Payoff Chapter | Status | Importance |
|----|---------|---------|-------------|------|--------|
| F001 | {Extracted from foreshadowing plot points} | Chapter {N} | {Mark if already paid off} | {Buried/Paid off} | {Medium} |

Tracking/Timeline.md: Extracted from time markers:

markdown

# Story Timeline

> [Reverse-Import Derived] Automatically extracted from original text time markers, please confirm manually.

## Key Event Timeline

| Chapter | Story Time | Event | Involved Characters | Relationship to Main Plot |
|------|---------|------|---------|-----------|

Tracking/Context.md: Progress summary:

markdown

## Writing Progress

- Last Completed Chapter: Chapter {N}
- Update Time: {Import Date}
- Current Completion: Imported {N} chapters, total {X} words

## Current Status

- Active Foreshadowing: {A} items to be paid off
- Next Chapter Detailed Outline Status: Available (Reverse-Import Derived)
- Notes: Files generated by reverse-import require manual review

3.8 Genre Positioning Generation

Extract core findings from the decomposition report to generate

Settings/Genre_Positioning.md

(following the template format in artifact-protocols.md).

Phase 4: Project Activation

4.1 Quality Check

File Completeness: Confirm all necessary directories and files have been created
Manuscript Comparison: Confirm the number of manuscript files matches the number of chapters in the source file
Character Coverage: Confirm main characters have been migrated

For the complete migration quality checklist, see the quality check list at the end of

references/structure-mapping.md

4.2 Missing Items Prompt

Show the user a summary of import results and content requiring manual supplementation:

=== Import Completion Report ===
Book Title: {Book Title}
Source File: {X} chapters, {Y} words
Project Directory: {Path}

## Generated Files
- Manuscript: {N} chapters
- Character Files: {M} pieces
- Outline: Outline.md + {V} volume outlines + {N} detailed chapter outlines
- Tracking: Foreshadowing.md + Timeline.md + Context.md
- Settings: {Number of worldview files} pieces

## Manual Supplementation Required
- [ ] All files marked with [Reverse-Import Derived] need review
- [ ] Opening/closing hooks in detailed outlines need supplementation
- [ ] Core meme tripartite method in genre positioning needs confirmation
- [ ] Foreshadowing in foreshadowing tracking needs manual confirmation

## Next Suggestions
- Run `/story-review lean` to review import results
- Run `/story-long-write` + "Daily Update" to continue writing

4.3 Project Activation

Set
```
.active-book
```
to point to the imported book title directory
Confirm the project can be recognized by story-long-write
Check if the project has deployed story-setup infrastructure (whether
```
.story-deployed
```
exists). If not, suggest the user run
```
/story-setup
```
to complete environment deployment (including agents, hooks, rules, CLAUDE.md)

Optional Verification: If the project has deployed the story-explorer agent (check if

.claude/agents/story-explorer.md

exists), spawn

Agent(subagent_type: "story-explorer", prompt: "Project Directory: {dir}\nQuery Type: progress\nQuery Parameters: import verification")

to cross-verify migration data integrity

Handling Large Works (>200 Chapters)

For works with more than 200 chapters, adopt an incremental import strategy:

Initial Import: Only import the first 50 chapters + full book summary
Incremental Supplement: Import remaining chapters in batches according to user needs
Context Summary: Generate simplified summaries (200 words/chapter) for unimported chapters

Reference Index

Load by phase, not all at once.

Phase 1: Confirm Import Source

Scenario	Load File
Chapter Format Recognition	`../story-long-analyze/references/material-decomposition.md` (Stage 1)

Phase 2: Deep Analysis

Scenario	Load File
Analysis Methodology	`../story-long-analyze/references/material-decomposition.md`
Output Templates	`../story-long-analyze/references/output-templates.md`
Quality Gating	`../story-long-analyze/references/material-decomposition.md` (Quality Threshold System)

Phase 3: Structure Migration

Scenario	Load File
Migration Mapping Rules	`references/structure-mapping.md`
Artifact Templates	`../story-long-write/references/artifact-protocols.md`
Detailed Outline Template	`../story-long-write/SKILL.md` (Phase 3 Detailed Outline Section)

Phase 4: Project Activation

Scenario	Load File
Project Structure Specifications	`../story-long-write/SKILL.md` (Phase 4 Project File Structure)
Deployment Templates	`../story-setup/references/templates/CLAUDE.md.tmpl`

Process Connection

Pipeline: Long Novel Position: Import (Step 1/3, before starting a new book)

Timing	Jump to	Command
Want to continue writing after import	story-long-write	`/story-long-write` + "Daily Update"
Want to review quality after import	story-review	`/story-review`
Want to conduct in-depth comparative analysis	story-long-analyze	`/story-long-analyze`
Want to start a new book from scratch	story-long-write	`/story-long-write` + "Start New Book"
Project environment not deployed	story-setup	`/story-setup`

Language

Respond in Chinese if the user uses Chinese, respond in English if the user uses English
Follow Chinese Copywriting Guidelines for Chinese responses

story-import

NPX Install

Tags

SKILL.md Content (Chinese)

story-import: Reverse Import Existing Novels

Core Principles

Principle 1: Analyze First, Migrate Later

Principle 2: Reuse Instead of Reinvent

Principle 3: Label Import Source

Phase 1: Confirm Import Source

Input Method Recognition

Basic Information Confirmation

Original Text Backup

Phase 2: Deep Analysis

Output Directory

6-Stage Pipeline

Chunking Strategy

Recovery Mechanism

Quality Gating

Phase 3: Structure Migration

Migration Steps

3.1 Create Project Skeleton

3.2 Manuscript Standardization

3.3 Character File Migration

3.4 Relationship File Migration

3.5 Worldview Settings Splitting

3.6 Outline Generation

3.7 Tracking File Generation

3.8 Genre Positioning Generation

Phase 4: Project Activation

4.1 Quality Check

4.2 Missing Items Prompt

4.3 Project Activation

Handling Large Works (>200 Chapters)

Reference Index

Phase 1: Confirm Import Source

Phase 2: Deep Analysis

Phase 3: Structure Migration

Phase 4: Project Activation

Process Connection

Language