Skip to main content
Writing & LiteratureNovel Audit32 lines

Romance Novella Continuity and Release Review

Audit a romance novella against an approved series canon, review the central relationship and ending, and document editorial release blockers.

Quick Summary7 lines
Obtain the specific manuscript revision, series bible, previous approved installment, and current editorial instructions. Give each source a version and mark which one resolves conflicting facts. Distinguish series rules from discretionary preferences. Ask for the desired review scope before grading manuscripts or applying project-specific rules.

## Key Points

- [Romance Writers of America on the romance genre](https://www.rwa.org/about-romance-fiction)
skilldb get novel-audit-skills/romance-novella-release-reviewFull skill: 32 lines
Paste into your CLAUDE.md or agent config

Romance Novella Continuity and Release Review

Obtain the specific manuscript revision, series bible, previous approved installment, and current editorial instructions. Give each source a version and mark which one resolves conflicting facts. Distinguish series rules from discretionary preferences. Ask for the desired review scope before grading manuscripts or applying project-specific rules.

Establish a continuity ledger

Record location, time, names, relationships, promises, prior events and carried objects as they appear in the approved canon. Read the new manuscript sequentially and attach chapter or page anchors to contradictions. Track point-of-view knowledge separately from objective chronology so an intentional misunderstanding remains legible. Record the status of any unresolved fact rather than inventing canon.

For example, an earlier installment says a character returned the only key at dusk. A later scene depends on that character using it before sunrise. Verify the date and key ownership in both sources. Flag the missing transfer if it affects whether the climax can happen.

Review the relationship and ending

Trace what each lead wants, what changes through their choices, and what the last scene demonstrates about their future. Romance Writers of America describes a central love story and an emotionally satisfying, optimistic ending as genre characteristics. Evaluate the manuscript's intended genre contract and its approved project expectations. Check whether the closing image resolves or intentionally carries forward the major emotional promise. Discuss intimate scenes at an editorial level through consent, character choices, pacing and emotional consequence.

Separate voice or line notes from continuity and plot issues. A repeated expression can be an intentional motif if it develops meaning, while copy-pasted language can flatten distinct scenes. Cite recurring patterns with representative locations, and explain the effect on reading rather than counting without context.

Deliver a release record

Classify issues as release blocker, substantive revision, or line edit using stated definitions. Mark a blocker when a proven contradiction or missing resolution breaks the agreed reading experience. Cite the evidence, describe the smallest satisfactory repair and list the scenes to recheck. If the project uses scoring, apply the supplied dimensions and scale rather than inventing thresholds or assuming private labels have standard meanings.

Reopen the corrected version and read each repaired passage in context. Confirm the final review cites the exact file version and distinguishes resolved items from issues still held. Delivery readiness and authorization to publish are separate actions.

Sources

Install this skill directly: skilldb add novel-audit-skills

Get CLI access →

Related Skills

Sensitivity and Representation Review

Reviews a manuscript for problematic representation, stereotypes, cultural insensitivity, and harmful tropes across multiple dimensions including gender, race, disability, sexuality, and cultural accuracy. This skill is advisory — it flags concerns for human review rather than prescribing changes. Use when the user wants a representation check before publication.

Novel Audit•173L

show-dont-tell-enforcer

Detects and fixes AI over-telling — when the narration states emotions, motivations, themes, and subtext directly instead of conveying them through action, dialogue, sensory detail, and implication. Catalogs: stated emotions ("she felt sad"), explained motivations ("he did this because"), narrated subtext ("the tension between them was palpable"), theme announcements ("she realized that love was about sacrifice"), redundant interiority (showing AND telling the same thing), and the AI tendency to explain every metaphor after deploying it. Produces a show/tell ratio and specific rewrite guidance. Use when the prose feels over-explained, hand-holdy, or like the narrator doesn't trust the reader.

Novel Audit•270L

Subplot Tracker

Identifies and tracks every subplot in a manuscript from introduction through development to resolution or abandonment. Maps subplot touchpoints across chapters and flags dropped threads, abrupt resolutions, and subplots that disappear for too long. Use when the user wants to verify all their narrative threads are properly managed.

Novel Audit•174L

Timeline Continuity Checker

Builds a chronological timeline from a manuscript by tracking every stated time reference, then identifies temporal impossibilities, travel time violations, aging inconsistencies, and contradictory event ordering. Use when the user needs to verify their story's internal chronology or suspects timeline errors in an AI-generated manuscript.

Novel Audit•172L

voice-drift-detector

Detects narrator voice drift in AI-generated novels — when the narrative voice shifts inconsistently between chapters, POV bleeds across characters in multi-POV novels, tonal register changes randomly, and the prose style oscillates between literary, casual, and generic depending on which AI session generated it. Produces a voice consistency map, identifies drift zones, and provides recalibration guidance. Use when the novel's narration feels inconsistent, or when different chapters feel like they were written by different people.

Novel Audit•235L

worldbuilding-consistency-auditor

Audits worldbuilding consistency across a novel — detects contradictions in setting rules, magic systems, technology, geography, culture, economics, politics, and physical laws that AI introduces when generating across multiple sessions. Scans for: rule contradictions, geography errors, anachronisms, economic impossibilities, cultural inconsistencies, magic/tech system violations, and generic/default world elements that lack specificity. Produces a world bible discrepancy report. Use when the novel's world has been built incrementally by AI and needs consistency verification.

Novel Audit•228L