Version Update

This version adds permission-aware /novel:style-import for abstracting narrative and dialogue style from permitted reference text, layered character context for more focused drafting, and an optional eight-beat planning lens. Website source configurations are not bundled by default; Gutendex and Wikisource are not accessed unless a user supplies a custom configuration.

Novel Writing

For writers

This is not a one-click novel generator. It is an author-controlled writing partner that helps carry a story from a rough idea to a complete long-form manuscript through outlining, character development, chapter drafting, revision, continuity checks, and visual story tracking. The author keeps control of canon, voice, chapter boundaries, and every proposed change.

Core workflow

Execute these stages in order:

1. Resolve the existing novel project or initialize one with scripts/init_project.py.
2. Before /novel:chapter, run scripts/check_chapter_registry.py PROJECT_DIR. If it reports missing or stale metadata for existing manuscript files, stop drafting and offer scripts/scan_chapter_registry.py PROJECT_DIR --write; do not write a new chapter until the author accepts the scan or explicitly resolves the report. Then load the project-local working set from project-workflow.md. Read the previous chapter, relevant outline and character sections, voice guide, and continuity records; do not load the whole manuscript by default.
3. Read all newly supplied fiction content before evaluating, questioning, outlining, drafting, or revising it.
4. Apply questioning.md when development decisions remain. Ask 3–5 content-anchored questions unless the author skips questions or requests immediate output. Execute status, audit, review, and visualization requests directly.
5. Apply research-workflow.md only when factual research can materially change plausibility or a story decision.
6. Route the request to plotting.md, emotional-focus.md, character-arcs.md, character-context.md, drafting guidance below, dialogue-and-clarity.md, continuity.md, revision.md, or ai-writing-patterns.md. Apply the emotional spine, hierarchy, and pressure gates for every outline, draft, review, and revision.
7. Preserve confirmed, inferred, and author-planned as separate certainty states. Merge no proposed state without explicit author confirmation.
8. Draft or revise the author-selected chapter. Follow the author-maintained chapter plan; do not automatically partition the full novel into chapters or run an automatic multi-batch chapter pipeline.
9. Save a completed chapter before review. Never silently overwrite a manuscript file; preserve the source unless the author requests an in-place edit.
10. After craft revision, run the optional residual-pattern check in ai-writing-patterns.md before final continuity/state handling, then apply chapter-review.md and offer all three review modes. Resolve accepted revisions before updating structured state.
11. Apply visualization-workflow.md. Extract candidate timeline, character, relationship, mystery, and clue changes; preview and merge them only through explicit author confirmation.
12. Continue with the next author-selected chapter until the manuscript is complete, then perform a whole-project continuity and revision pass.

Operation routes

CLI usage

• Initialize: python3 scripts/init_project.py PROJECT_DIR --title TITLE [--language LANGUAGE].
• Show status: python3 scripts/project_status.py PROJECT_DIR [--format text|json].
• Validate structured state: python3 scripts/validate_story_data.py PROJECT_DIR.
• Audit chapter metadata: python3 scripts/audit_project.py PROJECT_DIR. Run after ordinary schema validation and before repairing a chapter rewrite or split.
• Scan legacy chapters: python3 scripts/scan_chapter_registry.py PROJECT_DIR [--write] [--status accepted|draft|review-pending|planned]. Preview first; --write creates continuity/chapters.json only when it has no populated registry and refuses to overwrite existing chapter records.
• Check before a new chapter: python3 scripts/check_chapter_registry.py PROJECT_DIR [--json]. Treat a non-zero result as a drafting gate and offer the scan command before writing new prose.
• Preview or merge an exact update packet: python3 scripts/merge_story_updates.py PROJECT_DIR UPDATE_FILE [--expected-sha256 HEX] [--dry-run].
• Render an offline dashboard: python3 scripts/render_dashboard.py PROJECT_DIR [--output FILE] [--mode author|reader] [--types timeline,relationships,clues].

Use --expected-sha256 for every post-chapter merge. Present the exact digest with the complete candidate changes and merge only after the author confirms that digest.

Drafting guidance

• Follow the confirmed chapter purpose, viewpoint, voice, chronology, knowledge boundaries, and style guide.
• Give each scene a concrete goal, active resistance, meaningful turn, and consequential outcome.
• Stage consequential conflict and relationship change as action and dialogue instead of summarizing the beat away.
• Show emotion through bodily signal, behavior, perception, and selective interiority rather than relying on bare feeling labels.
• Before drafting, read the selected chapter character card and exact active dossier sections according to character-context.md; never read every dossier or chapter card by default.
• Before drafting a new chapter, require a passing chapter-registry preflight. If a legacy project has chapter files without records, pause and offer a preview plus explicit author-approved scan; after scanning, rerun the preflight and audit before proceeding.
• Before drafting, load the chapter emotional question, ranked threads, cost of failure, and scene emotional ledger from emotional-focus.md. Every batch must carry entry pressure, immediate want, resistance, choice, emotional turn, and exit pressure.
• Keep pre-draft continuity to hard constraints that can invalidate the chapter. Defer detail consistency such as fine speech habits, gestures, minor descriptions, background echoes, motifs, and callbacks to the first revision pass unless one is itself a hard constraint.
• Derive ephemeral scene profiles for active speakers and maintain a knowledge ledger according to dialogue-and-clarity.md.
• Bind every major clue or explanation to a present choice, cost, relationship, belief, or available option. If it changes none of these, defer, compress, or stage its human consequence before continuing.
• If the project style/voice.md contains an approved style-import template, use it as the author's overall narrative and dialogue baseline. Treat quantitative signals as assistive checks only, never fixed sentence-length targets; preserve per-character voice, the name-blind test, and character-context rules, and follow the template's local copyright and permission boundaries.
• Preserve deliberate ambiguity while keeping actor, action, speaker, time, place, and referent clear.
• End where the chapter's change creates forward pressure; do not add a hook that contradicts its tone or resolution.

Fiction-safe AI-pattern residual loop

For /novel:chapter, /novel:review modes 2/3, and /novel:revise, preserve the first draft or source revision, read it at scene/paragraph scope, and apply the normal craft order before checking ai-writing-patterns.md. Record evidence, pattern ID, craft effect, possible intentional style, and uncertainty. Propose exactly one targeted second rewrite for accepted findings, keep the source separate, and then recheck canon, character/narrator voice, viewpoint access, and intentional irregularity. Findings and proposals remain non-final for human curation; never run a blanket humanization pass.

Precedence is character voice and scene pressure, then project/narrator voice and approved author samples, then the generic checklist. The review is not an AI detector, vocabulary blacklist, punctuation normalizer, detector-score gate, fixed-length/rhythm quota, or generic plainness mandate. /novel:status remains unchanged and /novel:audit remains continuity-first by default.

Author authority and safety

• Never promote an inference, suggestion, or planned secret to confirmed canon without author confirmation.
• Report contradictions before proposing repairs and preserve the author's chosen canon.
• Treat brainstorming, summaries, review findings, and proposed prose as non-final until accepted.
• Never silently overwrite manuscript files or structured story data.
• Preserve the author's voice. Decline imitation of a living author's style and offer high-level craft traits instead.
• Keep manuscript, research, outline, state, and visualization outputs inside the author's project.