← LMTYCONTENT HISTORY

Update to LMTY

Snapshot Oct 24, 2026 · 13:40 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save LMTY and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Develop, pressure-test, or refresh product positioning against the alternatives customers actually consider. Use when defining a market position, revising positioning after competitor or category changes, preparing a positioning brief, clarifying differentiation, or testing whether current messaging still reflects customer value and the competitive landscape.",
  "included_files": [
    {
      "relative_path": "assets/positioning-brief-template.md",
      "size_in_bytes": 1102
    },
    {
      "relative_path": "references/CONTEXT.md",
      "size_in_bytes": 5344
    },
    {
      "relative_path": "references/DEGRADATION.md",
      "size_in_bytes": 4328
    },
    {
      "relative_path": "references/INTERNAL.md",
      "size_in_bytes": 4866
    },
    {
      "relative_path": "references/LMTY.md",
      "size_in_bytes": 5871
    },
    {
      "relative_path": "references/METHODOLOGY.md",
      "size_in_bytes": 2563
    },
    {
      "relative_path": "references/QUALITY.md",
      "size_in_bytes": 2640
    },
    {
      "relative_path": "references/TRUST.md",
      "size_in_bytes": 7363
    }
  ],
  "name": "competitive-positioning",
  "skill_md_contents": "---\nname: competitive-positioning\ndescription: Develop, pressure-test, or refresh product positioning against the alternatives customers actually consider. Use when defining a market position, revising positioning after competitor or category changes, preparing a positioning brief, clarifying differentiation, or testing whether current messaging still reflects customer value and the competitive landscape.\nlicense: MIT\nmetadata:\n  author: LMTY\n  com.lmty.category: ci\n---\n\n# Competitive Positioning\n\n## Mission\n\nHelp a PMM establish a credible, useful competitive position grounded in customer progress, real alternatives, current market behavior, and company strengths.\n\nThe skill should create the context that makes messaging easier. It should not jump straight to taglines.\n\n## Use this skill when\n\n- defining or refreshing product positioning\n- a competitor or category change may have weakened the current position\n- the team struggles to explain why customers should choose the product\n- a new segment, product, or GTM motion needs a position\n- messaging feels generic or increasingly similar to competitors\n- leadership asks how the company should be framed relative to alternatives\n- a launch or pricing change creates a positioning question\n\n## Do not use this skill when\n\n- the user only wants a competitor profile. Use `competitive-deep-dive`.\n- the user wants finished campaign copy without first needing positioning analysis.\n- the main question is a pricing decision. Use `competitive-pricing-packaging-review`.\n- the question is about a specific upcoming launch or release, including whether a capability is parity, catch-up, or real differentiation. Use `competitive-launch-readiness`.\n- the task is a one-off sales response. Use `competitive-battlecard`.\n- the position is settled and the question is whether the current copy or message hierarchy still carries it. Use `competitive-messaging-audit`.\n- the question is why deals are being won or lost, from deal evidence. Use `competitive-win-loss-analysis`, and bring its findings here.\n\n## Required outcome\n\nProduce a positioning brief that answers:\n\n1. What alternatives do customers use or consider?\n2. Which customers care most about the value we can uniquely deliver?\n3. What attributes or capabilities are meaningfully different?\n4. Why do those differences matter to the customer?\n5. What category or frame makes those differences easiest to understand?\n6. What has changed in the market that affects the position?\n7. What claims are credible, ownable, and defensible enough to repeat?\n8. Where is the current position vulnerable or unsupported?\n\n## Context acquisition\n\nRead `references/CONTEXT.md`. If call, CRM, win/loss or company-knowledge sources are connected, read `references/INTERNAL.md` before using them.\n\nMinimum useful context:\n- product or offer\n- target customer or segment\n- current positioning or website copy if it exists\n\nStrongly preferred:\n- LMTY competitor set, report, and relevant changes\n- win/loss or customer interviews\n- sales calls and objection themes\n- current strategy and GTM motion\n- pricing and packaging\n- product strengths and proof\n- category and adjacent alternatives\n\nDo not treat the tracked competitor set as the complete alternative set. Customers may compare against manual work, adjacent products, internal builds, services, or doing nothing.\n\n## Source priority for this job\n\n1. customer and win/loss evidence for what matters and what alternatives are considered\n2. product truth for what the home product can actually deliver\n3. LMTY for current competitor state and changes over time\n4. competitor primary sources for their claims and offer\n5. company strategy and target segment\n6. reviews, community, analysts, and third-party evidence for perception\n\n## Workflow\n\n### Step 1 - Frame the customer's progress\n\nDefine the functional, emotional, and social jobs when evidence supports them.\n\nIdentify:\n- situation or trigger\n- current struggle\n- desired progress\n- consequences of staying with the current alternative\n\nAvoid demographic positioning without causal relevance.\n\n### Step 2 - Identify competitive alternatives\n\nList what customers would do if this product did not exist.\n\nSeparate:\n- direct competitors\n- adjacent alternatives\n- internal or manual approaches\n- status quo or no decision\n\nRank by actual customer/deal relevance, not market fame.\n\n### Step 3 - Map the current market\n\nFor the alternatives that matter, establish:\n- target customer\n- core promise\n- key capabilities\n- pricing/packaging if material\n- proof and trust signals\n- recent positioning or product changes\n\nUse LMTY history to distinguish a durable position from a recent messaging experiment when possible.\n\n### Step 4 - Identify unique attributes\n\nFind attributes the home product has that relevant alternatives do not share, or executes in a meaningfully different way.\n\nUse these differentiation lenses where useful:\n- feature/capability\n- pricing/packaging\n- market segment\n- technology with a user-visible consequence\n- channel/distribution\n- customer experience\n\nDo not label an attribute unique until the evidence supports it.\n\n### Step 5 - Translate attributes into value themes\n\nFor each candidate attribute ask:\n- who cares?\n- in what situation?\n- what outcome changes?\n- what proof exists?\n- how easy is this for a competitor to copy?\n\nDiscard differences that do not matter to the target customer.\n\n### Step 6 - Choose the market frame\n\nDecide which context helps the customer understand the value fastest.\n\nTest whether the position is primarily:\n- market capture in an understood category\n- a focused subcategory or segment position\n- market creation that requires problem education or reframing\n\nDo not create a new category merely to sound unique.\n\n### Step 7 - Map switching forces\n\nFor the target customer, document:\n- push away from the current situation\n- pull toward the new solution\n- anxiety about adopting it\n- habit or switching cost holding them back\n\nUse this to reveal which parts of the position need proof, not just stronger copy.\n\n### Step 8 - Draft the positioning core\n\nProduce:\n- target customer\n- competitive alternatives\n- differentiated attributes\n- value themes\n- market/category frame\n- reasons to believe\n- positioning statement for internal use\n- messaging implications, not full campaign copy unless requested\n\n### Step 9 - Pressure-test against recent change\n\nUse relevant LMTY changes or current research to ask:\n- did a competitor move into our claimed territory?\n- did a new alternative change the evaluation set?\n- did pricing/packaging alter how value is perceived?\n- did our own product change enough to make old positioning stale?\n\n### Step 10 - Hand off what you do not own\n\nRequests routinely arrive as two questions joined by \"and\". Answer the one this skill owns, in full. For the rest, name the skill that owns it and stop there.\n\nThis is not a refusal and it is not a disclaimer at the bottom. Write it as a line the reader can act on:\n\n> **Pricing** - the position depends on a packaging change we have not decided. That is a separate decision: run `competitive-pricing-packaging-review` with this analysis as input.\n\nOne line per area the work touched, named explicitly:\n\n| The request also wants | Say to run |\n| --- | --- |\n| field talk tracks, objection handling, or a rep-facing card | `competitive-battlecard` |\n| a full profile of one competitor | `competitive-deep-dive` |\n| a decision-oriented version for leadership | `competitive-executive-market-brief` |\n| launch framing, claims, or enablement for a release | `competitive-launch-readiness` |\n| a recurring digest of what changed | `competitive-market-briefing` |\n| whether a pattern is a real shift or noise | `competitive-market-shift-analysis` |\n| a pricing or packaging decision | `competitive-pricing-packaging-review` |\n\nThe failure this prevents is quietly answering the other half yourself. It looks helpful, and it produces a recommendation built on this skill's evidence alone, without the context the other decision actually needs.\n\n### Step 11 - Produce the artifact\n\nUse `assets/positioning-brief-template.md`.\n\n## Evidence and reasoning rules\n\nRead `references/TRUST.md`.\n\nEspecially for positioning:\n- competitor marketing copy proves what they claim, not what customers believe\n- a customer quote proves one customer's perception unless repeated evidence exists\n- \"best\", \"only\", and category leadership claims require strong evidence\n- a technological difference matters only if it changes a customer-relevant outcome\n- do not hide where a competitor is stronger\n\n## Graceful fallback\n\nRead `references/DEGRADATION.md`. For what LMTY can and cannot do, read `references/LMTY.md`.\n\nWithout LMTY:\n- use current primary-source research for the alternatives that matter\n- state that historical movement and persistence of positioning claims may be unknown\n\nWithout customer evidence:\n- produce a market-grounded positioning hypothesis\n- clearly mark customer-value assumptions that need validation\n\nWithout product strategy context:\n- avoid prescriptive segment or category decisions\n\n## Composition\n\nEach companion below owns a decision this skill should not make on its own evidence. The hand-off step is where the request's own follow-on question gets named.\n\nCommon companions:\n- `competitive-deep-dive`\n- `competitive-market-shift-analysis`\n- `competitive-pricing-packaging-review`\n- `competitive-launch-readiness`\n- `competitive-battlecard`\n- `competitive-executive-market-brief`\n\n## Quality bar\n\nRead `references/QUALITY.md`.\n\nA strong result should make it obvious:\n- who the product is for\n- what it replaces or competes with\n- why the difference matters\n- what proof makes the story believable\n- how recent market movement affects the position\n\n## Examples of activating requests\n\n- \"Help me position this product against the alternatives customers actually use.\"\n- \"Our competitors all sound like us now. Pressure-test our positioning.\"\n- \"Has the market moved enough that we should change our position?\"\n- \"Build a positioning brief using our customer calls and LMTY data.\"\n- \"What is our strongest defensible position for enterprise buyers?\"\n\n## References\n\n- `references/METHODOLOGY.md`\n- `references/LMTY.md`\n- `references/TRUST.md`\n- `references/CONTEXT.md`\n- `references/DEGRADATION.md`\n- `references/INTERNAL.md`\n- `references/QUALITY.md`\n"
}

SHA-256 of public snapshot: b6af36cb94911108e7ffc76fff89db8bcb394a518ff87c3759a3717812381bfb