Individual skill

positioning-statement

Use when defining or sharpening what a product IS before writing copy or planning a launch. Triggers on "how do I position this", "what category are we in", "who is this really for", "positioning statement", "we sound like everyone else", "nobody gets what we do", "frame the product", "April Dunford positioning". Runs competitive alternatives → unique attributes → the value they enable → best-fit segment → market frame, producing one tight defensible paragraph. Do NOT use for the actual page/headline wording - use [[messaging-hierarchy]] instead; for price points - use [[pricing-strategy]] or [[saas-pricing]].

skills/positioning-statement/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Positioning Statement

Positioning is the context you set so a buyer instantly understands what you are,
why you are different, and why they should care. Get it wrong and every downstream
asset - the headline, the deck, the launch - is fluent nonsense written about the
wrong product for the wrong person. This is the first GTM step. Everything else
([[messaging-hierarchy]], [[launch-plan-sequencer]], [[launch-day-runbook]],
[[plg-motion-designer]], [[sales-enablement-kit]]) is calibrated to its output, so do
it first and do it honestly.

The trap is positioning from ambition - the category you wish you led, the buyer
you wish you had. Position from evidence instead: the alternatives real customers
weigh, the attributes you actually have, and the segment that already loves you.
This follows April Dunford's method (*Obviously Awesome*): build positioning bottom-up