positioning-statement — Claude Code skill: what it does and setup
Drafts a Geoffrey Moore positioning framework for your product. Helps pinpoint target buyers and sharp competitive differentiation.
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a claude-codeWhat positioning-statement does
This skill applies Geoffrey Moore's classic framework from Crossing the Chasm directly inside your coding assistant. It constructs two core blocks: the value proposition and the differentiation clause. You supply the product name and target audience. From there, the assistant prompts for the unresolved customer pain and tangible outcomes.
The workflow forces a focus on buyer results instead of raw feature lists. Next, it contrasts the offering with a genuine rival or default behavior like spreadsheets. A built-in stress test audits whether buyers recognize their pain and if rivals could replicate the advantage within six months. The entire exercise takes 10 to 15 minutes.
This framework fails completely on captive internal tools because it is designed strictly for competitive commercial markets. It also cannot compensate for skipped customer discovery interviews. You need verified user research before running the prompts.
What it helps with
- Define market positioning for a new product launch
- Sharpen messaging against specific commercial rivals
- Align stakeholders on customer pain and product category
- Stress-test value claims before drafting a PRD
Example prompts for the agent
- positioning-statement for a B2B SaaS tool targeting mid-market HR departments
- Draft a positioning statement for our automated feature flagging service aimed at platform leads
- Help sharpen our positioning against manual spreadsheets by focusing on team efficiency
How to install positioning-statement
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a claude-code2Manually: put the files in place
~/.claude/skills/positioning-statement/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/positioning-statement/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a codex2Manually: put the files in place
.agents/skills/positioning-statement/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a cursor2Manually: put the files in place
.cursor/skills/positioning-statement/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills positioning-statement2Manually: put the files in place
.github/skills/positioning-statement/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/positioning-statementManually: put the files in place
.devin/skills/positioning-statement/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about positioning-statement
How to install positioning-statement in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill positioning-statement -a claude-code. The tool downloads the skill definition directly into your local agent configuration.
What does positioning-statement do?
It guides you through drafting a structured statement based on Geoffrey Moore's model. It defines target users, needs, product categories, and concrete advantages over existing alternatives.
When should you avoid using this skill?
Skip it when building captive internal software or during early problem exploration before conducting customer interviews. The template synthesizes market evidence rather than inventing it.
