6e4edc09d1
Strip the Universalis-specific vault layout and card-management
machinery. The plugin is now a general-purpose fiction toolkit:
nine commands that take a manuscript path/glob/selection via
\$ARGUMENTS and write their output to the conversation.
Surviving commands, flattened into commands/:
- analyze-story: structural and statistical analysis
- bechdel-test: representation tests (Bechdel + related)
- check-continuity: plot/character/world continuity
- check-voice: per-character voice consistency
- developmental-review: structural feedback on a scene/chapter
- extract-research: world-building and research inventory
- final-review: synthesis of prior-phase reviews
- generate-timeline: chronology with consistency checks
- strategic-review: craft-based critique with priority ranking
Removed (vault and card management): 10 update-*-cards commands,
cleanup-generated, update-changed, update-links,
update-chapter-summaries, validate-story, validate-pdf, score-scenes.
The original bespoke command set is preserved in 65c29d7 for recovery.
Agent (line-editor) and skill (reviewing-fiction) were already
portable and are unchanged. plugin.json no longer needs the
commands subdirectory paths since the layout is flat. Marketplace
description updated to reflect the general-purpose scope.
BREAKING CHANGE: All update-*-cards, cleanup-generated, update-changed,
update-links, update-chapter-summaries, validate-story, validate-pdf,
and score-scenes commands are removed. perform-bechdel-tests is renamed
to bechdel-test. review-final is renamed to final-review.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
31 lines
1.8 KiB
Markdown
31 lines
1.8 KiB
Markdown
---
|
|
description: Generate structural and statistical analysis of a manuscript
|
|
argument-hint: "[path, glob, or selection]"
|
|
allowed-tools: [Read, Glob, Grep]
|
|
---
|
|
|
|
Analyze the manuscript at `$ARGUMENTS` (a file path, a glob of chapter files, or pasted text). If no argument is given, use the current selection or the most recently opened manuscript file.
|
|
|
|
Produce a structural and statistical report. Cite specific numbers — avoid vague assessments.
|
|
|
|
## Metrics to compute
|
|
|
|
- **Word and scene counts**: total words, chapter count, scene count, average lengths, longest/shortest chapter and scene
|
|
- **POV distribution**: who narrates, how often, and how POV is balanced across chapters
|
|
- **Character usage**: appearance frequency and dialogue volume for named characters; flag overload (too many minor characters) or imbalance (one character dominating)
|
|
- **Dialogue vs. narrative ratio**: rough percentage, and whether the balance shifts across the book
|
|
- **Pacing and scene shape**: scene-length variation, action vs. reflection balance, chapter-ending types (cliffhanger, resolution, transition)
|
|
- **Plot and conflict mapping**: active vs. resolved plotlines, internal vs. external conflicts, where tension peaks and troughs
|
|
|
|
## Output format
|
|
|
|
Present a compact Markdown report with these sections:
|
|
|
|
1. **Overview** — headline metrics (words, chapters, scenes, completion status if discernible)
|
|
2. **Characters** — frequency table, POV distribution, dialogue volume
|
|
3. **Plot and pacing** — plotline status, scene-type distribution, tension curve commentary
|
|
4. **Issues and observations** — patterns worth surfacing (imbalances, gaps, structural concerns)
|
|
5. **Recommendations** — three to five concrete next steps the writer could take
|
|
|
|
Output directly to the conversation. If the user wants the report saved, they will ask.
|