MCPInstall

pm-positioning

Create a Pragmatic Institute Positioning Document — describe a product by the market problems it solves (not features), for one persona in one segment. Use when the PM asks for positioning, messaging, "how do we describe/pitch this", an internal positioning doc, or a positioning statement. Produces a Positioning Document plus a Problem-Oriented Capabilities (POC) worksheet as a Markdown or Word .docx artifact.

Installs
40
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/julianoczkowski/product-manager --skill pm-positioning
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads pm-positioning automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Positioning Document (Pragmatic Framework: Planning → Positioning)

Rule: Positioning focuses on the problems you solve, not features. Create a separate positioning document for every persona whose problems differ. Write problems in the persona's first-person voice. This is an internal document (an "internal press release") used to gain buy-in, brief design/engineering, and hand off to marketing to build external messaging. See the primitives in ../pm-copilot/references/framework.md.

Prepare

Ideally a team of 3–6 people with market knowledge, staying objective. Start with one product and one persona/segment. If personas or market problems aren't defined yet, run pm-personas and pm-market-problems first (or gather them inline).

Interview the user for inputs (batch questions)

  1. Product and the one persona + market segment this doc is for.
  2. The problem — why does this persona care? What's painful today? (Be empathetic; use their words.)
  3. The ideal solution from the persona's point of view — clear and specific.
  4. Evidence the problem is real (interviews, win/loss, support tickets, surveys).
  5. What the product does — enough to map features to capabilities.

Build it in three steps (per the Pragmatic method)

