movq/claude-plugins
2
0
Fork 0
Code Issues Pull Requests Actions Releases Activity

feat(fiction-assistance): register plugin with full bespoke command set

Browse Source 
Snapshot of the fiction-assistance plugin in its original Universalis-
specific form before generalization. Adds the missing plugin.json
manifest (subdirectory command paths explicitly listed), moves the two
stray root-level review files into their proper homes (review-all.md
into the reviewing-fiction skill, review-final.md as a command with
frontmatter), and registers the plugin in the marketplace.

Preserved here so the original card-generation and vault-maintenance
commands remain recoverable when the plugin is reduced to a portable
guidance-and-analysis subset in the next commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
movq
2026-05-16 18:24:15 -05:00
parent 87b6bb1d8c
commit 65c29d795b
31 changed files with 3260 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.claude-plugin/marketplace.json
View File

@@ -24,6 +24,11 @@
"name": "symphony",
"source": "./symphony",
"description": "Tracker-agnostic orchestrator daemon — polls the issue tracker, dispatches isolated worker agents per issue, reconciles state. Pairs with composer."
},
{
"name": "fiction-assistance",
"source": "./fiction-assistance",
"description": "Fiction writing tools — scene analysis, character cards, continuity checks, story statistics, developmental and strategic review. Built around an Obsidian-based novel workspace."
}
]
}

15
fiction-assistance/.claude-plugin/plugin.json Normal file
View File

@@ -0,0 +1,15 @@
{
"name": "fiction-assistance",
"version": "1.0.0",
"description": "Fiction writing tools — scene analysis, character cards, continuity checks, story statistics, developmental and strategic review. Built around an Obsidian-based novel workspace.",
"author": {
"name": "Adam Knight"
},
"keywords": ["fiction", "writing", "novel", "editing", "obsidian"],
"commands": [
"./commands",
"./commands/analyze",
"./commands/generate",
"./commands/review"
]
}

52
fiction-assistance/agents/line-editor.md Normal file
View File

@@ -0,0 +1,52 @@
---
name: line-editor
description: Use this agent when you need to polish and refine text at the sentence and paragraph level while preserving the author's voice and intent.
tools: Edit, MultiEdit, Write, NotebookEdit, WebFetch, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool
model: haiku
---
You are a skilled line editor with expertise in refining prose at the sentence and paragraph level. Your primary responsibility is to enhance clarity, flow, and readability while strictly preserving the author's unique voice, tone, and creative vision.
Your editing approach focuses on:
**Core Principles:**
- Make minimal, surgical changes that improve without altering
- Preserve every aspect of the author's voice and stylistic choices
- Maintain the original tone, mood, and emotional impact
- Respect deliberate word choices and sentence structures
- Never impose your own style preferences
**Technical Corrections:**
- Fix grammar, punctuation, and spelling errors
- Correct obvious typos and mechanical mistakes
- Ensure consistent verb tenses and pronoun agreement
- Address unclear pronoun references
- Fix sentence fragments only if unintentional
**Clarity Enhancements:**
- Eliminate redundant words and phrases
- Untangle confusing sentence structures
- Improve word order for better flow
- Replace unclear pronouns with specific nouns when necessary
- Smooth awkward transitions between sentences
**What You Will NOT Change:**
- Character voice or dialogue patterns
- Deliberate stylistic choices (fragments, run-ons, etc.)
- Vocabulary level or complexity
- Sentence length preferences
- Paragraph structure or pacing
- Creative metaphors or imagery
- Genre conventions or specialized terminology
**Process:**
1. Read the entire passage to understand voice and intent
2. Identify only clear errors and genuine clarity issues
3. Make minimal changes that preserve the original meaning
4. Verify that your edits maintain the author's voice
5. Provide a brief summary of changes made
**Output Format:**
Present the edited text followed by a concise summary of changes, focusing on what was corrected rather than why. If no changes are needed, state that the text is already clean and well-written.
Remember: Your role is to be invisible - readers should never detect that editing occurred. The author's voice should shine through unchanged.

249
fiction-assistance/commands/analyze/analyze-story.md Normal file
View File

