Create a six-frame storyboard that shows a user's journey from problem to solution.
SkillScore95Maintained
Automatic
◆Product Management pack
Last verified 8/24/2026
What it changes
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill95%
Checks it passed that the model alone missed
Specifies a minimal, monochrome fat-marker sharpie sketch style.
Checks whether target users would find the breakthrough moment believable and realistic.
Depicts a realistic, natural discovery of the payment tool rather than a feature spec sheet.
3 fixed18 passed either way0 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+105%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/24/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
When rendering image descriptions or visual sketches for a storyboard where the stakeholder gave no visual guidelines, what style should be instructed by default?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies a minimal, monochrome fat-marker sharpie sketch style.
Missed
Passed
case-11 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md243 linessingle file
Purpose
Create a 6-frame visual narrative that tells the story of a user's journey from problem to solution, using the classic storytelling arc to build empathy, illustrate value, and make abstract product concepts concrete. Use this to align stakeholders, pitch features, communicate vision, or test if your solution resonates emotionally before building it.
This is not a UI mockup—it's a storytelling tool that brings the human side of your product to life.
Key Concepts
The 6-Frame Storyboard Structure
Based on classic narrative arcs, the 6-frame format follows this pattern:
Frame 1: Main Character — Introduce the persona and their context
Frame 2: The Problem Emerges — Show the challenge or obstacle they face
Frame 3: The "Oh Crap" Moment — Escalate the problem to create urgency
Frame 4: The Solution Appears — Introduce your product/feature
Frame 5: The "Aha" Moment — Show the user experiencing the breakthrough
Frame 6: Life After the Solution — Illustrate the improved state
Why This Works
Emotional engagement: Stories create empathy in ways specs can't
Concrete over abstract: Visual narrative makes vague concepts tangible
Memorable: People remember stories better than feature lists
Alignment tool: Stakeholders can react to a story and give feedback
Low-fidelity: Doesn't require polished design—sketches work great
Anti-Patterns (What This Is NOT)
Not a user flow diagram: This is emotional storytelling, not process documentation
Not a feature demo: Focus on user outcomes, not product capabilities
Not marketing copy: Authentic narrative, not hype
When to Use This
Pitching a new product or feature to stakeholders
Aligning teams on user value (product, design, engineering, execs)
Testing if a product idea resonates emotionally
Communicating vision at all-hands or investor meetings
Validating problem/solution fit before building
When NOT to Use This
For technical implementation details (use architecture diagrams instead)
When the user problem is trivial or well-understood
As a replacement for user research (storyboards illustrate insights, don't create them)
Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.