| name | positioning-mapper |
| slug | aaron-positioning-mapper |
| displayName | Positioning Mapper · 定位画布 |
| summary | 定位画布/竞争替代品/独特价值/滩头细分 |
| description | 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 message house or per-channel launch copy — use message-house-builder; not for audience/persona profiling itself — use audience-mapper; not for SEO keyword positioning — use keyword-research. 定位画布/竞争替代品/独特价值/滩头细分 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when defining launch positioning before any launch copy exists: naming the real competitive alternatives (including spreadsheet / manual process / status quo), isolating unique attributes, mapping value themes, choosing the beachhead segment, or writing the onlyness statement. The first move of the RAMP Research phase, the sole upstream of message-house-builder, and the entity-signal source for entity-registry. Not the message house itself and not persona research. |
| argument-hint | <product / offering> [known alternatives] [candidate segments] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"research","geo-relevance":"low","hermes":{"tags":["marketing","launch","research"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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). Every downstream message — tagline, PR-FAQ, store listing — is a restatement of this canvas, which is why message-house-builder takes it as its only upstream and entity-registry 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-builder), build audience/persona profiles (reuse audience-mapper), do SEO keyword positioning (keyword-research), adjudicate product or comparative claims (unverifiable ones are marked [needs source] and submitted to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py for the claims ledger), or compute the RAMP profile result (only the launch-readiness-auditor gate scores RAMP). It works one lever — positioning — and hands off.
Quick Start
Map the positioning for [product]. Users today solve this with [alternatives, if known]. Candidate segments: [list or "help me choose"].
Build a positioning canvas from these win-loss notes and user interviews: [paste]. Pick the beachhead.
Run the onlyness test on our current positioning: "[current one-liner]" — does it survive named alternatives?
Skill Contract
