Features
Deeply read and comprehend the story text, summarize the characters, character relationships, and plot, and organize them into a smooth story outline.
Use Cases
- Quickly understand the core content and structure of the story.
- Provide a story outline basis for scriptwriting.
- Create project application or promotional materials.
- Provide an overview for story evaluation and adaptation.
Core Steps
- Deep Reading: Deeply read the story text and accurately understand the characters, character relationships, and event plot in the story.
- Information Extraction: Extract the main characters, character relationships, and key plot points.
- Structural Organization: Organize information according to the logic of story development and build an outline framework.
- Outline Writing: Summarize the story into a smoothly written story outline.
Input Requirements
- Story Text: The complete original story text (supports first-person or third-person narration).
- Recommended Text Length: 300 characters or more.
Output Format
Directly output a smooth written summary of the story outline, without any title.
Constraints
- Word Count Control: Strictly control the summary word count between 300 and 500 Chinese characters.
- Content Accuracy: Summarize strictly according to the original text, without creating or adapting on your own.
- Unified Person: Summarize in the third person (even if the original text is in the first person).
- Format Requirements: Directly output the main text, without any title.
- Avoid Commentary: Do not provide a summarizing or evaluative overview of the text content.
Examples
See {baseDir}/references/examples.md directory for more detailed examples:
examples.md- Story outline examples containing different narrative perspectives (first person, third person) and complex character relationships.
Detailed Documentation
See {baseDir}/references/examples.md for detailed guidance and cases on story outline generation.
Version History
| Version | Date | Changes |
|---|---|---|
| 2.1.0 | 2026-01-11 | Optimized the description field to make it more concise and compliant with imperative language conventions; added allowed-tools (Read) and model (opus) fields; optimized descriptions such as features, use cases, core steps, input requirements, output format, and requirements to make them more compliant with imperative language conventions; 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 |