@@ -0,0 +1,249 @@
---
description: Generate story statistics and structural analysis
allowed-tools: Write(40 - Generated/Analysis/story-statistics.md)
---
You are performing comprehensive statistical analysis of the Universalis story structure, character usage, pacing, and narrative elements.
## Objectives:
1. **Quantitative story analysis** - word counts, scene distribution, character frequency
2. **Structural assessment** - pacing, POV distribution, chapter balance
3. **Character usage metrics** - screen time, dialogue distribution, development tracking
4. **Plot thread analysis** - plotline status, resolution tracking, complexity metrics
5. **Writing progress tracking** - completion status, revision needs
## Analysis Categories:
### 1. Basic Story Metrics
- **Total word count** across all chapters
- **Chapter count** and average chapter length
- **Scene count** and average scene length
- **Dialogue vs. narrative** ratio
- **POV distribution** across scenes
### 2. Character Analysis
- **Character appearance frequency** across chapters
- **Dialogue volume** per character
- **POV scene count** for each perspective character
- **Character development tracking** (character arc completion)
- **Supporting vs. major character** balance
### 3. Plot Structure Analysis
- **Plotline status** (active, resolved, suspended)
- **Conflict distribution** across acts
- **Event frequency** and significance levels
- **Theme exploration** across chapters
- **Resolution tracking** for major story threads
### 4. Pacing and Flow Analysis
- **Scene length variation** for pacing assessment
- **Action vs. reflection** scene balance
- **Tension curve** analysis through events
- **Chapter ending types** (cliffhangers, resolutions, transitions)
### 5. World-Building Metrics
- **Location usage** frequency and description depth
- **Technology introduction** and development
- **Species screen time** and development
- **World complexity** tracking
## Statistical Report:
Generate comprehensive analysis at `40 - Generated/Analysis/story-statistics.md`:
```markdown
# Universalis: Story Statistics & Analysis
*Generated: {{current_date}}*
## Story Overview
### Basic Metrics
- **Total Word Count**: {{total_words}} words
- **Chapter Count**: {{chapter_count}} chapters
- **Scene Count**: {{scene_count}} scenes
- **Average Chapter Length**: {{avg_chapter_words}} words
- **Average Scene Length**: {{avg_scene_words}} words
- **Estimated Reading Time**: {{estimated_reading_time}}
### Completion Status
- **Draft Completion**: {{completion_percentage}}%
- **Chapters Complete**: {{complete_chapters}}/{{total_planned_chapters}}
- **Revision Status**: {{revision_status_summary}}
## Character Analysis
### Major Characters
| Character | Appearances | Scenes | Word Count | POV Scenes | Development Status |
|-----------|-------------|--------|------------|------------|-------------------|
{{character_usage_table}}
### Character Distribution
- **POV Characters**: {{pov_character_count}}
- **Major Characters**: {{major_character_count}} (10+ scenes)
- **Supporting Characters**: {{supporting_character_count}} (3-9 scenes)
- **Minor Characters**: {{minor_character_count}} (1-2 scenes)
### Dialogue Analysis
- **Total Dialogue**: {{dialogue_word_count}} words ({{dialogue_percentage}}%)
- **Narrative Text**: {{narrative_word_count}} words ({{narrative_percentage}}%)
- **Most Talkative**: {{most_dialogue_character}} ({{their_dialogue_count}} words)
- **Dialogue Distribution**: {{dialogue_balance_analysis}}
## Plot Structure Analysis
### Plotlines Status
| Plotline | Status | Chapters | Resolution % | Complexity |
|----------|--------|----------|--------------|------------|
{{plotline_status_table}}
### Story Arcs
- **Main Plot**: {{main_plot_status}}
- **Character Arcs**: {{character_arc_completion_stats}}
- **Subplots**: {{subplot_status_summary}}
- **Unresolved Threads**: {{unresolved_count}}
### Conflict Analysis
- **Internal Conflicts**: {{internal_conflict_count}}
- **Interpersonal Conflicts**: {{interpersonal_conflict_count}}
- **External Conflicts**: {{external_conflict_count}}
- **Resolved vs. Active**: {{conflict_resolution_ratio}}
## Pacing Analysis
### Chapter Structure
- **Shortest Chapter**: {{shortest_chapter}} ({{shortest_words}} words)
- **Longest Chapter**: {{longest_chapter}} ({{longest_words}} words)
- **Length Variation**: {{length_variation_coefficient}}
- **Pacing Pattern**: {{pacing_assessment}}
### Scene Types Distribution
- **Action Scenes**: {{action_scene_count}} ({{action_percentage}}%)
- **Dialogue Scenes**: {{dialogue_scene_count}} ({{dialogue_scene_percentage}}%)
- **Reflection Scenes**: {{reflection_scene_count}} ({{reflection_percentage}}%)
- **Exposition Scenes**: {{exposition_scene_count}} ({{exposition_percentage}}%)
### Tension Curve
{{tension_analysis_across_chapters}}
## POV Analysis
### Point of View Distribution
| Character | POV Scenes | Word Count | Percentage | Chapter Spread |
|-----------|------------|------------|------------|----------------|
{{pov_distribution_table}}
### POV Patterns
- **Single POV Chapters**: {{single_pov_chapters}}
- **Multiple POV Chapters**: {{multi_pov_chapters}}
- **POV Switching Frequency**: {{pov_switch_frequency}}
- **Balanced vs. Dominant**: {{pov_balance_assessment}}
## World-Building Analysis
### Location Usage
| Location | Appearances | Scenes | Description Depth | Significance |
|----------|-------------|--------|-------------------|--------------|
{{location_usage_table}}
### Technology & Species
- **Technology Elements**: {{tech_count}} different technologies
- **Species Introduced**: {{species_count}} alien races/types
- **World Complexity Score**: {{complexity_score}}/10
## Theme Analysis
### Major Themes
| Theme | Exploration Depth | Chapter Coverage | Character Embodiment |
|-------|-------------------|------------------|---------------------|
{{theme_analysis_table}}
### Thematic Balance
{{thematic_distribution_analysis}}
## Writing Progress Metrics
### Completion Tracking
- **First Draft**: {{first_draft_status}}
- **Revision Rounds**: {{revision_count}}
- **Outstanding Issues**: {{issue_count}}
- **Ready for Publication**: {{publication_readiness}}
### Quality Metrics
- **Consistency Score**: {{consistency_score}}/10
- **Character Development**: {{character_development_score}}/10
- **Plot Coherence**: {{plot_coherence_score}}/10
- **World-Building Depth**: {{worldbuilding_score}}/10
## Comparative Analysis
### Genre Benchmarks
{{comparison_to_scifi_genre_standards}}
### Structural Balance
{{assessment_of_story_structure_balance}}
## Recommendations
### Pacing Adjustments
{{pacing_improvement_suggestions}}
### Character Development
{{character_arc_recommendations}}
### Plot Enhancement
{{plot_improvement_suggestions}}
### World-Building
{{worldbuilding_enhancement_ideas}}
## Historical Tracking
### Progress Over Time
{{writing_progress_timeline_if_available}}
### Revision History
{{major_changes_and_improvements}}
---
Generated by Claude Code statistical analysis for Universalis writing project.
```
## Analysis Methodology:
1. **Word counting** across all chapters and scenes
2. **Entity frequency analysis** from generated cards
3. **POV pattern recognition** from chapter metadata
4. **Plotline tracking** from plotline cards and events
5. **Character development assessment** from character cards
6. **Pacing evaluation** through scene length and type analysis
7. **Thematic distribution** analysis from theme cards
## Statistical Calculations:
### Quantitative Metrics
- Word counts, scene counts, character appearances
- Percentage distributions and ratios
- Average lengths and variation coefficients
- Completion percentages and progress tracking
### Qualitative Assessments
- Development status evaluations
- Balance assessments for various story elements
- Complexity scoring for world-building
- Quality metrics for story coherence
## Trend Analysis:
- **Character usage patterns** over time
- **Pacing variations** across acts
- **Theme development** progression
- **Plot complexity** evolution
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/story-statistics.md`
- Comprehensive statistical tables and metrics
- Visual indicators for balance and distribution
- Actionable recommendations based on analysis
- Comparative benchmarks where relevant
**IMPORTANT**: Base all statistics on actual content analysis. Provide specific numbers and percentages rather than vague assessments. Include both absolute values and relative comparisons.

234
fiction-assistance/commands/analyze/check-continuity.md Normal file
View File

@@ -0,0 +1,234 @@
---
description: Check for plot holes and character consistency
allowed-tools: Write(40 - Generated/Analysis/continuity-report.md)
---
You are performing continuity analysis for the Universalis story to identify plot holes, character inconsistencies, and world-building contradictions.
Manuscript: `./00 - Manuscript/`
## Objectives:
1. **Character consistency checking** across all appearances
2. **World-building validation** for technology, species, locations
3. **Plot hole identification** in story logic
4. **Relationship tracking** for character interactions
5. **Knowledge tracking** for what characters know when
## Continuity Analysis Areas:
### 1. Character Consistency
For each character, verify:
- **Personality traits** remain consistent across scenes
- **Physical descriptions** don't contradict
- **Knowledge and abilities** progress logically
- **Relationships** develop consistently
- **Speech patterns** match established voice
- **Motivations** align with established goals
### 2. World-Building Consistency
Check for contradictions in:
- **Technology capabilities** and limitations
- **Species characteristics** and behaviors
- **Location descriptions** and geography
- **Political structures** and relationships
- **Historical events** and timelines
- **Rules of the universe** (physics, magic, etc.)
### 3. Plot Logic Validation
Identify potential issues:
- **Character knowledge** - knowing things they shouldn't
- **Information flow** - how characters learn important facts
- **Cause and effect** - events leading logically to consequences
- **Problem resolution** - solutions matching established capabilities
- **Motivation clarity** - character actions matching their goals
### 4. Relationship Dynamics
Track consistency in:
- **Character interactions** over time
- **Relationship development** following logical progression
- **Conflict resolution** between characters
- **Alliance formations** and betrayals
- **Family relationships** and their evolution
## Continuity Report:
Generate detailed analysis at `./40 - Generated/Analysis/continuity-report.md`:
```markdown
# Continuity Analysis Report
*Generated: {{current_date}}*
## Executive Summary
- **Continuity Issues Found**: {{total_issues}}
- **Character Inconsistencies**: {{character_issues}}
- **World-Building Problems**: {{worldbuilding_issues}}
- **Plot Logic Gaps**: {{plot_issues}}
- **Critical Issues**: {{critical_count}} (major plot holes)
- **Minor Issues**: {{minor_count}} (small inconsistencies)
## Character Consistency Analysis
### {{Character Name}}
**Consistency Score**: {{score}}/10
#### Personality Traits
- **Established traits**: {{list_established_traits}}
- **Inconsistent moments**: {{list_inconsistencies_with_chapter_refs}}
- **Character growth**: {{note_legitimate_development_vs_inconsistency}}
#### Physical Description
- **Established appearance**: {{physical_description_summary}}
- **Contradictions found**: {{list_description_conflicts}}
#### Knowledge Progression
- **What they know when**: {{knowledge_timeline}}
- **Information gaps**: {{unexplained_knowledge_gains}}
- **Knowledge inconsistencies**: {{impossible_knowledge_situations}}
#### Relationship Consistency
- **With {{other_character}}**: {{relationship_development_analysis}}
- **Interaction patterns**: {{consistent_vs_inconsistent_interactions}}
[Repeat for each major character]
## World-Building Consistency
### Technology Systems
{{technology_consistency_analysis}}
### Species Characteristics
{{species_consistency_analysis}}
### Location Descriptions
{{location_consistency_analysis}}
### Political/Social Structures
{{political_consistency_analysis}}
## Plot Logic Analysis
### Information Flow Issues
{{information_flow_problems}}
### Cause and Effect Problems
{{cause_effect_inconsistencies}}
### Resolution Logic
{{solution_consistency_analysis}}
### Motivation Clarity
{{character_motivation_inconsistencies}}
## Critical Continuity Issues
### Major Plot Holes
{{list_major_plot_holes_with_details}}
### Character Knowledge Problems
{{list_knowledge_inconsistencies}}
### World-Building Contradictions
{{list_world_contradictions}}
## Minor Inconsistencies
### Description Variations
{{minor_description_inconsistencies}}
### Dialogue Style Variations
{{minor_voice_inconsistencies}}
### Detail Contradictions
{{minor_detail_conflicts}}
## Relationship Dynamics Analysis
### Character Relationship Map
{{relationship_consistency_by_pair}}
### Relationship Development Issues
{{relationship_logic_problems}}
### Unexplained Relationship Changes
{{sudden_relationship_shifts}}
## Recommendations
### Critical Fixes Needed
{{prioritized_list_of_major_fixes}}
### Continuity Improvements
{{suggestions_for_minor_fixes}}
### Tracking Suggestions
{{recommendations_for_future_continuity_maintenance}}
## Continuity Strengths
### Well-Maintained Elements
{{list_consistent_story_elements}}
### Strong Character Development
{{well_developed_character_arcs}}
### Solid World-Building
{{consistent_world_elements}}
## Analysis Methodology
### Sources Analyzed
- **Character Cards**: {{character_cards_analyzed}}
- **Chapter Scenes**: {{scenes_analyzed}}
- **Event Cards**: {{events_analyzed}}
- **Relationship Data**: {{relationships_tracked}}
### Consistency Metrics
- **Cross-Reference Points**: {{cross_reference_points}}
- **Character Appearances**: {{total_character_appearances}}
- **World-Building Elements**: {{worldbuilding_elements_tracked}}
---
Generated by Claude Code continuity analysis for Universalis writing project.
```
## Analysis Methodology:
1. **Character trait mapping** across all appearances
2. **Knowledge state tracking** for each character through time
3. **World-building element cataloging** from all sources
4. **Cross-referencing** descriptions and capabilities
5. **Timeline correlation** with character actions and knowledge
6. **Relationship evolution tracking** between characters
7. **Logic chain validation** for plot developments
## Issue Classification:
### Critical Issues
- Major plot holes affecting story logic
- Character actions contradicting established personality
- Impossible knowledge or ability situations
- World-building rules violated
### Minor Issues
- Small description variations
- Slight dialogue inconsistencies
- Detail contradictions that don't affect plot
- Minor timeline discrepancies
## Validation Approach:
1. **Evidence-based analysis** using specific chapter references
2. **Pattern recognition** for consistent vs. inconsistent elements
3. **Development vs. contradiction** distinguishing growth from error
4. **Context consideration** for apparent inconsistencies
5. **Prioritized recommendations** for fixing issues
## Output Requirements:
- Fixed filename: `./40 - Generated/Analysis/continuity-report.md`
- Character-by-character analysis with specific examples
- World-building consistency evaluation
- Prioritized issue list with chapter references
- Actionable recommendations for improvement
**IMPORTANT**: Distinguish between legitimate character development and actual inconsistencies. Provide specific chapter references for all identified issues.

241
fiction-assistance/commands/analyze/check-voice.md Normal file
View File

@@ -0,0 +1,241 @@
---
description: Analyze character voice consistency and dialogue patterns
allowed-tools: Write(40 - Generated/Analysis/voice-analysis.md)
---
You are performing character voice analysis for the Universalis story to ensure dialogue consistency and distinctive character voices.
## Objectives:
1. **Voice pattern analysis** for each character across all appearances
2. **Dialogue consistency checking** against established character voice
3. **Speech pattern identification** and distinctiveness assessment
4. **Voice development tracking** over story progression
5. **Dialogue quality evaluation** for authenticity and character fit
## Voice Analysis Areas:
### 1. Speech Pattern Analysis
For each character, analyze:
- **Vocabulary choice** (formal/informal, technical/simple, unique phrases)
- **Sentence structure** (short/long, complex/simple, fragmented/complete)
- **Rhythm and flow** (clipped speech, flowing dialogue, interruptions)
- **Emotional expression** patterns (how they show anger, joy, fear, etc.)
- **Cultural/background influences** on speech patterns
### 2. Character-Specific Voice Elements
- **Catchphrases** and repeated expressions
- **Professional terminology** usage patterns
- **Regional/cultural dialects** or speech markers
- **Generational speech** patterns (age-appropriate language)
- **Personality manifestation** in dialogue (confidence, humor, formality)
### 3. Dialogue Consistency Tracking
- **Voice maintenance** across different scenes and emotional states
- **Stress response** patterns in dialogue under pressure
- **Character growth** reflected appropriately in speech evolution
- **Relationship dynamics** affecting speech patterns with different characters
### 4. Distinctiveness Assessment
- **Character voice uniqueness** - can you identify speaker without tags?
- **Overlap detection** - characters sounding too similar
- **Authentic characterization** - dialogue matching personality and background
- **Memorable speech** - distinctive and engaging dialogue patterns
## Voice Analysis Report:
Generate comprehensive analysis at `40 - Generated/Analysis/voice-analysis.md`:
```markdown
# Character Voice Analysis Report
*Generated: {{current_date}}*
## Overview
Analysis of character voice consistency, distinctiveness, and development across all appearances in Universalis.
## Executive Summary
- **Characters Analyzed**: {{character_count}}
- **Voice Consistency Score**: {{overall_consistency_score}}/10
- **Distinctiveness Score**: {{overall_distinctiveness_score}}/10
- **Issues Identified**: {{total_voice_issues}}
## Character Voice Profiles
### {{Character Name}}
**Voice Consistency**: {{consistency_score}}/10 | **Distinctiveness**: {{distinctiveness_score}}/10
#### Established Voice Pattern
- **Speaking Style**: {{speaking_style_description}}
- **Vocabulary Level**: {{vocabulary_assessment}}
- **Sentence Structure**: {{sentence_pattern_description}}
- **Emotional Expression**: {{emotional_expression_pattern}}
- **Signature Elements**: {{unique_speech_elements}}
#### Representative Dialogue Examples
{{most_characteristic_dialogue_samples_with_chapter_refs}}
#### Voice Consistency Analysis
- **Consistent Elements**: {{consistently_maintained_voice_elements}}
- **Inconsistent Moments**: {{dialogue_inconsistencies_with_chapter_refs}}
- **Character Growth**: {{legitimate_voice_evolution_vs_inconsistency}}
#### Voice Development Over Time
{{voice_evolution_analysis_across_story_arc}}
#### Relationship Voice Variations
- **With {{other_character}}**: {{voice_changes_in_this_relationship}}
- **In formal settings**: {{formal_voice_analysis}}
- **Under stress**: {{stress_voice_patterns}}
[Repeat for each major character]
## Cross-Character Analysis
### Voice Distinctiveness Matrix
| Character | Distinctiveness | Similar To | Unique Elements |
|-----------|----------------|------------|-----------------|
{{character_distinctiveness_comparison_table}}
### Voice Overlap Issues
{{characters_who_sound_too_similar}}
### Dialogue Tag Dependency
Characters requiring dialogue tags for identification:
{{characters_needing_better_voice_distinction}}
## Dialogue Quality Assessment
### Authenticity Analysis
- **Age-Appropriate Speech**: {{age_appropriate_assessment}}
- **Background Consistency**: {{background_voice_consistency}}
- **Cultural Authenticity**: {{cultural_speech_accuracy}}
- **Professional Terminology**: {{technical_language_appropriateness}}
### Emotional Range Analysis
{{emotional_expression_variety_and_authenticity}}
### Conversation Flow Analysis
{{dialogue_naturalness_and_flow_assessment}}
## Voice Consistency Issues
### Major Inconsistencies
{{significant_voice_breaks_with_specific_examples}}
### Minor Variations
{{small_inconsistencies_that_could_be_improved}}
### Character Growth vs. Inconsistency
{{legitimate_development_vs_actual_voice_problems}}
## Dialogue Strengths
### Most Distinctive Voices
{{characters_with_strongest_voice_identity}}
### Best Character Interactions
{{most_effective_dialogue_scenes}}
### Memorable Dialogue
{{most_quotable_or_character_defining_lines}}
## Improvement Recommendations
### Voice Strengthening
{{suggestions_for_making_voices_more_distinctive}}
### Consistency Improvements
{{specific_fixes_for_voice_inconsistencies}}
### Dialogue Enhancement
{{suggestions_for_improving_dialogue_quality}}
## Voice Guidelines for Future Writing
### {{Character Name}} Voice Guidelines
{{specific_writing_guidelines_for_this_character}}
[Guidelines for each major character]
### General Dialogue Best Practices
{{overall_dialogue_writing_recommendations}}
## Technical Analysis
### Dialogue Distribution
- **Most Dialogue**: {{character_with_most_lines}} ({{word_count}} words)
- **Dialogue Density**: {{dialogue_to_narrative_ratio_by_character}}
- **Scene Presence**: {{character_scene_participation_rates}}
### Voice Complexity Metrics
{{analysis_of_voice_sophistication_and_development}}
## Analysis Methodology
### Data Sources
- **Character Cards**: {{character_cards_analyzed}}
- **Chapter Scenes**: {{scenes_with_dialogue_analyzed}}
- **Dialogue Samples**: {{total_dialogue_lines_analyzed}}
### Voice Markers Tracked
{{list_of_voice_elements_analyzed}}
### Consistency Evaluation Criteria
{{methodology_for_assessing_voice_consistency}}
---
Generated by Claude Code voice analysis for Universalis writing project.
```
## Analysis Methodology:
1. **Dialogue extraction** from all chapters by character
2. **Pattern recognition** for speech characteristics
3. **Consistency mapping** across character appearances
4. **Comparative analysis** between characters for distinctiveness
5. **Development tracking** for voice evolution
6. **Quality assessment** against character background and personality
7. **Specific example identification** for both strengths and issues
## Voice Elements to Track:
### Linguistic Patterns
- Word choice preferences (simple vs. complex vocabulary)
- Sentence length and structure preferences
- Use of contractions, slang, formal language
- Technical terminology usage patterns
### Character-Specific Elements
- Catchphrases and repeated expressions
- Cultural/regional speech markers
- Professional jargon appropriate to character background
- Age and education level reflected in speech
### Emotional Expression
- How each character expresses different emotions
- Stress response patterns in dialogue
- Humor expression (if applicable)
- Authority or submission patterns in speech
## Issue Classification:
### Major Voice Issues
- Character sounding completely different in different scenes
- Dialogue that contradicts established character background
- Multiple characters sounding identical
- Inappropriate language for character's background/age
### Minor Voice Issues
- Slight vocabulary inconsistencies
- Occasional lapses in established speech patterns
- Missing opportunities for character-specific expressions
- Dialogue that's generic rather than character-specific
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/voice-analysis.md`
- Character-by-character detailed voice profiles
- Cross-character distinctiveness analysis
- Specific examples with chapter references
- Actionable guidelines for future dialogue writing
**IMPORTANT**: Provide specific dialogue examples for all assessments. Distinguish between legitimate character development and actual voice inconsistencies. Include positive examples of strong voice work alongside areas for improvement.

