Story Summary Generation Expert
Functionality
Extract main plots and key points based on story text content, generate complete story summary.
Use Cases
- Quickly understand story main content and plot development.
- Provide story summary for script adaptation or film and TV development.
- Create story introduction for project promotion materials.
- Provide story overview for subsequent in-depth analysis.
Core Steps
- Careful Reading: Carefully read story text, understand overall content.
- Main Plot Identification: Identify story's main plot lines.
- Key Point Extraction: Extract key points of story.
- Development Organization: Organize story development process.
- Summary Generation: Generate complete story summary.
Input Requirements
- Story Text: Complete original story text (novels, scripts, story outlines, etc.).
- Recommended Text Length: 300+ words.
Output Format
[Story Summary]
[Story Background]
[Describe background, environmental settings, etc. where story takes place]
[Main Plot]
[Describe main plot development of story]
[Story Development]
[Describe story development process in chronological order]
[Key Turning Points]
[Describe key turning points and important changes in story]
[Story Ending]
[Describe story's ending and final state]
Constraints
- Summary should be concise and complete, usually 200-500 words.
- Strictly summarize according to story original content, do not create on your own.
- Maintain accuracy and completeness of plot.
- Include core elements of story: characters, events, conflicts, endings.
Examples
See {baseDir}/references/examples.md directory for more detailed examples:
examples.md - Contains detailed summary examples for different story types (such as romance, workplace, suspense).
Detailed Documentation
See {baseDir}/references/examples.md for detailed guidance and cases on story summary generation.
Version History
| Version |
Date |
Changes |
| 2.1.0 |
2026-01-11 |
Optimized description field to be more concise and comply with imperative language specifications; added allowed-tools (Read) and model (opus) fields; optimized descriptions of functionality, use cases, core steps, input requirements, output format, requirements, etc. to comply with imperative language specifications; added constraints, examples, and detailed documentation sections. |
| 2.0.0 |
2026-01-11 |
Refactored according to official specifications |
| 1.0.0 |
2026-01-10 |
Initial version |
1---2name: story-summarizer3description: Extract main plots and key points based on story text, generate complete story summary. Suitable for quickly understanding story content, script adaptation, project promotion4license: MIT5---6
7# Story Summary Generation Expert
8
9## Functionality
10
11Extract main plots and key points based on story text content, generate complete story summary.
12
13## Use Cases
14
15- Quickly understand story main content and plot development.
16- Provide story summary for script adaptation or film and TV development.
17- Create story introduction for project promotion materials.
18- Provide story overview for subsequent in-depth analysis.
19
20## Core Steps
21
221. **Careful Reading**: Carefully read story text, understand overall content.
232. **Main Plot Identification**: Identify story's main plot lines.
243. **Key Point Extraction**: Extract key points of story.
254. **Development Organization**: Organize story development process.
265. **Summary Generation**: Generate complete story summary.
27
28## Input Requirements
29
30- **Story Text**: Complete original story text (novels, scripts, story outlines, etc.).
31- **Recommended Text Length**: 300+ words.
32
33## Output Format
34
35```
36[Story Summary]
37
38[Story Background]
39[Describe background, environmental settings, etc. where story takes place]
40
41[Main Plot]
42[Describe main plot development of story]
43
44[Story Development]
45[Describe story development process in chronological order]
46
47[Key Turning Points]
48[Describe key turning points and important changes in story]
49
50[Story Ending]
51[Describe story's ending and final state]
52```
53
54## Constraints
55
56- Summary should be concise and complete, usually 200-500 words.
57- Strictly summarize according to story original content, do not create on your own.
58- Maintain accuracy and completeness of plot.
59- Include core elements of story: characters, events, conflicts, endings.
60
61## Examples
62
63See `{baseDir}/references/examples.md` directory for more detailed examples:
64- `examples.md` - Contains detailed summary examples for different story types (such as romance, workplace, suspense).
65
66## Detailed Documentation
67
68See `{baseDir}/references/examples.md` for detailed guidance and cases on story summary generation.
69
70---
71
72## Version History
73
74| Version | Date | Changes |
75|---------|------|---------|
76| 2.1.0 | 2026-01-11 | Optimized description field to be more concise and comply with imperative language specifications; added allowed-tools (Read) and model (opus) fields; optimized descriptions of functionality, use cases, core steps, input requirements, output format, requirements, etc. to comply with imperative language specifications; added constraints, examples, and detailed documentation sections. |
77| 2.0.0 | 2026-01-11 | Refactored according to official specifications |
78| 1.0.0 | 2026-01-10 | Initial version |
majiayu000