Pm Use Scenarios

Community

julianoczkowski

pm-use-scenarios

Write Pragmatic Institute use scenarios — short stories that put a market problem in context from the persona's point of view (a component of requirements). Use when the PM asks for "use scenarios", "a day in the life", "user story context", "problem statements", or needs to reframe a feature request as a real problem so development understands the WHAT (not the HOW). Produces a Use Scenarios document as a Markdown or Word .docx artifact.

Overview

Publisher	julianoczkowski
Repository	`product-manager`
Skill name	`pm-use-scenarios`
Stars	51
Forks	7
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by julianoczkowski on GitHub. Read the source before you install it.

Installation

Install the Pm Use Scenarios AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-use-scenarios
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/julianoczkowski/product-manager.git /tmp/product-manager
mkdir -p .claude/skills
cp -r /tmp/product-manager/skills/pm-use-scenarios .claude/skills/pm-use-scenarios

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pm Use Scenarios in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pm Use Scenarios on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pm Use Scenarios is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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.
Edge cases ("what if?") — will your persona actually do it? Don't design for situations that won't happen.
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)

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

Artifact template

markdown
# Use Scenarios — <Product / Release>

**Company:** <company>  ·  **Feature / Product:** <feature / product name>
**Author:** <author>  ·  **Date created:** <date>  ·  **Version:** 1.0

## Scenario 1 — <Problem Name>
**Problem Card**
- **Problem Name:** <what>
- **Persona:** <who>
- **Use Scenario:** <why — the situation that causes the problem>
- **Frequency:** <when / how often>

**Day in the life**
<A short first-person narrative: the persona's context, the trigger, what they do today,
and the frustrating current result. Concrete and specific — no ambiguous terms.>

**Market evidence:** <# of documented occurrences across inputs>
**Impact:** <1–5 on the impact scale (or 99999 if contractual)>

## Scenario 2 — <Problem Name>
…

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.

Frequently asked questions

What does the Pm Use Scenarios AI skill do?

Why use Pm Use Scenarios on TypingMind?

Because you install it once and use it with any model. Pm Use Scenarios is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pm Use Scenarios in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-use-scenarios. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Pm Use Scenarios?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pm Use Scenarios?

As many as you like. As long as a model supports skills, you can use Pm Use Scenarios with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pm Use Scenarios AI skill free?

Yes. It is published on GitHub by julianoczkowski under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

3 Statement Model

NousResearch

OrganizationPopular

Build integrated IS/BS/CF financial workbooks in Excel.

Comps Analysis

Build comparable-company valuation workbooks in Excel.

Lbo Model

Build leveraged buyout workbooks with IRR/MOIC in Excel.

Pptx Author

Build PowerPoint decks headless with python-pptx.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Use Scenarios (Pragmatic Framework: Planning → Use Scenarios)

Anatomy of a Problem Card

What vs. How — stay on the WHAT

Three considerations when articulating a problem

Interview the user (batch questions)

Artifact template

Deliver the artifact

Frequently asked questions

Related AI Skills

Set up your own AI workspace now