Storyboard

What Is This?

Storyboard is a structured prompt skill designed for product managers, designers, and developers who need to quickly communicate a user journey in a clear, visual narrative format. The skill generates a six-frame storyboard that walks through a user's experience from the moment they encounter a problem all the way through to the resolution that your product or feature provides.

Each frame in the storyboard represents a distinct stage in the user's journey. The output is a written narrative that can be used as the foundation for visual storyboards, slide decks, stakeholder presentations, or design briefs. Rather than writing lengthy documentation, you get a compact, story-driven format that anyone on a team can read and immediately understand.

This skill comes from the deanpeters/Product-Manager-Skills repository and is built for speed and alignment. It is not a replacement for detailed specifications or user research reports. It is a fast narrative tool that gets everyone on the same page before deeper work begins.

Why Use It?

Product teams often struggle to communicate the "why" behind a feature or product decision. Technical documentation explains what a system does, but it rarely captures the human context that motivates the work. Storyboards fill that gap.

A six-frame narrative forces clarity. You cannot ramble or over-explain when you have six frames to work with. This constraint pushes you to identify the most important moments in the user journey and present them in a logical sequence. The result is a story that is easy to follow, easy to share, and easy to critique.

Storyboards also accelerate alignment. When a team reviews a written storyboard together, disagreements surface quickly. Someone might point out that frame three assumes the user already knows something they would not know at that point. Another person might notice that the solution in frame six does not actually address the problem introduced in frame one. These are valuable conversations to have early, before design or development work begins.

For demos and concept reviews, a storyboard gives your audience a narrative anchor. Instead of jumping straight into a prototype or a feature walkthrough, you set the scene, introduce the user, and build toward the solution. This makes the demo more persuasive and easier to remember.

How to Use It?

To use this skill, you provide context about the user, the problem they face, and the solution your product offers. The skill then generates a six-frame storyboard structured around that input.

A basic prompt might look like this:

User: A freelance graphic designer managing multiple client projects
Problem: Losing track of client feedback across email, Slack, and PDF comments
Solution: A centralized feedback inbox that consolidates all client communication

Generate a six-frame storyboard showing this user's journey from problem to solution.

The output will follow a consistent frame structure:

Frame 1: Context - Introduce the user and their environment
Frame 2: Problem - Show the specific pain point or friction
Frame 3: Struggle - Illustrate the consequences of the problem
Frame 4: Discovery - Show how the user finds the solution
Frame 5: Adoption - Demonstrate the user trying the solution
Frame 6: Resolution - Show the improved outcome and emotional payoff

Each frame includes a brief scene description and a line of dialogue or internal thought from the user. This gives the storyboard both visual and emotional texture, making it easier to translate into actual illustrations or presentation slides if needed.

When to Use It?

Use this skill at the beginning of a product cycle when you need to build shared understanding across a team. It works well in discovery phases, before kickoff meetings, and during concept reviews where stakeholders need to evaluate whether a proposed solution actually addresses a real user need.

It is also useful when preparing for demos. A storyboard gives you a narrative script that you can follow during a live walkthrough, ensuring you present the feature in the context of a real user problem rather than as a list of capabilities.

Use it when onboarding new team members who need to understand the purpose behind a product or feature quickly. A storyboard communicates intent faster than a requirements document.

Important Notes

Keep the user persona specific. Vague personas produce vague storyboards. The more concrete your input, the more useful the output.

The six-frame format is intentionally limited. If your journey requires more frames, consider whether you are trying to tell too many stories at once. Break complex journeys into multiple focused storyboards instead.

Storyboards generated by this skill are narrative starting points, not final deliverables. Treat them as drafts that your team refines together.