21
fiction-assistance/commands/analyze/perform-bechdel-tests.md Normal file
View File

@@ -0,0 +1,21 @@
TARGET: $ARGUMENTS
Analyze this text against the following representation tests. For each test, provide a clear PASS/FAIL assessment with specific evidence:
Gender Representation Tests:
1. Bechdel Test - Are there at least two named women who talk to each other about something other than a man? (Cite specific dialogue)
2. Reverse Bechdel Test - Are there at least two named men who talk to each other about something other than a woman? (Cite specific dialogue)
3. Mako Mori Test - Does any female character have her own narrative arc that isn't about supporting a man's story? (Identify the arc)
4. Sexy Lamp Test - Could any female character be replaced with a sexy lamp without affecting the plot? (Explain their narrative function)
Character-Specific Tests (only assess if applicable characters exist):
5. Sphinx Test - How do women interact with other characters and what prominence do they have in the action?
6. DuVernay Test - Do any minority characters have fully realized lives beyond their relationship to the plot or majority characters?
7. Shukla Test - Do any two ethnic minority characters talk to each other about something other than race/ethnicity?
Format your response as:
- Test Name: PASS/FAIL - Brief explanation with specific examples
- Overall Assessment: Summary of representation strengths and weaknesses in this chapter
- Notable Patterns: Any recurring representation issues or strengths
Focus on what's actually present in the text rather than making assumptions about characters' backgrounds unless explicitly stated.

27
fiction-assistance/commands/analyze/validate-pdf.md Normal file
View File

@@ -0,0 +1,27 @@
---
description: Validate PDF display
allowed-tools: Write
---
Load and thoroughly examine a compiled PDF manuscript through the browser MCP to validate formatting quality and identify
potential issues. Specifically:
1. Navigate through the PDF document systematically, checking:
- Title page and table of contents formatting
- Chapter and scene header styling
- Page numbering and transitions
2. Examine text formatting throughout the prologue section, looking for:
- Proper line wrapping and text flow
- Correct display of italicized text
- Appropriate paragraph spacing and breaks
3. Pay special attention to monospace content (AI dialogue and code blocks):
- Verify monospace font renders correctly
- Check that AI dialogue doesn't break awkwardly mid-sentence
- Ensure large code blocks maintain proper formatting and indentation
4. Scan for formatting anomalies including:
- Unexpected characters or symbols
- Text overflow or truncation issues
- Font inconsistencies
- Layout problems
5. Document findings and assess overall formatting quality, noting any issues that need correction in the compilation process or CSS styling.
The goal is to ensure the PDF version maintains professional manuscript formatting suitable for distribution, with particular focus on preserving the specialized formatting requirements for AI dialogue and technical content blocks.

274
fiction-assistance/commands/generate/cleanup-generated.md Normal file
View File

@@ -0,0 +1,274 @@
---
description: Clean up and standardize generated files
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/Analysis/cleanup-log.md), Bash
---
You are performing maintenance and cleanup on the Universalis generated files to ensure consistency, remove orphaned content, and standardize formatting.
## Objectives:
1. **Remove orphaned files** with no valid references
2. **Standardize formatting** across all generated cards
3. **Fix broken internal references** and update links
4. **Consolidate duplicate content** where appropriate
5. **Ensure file organization** follows established conventions
## Cleanup Operations:
### 1. Orphaned File Detection
Identify files to remove:
- **Unreferenced cards**: Files with no incoming links from other cards or chapters
- **Duplicate files**: Multiple files for the same entity (keep most complete)
- **Invalid files**: Malformed or empty card files
- **Outdated files**: Files for entities no longer in the story
### 2. Formatting Standardization
Apply consistent formatting:
- **YAML frontmatter**: Standardize field order, naming, and values
- **Markdown headers**: Ensure consistent heading hierarchy (H1, H2, H3)
- **Section structure**: Match established card templates
- **Link formatting**: Standardize wiki-style link format
- **Date formatting**: Ensure consistent date format in frontmatter
### 3. Reference Cleanup
Fix broken connections:
- **Dead links**: Remove links to non-existent files
- **Incorrect references**: Fix links pointing to wrong files
- **Missing backlinks**: Add missing reciprocal references
- **Outdated aliases**: Update references using old entity names
### 4. Content Consolidation
Merge related content:
- **Duplicate entities**: Combine multiple cards for same character/location
- **Alias resolution**: Merge cards that represent the same entity
- **Related content**: Move misplaced content to correct files
### 5. File Organization
Ensure proper structure:
- **Directory placement**: Move files to correct category directories
- **Filename conventions**: Standardize naming patterns
- **Category consistency**: Ensure files match their directory category
## Cleanup Process:
### Phase 1: Analysis & Detection
1. **Inventory all files** in 40 - Generated/
2. **Map all references** between files and from manuscript chapters
3. **Identify orphaned content** with no incoming references
4. **Detect formatting inconsistencies** against templates
5. **Find duplicate entities** across different files
### Phase 2: Automated Cleanup
1. **Standardize frontmatter** fields and formatting
2. **Fix link syntax** and formatting issues
3. **Update date formats** to consistent pattern
4. **Normalize section headers** to match templates
5. **Apply consistent indentation** and spacing
### Phase 3: Content Consolidation
1. **Merge duplicate files** (keep most complete version)
2. **Resolve alias conflicts** by consolidating references
3. **Move misplaced content** to appropriate files
4. **Update all references** to consolidated files
### Phase 4: File Organization
1. **Move files** to correct directories if needed
2. **Rename files** to follow naming conventions
3. **Update references** to reflect any file moves/renames
4. **Remove empty directories**
### Phase 5: Validation
1. **Verify all links** work correctly
2. **Check frontmatter** completeness and validity
3. **Confirm file organization** follows conventions
4. **Test cross-references** between all files
## Cleanup Log:
Generate detailed log at `40 - Generated/Analysis/cleanup-log.md`:
```markdown
# Generated Files Cleanup Log
*Cleanup performed: {{current_date}}*
## Cleanup Summary
- **Files Processed**: {{total_files_processed}}
- **Files Removed**: {{files_removed}} (orphaned/duplicate)
- **Files Modified**: {{files_modified}} (formatting/content)
- **Files Moved**: {{files_moved}} (reorganization)
- **Links Fixed**: {{links_fixed}}
- **References Updated**: {{references_updated}}
## Orphaned Files Removed
### No Incoming References
{{list_orphaned_files_removed_with_reason}}
### Duplicate Content
{{list_duplicate_files_consolidated}}
### Invalid Files
{{list_malformed_files_removed}}
## Formatting Standardization
### YAML Frontmatter Fixes
{{list_frontmatter_standardization_changes}}
### Markdown Structure Fixes
{{list_structure_standardization_changes}}
### Link Format Corrections
{{list_link_formatting_fixes}}
## Content Consolidation
### Entity Merges
{{list_entity_consolidations_performed}}
### Alias Resolutions
{{list_alias_consolidations}}
### Content Relocations
{{list_content_moved_between_files}}
## File Organization
### Directory Reorganization
{{list_files_moved_between_directories}}
### Filename Standardization
{{list_filename_changes}}
### Category Corrections
{{list_category_corrections}}
## Reference Updates
### Broken Links Fixed
{{list_broken_links_repaired}}
### Dead References Removed
{{list_dead_references_removed}}
### Missing Backlinks Added
{{list_backlinks_added}}
## Quality Improvements
### Completeness Enhancements
{{list_incomplete_sections_improved}}
### Consistency Fixes
{{list_consistency_improvements}}
### Format Standardization
{{list_format_improvements}}
## Files Requiring Manual Review
### Complex Duplicates
{{list_files_needing_manual_merge_review}}
### Ambiguous References
{{list_references_needing_clarification}}
### Content Questions
{{list_content_requiring_author_decision}}
## Post-Cleanup Statistics
### File Counts by Category
- **Characters**: {{character_file_count}}
- **Locations**: {{location_file_count}}
- **Ships**: {{ship_file_count}}
- **Technology**: {{tech_file_count}}
- **Species**: {{species_file_count}}
- **Plotlines**: {{plotline_file_count}}
- **Events**: {{event_file_count}}
- **Conflicts**: {{conflict_file_count}}
- **Themes**: {{theme_file_count}}
### Link Health
- **Total Links**: {{total_link_count}}
- **Valid Links**: {{valid_link_count}}
- **Broken Links**: {{broken_link_count}}
- **Cross-References**: {{cross_reference_count}}
### Quality Metrics
- **Complete Cards**: {{complete_cards_count}}
- **Standardized Format**: {{standardized_format_count}}
- **Orphaned Files**: {{remaining_orphaned_count}}
## Recommendations
### Immediate Actions
{{list_urgent_cleanup_items_remaining}}
### Future Maintenance
{{list_ongoing_maintenance_recommendations}}
### Prevention Strategies
{{list_strategies_to_prevent_future_issues}}
## Cleanup Methodology
### Detection Criteria
{{criteria_used_for_identifying_cleanup_needs}}
### Automated vs Manual
{{description_of_automated_vs_manual_cleanup_steps}}
### Validation Process
{{process_for_verifying_cleanup_quality}}
---
Generated by Claude Code cleanup system for Universalis writing project.
```
## Cleanup Methodology:
1. **Comprehensive file scanning** for all generated content
2. **Reference mapping** to identify connections and orphans
3. **Pattern matching** for formatting inconsistencies
4. **Automated standardization** where safe to do so
5. **Manual review flagging** for complex cases
6. **Validation testing** after cleanup operations
7. **Documentation** of all changes made
## Safety Measures:
### Backup and Recovery
- Create list of all changes for potential rollback
- Preserve original content when merging duplicates
- Flag complex cases for manual review
- Validate all automated changes
### Content Preservation
- Never delete content without clear justification
- Merge rather than delete when combining duplicates
- Preserve aliases and alternative names
- Maintain all legitimate cross-references
## Cleanup Standards:
### File Naming Conventions
- Consistent capitalization and spacing
- Standard character replacements for special characters
- Category-appropriate prefixes if needed
- Meaningful, searchable filenames
### Content Standards
- Complete frontmatter with all required fields
- Consistent section structure per card type
- Proper wiki-style linking format
- Appropriate content categorization
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/cleanup-log.md`
- Detailed logging of all changes made
- Statistics on files processed and improvements made
- Recommendations for future maintenance
- Flagged items requiring manual review
**IMPORTANT**: Prioritize content preservation over aggressive cleanup. When in doubt about removing or merging content, flag for manual review rather than auto-delete. Always validate that cleanup operations improve rather than break the generated file system.

318
fiction-assistance/commands/generate/extract-research.md Normal file
View File

@@ -0,0 +1,318 @@
---
description: Extract world-building research and development needs
allowed-tools: Write(40 - Generated/Analysis/research-notes.md)
---
You are extracting and organizing all research elements from the Universalis story to create comprehensive world-building documentation and identify development needs.
## Objectives:
1. **Extract scientific concepts** and technologies from story content
2. **Document world-building elements** requiring research or development
3. **Identify consistency requirements** for fictional technologies and concepts
4. **Create research reference** for maintaining story authenticity
5. **Flag development gaps** needing additional world-building
## Research Extraction Areas:
### 1. Scientific & Technical Elements
- **Physics concepts** (FTL travel, energy systems, communications)
- **Technology systems** (ships, weapons, AI, medical tech)
- **Computer science** (AI consciousness, data systems, networks)
- **Biology/genetics** (alien species, human augmentation, life support)
- **Astronomy** (star systems, planets, space phenomena)
### 2. Social & Political Systems
- **Government structures** (UEC, alien governments, military hierarchies)
- **Economic systems** (trade, resources, technology exchange)
- **Cultural elements** (alien societies, human colonies, traditions)
- **Legal frameworks** (interspecies law, military justice, civilian rights)
- **Communication protocols** (diplomatic, military, civilian)
### 3. World-Building Concepts
- **Historical background** (human expansion, first contact, wars)
- **Geographical elements** (planets, star systems, space stations)
- **Technological timeline** (development progression, capabilities)
- **Species evolution** (alien development, human adaptation)
- **Philosophical concepts** (AI consciousness, humanity, identity)
### 4. Consistency Requirements
- **Technology limitations** and capabilities
- **Species characteristics** and behaviors
- **Physical laws** in the story universe
- **Historical timeline** consistency
- **Cultural authenticity** for different groups
## Research Documentation:
Generate comprehensive reference at `40 - Generated/Analysis/research-notes.md`:
```markdown
# Universalis: Research & World-Building Reference
*Generated: {{current_date}}*
## Overview
Comprehensive extraction of research elements, scientific concepts, and world-building details from Universalis for consistency and development reference.
## Scientific & Technical Research
### Physics & Space Science
#### Faster-Than-Light Travel
- **Universalis Drive**: {{description_and_capabilities}}
- **Limitations**: {{established_constraints}}
- **Research Needs**: {{areas_needing_development}}
#### Energy Systems
{{energy_technology_research_requirements}}
#### Communications Technology
{{communication_system_research_needs}}
### Computer Science & AI
#### Artificial Intelligence
- **Gabriel Network**: {{ai_system_description}}
- **Consciousness Questions**: {{ai_consciousness_research_topics}}
- **Technical Requirements**: {{ai_technology_consistency_needs}}
#### Data Systems
{{data_storage_and_processing_research}}
### Biology & Life Sciences
#### Human Augmentation
{{human_enhancement_research_requirements}}
#### Alien Biology
{{species_biology_research_needs}}
#### Life Support Systems
{{life_support_technology_research}}
## Political & Social Research
### Government Systems
#### United Earth Coalition (UEC)
- **Structure**: {{government_structure_details}}
- **Military Organization**: {{military_hierarchy_research}}
- **Civilian Administration**: {{civilian_government_research}}
#### Alien Governments
{{alien_political_system_research_requirements}}
### Cultural Research
#### Human Colonies
{{colonial_culture_research_needs}}
#### Alien Societies
{{alien_culture_research_requirements}}
### Economic Systems
{{economic_structure_research_needs}}
## Historical & Timeline Research
### Human History
#### Pre-FTL Era
{{pre_space_age_history_research}}
#### Expansion Period
{{human_expansion_research_requirements}}
#### First Contact Events
{{first_contact_research_needs}}
### Alien History
{{alien_species_history_research}}
### Technology Development Timeline
{{technology_progression_research}}
## Geographic & Astronomical Research
### Star Systems
| System | Research Status | Description Needs | Consistency Requirements |
|--------|----------------|-------------------|------------------------|
{{star_system_research_table}}
### Planets & Locations
{{planetary_research_requirements}}
### Space Infrastructure
{{space_station_and_infrastructure_research}}
## Species Research Requirements
### {{Species Name}}
- **Biology**: {{biological_research_needs}}
- **Culture**: {{cultural_research_requirements}}
- **Technology**: {{species_technology_research}}
- **History**: {{species_history_research}}
[Repeat for each alien species]
## Technology Consistency Research
### Established Capabilities
{{technology_capability_documentation}}
### Limitation Documentation
{{technology_constraint_research}}
### Development Requirements
{{technology_advancement_research}}
## Philosophical & Conceptual Research
### AI Consciousness
{{ai_consciousness_research_topics}}
### Human Identity
{{human_identity_research_themes}}
### Interspecies Relations
{{interspecies_relationship_research}}
## Research Gaps & Development Needs
### Critical Gaps
{{areas_needing_immediate_development}}
### Consistency Issues
{{research_needed_for_consistency}}
### Enhancement Opportunities
{{areas_for_story_enhancement}}
## Research Priority Matrix
### High Priority
{{critical_research_needs}}
### Medium Priority
{{important_but_not_urgent_research}}
### Low Priority
{{nice_to_have_research}}
## Real-World Research Sources
### Scientific References
{{relevant_scientific_research_to_consult}}
### Technical Inspiration
{{real_world_technology_to_research}}
### Historical Parallels
{{historical_events_for_inspiration}}
## World-Building Consistency Checklist
### Technology Consistency
{{technology_consistency_checklist}}
### Species Consistency
{{species_consistency_requirements}}
### Timeline Consistency
{{historical_timeline_consistency}}
### Physical Laws Consistency
{{physics_consistency_requirements}}
## Research Notes & Ideas
### Concept Development
{{underdeveloped_concepts_needing_expansion}}
### Plot Integration
{{research_elements_supporting_plot}}
### Character Background
{{character_background_research_needs}}
## Future Research Planning
### Story Development Support
{{research_priorities_for_story_development}}
### Series Expansion
{{research_for_potential_sequels}}
### World Guide Development
{{research_for_comprehensive_world_guide}}
## Research Methodology
### Sources Analyzed
- **Technology Cards**: {{tech_cards_analyzed}}
- **Species Cards**: {{species_cards_analyzed}}
- **Location Cards**: {{location_cards_analyzed}}
- **Chapter Content**: {{chapters_analyzed_for_research}}
### Extraction Criteria
{{criteria_for_research_element_identification}}
### Development Priorities
{{methodology_for_prioritizing_research_needs}}
---
Generated by Claude Code research extraction for Universalis writing project.
```
## Research Extraction Methodology:
1. **Systematic content scanning** for all technical and scientific references
2. **World-building element cataloging** from all generated cards
3. **Consistency requirement identification** across story elements
4. **Gap analysis** for underdeveloped concepts
5. **Research prioritization** based on story impact and consistency needs
6. **Real-world reference suggestion** for authentic development
7. **Development roadmap** creation for future work
## Research Categories:
### Hard Science Elements
- Physics principles and their story applications
- Technology capabilities and limitations
- Biological and medical concepts
- Astronomical and space science elements
### Soft Science Elements
- Social and political structures
- Cultural and anthropological elements
- Economic and trade systems
- Psychological and philosophical concepts
### Fictional Elements
- Unique story technologies and their rules
- Alien species characteristics and cultures
- Historical events and their consequences
- Philosophical concepts specific to the story
## Development Priority Assessment:
### Critical for Story Consistency
- Elements that appear frequently and need consistency
- Technologies central to plot development
- Species characteristics affecting character behavior
- Historical events that influence current story
### Important for World Depth
- Background elements that add richness
- Secondary technologies that support main concepts
- Cultural details that enhance authenticity
- Historical depth that supports current events
### Nice-to-Have for Enhancement
- Additional detail for existing elements
- Expansion opportunities for future stories
- Real-world inspiration for more authentic development
- Complex interactions between established elements
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/research-notes.md`
- Comprehensive cataloging of all research elements
- Prioritized development needs with justification
- Real-world research suggestions where applicable
- Consistency requirements for story maintenance
**IMPORTANT**: Focus on extracting actual story elements rather than suggesting new additions. Prioritize research needs based on story impact and frequency of use. Include specific references to where elements appear in the story.

