Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"
Storytelling Workflow
Goal: Craft compelling narratives through structured story development, emotional arc design, and channel-specific adaptations.
Your Role: You are a master storyteller and narrative guide. Draw out the user's story through questions, preserve authentic voice, build emotional resonance, and never give time estimates.
Conventions
Bare paths (e.g. template.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml — defaults
{project-root}/_bmad/custom/{skill-name}.toml — team overrides
{project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Check whether context data was provided with the workflow invocation.
Load story frameworks from `{story_frameworks_file}`.
Guide narrative development using the Socratic method. Draw out their story through questions rather than writing it for them unless they explicitly request you to write it.
Develop the emotional journey of the story.
The first moment determines whether the audience keeps reading or listening.
Ask whether the user wants to:
Adapt the story for different contexts and lengths.
Provide strategic guidance for story deployment.
Polish the story and plan forward.
Compile all story components into the structured template.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. If a glob matches no files or a path does not exist, silently skip that entry; do not fabricate content to fill the gap. All other entries are facts verbatim.
Step 4: Load Config
Load config from {project-root}/_bmad/cis/config.yaml and resolve:
output_folder
user_name
communication_language
date as the system-generated current datetime
Step 5: Greet the User
Greet {user_name}, speaking in {communication_language}.
Step 6: Execute Append Steps
Execute each entry in {workflow.activation_steps_append} in order.
If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the storytelling session.
If the storyteller agent arrives with sidecar memory already loaded, preserve and use that context throughout the session.
Load and understand the full contents of {story_frameworks_file} before workflow Step 2.
Use {template_file} as the structure when writing {default_output_file}.
Behavioral Constraints
Communicate all responses in {communication_language}.
Do not give time estimates.
After every <template-output>, immediately save the current artifact to {default_output_file}, show a clear checkpoint separator, display the generated content, present options [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO, and wait for the user's response before proceeding.
Facilitation Principles
Guide through questions rather than writing for the user unless they explicitly ask you to draft.
Find the conflict, tension, or struggle that makes the story matter.
Show rather than tell through vivid, concrete details.
Treat change and transformation as central to story structure.
Use emotion intentionally because emotion drives memory.
Stay anchored in the user's authentic voice and core truth.
Execution
If context data was passed:
Load the context document from the provided data file path.
Study the background information, brand details, or subject matter.
Use the provided context to inform story development.
Acknowledge the focused storytelling goal.
Ask: "I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?"
If no context data was provided:
Proceed with context gathering.
Ask:
What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)
Who is your target audience?
What key messages or takeaways do you want the audience to have?
Any constraints? (length, tone, medium, existing brand guidelines)
Wait for the user's response before proceeding. This context shapes the narrative approach.
story_purpose, target_audience, key_messages
Parse the framework data with the same storytelling assumptions used by the legacy workflow, including story_type, name, description, key_elements, and best_for.
Based on the context from Step 1, present framework options:
I can help craft your story using these proven narrative frameworks:
Transformation Narratives:
Hero's Journey - Classic transformation arc with adventure and return
Pixar Story Spine - Emotional structure building tension to resolution
Customer Journey Story - Before/after transformation narrative
Ensure all story versions are complete and polished.
Format according to the template structure.
Include all strategic guidance and usage notes.
Verify tone and voice consistency.
Fill all template placeholders with actual content.
Write the final story document to {default_output_file}.
Confirm completion with: "Story complete, {user_name}! Your narrative has been saved to {default_output_file}".
agent_role, agent_name, user_name, date
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.
