positioning-mapper
Use when the user asks to "map our positioning", "name our competitive alternatives", or "pick a beachhead segment for the launch"; produces a Dunford-style positioning canvas — named competitive alternatives (including spreadsheet and status quo), unique attributes (verifiable, or routed to the claims ledger), value themes (attribute→benefit→value chains), a target beachhead segment scored on serviceability / pain intensity / reachability, and a one-sentence onlyness statement — the sole upstream of the message house and the entity-signal source for the canonical entity profile. Not for the m
npx skills add aaron-he-zhu/aaron-marketing-skills --skill positioning-mapper --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Positioning Mapper Builds the Dunford-style positioning canvas that the rest of the launch stands on — the named competitive alternatives users actually weigh (including spreadsheet, manual process, and "do nothing"), the unique attributes only this product has, the value themes those attributes ladder up to, the beachhead segment to win first, and the one-sentence onlyness statement. It is the first move of the RAMP **Research** phase and feeds two RAMP-`R` sub-items directly: *positioning canvas complete (named competitive alternatives, unique attributes, value themes)* and *ICP/beachhead segment defined and matched to launch scope* (see [ramp-benchmark.md](../../../references/ramp-benchmark.md)). Every downstream message — tagline, PR-FAQ, store listing — is a restatement of this canvas, which is why [message-house-builder](../../assemble/message-house-builder/SKILL.md) takes it as its only upstream and [entity-registry](../../../protocol/entity-registry/SKILL.md) reads it as the entity-signal source. **Scope guard**: this skill produces the positioning canvas *document* only. It does **not** write the message house, taglines, or per-channel copy (that is [message-house-builde
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the positioning-mapper skill do?
Use when the user asks to "map our positioning", "name our competitive alternatives", or "pick a beachhead segment for the launch"; produces a Dunford-style positioning canvas — named competitive alternatives (including spreadsheet and status quo), unique attributes (verifiable, or routed to the claims ledger), value themes (attribute→benefit→value chains), a target beachhead segment scored on serviceability / pain intensity / reachability, and a one-sentence onlyness statement — the sole upstream of the message house and the entity-signal source for the canonical entity profile. Not for the m
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill positioning-mapper --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 aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 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.