Pm distinctive competence

Skill julianoczkowski/product-manager/skills/pm-distinctive-competence

A market-driven Product Manager copilot (Agent Skills + Claude Code plugin) based on the Pragmatic Framework — guides PMs from idea to launch and produces a client-ready artifact (Markdown or .docx) at every stage.

Install

npx -y skills add julianoczkowski/product-manager --skill pm-distinctive-competence

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.3 KB, as published. Nobody here has run it

Distinctive Competencies (Framework: Market → Distinctive Competencies)

Articulate and leverage the organization's unique abilities to deliver value to the market. These are the strengths you intersect with validated market problems to find opportunities that are ideal for you (see the market-problem test and the opportunity-scoring attributes in ../pm-copilot/references/framework.md).

The test — an attribute is a distinctive competency only if it is all three

Valued — the market actually cares about it (it maps to a real problem they'll pay to solve).
Different — materially different from competitors and alternatives, not table stakes.
Provable — you have proof (data, track record, patents, references), not just a claim.

Brainstorm broadly first (how you build, deliver, sell, and support), then filter hard. Most candidate strengths fail the "different" or "provable" test — that's expected.

Interview the user (batch questions)

Brainstorm: where does your organization deliver value across the whole lifecycle (build, deliver, sell, support, data, brand, relationships, IP)?
For each attribute — is it materially different from competitors and alternatives?
What's your proof it's both valued and different? (metrics, wins, patents, references)
Which market problems (from pm-market-problems) do these strengths let you solve better than anyone?

Artifact template

# Distinctive Competencies — <organization / product>

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

Brainstorm attributes where your organization delivers value, then test each:
*valued? · materially different? · provable?*

| Attribute | Valued? (Y/N) | Different? (Y/N) | Proof |
| :--- | :---: | :---: | :--- |
| <attribute> | Y | Y | <evidence> |
| <attribute> | Y | N | <why it fails — table stakes> |

## Articulate your Distinctive Competencies
Based on this assessment, the attributes that are valued **and** different **and**
provable are:

1. **Distinctive Competency:** <statement>
2. **Distinctive Competency:** <statement>
3. **Distinctive Competency:** <statement>

## How these map to market problems
| Distinctive Competency | Market problem it lets us win | Evidence |
| :-- | :-- | :-- |

Deliver the artifact

Follow ../pm-copilot/references/artifact-output.md: 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: score opportunities against these strengths in pm-opportunity-scoring, or set direction in pm-product-strategy.