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

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>

fiction-assistance/commands/review/developmental-review.md

@@ -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.

fiction-assistance/commands/review/review-final.md

@@ -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`.

fiction-assistance/commands/review/score-scenes.md

@@ -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.

fiction-assistance/commands/review/strategic-review.md

@@ -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