Files
claude-plugins/fiction-assistance/commands/check-continuity.md

42 lines
2.1 KiB
Markdown
Raw Normal View History

refactor(fiction-assistance)!: reduce to portable guidance and analysis (v2.0.0) Strip the Universalis-specific vault layout and card-management machinery. The plugin is now a general-purpose fiction toolkit: nine commands that take a manuscript path/glob/selection via \$ARGUMENTS and write their output to the conversation. Surviving commands, flattened into commands/: - analyze-story: structural and statistical analysis - bechdel-test: representation tests (Bechdel + related) - check-continuity: plot/character/world continuity - check-voice: per-character voice consistency - developmental-review: structural feedback on a scene/chapter - extract-research: world-building and research inventory - final-review: synthesis of prior-phase reviews - generate-timeline: chronology with consistency checks - strategic-review: craft-based critique with priority ranking Removed (vault and card management): 10 update-*-cards commands, cleanup-generated, update-changed, update-links, update-chapter-summaries, validate-story, validate-pdf, score-scenes. The original bespoke command set is preserved in 65c29d7 for recovery. Agent (line-editor) and skill (reviewing-fiction) were already portable and are unchanged. plugin.json no longer needs the commands subdirectory paths since the layout is flat. Marketplace description updated to reflect the general-purpose scope. BREAKING CHANGE: All update-*-cards, cleanup-generated, update-changed, update-links, update-chapter-summaries, validate-story, validate-pdf, and score-scenes commands are removed. perform-bechdel-tests is renamed to bechdel-test. review-final is renamed to final-review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-16 18:28:53 -05:00
---
description: Check a manuscript for continuity problems — plot holes, character inconsistencies, world-building contradictions
argument-hint: "[path, glob, or selection]"
allowed-tools: [Read, Glob, Grep]
---
Read the manuscript at `$ARGUMENTS` (a file, a glob of chapters, or pasted text) and identify continuity issues. Report what you find directly to the conversation.
## What to check
### Character consistency
- **Traits and personality** — does the character act consistently across scenes?
- **Physical description** — height, eye color, age, scars, clothing — any contradictions?
- **Knowledge** — do they know something in chapter 4 that they shouldn't learn until chapter 7?
- **Relationships** — do established relationships develop consistently or shift without cause?
- **Speech patterns** — does their voice stay recognizable?
- **Motivations** — do their goals stay aligned with what's been established?
### World-building consistency
- **Rules of the universe** — physics, magic, technology limits, social structures
- **Geography and locations** — distances, layouts, travel times
- **History and timeline** — past events referenced consistently
- **Cultural and political details** — group behaviors, hierarchies, allegiances
### Plot logic
- **Information flow** — how does each character learn what they know? Track it
- **Cause and effect** — does each consequence have a setup?
- **Object and detail persistence** — items, wounds, weather, time of day
- **Pacing of revelations** — anything resolved before it was a problem, or set up and never paid off
## Output format
For each issue found:
- **Type** (character / world / plot)
- **Location** (chapter/scene, with quoted context where possible)
- **Issue** (what contradicts what, with both references)
- **Severity** (minor — reader probably won't catch / moderate — attentive readers will / major — breaks the story)
- **Suggested fix** (a concrete option, not just "address this")
Close with a short summary of the most load-bearing issues — the three to five the writer should fix first.