From mimir-dm
Audits campaign documents for plot continuity by cross-referencing NPCs, locations, timelines, items, and factions to detect contradictions, orphan references, and naming inconsistencies.
npx claudepluginhub mimir-dm/mimir --plugin mimir-dmThis skill uses the workspace's default tool permissions.
Systematically verify that all references in campaign documents are internally consistent — NPCs exist, locations are established, timelines align, and facts do not contradict each other.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Systematically verify that all references in campaign documents are internally consistent — NPCs exist, locations are established, timelines align, and facts do not contradict each other.
Load and analyze all campaign content:
get_campaign_details()
# Campaign-level documents (world lore, session notes, etc.)
list_documents() # omit module_id for campaign-level docs
read_document(document_id: document_id)
# Module-level documents
list_modules()
# For each module:
get_module_details(module_id: module_id)
list_documents(module_id: module_id)
read_document(document_id: document_id)
Extract and catalog all named entities:
list_characters(character_type: "npc")list_characters(character_type: "npc", location: "..."), list_characters(character_type: "npc", faction: "...")get_character_inventory(character_id)search_catalog(category: "item")For each reference, verify:
| Check | Question |
|---|---|
| Existence | Does this NPC/location actually exist in the campaign? |
| Spelling | Is the name spelled consistently everywhere? |
| Facts | Are stated facts consistent across documents? |
| Timeline | Do dates and sequences make sense? |
| Relationships | Are NPC relationships consistently described? |
Look specifically for:
Provide a structured continuity report:
# Continuity Report: [Campaign Name]
## Summary
- Documents analyzed: X
- NPCs referenced: Y
- Locations referenced: Z
- Issues found: N
## Character Continuity
### Verified NPCs
| Name | Location | Role | Status |
|------|----------|------|--------|
| [Name] | [Location] | [Role] | [OK] Consistent |
### Orphan References
- "[Name]" mentioned in [Document] but no character record exists
- Suggestion: Create NPC or clarify reference
### Inconsistencies
- [NPC] described as [X] in [Doc1] but [Y] in [Doc2]
## Location Continuity
### Verified Locations
- [Location]: Referenced in [X] documents, consistent
### Naming Inconsistencies
- "[Name1]" vs "[Name2]" - likely same location?
## Timeline Continuity
### Verified Events
| Event | When | Referenced In |
|-------|------|---------------|
| [Event] | [Time] | [Documents] |
### Paradoxes
- [Event1] and [Event2] create impossible timeline
## Recommendations
1. [Specific fix]
2. [Specific fix]
When checking interactively: