92 lines
3.7 KiB
Markdown
92 lines
3.7 KiB
Markdown
|
---
|
||
|
|
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.
|