# Pm Use Scenarios

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-julianoczkowski-product-manager-pm-use-scenarios`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [julianoczkowski](https://agentstack.voostack.com/s/julianoczkowski)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [julianoczkowski](https://github.com/julianoczkowski)
- **Source:** https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-use-scenarios

## Install

```sh
agentstack add skill-julianoczkowski-product-manager-pm-use-scenarios
```

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

## About

# Use Scenarios (Pragmatic Framework: Planning → Use Scenarios)

**Rule:** *articulate problems from the persona's point of view.* A use scenario
illustrates a market problem as a "story" that puts it in context (including current
results) — it is one component of requirements. See
`../pm-copilot/references/framework.md`. Personas should exist first (`pm-personas`).

## Anatomy of a Problem Card
Map interrogatives to fields:

| Field | Interrogative |
| :--- | :--- |
| **[Problem Name]** | *What* problem |
| **[Persona]** | *Who* has it |
| **has [use scenario]** | *Why* it occurs |
| **with [frequency]** | *When* it occurs |

Reframing sentence (great for turning a feature request into a problem):
> **[Persona]** struggles with **[problem]** when **[context]** because **[why it matters]**.

## What vs. How — stay on the WHAT
| WHAT = the problem → **PM → DEFINE** | HOW = the solution → **Team → DESIGN/BUILD** |
| :--- | :--- |
| Name, Persona, Use Scenario, Frequency, Market evidence, Impact | Overview, flow chart, use cases, UI, prototypes, error conditions |

A use scenario ≠ a use case. A use scenario tells the problem story; a use case
enumerates every interaction in the functional spec (the team's job).

## Three considerations when articulating a problem
1. **Avoid ambiguous terms** — do not use: *flexible, adaptable, user-friendly, TBD,
   adequate, rapidly/quickly/fast, fault tolerant, scalable, ASAP,
   maximize/minimize/optimize (any "-ize" word), and/or, etc.* Replace each with a
   concrete, observable statement.
2. **Edge cases ("what if?")** — will your persona *actually* do it? Don't design for
   situations that won't happen.
3. **Who is significant?** — the U-curve: the vocal extremes (novices + experts) are
   *where we listen*; the proficient majority is *where we should listen.* Write for
   the majority.

## Interview the user (batch questions)
1. Which persona and which market problem is this scenario for?
2. Walk me through a real situation where this happens — what triggers it, what do they
   do today, and what's the current (bad) result?
3. How often does it occur (frequency)?
4. What evidence shows this is real (counts across inputs) and how bad is it (impact)?

## Artifact template
```markdown
# Use Scenarios — 

**Company:**   ·  **Feature / Product:** 
**Author:**   ·  **Date created:**   ·  **Version:** 1.0

## Scenario 1 — 
**Problem Card**
- **Problem Name:** 
- **Persona:** 
- **Use Scenario:** 
- **Frequency:** 

**Day in the life**

**Market evidence:** 
**Impact:** 

## Scenario 2 — 
…
```

## Deliver the artifact
Follow `../pm-copilot/references/artifact-output.md`: confirm inputs, **ask Markdown
or .docx**, write the `.md`, convert to `.docx` on request via your environment's native document-creation capability. Then offer the next stage: roll these scenarios into prioritized
**`pm-requirements`** or a full **`pm-prd`**.

## Source & license

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

- **Author:** [julianoczkowski](https://github.com/julianoczkowski)
- **Source:** [julianoczkowski/product-manager](https://github.com/julianoczkowski/product-manager)
- **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-julianoczkowski-product-manager-pm-use-scenarios
- Seller: https://agentstack.voostack.com/s/julianoczkowski
- 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%.