Agent skill

positioning-statement

Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/positioning-statement/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Purpose Create a Geoffrey Moore-style positioning statement that clearly articulates who your product serves, what need it addresses, how it's categorized, what benefit it delivers, and how it differs from alternatives. Use this when you need to align stakeholders on product strategy, guide messaging, or test if your value proposition is crisp and defensible. This is not a tagline or elevator pitch—it's a strategic clarity tool that forces you to make hard choices about target, need, and differentiation. ## Input **Works best with:** The product and its target customer. **Also useful:** The unmet need, product category, primary benefit, and nearest alternative — the skill drafts from what you give and asks only for what's missing. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks for product and target customer first, then works through the Moore template slots. **Example invocation:** `Positioning statement for LaunchDarkly-style feature flags aimed at platfo

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. The Geoffrey Moore Framework
  5. Why This Structure Works
  6. Anti-Patterns (What This Is NOT)
  7. When to Use This
  8. When NOT to Use This
  9. Application
  10. Step 1: Gather Context
  11. Step 2: Draft the Value Proposition
  12. Step 3: Draft the Differentiation Statement
  13. Step 4: Stress-Test the Positioning
  14. Step 5: Socialize and Iterate
Ships with 2 files
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the positioning-statement skill do?

Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going