# Pm Storyboard

> Create a 6-frame visual narrative storyboard that tells a user's journey from problem to solution. Use when the user asks to "create a storyboard", "build a narrative", "tell the product story", "visualise the user journey", or wants to pitch/align stakeholders on a product or feature using storytelling.

- **Type:** Skill
- **Install:** `agentstack add skill-jiplet-transformation-os-pm-storyboard`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Jiplet](https://agentstack.voostack.com/s/jiplet)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Jiplet](https://github.com/Jiplet)
- **Source:** https://github.com/Jiplet/transformation-os/tree/main/skills/product/pm-storyboard

## Install

```sh
agentstack add skill-jiplet-transformation-os-pm-storyboard
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

## 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

1. **Frame 1: Main Character** — Introduce the persona and their context
2. **Frame 2: The Problem Emerges** — Show the challenge or obstacle they face
3. **Frame 3: The "Oh Crap" Moment** — Escalate the problem to create urgency
4. **Frame 4: The Solution Appears** — Introduce your product/feature
5. **Frame 5: The "Aha" Moment** — Show the user experiencing the breakthrough
6. **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

### When to Use
- Pitching a new product or feature to stakeholders
- Aligning teams on user value
- Testing if a product idea resonates emotionally
- Communicating vision at all-hands or investor meetings

### When NOT to Use
- For technical implementation details
- As a replacement for user research

## Application

### Step 1: Gather Context
Ensure you have:
- **Persona clarity:** Who is the main character?
- **Problem understanding:** What challenge do they face?
- **Solution definition:** What product/feature will help?
- **Desired outcome:** What does success look like?

### Step 2: Ask the 7 Storyboard Questions (one at a time)

1. Who is the main character? (Name, age, role, context)
2. What problem or challenge are they facing?
3. What is the "Oh Crap" moment where the problem escalates?
4. How is the solution introduced?
5. What is the "Aha" moment using the solution?
6. What does life look like after the solution?
7. Any specific visual style? (Default: fat-marker sharpie sketches, minimal monochrome)

### Step 3: Write the 6-Frame Narrative

```markdown
## 6-Frame Storyboard: [Title]

**Frame 1: Main Character**
[Persona, setting, context]

**Frame 2: The Problem Emerges**
[Challenge and how it affects their life]

**Frame 3: The "Oh Crap" Moment**
[Escalation — the problem becomes a major issue]

**Frame 4: The Solution Appears**
[How product/feature is discovered; initial reaction]

**Frame 5: The "Aha" Moment**
[Breakthrough experience using the solution]

**Frame 6: Life After the Solution**
[Resolution — specific, aspirational, measurable]

**Visual Style:** [fat-marker sketches / provided direction]
```

### Step 4: Test the Storyboard
1. Is the main character relatable?
2. Is the problem visceral — do people *feel* the frustration?
3. Is the "Oh Crap" moment real and escalating?
4. Is the solution introduction natural (not forced)?
5. Is the "Aha" moment believable?
6. Is the "after" state aspirational and specific?

## Common Pitfalls

- **Generic persona:** "Meet User, a busy professional" → fix: get specific
- **Weak problem:** "User has efficiency issues" → fix: make it visceral
- **Forced solution:** "User magically discovers our product" → fix: realistic discovery
- **Feature-centric Aha:** "User loves the dashboard" → fix: focus on emotional outcome
- **Vague after state:** "Life is better" → fix: be specific and measurable

## Related Skills
- `pm-proto-persona` — Defines the main character
- `pm-problem-statement` — Frames the problem for Frames 2-3

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Jiplet](https://github.com/Jiplet)
- **Source:** [Jiplet/transformation-os](https://github.com/Jiplet/transformation-os)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jiplet-transformation-os-pm-storyboard
- Seller: https://agentstack.voostack.com/s/jiplet
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.