storyboard by deanpeters/product-manager-skills
npx skills add https://github.com/deanpeters/product-manager-skills --skill storyboard创建一个包含 6 个画面的视觉叙事,讲述用户从遇到问题到获得解决方案的旅程。运用经典的故事弧线来建立同理心、阐明价值,并使抽象的产品概念具体化。你可以用它来协调利益相关者、推介功能、传达愿景,或在构建产品之前测试你的解决方案是否能引起情感共鸣。
这不是 UI 原型图——它是一个讲故事的工具,旨在让你的产品人性化的一面鲜活起来。
基于经典的叙事弧线,6 画面格式遵循以下模式:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
使用 template.md 获取完整的填写结构。
在创建故事板之前,请确保你拥有:
skills/proto-persona/SKILL.md)skills/problem-statement/SKILL.md)skills/positioning-statement/SKILL.md)如果缺少背景信息: 请先进行探索性工作。不要编造人物角色或问题。
逐一回答这些问题来构建叙事:
基于以上答案,起草叙事:
## 生成的 6 画面故事情节
**画面 1:介绍主角**
- [插入对主角、其场景和背景的描述]
- [示例:"Sarah,35 岁,是一名自由职业平面设计师,在她的家庭办公室同时处理着 10 个客户项目"]
**画面 2:问题浮现**
- [描述主角的挑战及其如何影响他们的生活]
- [示例:"她深陷发票追踪的泥潭——每月花 8 小时通过电子表格和电子邮件追讨逾期付款"]
**画面 3:“糟糕”时刻**
- [强调问题升级为重大事件的过程]
- [示例:"一个重要客户的付款已逾期 2 周。Sarah 意识到她因为专注于设计工作而忘了跟进。该客户现已失联,她开始为现金流感到焦虑。"]
**画面 4:解决方案出现**
- [解释解决方案是如何被引入的,以及主角的初步反应]
- [示例:"Sarah 发现了 SmartInvoice,一个能在最佳时间自动发送付款提醒的工具。她持怀疑态度——这听起来会不会太咄咄逼人?——但还是决定试一试。"]
**画面 5:“顿悟”时刻**
- [展示主角使用解决方案并体验到突破性进展]
- [示例:"两天后,Sarah 收到一条通知:'客户 XYZ 刚刚付款!' AI 定时的提醒奏效了——无需尴尬的跟进电话。她感到如释重负,并且掌控感十足。"]
**画面 6:解决方案后的生活**
- [描述问题解决后的状态以及生活如何得到改善]
- [示例:"Sarah 现在每月在发票处理上只花 30 分钟,而不是 8 小时。她重新拥有了晚上的时间,与家人共度而不是追讨付款。她的现金流变得可预测,焦虑也消失了。"]
**可选视觉元素**
- [如果未指定视觉风格:"使用粗记号笔风格的草图——极简、单色、手绘感"]
- [如果提供了视觉元素:"包含用户提供的图片、GIF 或图标"]
为每个画面创建或描述视觉内容:
画面 1:主角
画面 2:问题浮现
画面 3:“糟糕”时刻
画面 4:解决方案出现
画面 5:“顿悟”时刻
画面 6:解决方案后的生活
询问以下问题:
如果任何答案是“否”,请进行修改。
查看 examples/sample.md 获取完整的故事板示例。
迷你示例摘录:
**画面 1:** Sarah,35 岁,自由职业设计师,同时处理 10 个客户\n**画面 2:** 每月花 8 小时追讨逾期发票\n**画面 3:** $5,000 付款逾期 2 周\n```
症状: “认识一下用户,一位忙碌的专业人士”
后果: 没有人能认同这个角色。
解决方法: 具体化:“认识一下 Sarah,35 岁,自由职业设计师,同时处理 10 个客户,家庭办公室,热爱设计但讨厌行政工作。”
症状: “用户在效率方面有问题”
后果: 问题无法引起情感共鸣。
解决方法: 使其切肤:“Sarah 每月花 8 小时追讨逾期发票,错过了家庭晚餐,为现金流感到焦虑。”
症状: “用户神奇地发现了我们的产品”
后果: 感觉做作,不真实。
解决方法: 展示现实的发现过程:“Sarah 在设计论坛上看到推荐”或“Sarah 的同事提到了它。”
症状: “用户看到仪表盘并爱上了这些功能”
后果: 没有情感回报。
解决方法: 关注结果:“Sarah 收到通知:'收到 $5,000!' 她松了口气——无需尴尬的电话。”
症状: “现在生活更好了”
后果: 不令人向往或不具体。
解决方法: 具体化:“Sarah 现在下午 6 点下班,晚上与孩子们共度而不是追讨客户。按时付款率从 50% 跃升至 80%。”
skills/proto-persona/SKILL.md —— 定义主角skills/problem-statement/SKILL.md —— 为画面 2-3 构建问题框架skills/positioning-statement/SKILL.md —— 为画面 4 中的解决方案引入提供信息skills/jobs-to-be-done/SKILL.md —— 为画面 6 中的期望结果提供信息https://github.com/deanpeters/product-manager-prompts 仓库中的 prompts/storyboard-storytelling-prompt.md。技能类型: 组件
建议文件名: storyboard.md
建议放置位置: /skills/components/
依赖项: 引用 skills/proto-persona/SKILL.md, skills/problem-statement/SKILL.md, skills/positioning-statement/SKILL.md, skills/jobs-to-be-done/SKILL.md
每周安装次数
240
仓库
GitHub 星标数
1.5K
首次出现
Feb 12, 2026
安全审计
安装于
codex214
opencode212
gemini-cli209
github-copilot208
cursor206
kimi-cli204
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.
Based on classic narrative arcs, the 6-frame format follows this pattern:
Use template.md for the full fill-in structure.
Before creating the storyboard, ensure you have:
skills/proto-persona/SKILL.md)skills/problem-statement/SKILL.md)skills/positioning-statement/SKILL.md)If missing context: Run discovery work first. Don't fabricate personas or problems.
Ask these questions one at a time to develop the narrative:
Based on the answers above, draft the narrative:
## Generated 6-Frame Storyline
**Frame 1: Introducing the Main Character**
- [Insert description of the main character, their setting, and context]
- [Example: "Sarah, 35, is a freelance graphic designer juggling 10 client projects from her home office"]
**Frame 2: The Problem Emerges**
- [Describe the main character's challenge and how it affects their life]
- [Example: "She's drowning in invoice tracking—8 hours per month chasing late payments via spreadsheets and email"]
**Frame 3: The 'Oh Crap' Moment**
- [Highlight the escalation of the problem into a major issue]
- [Example: "A major client's payment is 2 weeks overdue. Sarah realizes she forgot to follow up because she was focused on design work. The client has now gone silent, and she's anxious about cash flow."]
**Frame 4: The Solution Appears**
- [Explain how the solution is introduced and the main character's initial reaction]
- [Example: "Sarah discovers SmartInvoice, a tool that automatically sends payment reminders at optimal times. She's skeptical—will it sound too pushy?—but decides to try it."]
**Frame 5: The 'Aha' Moment**
- [Show the main character using the solution and experiencing a breakthrough]
- [Example: "Two days later, Sarah receives a notification: 'Client XYZ just paid!' The AI-timed reminder worked—no awkward follow-up call needed. She feels relieved and in control."]
**Frame 6: Life After the Solution**
- [Describe the resolution and how life improves after overcoming the problem]
- [Example: "Sarah now spends 30 minutes per month on invoicing instead of 8 hours. She's reclaimed her evenings, spending time with family instead of chasing payments. Her cash flow is predictable, and her anxiety is gone."]
**Optional Visual Elements**
- [If no visual style specified: "Use fat-marker, sharpie-style sketches—minimal, monochrome, hand-drawn feel"]
- [If visual elements provided: "Include user-provided images, GIFs, or icons"]
For each frame, create or describe the visual:
Frame 1: Main Character
Frame 2: The Problem Emerges
Frame 3: The 'Oh Crap' Moment
Frame 4: The Solution Appears
Frame 5: The 'Aha' Moment
Frame 6: Life After the Solution
Ask these questions:
If any answer is "no," revise.
See examples/sample.md for full storyboard examples.
Mini example excerpt:
**Frame 1:** Sarah, 35, freelance designer juggling 10 clients\n**Frame 2:** Spends 8 hours/month chasing overdue invoices\n**Frame 3:** $5,000 payment is 2 weeks overdue\n```
---
## Common Pitfalls
### Pitfall 1: Generic Persona
**Symptom:** "Meet User, a busy professional"
**Consequence:** No one identifies with this character.
**Fix:** Get specific: "Meet Sarah, 35, freelance designer, juggling 10 clients, home office, loves design but hates admin."
---
### Pitfall 2: Weak Problem
**Symptom:** "User has a problem with efficiency"
**Consequence:** Problem doesn't resonate emotionally.
**Fix:** Make it visceral: "Sarah spends 8 hours/month chasing overdue invoices, missing family dinners, feeling anxious about cash flow."
---
### Pitfall 3: Forced Solution Introduction
**Symptom:** "User magically discovers our product"
**Consequence:** Feels contrived, not authentic.
**Fix:** Show realistic discovery: "Sarah sees a recommendation in a designer forum" or "Sarah's colleague mentions it."
---
### Pitfall 4: Feature-Centric "Aha" Moment
**Symptom:** "User sees the dashboard and loves the features"
**Consequence:** No emotional payoff.
**Fix:** Focus on outcome: "Sarah gets notification: '$5,000 received!' She's relieved—no awkward call needed."
---
### Pitfall 5: Vague "After" State
**Symptom:** "Life is better now"
**Consequence:** Not aspirational or concrete.
**Fix:** Be specific: "Sarah leaves work at 6pm now, spending evenings with her kids instead of chasing clients. On-time payments jumped from 50% to 80%."
---
## References
### Related Skills
- `skills/proto-persona/SKILL.md` — Defines the main character
- `skills/problem-statement/SKILL.md` — Frames the problem for Frame 2-3
- `skills/positioning-statement/SKILL.md` — Informs the solution introduction in Frame 4
- `skills/jobs-to-be-done/SKILL.md` — Informs the desired outcome in Frame 6
### External Frameworks
- Joseph Campbell, *The Hero's Journey* (1949) — Classic narrative structure
- Pixar's story rules — "Once upon a time... Every day... Until one day..."
- Donald Miller, *Building a StoryBrand* (2017) — Story-driven marketing frameworks
### Dean's Work
- Storyboard Storytelling Prompt (6-Frame Storyline Generator)
### Provenance
- Adapted from `prompts/storyboard-storytelling-prompt.md` in the `https://github.com/deanpeters/product-manager-prompts` repo.
---
**Skill type:** Component
**Suggested filename:** `storyboard.md`
**Suggested placement:** `/skills/components/`
**Dependencies:** References `skills/proto-persona/SKILL.md`, `skills/problem-statement/SKILL.md`, `skills/positioning-statement/SKILL.md`, `skills/jobs-to-be-done/SKILL.md`
Weekly Installs
240
Repository
GitHub Stars
1.5K
First Seen
Feb 12, 2026
Security Audits
Gen Agent Trust HubPassSocketFailSnykPass
Installed on
codex214
opencode212
gemini-cli209
github-copilot208
cursor206
kimi-cli204
注册流程转化率优化指南:减少摩擦、提高完成率的专家技巧
24,500 周安装