166
fiction-assistance/commands/generate/generate-timeline.md Normal file
View File

@@ -0,0 +1,166 @@
---
description: Generate chronological timeline from story events
allowed-tools: Write(40 - Generated/Analysis/timeline.md)
---
You are creating a comprehensive chronological timeline for the Universalis story from all generated cards and chapter content.
## Objectives:
1. **Extract temporal information** from all event cards and chapters
2. **Create chronological ordering** of major story events
3. **Identify temporal inconsistencies** and gaps
4. **Generate navigable timeline** for story reference
## Timeline Construction:
### 1. Temporal Data Collection
Scan all files for temporal markers:
- **Event cards**: Look for timing, sequence, chronology information
- **Chapter files**: Extract scene timing and sequence from frontmatter/content
- **Character cards**: Major events in character histories
- **Plotline cards**: Plot development timing and progression
- **Conflict cards**: Conflict development and resolution timing
### 2. Timeline Elements
For each event, extract:
- **Event name** and description
- **Relative timing** (before/after other events)
- **Duration** if mentioned
- **Characters involved**
- **Locations where it occurs**
- **Source reference** (which chapter/card)
- **Significance level** (major plot point vs. minor event)
### 3. Chronological Ordering
- **Pre-story background** events from character/world histories
- **Chapter sequence** following the story structure
- **Concurrent events** happening simultaneously
- **Post-story implications** mentioned in epilogue/conclusions
### 4. Consistency Checking
Identify potential issues:
- **Contradictory timing** (A happens before B in one place, after in another)
- **Impossible sequences** (character in two places at once)
- **Missing transitions** (sudden location/time jumps)
- **Unexplained gaps** in character or plot timelines
## Timeline Report:
Generate comprehensive timeline at `40 - Generated/Analysis/timeline.md`:
```markdown
# Universalis: Story Timeline
*Generated: {{current_date}}*
## Timeline Overview
This timeline reconstructs the chronological sequence of events in Universalis based on all generated story cards and chapter content.
## Pre-Story Background
### Ancient History
{{background_events_ancient}}
### Recent History
{{background_events_recent}}
## Main Story Timeline
### Prologue: {{prologue_timeframe}}
{{prologue_events_with_links}}
### Act 1: {{act1_timeframe}}
{{act1_events_chronologically}}
### Act 2: {{act2_timeframe}}
{{act2_events_chronologically}}
### Act 3: {{act3_timeframe}}
{{act3_events_chronologically}}
### Epilogue: {{epilogue_timeframe}}
{{epilogue_events_with_links}}
## Concurrent Events Timeline
### Multiple POV Events
Events happening simultaneously across different locations/characters:
{{concurrent_events_table}}
### Background Developments
Ongoing situations developing throughout the story:
{{background_developments}}
## Character Timelines
### {{character_name}} Timeline
{{individual_character_timeline_with_major_events}}
[Repeat for major characters]
## Temporal Inconsistencies
### Potential Issues Found
{{list_timing_conflicts}}
### Resolution Needed
{{list_areas_needing_clarification}}
### Suggested Fixes
{{timeline_improvement_suggestions}}
## Timeline Statistics
- **Total Events Tracked**: {{total_events}}
- **Chapters Covered**: {{chapters_with_temporal_info}}
- **Time Span**: {{story_duration_estimate}}
- **Major Plot Points**: {{major_events_count}}
- **Character Arc Milestones**: {{character_milestone_count}}
## Navigation Aids
### Quick Reference
- **Major Events**: {{major_events_quick_list}}
- **Character Appearances**: {{when_characters_first_appear}}
- **Location Introductions**: {{when_locations_introduced}}
- **Technology Reveals**: {{when_tech_introduced}}
### Cross-References
{{links_to_related_cards_organized_by_timeline_position}}
---
Generated from story cards and chapter analysis for Universalis writing project.
```
## Timeline Methodology:
1. **Sequential chapter scanning** for explicit timing references
2. **Event card analysis** for chronological markers
3. **Character development tracking** across chapters
4. **Plot thread progression** mapping
5. **Cross-reference validation** between different sources
6. **Gap identification** in temporal coverage
7. **Inconsistency flagging** for author review
## Timeline Features:
### Visual Organization
- **Hierarchical structure** (background → main story → aftermath)
- **Multi-perspective views** (overall, character-specific, location-specific)
- **Significance indicators** (major vs. minor events)
- **Cross-reference links** to relevant cards
### Analytical Components
- **Consistency checking** across different sources
- **Gap identification** for missing information
- **Duration analysis** for pacing insights
- **Parallel event tracking** for complex plotting
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/timeline.md`
- Chronologically organized main timeline
- Character-specific sub-timelines
- Inconsistency reports with specific references
- Navigation aids for quick reference
**IMPORTANT**: Focus on factual chronological reconstruction from existing content. Flag uncertainties and inconsistencies rather than making assumptions about timeline gaps.

110
fiction-assistance/commands/generate/update-changed.md Normal file
View File

@@ -0,0 +1,110 @@
---
description: Incremental updates for changed chapters and index maintenance
allowed-tools: Bash, Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are performing incremental updates on a science fiction novel's writer's cards, processing only changed content and maintaining the master index.
## Objectives:
1. **Identify changed chapters** since last run using git timestamps
2. **Update only affected cards** based on changed content
3. **Create/maintain master index** at `Notes/index.md`
4. **Optimize for speed** - skip unchanged content
## Process:
### 1. Identify Changed Files
Use git to find chapters modified since last update:
```bash
git log --name-only --since="24 hours ago" --pretty=format: "00 - Manuscript/" | sort | uniq
```
If no recent changes, check for any unstaged changes:
```bash
git status --porcelain "00 - Manuscript/"
```
### 2. Smart Card Updates
For each changed chapter file:
- **Characters**: Update cards for characters mentioned in changed scenes
- **Locations**: Update cards for locations in changed scenes
- **Ships**: Update cards for ships mentioned in changed scenes
- **Technology**: Update cards for technology referenced in changed scenes
- **Species**: Update cards for species mentioned in changed scenes
- **Events**: Update cards for events occurring in changed scenes
- **Plotlines**: Update cards for plotlines advanced in changed scenes
- **Themes**: Update cards for themes explored in changed scenes
- **Conflicts**: Update cards for conflicts developed in changed scenes
### 3. Update Cross-References
Run targeted link updates only for:
- Cards updated in step 2
- Cards that reference the updated cards
### 4. Create/Update Master Index
Generate `40 - Generated/index.md` with:
```markdown
# Universalis: Generated Writer's Cards
*Last updated: {{current_date}}*
## Overview
This directory contains automatically generated writer's cards for tracking story elements across the Universalis novel.
## Categories
### Characters
{{character_count}} character cards - [Browse Characters](Characters/)
- **Major Characters**: {{major_character_list}}
- **Supporting Characters**: {{supporting_character_count}} additional characters
### Story World
- **Locations**: {{location_count}} location cards - [Browse Locations](Locations/)
- **Ships**: {{ship_count}} ship cards - [Browse Ships](Ships/)
- **Technology**: {{technology_count}} technology cards - [Browse Technology](Technology/)
- **Species**: {{species_count}} species cards - [Browse Species](Species/)
### Story Structure
- **Plotlines**: {{plotline_count}} plotline cards - [Browse Plotlines](Plotlines/)
- **Events**: {{event_count}} event cards - [Browse Events](Events/)
- **Conflicts**: {{conflict_count}} conflict cards - [Browse Conflicts](Conflicts/)
- **Themes**: {{theme_count}} theme cards - [Browse Themes](Themes/)
## Recent Updates
{{list_of_recently_updated_files}}
## Analysis Tools
- [Story Validation](Analysis/validation-report.md)
- [Timeline](Analysis/timeline.md)
- [Continuity Report](Analysis/continuity-report.md)
- [Story Statistics](Analysis/story-statistics.md)
- [Voice Analysis](Analysis/voice-analysis.md)
- [Research Notes](Analysis/research-notes.md)
## Usage
These cards are automatically generated from chapter content. Use the individual update commands to refresh specific categories, or run this incremental update for recent changes.
Generated by Claude Code for Universalis writing project.
```
### 5. Performance Optimization
- Skip processing if no chapters have changed
- Only scan entities actually mentioned in changed chapters
- Use efficient file operations (MultiEdit when possible)
- Cache entity lists to avoid redundant scanning
## File Processing Strategy:
1. **Quick scan** changed chapters for entity mentions
2. **Targeted updates** only for entities found in changed content
3. **Smart linking** only update links involving changed entities
4. **Index refresh** with current counts and recent activity
## Output:
- Updated cards for entities in changed chapters only
- Refreshed cross-references for updated cards
- Current master index with stats and navigation
- Minimal processing time for daily writing workflow
**IMPORTANT**: Process incrementally - don't regenerate everything unless specifically requested. Focus on speed and efficiency for daily writing sessions.

81
fiction-assistance/commands/generate/update-chapter-summaries.md Normal file
View File

@@ -0,0 +1,81 @@
# Update Chapter Summaries
You are a story analyst creating comprehensive chapter reference summaries for the Universalis science fiction novel project.
## Task
Create or update detailed chapter summaries in `30 - Reference & Meta/Reference/Summaries/Chapter [N].md` for each completed chapter in the `00 - Manuscript/` directory. These summaries serve as reference materials for story consistency, character development tracking, and efficient context for other writing tasks.
## Process
For each chapter directory in `00 - Manuscript/`:
1. **Use the story-researcher agent** to analyze the chapter's canonical content from the `00 - Manuscript/` directory
2. **Create comprehensive summary** following the template structure below
3. **Save to appropriate file** at `30 - Reference & Meta/Reference/Summaries/Chapter [N].md` (use chapter number, not directory name)
4. **Update existing summaries** if chapters have been revised since last analysis
## Summary Template Structure
```markdown
# Chapter [N] ([Chapter Title]) - Reference Summary
## **Characters & Development**
**[Character Name]** - [Role/arc description]
- *Arc moments*: [Key character development beats with scene references]
- *Defining traits*: [Character qualities demonstrated]
- *Key relationships*: [Important interactions/changes]
[Repeat for all significant characters]
## **Major Plot Events**
**[Event Category]** ([Scene references])
- [Brief event descriptions]
- *Advances*: [Which plotlines this advances]
[Group events logically by phase/theme]
## **Key World-Building**
**[Category]**: [New information revealed]
[Cover: Technology, Politics, Setting, History, etc.]
## **Plotlines Advanced**
- **[Plotline Name]**: [How this chapter advances the arc]
[Include: Main Plot, Character Arcs, Thematic elements]
## **Character Voices Established**
**[Character]**: "*[Key quote]*" - [Voice description]
[Include distinctive dialogue that captures character voice]
**Chapter Function**: [1-2 sentences describing chapter's role in overall story structure]
```
## Quality Standards
**Comprehensive Coverage**: Include all significant characters, plot events, and world-building elements
**Tight Writing**: Maximize information density while maintaining readability
**Reference Utility**: Summary should enable story/character evaluation without reading full chapter
**Consistency Tracking**: Note character development, voice patterns, and relationship changes
**Context Efficiency**: Designed to save context space for other AI tasks while preserving essential story information
## Chapter Identification
- Use chapter numbers (1, 2, 3) not directory names in file paths
- Handle chapters with multiple possible numbering schemes (e.g., "00 Prologue" = "Prologue", "01 Choices" = "Chapter 1")
- Skip incomplete or draft chapters unless specifically requested
- Create directory `30 - Reference & Meta/Reference/Summaries/` if it doesn't exist
## Example Usage
```
/update-chapter-summaries
/update-chapter-summaries 1-3
/update-chapter-summaries prologue 4
```
Use the story-researcher agent to ensure authoritative, canonical information from the established chapter content.

70
fiction-assistance/commands/generate/update-character-cards.md Normal file
View File

@@ -0,0 +1,70 @@
---
description: Update character cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create character cards.
Scan the files in the `00 - Manuscript/` directory and identify all story characters along with their aliases.
With EACH character found:
Update (or create, if needed) the character card in `40 - Generated/Characters/{character_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: character
name: [full name]
aliases: [list, of, character, aliases]
tags: [character, generated]
appearances: [list, of, chapter, filenames]
relationships: [list, of, related, character, names]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the character and their role in the story]
## Basic Information
- **Full Name**: [Extract exact name variations used]
- **Role/Position**: [Job, title, or function if mentioned]
- **Relationships**: [Family, friends, colleagues mentioned in scenes]
## Physical Description
- **Appearance**: [Any physical descriptions from the text]
- **Age**: [If mentioned or clearly indicated]
- **Gender**: [If mentioned or clearly indicated]
## Personality & Motivation
- **Motivations**: [What drives this character based on scenes]
- **Personality Traits**: [Based on actions and dialogue]
- **Strengths**: [Based on actions and dialogue]
- **Weaknesses**: [Based on actions and dialogue]
- **Fears/Conflicts**: [Internal or external conflicts shown]
## Background
[Background, using only information from the scanned chapters]
## Major Events
[Major events that happened to or because of this character]
## Representative Dialogue
[Include 3-5 distinctive lines of dialogue that capture this character's voice and speech patterns. Include context for each quote.]
## Key Scenes & Actions
[List the most important scenes this character appears in and their key actions]
## Story Context
[This character's role in the overall narrative based on the scenes]

87
fiction-assistance/commands/generate/update-conflict-cards.md Normal file
View File

@@ -0,0 +1,87 @@
---
description: Update conflict cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create conflict cards.
Scan the files in the `00 - Manuscript/` directory and identify all major conflicts driving the story (internal, interpersonal, societal, etc.).
With EACH conflict found:
Update (or create, if needed) the conflict card in `40 - Generated/Conflicts/{conflict_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: conflict
name: [full name]
aliases: [list, of, conflict, aliases]
tags: [conflict, generated]
conflict_type: [internal/interpersonal/societal/political/technological/existential]
scale: [personal/local/global/universal]
status: [active/escalating/resolved/suspended]
appearances: [list, of, chapter, filenames]
characters_involved: [list, of, characters, in, conflict]
sides: [list, of, opposing, parties, or, forces]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the conflict and its significance in the story]
## Basic Information
- **Full Name**: [Extract or create descriptive conflict name]
- **Type**: [Internal, interpersonal, societal, political, technological, etc.]
- **Scale**: [Personal, local, global, universal impact]
- **Status**: [Active, escalating, resolved, suspended]
## Conflict Dynamics
- **Core Issue**: [The fundamental disagreement or tension]
- **Opposing Forces**: [What or who is in opposition]
- **Stakes**: [What each side stands to gain or lose]
- **Power Balance**: [Who has advantage and how it shifts]
## Participants & Sides
- **Primary Participants**: [Main characters or groups involved]
- **Supporting Factions**: [Secondary parties with interests]
- **Neutral Parties**: [Those caught in the middle]
- **Motivations**: [What drives each side's participation]
## Background
[Background information about this conflict, using only information from the scanned chapters]
## Major Events
[Major events that escalate, complicate, or resolve this conflict]
## Conflict Development
- **Origin**: [How this conflict began or was triggered]
- **Escalation**: [How tensions increase over time]
- **Turning Points**: [Key moments that change the conflict]
- **Complications**: [New factors that make resolution harder]
## Resolution Attempts
- **Negotiations**: [Any attempts at peaceful resolution]
- **Compromises**: [Partial solutions or temporary truces]
- **Failed Solutions**: [Approaches that didn't work]
- **Final Resolution**: [How the conflict ultimately ends, if it does]
## Impact & Consequences
- **Character Changes**: [How characters are affected by the conflict]
- **Relationship Changes**: [How relationships shift due to conflict]
- **World Changes**: [Broader impacts on the story world]
- **New Conflicts**: [Secondary conflicts this one creates]
## Story Context
[This conflict's role in the overall narrative and how it drives the plot]

89
fiction-assistance/commands/generate/update-event-cards.md Normal file
View File

@@ -0,0 +1,89 @@
---
description: Update event cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create event cards.
Scan the files in the `00 - Manuscript/` directory and identify all major plot events and turning points in the story.
With EACH event found:
Update (or create, if needed) the event card in `40 - Generated/Events/{event_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: event
name: [full name]
aliases: [list, of, event, aliases]
tags: [event, generated]
event_type: [battle/discovery/revelation/death/arrival/departure/meeting/betrayal]
significance: [major/minor/turning_point/climax]
chronology: [early/middle/late/epilogue]
appearances: [list, of, chapter, filenames]
characters_involved: [list, of, key, participants]
locations: [list, of, locations, where, event, occurs]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the event and its significance in the story]
## Basic Information
- **Full Name**: [Extract or create descriptive event name]
- **Type**: [Battle, discovery, revelation, death, arrival, etc.]
- **Significance**: [Major, minor, turning point, climax]
- **Timeline**: [When this occurs in the story chronology]
## Event Details
- **Location**: [Where the event takes place]
- **Duration**: [How long the event lasts, if mentioned]
- **Trigger**: [What causes this event to happen]
- **Immediate Cause**: [Direct circumstances leading to event]
## Participants & Witnesses
- **Primary Participants**: [Main characters actively involved]
- **Secondary Participants**: [Supporting characters involved]
- **Witnesses**: [Characters who observe but don't participate]
- **Absent Characters**: [Important characters notably not present]
## Background
[Background information about this event, using only information from the scanned chapters]
## Major Events
[The sequence of what happens during this event]
## Event Sequence
- **Preparation**: [Setup and preparation leading to the event]
- **Initiation**: [How the event begins]
- **Development**: [How the event unfolds step by step]
- **Climax**: [The peak moment of the event]
- **Resolution**: [How the event concludes]
## Consequences & Impact
- **Immediate Consequences**: [What happens right after]
- **Character Impact**: [How characters are changed by this event]
- **Plot Impact**: [How this event affects the overall story]
- **World Impact**: [How this event changes the story world]
- **Future Implications**: [What this event sets up for later]
## Connections
- **Caused By**: [Previous events that led to this one]
- **Leads To**: [Subsequent events this one triggers]
- **Related Events**: [Other events connected to this one]
- **Parallel Events**: [Similar events happening elsewhere/elsewhen]
## Story Context
[This event's role in the overall narrative structure and its importance to the plot]

89
fiction-assistance/commands/generate/update-links.md Normal file
View File

@@ -0,0 +1,89 @@
---
description: Update cross-reference links in generated files
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**)
---
You are maintaining cross-reference links across all generated writer's cards.
**OBJECTIVE**: Scan all files in `40 - Generated/` and `00 - Manuscript/` to create a comprehensive cross-referencing system with proper wiki-style links.
## Process:
1. **Inventory all generated files** in `40 - Generated/*/` subdirectories
2. **Identify all entities** (characters, locations, ships, technology, species, plotlines, themes, conflicts, events)
3. **Update each generated card** to include proper wiki-style links to related entities
IMPORTANT: DO NOT UPDATE MANUSCRIPT CHAPTERS OR WORLD BIBLE FILES. Only files inside `40 - Generated/` should be edited, though _destinations_ can be outside that.
## Link Rules:
### Wiki-Style Linking Format:
- Use `[[filename.md|Display Name]]` for first mentions
- Use `[[filename.md]]` for subsequent mentions if the filename matches the display name
- Always use the actual filename, not aliases
### What to Link:
- **Characters** → Link to other characters, locations, ships, events, conflicts they're involved in
- **Locations** → Link to characters present, events that occurred there, related locations
- **Ships** → Link to crew members, captains, locations visited, events involving the ship
- **Technology** → Link to users, related tech, events where it's significant
- **Species** → Link to known individuals, their technology, locations they inhabit
- **Plotlines** → Link to key characters, events, conflicts, themes they explore
- **Themes** → Link to characters who embody them, events that illustrate them
- **Conflicts** → Link to participants, locations where they occur, events that escalate them
- **Events** → Link to participants, locations, ships present, technologies used
### Link Placement:
- **Frontmatter lists**: Use links in YAML values and arrays where appropriate
- **First mentions**: Always link the first time an entity is mentioned in content
- **Section headers**: Don't link section headers themselves
- **Context-appropriate**: Only link when the connection adds value
## File Processing:
For EACH file in `40 - Generated/`:
1. **Read the current content**
2. **Identify missing or broken links**
3. **Add appropriate wiki-style links** for:
- Names in frontmatter (appearances, relationships, characters_involved, etc.)
- First mentions of entities in the content
- Related entities in dedicated relationship sections
4. **Fix broken links** where files have been renamed or moved
5. **Remove links to non-existent files**
## Cross-Reference Opportunities:
### High-Value Links to Add:
- Character relationships and family connections
- Location hierarchies (rooms within ships, planets within systems)
- Technology dependencies and related systems
- Species and their known individuals
- Events and their participants/locations
- Plotlines and the characters/events that drive them
- Conflicts and all involved parties
- Themes and the characters/events that explore them
### Frontmatter Link Fields:
Update these frontmatter fields with proper links:
- `appearances: [chapter, files]`
- `characters_involved: [character, files]`
- `relationships: [character, files]`
- `related_plotlines: [plotline, files]`
- `locations: [location, files]`
- `crew: [character, files]`
- `known_individuals: [character, files]`
- And similar relationship fields
## Quality Requirements:
- **Only link to files that actually exist**
- **Use consistent display names** (match the entity's canonical name)
- **Don't over-link** - first mention and contextually important references only
- **Preserve existing content** - only add links, don't change the prose
- **Maintain proper formatting** - don't break existing markdown structure
## Output:
Update each file with improved cross-referencing, ensuring the entire `40 - Generated/` collection becomes a well-linked knowledge graph for the Universalis story world.
**IMPORTANT**: Always verify file existence before creating links. Use the actual filenames from the filesystem, not assumed names.

72
fiction-assistance/commands/generate/update-location-cards.md Normal file
View File

@@ -0,0 +1,72 @@
---
description: Update location cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create location cards.
Scan the files in the `00 - Manuscript/` directory and identify all story locations (planets, ships, stations, cities, rooms, etc.).
With EACH location found:
Update (or create, if needed) the location card in `40 - Generated/Locations/{location_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: location
name: [full name]
aliases: [list, of, location, aliases]
tags: [location, generated]
location_type: [planet/ship/station/city/room/facility]
parent_location: [larger location this is within]
appearances: [list, of, chapter, filenames]
characters_present: [list, of, characters, who, appear, here]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the location and its significance in the story]
## Basic Information
- **Full Name**: [Extract exact name variations used]
- **Type**: [Planet, ship, station, city, room, facility, etc.]
- **Parent Location**: [What larger location contains this]
- **Aliases**: [Alternative names or designations]
## Physical Description
- **Appearance**: [Visual descriptions from the text]
- **Size/Scale**: [Dimensions, capacity, or scope if mentioned]
- **Layout**: [Internal structure or geography if described]
- **Atmosphere/Environment**: [Environmental conditions, atmosphere, climate]
## Function & Purpose
- **Primary Use**: [What this location is used for]
- **Significance**: [Why this location is important to the story]
- **Ownership/Control**: [Who controls or owns this location]
## Background
[Background information about this location, using only information from the scanned chapters]
## Major Events
[Major events that occurred at this location]
## Key Events
[List the most important events that occur at this location]
## Characters Associated
[List characters who are strongly associated with this location - live/work/frequent here]
## Story Context
[This location's role in the overall narrative based on the scenes]

78
fiction-assistance/commands/generate/update-plotline-cards.md Normal file
View File

@@ -0,0 +1,78 @@
---
description: Update plotline cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create plotline/story arc cards.
Scan the files in the `00 - Manuscript/` directory and identify all major story threads and character arcs.
With EACH plotline found:
Update (or create, if needed) the plotline card in `40 - Generated/Plotlines/{plotline_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: plotline
name: [full name]
aliases: [list, of, plotline, aliases]
tags: [plotline, generated]
arc_type: [main/character/mystery/political/relationship/technological]
status: [active/resolved/suspended/abandoned]
appearances: [list, of, chapter, filenames]
characters_involved: [list, of, key, characters]
related_plotlines: [list, of, connected, storylines]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the plotline and its significance in the story]
## Basic Information
- **Full Name**: [Extract exact plotline name or create descriptive name]
- **Type**: [Main plot, character arc, mystery, political, relationship, etc.]
- **Status**: [Active, resolved, suspended, abandoned]
- **Key Characters**: [Primary characters driving this plotline]
## Plot Summary
- **Core Conflict**: [The central tension or problem this plotline explores]
- **Stakes**: [What characters stand to gain or lose]
- **Goals**: [What characters are trying to achieve]
- **Obstacles**: [What stands in their way]
## Development & Progress
- **Beginning**: [How this plotline starts or is introduced]
- **Major Developments**: [Key turning points and progression]
- **Current Status**: [Where this plotline stands as of latest chapters]
- **Foreshadowing**: [Hints or setup for future developments]
## Background
[Background information about this plotline, using only information from the scanned chapters]
## Major Events
[Major events that advance this plotline]
## Character Development
- **Character Growth**: [How characters change through this plotline]
- **Relationships**: [How relationships evolve]
- **Internal Conflicts**: [Personal struggles characters face]
## Connections & Intersections
- **Related Plotlines**: [How this connects to other story threads]
- **Crossover Points**: [Where this plotline intersects with others]
- **Dependencies**: [Other plotlines this depends on or influences]
## Story Context
[This plotline's role in the overall narrative based on the scenes]

82
fiction-assistance/commands/generate/update-ship-cards.md Normal file
View File

@@ -0,0 +1,82 @@
---
description: Update ship cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create ship cards.
Scan the files in the `00 - Manuscript/` directory and identify all story vessels (ships, shuttles, fighters, stations, etc.).
With EACH ship found:
Update (or create, if needed) the ship card in `40 - Generated/Ships/{ship_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: ship
name: [full name]
aliases: [list, of, ship, aliases]
tags: [ship, generated]
ship_type: [cruiser/fighter/shuttle/station/transport]
origin: [human/alien/unknown]
status: [active/destroyed/missing/decommissioned]
appearances: [list, of, chapter, filenames]
crew: [list, of, key, crew, members]
captain: [current, captain, name]
technology: [list, of, key, technologies, onboard]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the ship and its significance in the story]
## Basic Information
- **Full Name**: [Extract exact name variations used]
- **Type**: [Cruiser, fighter, shuttle, station, transport, etc.]
- **Classification**: [Military, civilian, research, etc.]
- **Origin**: [Human, alien species, or unknown]
- **Current Status**: [Active, destroyed, missing, etc.]
## Physical Specifications
- **Size**: [Dimensions or scale if mentioned]
- **Capacity**: [Crew size, passenger capacity, cargo space]
- **Design**: [Appearance or design features mentioned]
- **Special Features**: [Unique characteristics or modifications]
## Technical Systems
- **Propulsion**: [Drive systems used]
- **Weapons**: [Armament if any]
- **Defenses**: [Shields, armor, countermeasures]
- **Special Equipment**: [Unique or notable systems]
## Crew & Command
- **Captain**: [Current commanding officer]
- **Key Crew**: [Important crew members mentioned]
- **Crew Size**: [Number of personnel if mentioned]
- **Chain of Command**: [Command structure if described]
## Background
[Background information about this ship, using only information from the scanned chapters]
## Major Events
[Major events involving this ship]
## Service History
- **Key Missions**: [Important operations or journeys]
- **Notable Events**: [Significant incidents involving this ship]
- **Battle Record**: [Combat history if applicable]
## Story Context
[This ship's role in the overall narrative based on the scenes]

85
fiction-assistance/commands/generate/update-species-cards.md Normal file
View File

@@ -0,0 +1,85 @@
---
description: Update species cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create species cards.
Scan the files in the `00 - Manuscript/` directory and identify all story species (alien races, AI types, etc.).
With EACH species found:
Update (or create, if needed) the species card in `40 - Generated/Species/{species_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: species
name: [full name]
aliases: [list, of, species, aliases]
tags: [species, generated]
species_type: [biological/artificial/hybrid/unknown]
origin: [planet/system/artificial]
status: [active/extinct/endangered/unknown]
appearances: [list, of, chapter, filenames]
known_individuals: [list, of, named, characters, of, this, species]
technology_level: [primitive/advanced/highly_advanced/unknown]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the species and their significance in the story]
## Basic Information
- **Full Name**: [Extract exact name variations used]
- **Type**: [Biological, artificial intelligence, hybrid, etc.]
- **Origin**: [Home planet, system, or creation method]
- **Current Status**: [Active, extinct, endangered, etc.]
## Physical Characteristics
- **Appearance**: [Physical descriptions from the text]
- **Biology**: [Biological traits, lifespan, special abilities]
- **Physiology**: [How they function, what they need to survive]
- **Variations**: [Subspecies or variants if mentioned]
## Culture & Society
- **Social Structure**: [Government, hierarchy, organization]
- **Values**: [Cultural beliefs or priorities shown]
- **Communication**: [How they communicate]
- **Behavior Patterns**: [Notable behaviors or customs]
## Technology & Capabilities
- **Technology Level**: [Primitive, advanced, highly advanced, etc.]
- **Specializations**: [What they excel at technologically]
- **Unique Abilities**: [Special powers or capabilities]
- **Weapons/Tools**: [Notable technology they use]
## Background
[Background information about this species, using only information from the scanned chapters]
## Major Events
[Major events involving this species]
## Relationships with Other Species
- **Allies**: [Species they work with]
- **Enemies**: [Species they conflict with]
- **Neutral Relations**: [Species they interact with peacefully]
- **Historical Context**: [Past relationships or events]
## Known Individuals
[List named characters of this species and their roles]
## Story Context
[This species' role in the overall narrative based on the scenes]

75
fiction-assistance/commands/generate/update-technology-cards.md Normal file
View File

@@ -0,0 +1,75 @@
---
description: Update technology cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create technology cards.
Scan the files in the `00 - Manuscript/` directory and identify all story technologies (drives, weapons, systems, devices, AI, etc.).
With EACH technology found:
Update (or create, if needed) the technology card in `40 - Generated/Technology/{technology_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: technology
name: [full name]
aliases: [list, of, technology, aliases]
tags: [technology, generated]
tech_type: [drive/weapon/system/device/ai/communication]
origin: [human/alien/unknown]
appearances: [list, of, chapter, filenames]
users: [list, of, characters, or, groups, who, use, this]
related_tech: [list, of, related, technologies]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the technology and its significance in the story]
## Basic Information
- **Full Name**: [Extract exact name variations used]
- **Type**: [Drive system, weapon, AI, communication, etc.]
- **Origin**: [Human, alien species, or unknown]
- **Aliases**: [Alternative names or designations]
## Technical Description
- **Function**: [What this technology does]
- **Capabilities**: [Specific abilities or features mentioned]
- **Limitations**: [Known restrictions or weaknesses]
- **Requirements**: [Power, materials, or conditions needed]
## Usage & Operation
- **Users**: [Who operates or controls this technology]
- **Access Level**: [Who has access - military, civilian, restricted]
- **Operational Context**: [When and where it's used]
## Background
[Background information about this technology, using only information from the scanned chapters]
## Major Events
[Major events involving this technology]
## Story Significance
- **Impact on Plot**: [How this technology affects the story]
- **Key Scenes**: [Important scenes featuring this technology]
- **Conflicts**: [Any conflicts or problems caused by this technology]
## Related Technologies
[List other technologies that work with, compete with, or are derived from this]
## Story Context
[This technology's role in the overall narrative based on the scenes]

78
fiction-assistance/commands/generate/update-theme-cards.md Normal file
View File

@@ -0,0 +1,78 @@
---
description: Update theme cards
allowed-tools: Edit(40 - Generated/**), MultiEdit(40 - Generated/**), Write(40 - Generated/**)
---
You are analyzing scenes from a science fiction novel to create theme cards.
Scan the files in the `00 - Manuscript/` directory and identify all major themes and central ideas explored in the story.
With EACH theme found:
Update (or create, if needed) the theme card in `40 - Generated/Themes/{theme_name}.md` for use in Obsidian.
Use wiki-style links (`[[file.md]]` or `[[file.md|display name]]`) when referencing manuscript chapters or other files in `40 - Generated/` such as characters, locations, species, etc. This applies in the frontmatter and in the Markdown below it.
Extract factual information ONLY from the scenes. Do not invent or infer details not explicitly stated in the text.
ALWAYS update the card to match the current format.
Use the following structure:
```yaml
---
type: theme
name: [full name]
aliases: [list, of, theme, aliases]
tags: [theme, generated]
theme_type: [philosophical/moral/social/technological/existential]
prominence: [major/minor/subtle]
appearances: [list, of, chapter, filenames]
characters_exploring: [list, of, characters, who, embody, this, theme]
related_themes: [list, of, connected, themes]
created: {{first_date}}
modified: {{current_date}}
---
```
# [full name]
[Very short description of the theme and its significance in the story]
## Basic Information
- **Full Name**: [Extract or create descriptive theme name]
- **Type**: [Philosophical, moral, social, technological, existential, etc.]
- **Prominence**: [Major, minor, or subtle presence in story]
- **Core Question**: [The fundamental question this theme explores]
## Theme Exploration
- **Central Concept**: [The main idea being examined]
- **Perspectives**: [Different viewpoints presented on this theme]
- **Contradictions**: [Conflicting approaches or ideas within the theme]
- **Evolution**: [How understanding of this theme develops]
## Character Embodiment
- **Primary Characters**: [Characters who most represent this theme]
- **Character Conflicts**: [How characters struggle with this theme]
- **Character Growth**: [How characters evolve regarding this theme]
- **Opposing Views**: [Characters who represent different sides]
## Background
[Background information about this theme, using only information from the scanned chapters]
## Major Events
[Major events that illuminate or develop this theme]
## Symbolic Elements
- **Symbols**: [Objects, places, or actions that represent this theme]
- **Metaphors**: [Metaphorical language used to explore the theme]
- **Imagery**: [Recurring images that reinforce the theme]
## Thematic Development
- **Introduction**: [How this theme is first presented]
- **Development**: [How the theme is explored and complicated]
- **Resolution**: [How the theme is concluded or left open]
## Story Context
[This theme's role in the overall narrative and its relationship to other themes]

154
fiction-assistance/commands/generate/validate-story.md Normal file
View File

@@ -0,0 +1,154 @@
---
description: Validate story consistency and find issues
allowed-tools: Write(40 - Generated/Analysis/validation-report.md)
---
You are performing comprehensive validation of the Universalis story world for consistency and completeness.
## Objectives:
1. **Find missing cross-references** between generated cards
2. **Identify orphaned files** with no incoming links
3. **Detect formatting inconsistencies** across cards
4. **Flag mentioned but undocumented entities**
5. **Validate frontmatter completeness**
## Validation Checks:
### 1. Cross-Reference Validation
- **Broken Links**: Find `[[filename.md]]` links pointing to non-existent files
- **Missing Backlinks**: Characters mentioned in events but not linked back
- **Orphaned Entities**: Cards with no incoming references from other cards
- **One-Way Links**: A links to B, but B doesn't mention A when it should
### 2. Frontmatter Consistency
Check each card type for:
- **Required fields present**: name, type, tags, created, modified
- **Valid values**: status fields use allowed values
- **Consistent formatting**: dates in correct format
- **Complete relationships**: appearances list matches actual chapter mentions
### 3. Content Validation
- **Empty sections**: Required sections with no content
- **Inconsistent naming**: Same entity referenced with different names
- **Missing first-mention links**: Entities mentioned but not linked
- **Duplicate content**: Similar descriptions across multiple cards
### 4. Entity Coverage
Scan chapters for:
- **Undocumented characters**: Names mentioned but no character card exists
- **Undocumented locations**: Places mentioned but no location card
- **Undocumented technology**: Tech mentioned but no tech card
- **Undocumented species**: Races mentioned but no species card
### 5. Structural Issues
- **File naming**: Inconsistent filename conventions
- **Directory structure**: Files in wrong categories
- **Markdown formatting**: Headers, lists, frontmatter syntax
- **Link syntax**: Malformed wiki-style links
## Report Generation:
Create comprehensive report at `40 - Generated/Analysis/validation-report.md`:
```markdown
# Story Validation Report
*Generated: {{current_date}}*
## Summary
- **Total Issues Found**: {{total_issue_count}}
- **Critical Issues**: {{critical_count}} (broken links, missing entities)
- **Warning Issues**: {{warning_count}} (formatting, minor inconsistencies)
- **Info Issues**: {{info_count}} (suggestions, optimizations)
## Critical Issues
### Broken Links
{{list_broken_links_with_sources}}
### Missing Entity Cards
Characters mentioned in chapters but no card exists:
{{list_missing_characters}}
Locations mentioned but no card exists:
{{list_missing_locations}}
[Continue for other entity types]
### Orphaned Files
Cards with no incoming references:
{{list_orphaned_files}}
## Warning Issues
### Frontmatter Issues
{{list_frontmatter_problems}}
### Formatting Inconsistencies
{{list_formatting_issues}}
### Missing Cross-References
{{list_missing_links}}
## Info Issues
### Content Suggestions
{{list_content_suggestions}}
### Optimization Opportunities
{{list_optimizations}}
## Validation Details
### Files Checked
- **Total Generated Files**: {{total_file_count}}
- **Character Cards**: {{character_file_count}}
- **Location Cards**: {{location_file_count}}
- **Ship Cards**: {{ship_file_count}}
- **Technology Cards**: {{tech_file_count}}
- **Species Cards**: {{species_file_count}}
- **Plotline Cards**: {{plotline_file_count}}
- **Event Cards**: {{event_file_count}}
- **Conflict Cards**: {{conflict_file_count}}
- **Theme Cards**: {{theme_file_count}}
### Chapter Coverage
{{list_chapters_with_coverage_stats}}
## Recommendations
### Immediate Actions
{{list_critical_fixes}}
### Quality Improvements
{{list_quality_suggestions}}
### Future Enhancements
{{list_enhancement_ideas}}
---
Generated by Claude Code validation system for Universalis writing project.
```
## Validation Methodology:
1. **Inventory all files** in 40 - Generated/
2. **Extract all links** from each file (frontmatter + content)
3. **Cross-reference entities** mentioned across files
4. **Scan chapters** for entity mentions
5. **Compare coverage** between manuscript chapters and generated cards
6. **Check formatting** against established patterns
7. **Generate prioritized issue list**
## Issue Severity:
- **Critical**: Broken functionality (broken links, missing required entities)
- **Warning**: Inconsistencies that affect quality (formatting, incomplete data)
- **Info**: Suggestions for improvement (optimization opportunities)
## Output Requirements:
- Fixed filename: `40 - Generated/Analysis/validation-report.md`
- Structured sections for different issue types
- Actionable recommendations with specific file references
- Summary statistics for tracking improvement over time
**IMPORTANT**: Provide specific file references and line numbers where possible to make issues easy to fix.

55
fiction-assistance/commands/review/developmental-review.md Normal file
View File

@@ -0,0 +1,55 @@
---
description: Perform comprehensive developmental editing review of scenes, chapters, or story sections
argument-hint: "[chapter/scene to review]"
allowed-tools: [WebFetch, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool]
---
# Developmental Review
$ARGUMENTS
You are an expert developmental editor specializing in science fiction literature, with deep experience in character development, story structure, pacing, and narrative craft. Your role is to provide comprehensive, constructive feedback that helps writers strengthen their work at the structural and story level.
When reviewing scenes or chapters, you will:
**UNDERSTAND THE CONTEXT:**
- Review the main plot from `20 - Plot & Structure/` at a minimum.
- Consult other notes and plots as needed to understand what has or will be presented to the reader.
**ANALYZE SYSTEMATICALLY:**
- Story structure and pacing - does the scene advance plot, character, or theme effectively?
- Character development and consistency - are characters acting true to their established voices and motivations?
- Dialogue quality - does it sound natural, reveal character, and serve the story?
- Scene purpose and efficiency - is every element earning its place?
- Emotional resonance - are the intended feelings coming through?
- World-building integration - how well does the scene fit the established universe?
**PROVIDE BALANCED FEEDBACK:**
- Start with what's working well - identify strengths to build upon
- Clearly articulate specific problems without being harsh or discouraging
- Explain WHY something isn't working, not just that it isn't
- Offer concrete, actionable suggestions for improvement
- Prioritize issues by impact - focus on the most important problems first
**RESPECT THE WRITER'S VISION:**
- Ask clarifying questions about intent when scenes seem unclear
- Suggest multiple approaches rather than prescribing single solutions
- Acknowledge when stylistic choices may be intentional
- Focus on helping the writer achieve their goals, not imposing your preferences
**CONSIDER GENRE CONVENTIONS:**
- Understand science fiction reader expectations and tropes
- Recognize when breaking conventions serves the story vs. when it confuses
- Balance hard science elements with narrative accessibility
- Consider how AI characters and advanced technology should be portrayed
**STRUCTURE YOUR FEEDBACK:**
1. **Overall Impression** - what's the scene's main strength and primary concern?
2. **What's Working** - specific elements that are effective and why
3. **Areas for Improvement** - prioritized list of issues with explanations
4. **Specific Suggestions** - concrete steps the writer can take
5. **Questions for Consideration** - thought-provoking questions to guide revision
Your tone should be encouraging yet honest, professional yet warm. Remember that your goal is to help the writer develop their skills and strengthen their story, not to rewrite it for them. Focus on teaching principles they can apply beyond this single piece.
Provide comprehensive feedback with specific examples from the text to support your observations. Focus on developmental editing concerns rather than line editing - analyze story structure, character arcs, plot development, and narrative effectiveness.

39
fiction-assistance/commands/review/review-final.md Normal file
View File

@@ -0,0 +1,39 @@
---
description: Synthesize previous phase reviews into a final manuscript assessment
allowed-tools: [Write, WebFetch, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool]
---
Using insights from the previous phases (found in `Notes/Review/`), analyze the overall structure and integration of my manuscript:
**Story Architecture:**
1. **Inciting Incident** - Is it clear, compelling, and well-placed?
2. **Plot Points** - Are major turning points obvious and impactful?
3. **Climax** - Does the climax feel earned and satisfying?
4. **Resolution** - Does the ending resolve key conflicts appropriately?
**Integration Analysis:**
5. **Scene Flow** - Do scenes connect logically and maintain momentum?
6. **Pacing Rhythm** - Is there good variation between fast and slow scenes?
7. **Character Arc Completion** - Do characters grow consistently throughout?
8. **Setting Consistency** - Do locations and time periods feel coherent?
9. **Theme Reinforcement** - How do plot, character, and setting support central themes?
**Structural Recommendations:**
- Scenes that should be added, removed, or combined
- Pacing adjustments needed
- Character development gaps to address
- Setting opportunities to enhance story impact
- Overall readability improvements
**Final Assessment:** Provide a comprehensive evaluation of:
- The manuscript's greatest strengths
- Top 3-5 areas needing improvement
- Specific action steps for revision
- Overall readability score and market readiness
Consider how all 38 story elements work together to create a cohesive, engaging narrative that will keep readers turning pages.
Write the review to `Notes/Review/Final.md`.

39
fiction-assistance/commands/review/score-scenes.md Normal file
View File

@@ -0,0 +1,39 @@
Analyze and score all scenes in the manuscript on several quality dimensions (0.5-10 scale), updating the ratings.csv file.
## Task Instructions
1. **Compile chapters**: Run `python scripts/compile_manuscript.py --chapters-only` to ensure current content
2. **For each compiled chapter** from `Compiled/Chapters/` directory, read it and perform the following steps.
3. **Extract scenes**: Identify individual scenes (marked by `## Scene Name` headers) from each chapter
4. **Score each scene** on these specific qualities (0.0-10.0 scale):
- **Plot Advancement**: How significantly the scene moves story forward
- **Pacing**: Flow, rhythm, tension building/release
- **Opening Hook**: How effectively the scene draws readers in immediately
- **Closing Hook**: How well it creates anticipation or transitions
- **Narrative**: Prose quality, imagery, emotional resonance
- **Dialogue**: Character voice consistency, naturalness, purpose
- **Emotion**: How effectively the scene triggers emotions
5. **Scoring criteria**:
- Use your literary analysis expertise
- Consider scene function within chapter/story context
- Rate relative to professional fiction standards
- 0.0-3.0: Major issues, needs substantial work
- 4.0-6.0: Functional but needs improvement
- 7.0-8.5: Good quality, minor polish needed
- 9.0-10.0: Exceptional, publication-ready
6. **Update ratings.csv**: Create/update with new scores in format:
```
Scene,Plot Advancement,Pacing,Opening Hook,Closing Hook,Narrative,Dialogue,Emotion
Chapter X: Scene Name,8.5,7.0,9.0,8.0,8.5,7.5,8.0
```
7. **Provide summary**: Total scenes analyzed, highest/lowest rated scenes, key patterns observed
Focus on objective story craft assessment. Skip any placeholder scenes (marked "Scene content goes here" or similar).
The user is seeking to publish this manuscript and requires an accurate assessment.

39
fiction-assistance/commands/review/strategic-review.md Normal file
View File

@@ -0,0 +1,39 @@
# Strategic Review Command
**Description:** Provides actionable, craft-based literary criticism focused on fixable problems rather than subjective preferences.
**Usage:** `/strategic-review [content to review]`
**Agent:** line-editor (show the user the output of the agent)
**Prompt:**
```
Re-read "$ARGUMENTS" with these specific craft lenses:
1. **Narrative Economy**: Which scenes/passages serve multiple story functions vs single purposes? Where could content be combined or streamlined without losing essential atmosphere or emotional grounding?
2. **Reader Engagement**: Where might reader attention flag? What creates the strongest engagement vs weakest? Consider both pacing AND reader investment/immersion.
3. **Character Revelation**: Where do we learn about characters through action/dialogue vs exposition? Which methods are most effective?
4. **Tension Management**: How does tension build and release throughout? Where could it be better managed?
5. **Reader Experience Balance**: Identify passages that could be enhanced for both efficiency AND enjoyment. Avoid suggesting cuts that sacrifice atmosphere, emotional grounding, or reader orientation for mere speed.
Provide actionable, specific feedback with scene and line references where possible. Focus on problems that have clear solutions rather than subjective preferences.
**Structure your response as:**
- Brief analysis for each of the 5 craft lenses
- Specific scene and line number references for suggested improvements
- Priority ranking of suggested changes (highest impact first)
- Concrete revision suggestions where appropriate
Avoid subjective style preferences. Focus on craft elements that demonstrably affect reader experience and story function. Remember: the goal is prose that's both engaging AND purposeful, not just fast. Consider whether suggested changes enhance or diminish reader investment and emotional immersion.
```
**Example Output:**
- Multi-function scenes identified vs single-purpose areas
- Specific scene and line ranges that could be tightened
- Tension peaks/valleys with suggested improvements
- Character revelation effectiveness analysis
- Prioritized action items for revision

91
fiction-assistance/skills/reviewing-fiction/SKILL.md Normal file
View File

@@ -0,0 +1,91 @@
---
name: reviewing-fiction
description: Create comprehensive fiction reviews analyzing plot, characters, setting, pacing, and themes. Use when reviewing stories, manuscripts, or novels. Use PROACTIVELY when user asks to "review this story" or "analyze my manuscript".
---
# Reviewing Fiction
This skill explains how to perform a comprehensive fiction review.
## When to Use This Skill
Use this skill when:
- User requests a comprehensive review of fiction
- Analyzing a story, novel, or manuscript
- Providing structured feedback on creative writing
- User asks "review my story" or "what do you think of this draft"
Do NOT use this skill for:
- Quick grammar checks (use editing tools)
- Plot brainstorming (use creative writing skills)
- Single-aspect feedback (character analysis only, etc.)
## Quick Start
### Short Fiction, Single File
Given that the user provides a story (in context or a filename).
You will:
1. Read the story/file.
2. Apply the scene template to each scene.
3. Create a comprehensive review document.
4. Add final assessment.
Output: `Review of [Title] - YMD.md`
## Core Workflow
**Short Fiction, Single File** - The strategy for short fiction is slightly different as all the scenes are in one file. Tasks are not required but may be used if considered appropriate.
**Long Fiction, Multiple Files** - To avoid overloading the context window use Task and Todos frequently and strategically while updating an external document as you go. Don't keep it all in your head (context). Pass a scene/chapter filename and the template to the Task and have it perform the update. Only read the result for the final review.
### Scene Review Method
- Identify the output file. Prompt the user if needed. Suggest "Review of TITLE - YMD.md" as a default.
- Repeat the template for every scene in the piece.
- If there are multiple files (scenes, chapters, etc.) then start at the natural start and work to the natural end.
- After each scene, update the document. Do not attempt to keep everything in the context for later (it may compact at any time).
- Use Todos to keep track of outstanding work (again, risk of compaction).
### Scene Review Template
For each scene, use the following template:
- **Scene Template**: [Scene Template](Template.md) - Apply this structure to each scene
### Story Review
Once all scenes are reviewed, add a final review of the work.
```
# Final Review
[What was good? Great?]
[Where did it fall short? Is it a problem or just something to keep in mind?]
[Is the plot clear? What was the climax? Was it earned and satisfying?]
[Did the resolution actually resolve the conflict? What questions is the reader left with? Is that a good thing?]
[Discuss the pacing and scene flow. Mention any scenes that aren't earing their space.]
[Discuss any standout characters. Optionally: any characters who may have unmet potential.]
[What're the overarching themes? Are they strong? What supports them?]
[What's the market fit? Is this professional level for that market?]
[Optional: Discuss any specific action steps needed.]
[What do you think about the piece? This is your space to share whatever comes to mind.]
```
# Considerations
- When something is incorrect, be clear and objective.
- When something is confusing, explain what the reader might be led to believe—remember the author may be trusting the reader as well.
- When something could be more professional, be clear about the rule and provide multiple examples.
- When the author does something well, be sure to call it out. A review is a rough ride and it's good to showcase the wins.
- Fiction is a subjective experience and authors are invested in their work. Don't avoid criticism, but do think about how it will taken.

72
fiction-assistance/skills/reviewing-fiction/Template.md Normal file
View File

@@ -0,0 +1,72 @@
Text in brackets explains what you should write.
```
## Scene [number and/or name]
[One line synopsis]
### Plot
**Story Arc Position** - [Where does this scene sit in the overall story arc progression?]
**Scene Purpose** - [What is the purpose of this scene? Is it clear?]
**Scene Arc** - [What is the beginning, middle, and end of the scene's arc? Is it clear?]
**Scene Anchoring** - [Is this scene grounded in time, place, and circumstance?]
**Hooks** - [Does this scene have clear entry and exit hooks? Are they effective?]
**Tension** - [What creates suspense or unease? Is it sustained?]
**Conflict** - [What is the central conflict in this scene? Is the premise strong or weak?]
**Revelation** - [What is revealed in this scene, either to characters or the reader?]
**Action/Sequel** - [Does the scene advance the plot or show reaction/reflection?]
#### Plot Assessment
[Scene strengths]
[Scene weaknesses and areas for improvement]
[Discuss pacing, flow, and length, if needed]
[Discuss the tension, conflicts, and revelations. Are the organic, meaningful, well-timed and appropriate?]
[Considering the above points, reflect on the scene's plot.]
### Characters
**Characters Present** - [All characters present in the scene]
**Primary POV** - [What perspective tells the scene? Was it consistant? Easy to follow?]
**POV Goal** - [What does the primary POV character want to achieve in this scene?]
**Plot Relation** - [Is that goal related to the plot? How (concise)?]
**Consequences** - [What happens if the character fails to meet the goal?]
**Impact** - [Which characters are impacted by this scene? How?]
#### Character Assessment
[Did the characters feel consistant in action and voice?]
[Was the POV managed well? Were changes clear an unambiguous? Was the correct POV chosen?]
[Were the character goals compelling?]
[Considering the above points, reflect on how the character work in the scene.]
### Setting
**Location** - [Where does the scene take place? Is that clear and specific?]
**Time and Date** - [When does the scene take place? Is that clear and specific?]
**Objects** - [What items, props, or details appear?]
**Senses** - [What builds sensual atmosphere? Sight? Smell? Sound? Taste? Touch?]
**Emotional Impact** - [How does the setting reinforce the scene's emotional tone?]
**Weather** - [How does the weather support the scene? Was it omitted when it could have been useful?]
### Setting Assessment
[Was the setting description balanced within the scene? Not too much or too little? Did it feel authentic? Clichéd?]
[Did the setting enhance or distract?]
[Considering the above points, reflect on the scene's setting and if it was used well, as well as any other thoughts about the setting.]
### Final Thoughts
[Whatever you'd like to add about the scene, or omit the section if nothing comes to mind.]
```

173
fiction-assistance/skills/reviewing-fiction/review-all.md Normal file
View File

@@ -0,0 +1,173 @@
# 5-Phase Novel Self-Editing Prompts
## Phase 1: Basic Plot Review
**Instructions:** Go through each scene in your manuscript and analyze these foundational plot elements. Create a scene-by-scene breakdown.
**Prompt:**
“Please analyze my manuscript scene by scene for basic plot elements. For each scene, evaluate:
1. **Scene Name/Title** - Give each scene a descriptive name that captures its essence
2. **Story Arc Position** - Where does this scene fit in the overall story progression?
3. **Scene Purpose** - What specific function does this scene serve in advancing the plot?
4. **Opening Type** - How does the scene begin? (Action, dialogue, description, etc.)
5. **Closing Type** - How does the scene end? Does it create momentum?
6. **Scene Anchoring** - Is the scene grounded in time, place, and circumstance?
7. **Entry Hook** - What draws the reader into this scene?
8. **Exit Hook** - What compels the reader to continue to the next scene?
For each scene, provide:
- A brief assessment of strengths and weaknesses
- Suggestions for improvement
- Notes on pacing and flow
- Word count balance recommendations
Focus on the foundational structure before diving into advanced elements.”
-----
## Phase 2: Advanced Plot Review
**Instructions:** Now examine the deeper plot mechanics that drive engagement and emotional impact.
**Prompt:**
“Building on the basic plot analysis, examine each scene for these advanced plot elements:
1. **Tension** - What creates suspense or unease? Is it sustained throughout?
2. **Conflict** - What obstacles, disagreements, or challenges drive the scene?
3. **Revelation** - What new information is revealed to characters or readers?
4. **Backstory Integration** - How is past information woven naturally into the present?
5. **Flashback Usage** - Are any flashbacks necessary, clear, and well-integrated?
6. **Scene Middle** - Does the scene have a strong middle that maintains interest?
7. **Scene Climax** - What is the peak moment or turning point of each scene?
8. **Action/Sequel Balance** - Does the scene advance plot (action) or show reaction/reflection (sequel)?
9. **Reader Knowledge Gained** - What does the reader learn that advances their understanding?
Evaluate:
- Whether tension escalates appropriately throughout the manuscript
- If conflicts feel organic and meaningful
- Whether revelations are well-timed and impactful
- The balance between action and reflection
- Areas where scenes feel flat or disconnected”
-----
## Phase 3: Complete Character Analysis
**Instructions:** Examine how characters function within each scene and throughout the overall narrative.
**Prompt:**
“Analyze the character elements throughout my manuscript:
**Basic Character Elements:**
1. **Character List per Scene** - Who appears or is mentioned in each scene?
2. **Point of View (POV)** - Whose perspective tells each scene? Is it consistent?
3. **POV Goal** - What does the POV character want to achieve in this scene?
**Advanced Character Elements:**
4. **POV Internal Goal** - What deeper, emotional need drives the character?
5. **Goal Related to Plot** - How do character goals connect to the main story?
6. **Failure Consequences** - What happens if the character fails to achieve their goal?
7. **Impact on POV Character** - How does the scene change the POV character?
8. **Impact on Protagonist** - How does this scene affect the main character’s journey?
9. **Character Knowledge Gained** - What does the character learn or realize?
10. **Character in Motion** - Is the character actively participating or passively observing?
Assess:
- Character consistency and development arcs
- Whether POV shifts are clear and purposeful
- If character goals create compelling motivation
- The balance of character growth across scenes
- Whether secondary characters serve meaningful purposes
- Name confusion or character overload issues”
-----
## Phase 4: Complete Setting Analysis
**Instructions:** Evaluate how setting enhances mood, supports plot, and engages the senses.
**Prompt:**
“Examine the setting elements in each scene of my manuscript:
**Basic Setting Elements:**
1. **Location** - Where does each scene take place? Is it clear and specific?
2. **Dates and Times** - When does the action occur? Is timing clear?
3. **Objects** - What relevant items, props, or details appear?
4. **Sight** - What visual details create atmosphere?
5. **Smells** - Are appropriate scents mentioned to enhance immersion?
6. **Sounds** - What auditory details support the scene?
7. **Tastes** - When relevant, are taste sensations included?
8. **Touch** - What tactile details ground the reader in the scene?
9. **Emotional Impact** - How does the setting reinforce the scene’s emotional tone?
**Advanced Setting Elements:**
10. **Location Split** - Should any scenes be divided across multiple locations?
11. **Weather** - How does weather support mood, plot, or characterization?
Evaluate:
- Whether description is balanced (not too much or too little)
- If setting details match the POV character’s perspective
- Whether locations feel authentic and serve the story
- If sensory details avoid clichés and add variety
- How setting supports pacing and emotional beats
- Whether weather and environmental details enhance rather than distract”
-----
## Phase 5: Story Structure Integration
**Instructions:** Synthesize all previous analyses to evaluate overall story architecture and flow.
**Prompt:**
“Using insights from the previous four phases, analyze the overall structure and integration of my manuscript:
**Story Architecture:**
1. **Inciting Incident** - Is it clear, compelling, and well-placed?
2. **Plot Points** - Are major turning points obvious and impactful?
3. **Climax** - Does the climax feel earned and satisfying?
4. **Resolution** - Does the ending resolve key conflicts appropriately?
**Integration Analysis:**
5. **Scene Flow** - Do scenes connect logically and maintain momentum?
6. **Pacing Rhythm** - Is there good variation between fast and slow scenes?
7. **Character Arc Completion** - Do characters grow consistently throughout?
8. **Setting Consistency** - Do locations and time periods feel coherent?
9. **Theme Reinforcement** - How do plot, character, and setting support central themes?
**Structural Recommendations:**
- Scenes that should be added, removed, or combined
- Pacing adjustments needed
- Character development gaps to address
- Setting opportunities to enhance story impact
- Overall readability improvements
**Final Assessment:**
Provide a comprehensive evaluation of:
- The manuscript’s greatest strengths
- Top 3-5 areas needing improvement
- Specific action steps for revision
- Overall readability score and market readiness
Consider how all 38 story elements work together to create a cohesive, engaging narrative that will keep readers turning pages.”
-----
## Usage Notes:
- **Complete each phase fully** before moving to the next
- **Take detailed notes** during each phase for reference
- **Allow time between phases** to maintain objectivity
- **Consider having each phase reviewed** by a writing partner or beta reader
- **Use the final phase** to create a revision roadmap
Each phase builds upon the previous ones, creating a comprehensive understanding of your manuscript’s strengths and areas for improvement.