Step 1 — Draft the first four sections of the document:

  • Problem — "There is a problem in the industry today…" (persona's first person).
  • Solution — "The ideal solution to this problem is…" (clear, specific).
  • Positioning Statement — the "billboard," ≤25 words, using the formula:

    For [persona], [product] [verb] [problem] by [verb] [primary benefit].

  • Product Description — overview, ≤50 words.

Step 2 — Problem-Oriented Capabilities (POC) worksheet. List every problem the product solves for this persona (first person) → group similar problems and condense to 3–5 problem groups → name the problem-oriented capability for each group → map product features to each capability. Table: Market Problems | Problem-Oriented Capabilities | Product Features.

Step 3 — Finish the document by listing the 3–5 problem-oriented capabilities.

Artifact templates

Positioning Document

# Positioning Document — <Product Name>

**Product Name:** <name>
**Persona & Market Segment:** <persona> / <segment>
**Company:** <company>  ·  **Feature / Product:** <name>
**Author:** <author>  ·  **Date created:** <date>  ·  **Version:** 1.0
*Internal document — describes the product by the problems it solves.*

## Problem
There is a problem in the industry today: <persona's first-person description of the pain, with evidence>.

## Solution
The ideal solution to this problem is <clear, specific solution from the persona's point of view>.

## Positioning Statement
> For <persona>, <product> <verb> <problem> by <verb> <primary benefit>.
<!-- ≤25 words -->

## Product Description
<≤50-word overview of the product.>

## Problem-Oriented Capabilities
1. <Capability> — <benefit>
2. <Capability> — <benefit>
3. <Capability> — <benefit>
4. <Capability> — <benefit>
5. <Capability> — <benefit>

## Evidence & open questions
- <evidence sources / interview counts>
- > TODO: <anything unproven, flagged as an assumption>

Problem-Oriented Capabilities worksheet

# Problem-Oriented Capabilities — <Product> / <Persona>

| Market Problems (persona's first person) | Problem-Oriented Capability | Product Features |
| :--- | :--- | :--- |
| "I can't …" | <Capability> | <feature>, <feature> |
| "It takes too long to …" | <Capability> | <feature> |

Worked reference (from Pragmatic's example)

For Robin the product manager, Product Minder reduces the frustration of managing ideas and requirements from everywhere by integrating all product information into a single system. Capabilities: Instant Requirements, Idea Store, Auto Feedback, Trace Link, Status View.

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. Deliver both the Positioning Document and the POC worksheet. Then offer the next stage: turning these problems into prioritized pm-requirements.

FAQ

What does the pm-positioning skill do?

Create a Pragmatic Institute Positioning Document — describe a product by the market problems it solves (not features), for one persona in one segment. Use when the PM asks for positioning, messaging, "how do we describe/pitch this", an internal positioning doc, or a positioning statement. Produces a Positioning Document plus a Problem-Oriented Capabilities (POC) worksheet as a Markdown or Word .docx artifact.

How do I install pm-positioning?

Run npx skills add https://github.com/julianoczkowski/product-manager --skill pm-positioning in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pm-positioning/ (personal) or .claude/skills/pm-positioning/ (project).

Which AI agents can use pm-positioning?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is pm-positioning safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains pm-positioning?

It is published by julianoczkowski in julianoczkowski/product-manager. It has 40 recorded installs.

More from julianoczkowski/product-manager

View all →

pm-copilot

julianoczkowski/product-manager

Product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Use this as the entry point whenever a product manager wants to work through building a product or feature the market-driven way — e.g. "I want to build a feature", "help me plan this product", "where do I start", "I have an idea for X". It figures out where the PM is in the Pragmatic journey, guides them through the right stages (market research, personas, positioning, strategy, requirements, roadmap, launch), and produces a client-ready artifact (Markdown or Word .docx) at every stage. Also use it to explain the Pragmatic Framework or choose which PM artifact to create.

Docs & Writing41 installs

pm-market-problems

julianoczkowski/product-manager

Run Pragmatic Institute market discovery and validate real market problems before anything gets built. Use when a PM says "I want to build a feature", "do market research", "talk to customers", "discovery", "validate this idea", "is this problem real", "NIHITO", or "who should I interview". Enforces the outside-in rule: build only for problems that are urgent, pervasive, and that the market will pay to solve. Produces a Market Discovery Document and a Market Problems Table as a Markdown or Word .docx artifact.

Docs & Writing41 installs

pm-opportunity-scoring

julianoczkowski/product-manager

Score and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare options objectively instead of by opinion. Produces an Opportunity Scorecard as a Markdown or Word .docx artifact.

Docs & Writing41 installs

pm-product-strategy

julianoczkowski/product-manager

Build a Pragmatic Institute Strategy Matrix — a forced-choice 4×4 that decides who to win and what to build over a set time frame, and surfaces alignment between the product team and leadership. Use when the PM asks about product strategy, "where should we invest", "what should we build for whom", focus, prioritizing markets, or avoiding a spread-too-thin roadmap. Produces a Strategy Matrix as a Markdown or Word .docx artifact.

Docs & Writing40 installs

pm-distinctive-competence

julianoczkowski/product-manager

Articulate your organization's Distinctive Competencies the Pragmatic Institute way — the unique abilities to deliver value that are valued, different, and provable. Use when a PM says "what makes us different", "our moat", "unique strengths", "why us", "competitive advantage", or "distinctive competence". Strategy = intersect market problems with what only you can do. Produces a Distinctive Competencies worksheet as a Markdown or Word .docx artifact.

Docs & Writing40 installs

pm-requirements

julianoczkowski/product-manager

Write market-driven, prioritized product requirements (a Market Requirements Document / MRD) the Pragmatic Institute way. Use when the PM asks for "requirements", "an MRD", "what should we build", "prioritize features", "market requirements", or wants development to stop saying "requirements aren't specific enough". Articulates each requirement as a persona's problem, prioritizes with Market Evidence × Impact, and groups them for delivery. Produces a Market Requirements Document as a Markdown or Word .docx artifact.

Docs & Writing40 installs

Popular docs & writing skills

View category →

grill-with-docs

mattpocock/skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Docs & Writing1.2M installs

lark-markdown

open.feishu.cn

飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。

Docs & Writing778.7K installs

writing-beats

mattpocock/skills

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Docs & Writing490.7K installs

writing-shape

mattpocock/skills

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Docs & Writing490.2K installs

writing-fragments

mattpocock/skills

Writing, explore: mine raw fragments, no structure yet.

Docs & Writing489.6K installs

writing-for-agents

mattpocock/skills

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Docs & Writing479.3K installs