storytelling

Applies four narrative patterns to structure design work for empathy, coordination, orientation, and persuasion.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill storytelling-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storytelling
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/storytelling
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill storytelling-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often defaults to sterile data and frameworks, leaving journeys, blueprints, briefs, and decks structurally complete but emotionally lifeless. This Skill gives design artifacts narrative structure so stakeholders can locate themselves in the user's experience, without sacrificing evidentiary rigor. ## Core Features & Use Cases - Four canonical patterns: protagonist-arc for empathy, choreography for service coordination, situation/complication/resolution for strategic orientation, and what-is/what-could-be for persuasion — each with a named pathology to avoid. - Discipline guardrails: five explicit refusals that prevent smoothing user data into clean arcs, manufacturing tension, or substituting emotional appeal for evidence. - Use Case: A team has a service blueprint that is technically accurate but no stakeholder connects with it. Invoke the skill to apply the choreography pattern, mapping actors across time and handoffs so every human can locate themselves in the service story. ## Quick Start Ask the assistant to use the storytelling skill to tell the story of your current user journey or design brief.

Frequently Asked Questions about storytelling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add narrative structure to a user journey map?

Apply the protagonist-arc pattern, which maps a user with a goal through stages of rising and falling tension toward resolution, carrying an emotional curve. The skill refuses to smooth messy data into clean arcs, so the story reflects what the evidence actually shows.

What narrative pattern works best for a strategy brief?

Use the situation/complication/resolution pattern, which orients readers through three beats: present state, the tension that broke equilibrium, and the proposed change. The complication must come from evidence, not be reverse-engineered from the proposal.

Can storytelling be used for service blueprints with multiple actors?

Yes, the choreography pattern structures services as performances across actors, frontstage and backstage, over time, with no single protagonist. It guards against role reduction, where people disappear into system roles and no human can locate themselves in the blueprint.

When should I not use a conflict-based story arc?

Avoid conflict arcs when the experience is habit-shaped, ambient, or recurring rather than goal-driven. The skill offers kishōtenketsu, a four-beat non-conflict structure, as a protagonist-arc variant for calm products and recurring use.

What happens when there is not enough user data for a story?

The skill surfaces the evidence gap instead of composing fiction and recommends running user research first. Story without evidence becomes fabrication, so it defers to investigation before composing an empathy arc.