storyboard — Claude Code skill: a six-frame user story
This skill drafts a six-frame storyboard tracing one person from a problem to its fix. Handy before a concept review or a demo.
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a claude-codeWhat storyboard does
The skill walks the agent through a classic narrative arc and splits it into six frames: the character, the trouble appearing, the moment it escalates, the arrival of the solution, the breakthrough, and the improved state afterward. What comes back is written description for each frame, not a screen mockup. The point is to give an abstract idea something people can argue with before anyone builds it.
Three steps. First the agent gathers context: who the character is, what they struggle with, which solution is in play, and what a good outcome looks like. Then it asks seven questions one at a time — character, problem, escalation, how the solution shows up, the breakthrough, life afterward, and any drawing style. Finally it writes the frame-by-frame narrative. Context passed along with the invocation is treated as already answered, so those questions get skipped.
The skill does not stand in for user research; it illustrates what you already know. It will not invent personas or problems, so without that context you do discovery first. Technical implementation is out of scope too — architecture diagrams cover that.
What it helps with
- turn a user story into six frames for a concept pitch
- explain a feature's value to the team before a prototype exists
- test whether an idea lands emotionally before building it
- walk stakeholders through the path from problem to solution
- make a vague product description concrete scene by scene
Example prompts for the agent
- Storyboard this: an overwhelmed pharmacy tech finds our auto-refill queue and finishes the shift on time — for next week's concept review
- Build a six-frame storyboard for the new feature
How to install storyboard
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a claude-code2Manually: put the files in place
~/.claude/skills/storyboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/storyboard/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a codex2Manually: put the files in place
.agents/skills/storyboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a cursor2Manually: put the files in place
.cursor/skills/storyboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills storyboard2Manually: put the files in place
.github/skills/storyboard/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/storyboardManually: put the files in place
.devin/skills/storyboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about storyboard
How do I install storyboard in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill storyboard -a claude-code. The skill file lands at ~/.claude/skills/storyboard/SKILL.md.
What does storyboard do?
It produces a written six-frame storyboard: character, problem, escalation, solution, breakthrough, and the better state that follows. The structure follows a classic narrative arc.
How is storyboard different from a UI mockup?
It is a storytelling tool, not screen design. It covers the emotional side of a product, which suits alignment and idea review rather than implementation detail.