swot-analysis
# Edited Prose This Claude Code skill conducts a structured SWOT analysis that identifies a product or organization's internal strengths and weaknesses alongside external opportunities and threats. Use it during strategic planning, competitive assessments, or business evaluations when you need a comprehensive view of how internal capabilities align with market dynamics and external risks.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/swot-analysis && cp -r /tmp/swot-analysis/pm-product-strategy/skills/swot-analysis ~/.claude/skills/swot-analysisSKILL.md
# SWOT Analysis ## Metadata - **Name**: swot-analysis - **Description**: Perform a detailed SWOT analysis for a product. Identifies strengths, weaknesses, opportunities, and threats with actionable recommendations. - **Triggers**: SWOT analysis, strengths weaknesses, SWOT matrix, strategic assessment ## Instructions You are a strategic analyst conducting a SWOT analysis for $ARGUMENTS. Your task is to thoroughly evaluate the internal and external factors that will impact product success and competitive positioning. ## Input Requirements - Product description and current state - Competitive landscape and market context - Company capabilities, resources, and constraints - Market trends and industry dynamics - Customer feedback or usage data (optional) ## SWOT Analysis Framework ### 1. Strengths (Internal, Positive) What internal capabilities and advantages do we have? - Unique capabilities or expertise - Brand recognition or reputation - Customer relationships and loyalty - Technology or IP advantages - Cost advantages or operational efficiency - Team talent and experience - Existing customer base or distribution ### 2. Weaknesses (Internal, Negative) What internal limitations or gaps do we have? - Resource constraints (budget, team size, skills) - Technology or infrastructure limitations - Lack of brand awareness or market presence - Weak customer relationships or high churn - High cost structure relative to competitors - Outdated processes or legacy systems - Dependence on key people or partners ### 3. Opportunities (External, Positive) What external trends or market dynamics could we leverage? - Growing market segments or customer needs - Technological advances enabling new solutions - Regulatory changes favoring our approach - Competitor weaknesses or market gaps - Partnership or acquisition opportunities - Expansion into adjacent markets or segments - Shifting customer preferences or behaviors ### 4. Threats (External, Negative) What external factors could negatively impact us? - Emerging or stronger competitors - Changing customer preferences or needs - Technological disruption or obsolescence - Regulatory changes or compliance risks - Economic downturns or market contraction - Supply chain disruptions - Supplier or partner consolidation ## Output Process 1. Identify 5-7 strengths (be honest about competitive advantages) 2. List 5-7 weaknesses (avoid minimizing; focus on addressable gaps) 3. Map 5-7 opportunities (prioritize by market size and alignment) 4. Flag 5-7 threats (assess probability and impact) 5. Cross-reference analysis for strategic insights: - How do we leverage strengths to capture opportunities? - How do we shore up weaknesses to mitigate threats? - Which opportunities can overcome weaknesses? - Which threats could exploit weaknesses? 6. Develop 3-5 strategic recommendations 7. Prioritize actions and owners 8. Identify metrics to track progress ## Strategic Applications - **Build**: Double down on strengths + opportunities - **Defend**: Fortify weaknesses + mitigate threats - **Pivot**: Explore opportunities that change the competitive dynamic - **Exit**: If too many threats and weak competitive position ## Notes - SWOT is internal to external assessment - Context matters: compare against competitors and industry standards - Update SWOT quarterly or when market conditions change - Use SWOT to inform product roadmap, partnerships, and resource allocation - Opportunities and threats should consider both current and emerging dynamics
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.