positioning-ideas
This Claude Code skill analyzes competitive positioning landscapes and generates differentiated positioning statements for products. It identifies top competitors, maps their positioning angles and target audiences, then brainstorms five unique positioning ideas with supporting rationale, messaging, and competitive advantages. Use this when developing product positioning strategy, creating brand differentiation, identifying market gaps, or crafting positioning statements that resonate with target audiences while claiming unclaimed market territory.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/positioning-ideas && cp -r /tmp/positioning-ideas/pm-marketing-growth/skills/positioning-ideas ~/.claude/skills/positioning-ideasSKILL.md
# Positioning Ideas Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with strategic rationale. Use when developing product positioning, differentiating from competitors, or crafting brand positioning strategy. ## When to Use - Developing product positioning strategy - Differentiating from competitors - Crafting brand positioning statements - Identifying market positioning gaps - Triggers: positioning, brand positioning, differentiation, how to position, positioning statement ## Prompt You are an experienced brand strategist with expertise in competitive positioning, market differentiation, and brand strategy. Given the following product and market context: $ARGUMENTS Follow these steps: **Step 1: Competitive Landscape Analysis** Identify and briefly describe the top 5 competitors in this market. For each, note: - Their primary positioning angle - Their target audience focus - Key differentiators they emphasize - Potential positioning gaps they leave open **Step 2: Positioning Brainstorm** Generate 5 unique positioning ideas for this product that target the specified market segment. Each positioning idea should: - Be clearly differentiated from competitor positioning - Resonate with the target audience's values and needs - Emphasize specific capabilities that competitors downplay or ignore - Open an unclaimed market territory **Step 3: Positioning Statements** For each idea, provide: 1. **Positioning Statement**: A one-sentence statement that captures the core positioning (e.g., "The [product] is the only [category] designed for [target segment] who want to [primary benefit]") 2. **Strategic Rationale**: Explain why this positioning would resonate with the audience and create differentiation 3. **Supporting Message**: Key supporting messages that reinforce this positioning 4. **Competitive Advantage**: What specific advantages enable this positioning claim ## Tips for Best Results - Provide detailed target audience profiles and their pain points - Share your product's unique capabilities and differentiators - Mention current positioning (if any) and what's working or not working - Include information about competitor positioning and messaging - Describe what market segment or niche you want to own - Share your long-term vision and business strategy --- ### Further Reading - [Product Management vs. Product Marketing vs. Product Growth 101](https://www.productcompass.pm/p/product-management-vs-product-marketing) - [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.