pestle-analysis
# ClaudeWave Entry: pestle-analysis The pestle-analysis skill conducts structured evaluations of Political, Economic, Social, Technological, Legal, and Environmental factors affecting a business or market. Use this when developing strategy, assessing market entry viability, analyzing competitive landscapes, or identifying external risks and opportunities that could impact product positioning or business operations.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/pestle-analysis && cp -r /tmp/pestle-analysis/pm-product-strategy/skills/pestle-analysis ~/.claude/skills/pestle-analysisSKILL.md
# PESTLE Analysis ## Metadata - **Name**: pestle-analysis - **Description**: Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing macro-environment, evaluating market entry risks, or doing strategic planning. - **Triggers**: PESTLE analysis, macro environment, market environment, external factors analysis ## Instructions You are a strategic analyst conducting a PESTLE analysis for $ARGUMENTS. Your task is to evaluate the macro-environmental factors that could impact product strategy, market entry, or business viability. ## Input Requirements - Industry and market context - Geographic market or region(s) - Product or business type - Current strategic challenges or questions - Any known regulatory or market changes ## PESTLE Analysis Framework ### 1. Political What government policies, regulations, and political stability affect the business? - Government policies and incentives - Tax regulations and tariffs - Political stability and risk - Government spending and subsidies - Trade agreements and regulations - Licensing and permits required - Government relationships and lobbying needs ### 2. Economic What economic conditions and financial factors matter? - Economic growth and GDP trends - Interest rates and inflation - Currency exchange rates - Consumer spending and confidence - Employment and labor costs - Disposable income trends - Access to financing and capital ### 3. Social What demographic and cultural trends shape the market? - Population demographics and trends - Cultural attitudes and values - Consumer lifestyle and behaviors - Education and skills availability - Health and wellness trends - Social media and digital adoption - Diversity and inclusion preferences ### 4. Technological What technological advances or disruptions are relevant? - Emerging technologies (AI, blockchain, cloud, etc.) - Digital transformation trends - Cybersecurity and data privacy requirements - Automation and robotics - Internet of Things (IoT) and connectivity - Research and development capabilities - Technology adoption rates and digital literacy ### 5. Legal What laws, regulations, and compliance requirements apply? - Data protection and privacy laws (GDPR, CCPA, etc.) - Employment and labor laws - Intellectual property and patent laws - Consumer protection laws - Industry-specific regulations - Compliance costs and audit requirements - Liability and insurance requirements ### 6. Environmental What environmental, climate, and sustainability factors exist? - Climate change and environmental regulations - Carbon emissions and sustainability requirements - Natural resource availability and scarcity - Waste management and circular economy trends - Renewable energy adoption - ESG (Environmental, Social, Governance) expectations - Green certification and eco-friendly standards ## Output Process 1. For each PESTLE category, identify 3-5 relevant factors 2. Assess impact on product/business (High, Medium, Low) 3. Assess probability or likelihood (High, Medium, Low) 4. Prioritize factors by impact x probability 5. Develop strategic responses: - Which factors are opportunities to leverage? - Which factors are threats to mitigate or avoid? - Which factors require compliance or adaptation? 6. Identify key metrics or leading indicators to monitor 7. Build contingency plans for high-impact factors 8. Document assumptions and unknowns requiring research ## Strategic Applications - Market entry assessment: Is this market viable to enter? - Risk assessment: What macro risks could derail our strategy? - Opportunity identification: What external shifts create new possibilities? - Scenario planning: How would strategy change under different conditions? - Regulatory roadmap: What compliance needs must we plan for? ## Notes - PESTLE is complementary to SWOT (macro vs. micro analysis) - Some factors span multiple categories (e.g., regulations affect legal, political, and economic) - Geographic and industry context matter significantly - Trends evolve; re-assess PESTLE annually or when markets shift - Use PESTLE early in strategy development to avoid blind spots --- ### Further Reading - [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
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.