/pestel-analysis
Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.
$ npx -y skills add getcrew44/crew44 --skill pestel-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pestel-analysis
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.
SKILL.md
pestel-analysis.SKILL.mdname: pestel-analysis
description: Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.
intent: >-
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.
type: component
Purpose
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.
This is not internal analysis—it's outward-facing assessment of the big-picture forces shaping your product's environment.
Key Concepts
The PESTEL Framework
Originating from Francis Joseph Aguilar's 1967 PEST analysis, PESTEL extends the framework to six categories:
1. **Political:** Government policies, stability, trade regulations, taxation 2. **Economic:** Growth rates, inflation, exchange rates, consumer spending 3. **Social:** Demographics, cultural trends, lifestyle changes, consumer attitudes 4. **Technological:** Advancements, R&D, automation, digital transformation 5. **Environmental:** Climate change, sustainability, resource scarcity, regulations 6. **Legal:** Compliance, IP rights, employment laws, health/safety regulations
Why This Works
- **Comprehensive:** Covers all major external forces affecting your product
- **Proactive:** Identifies threats and opportunities before they become critical
- **Strategic:** Informs long-term planning, not just tactical decisions
- **Risk management:** Highlights vulnerabilities in your product strategy
Anti-Patterns (What This Is NOT)
- **Not competitive analysis:** PESTEL looks at macro factors, not competitors
- **Not internal analysis:** Focuses on external environment, not your company's strengths/weaknesses
- **Not static:** Macro environment changes—reassess regularly
When to Use This
- Entering a new market or geography
- Strategic planning (annual roadmapping, 3-5 year planning)
- Assessing product viability in a changing environment
- Risk assessment for new product initiatives
- Pitching to execs or investors (shows environmental awareness)
When NOT to Use This
- For tactical, short-term decisions (use competitive analysis instead)
- When external factors are stable and well-understood
- As a substitute for customer research (PESTEL is macro, not micro)
---
Application
Use `template.md` for the full fill-in structure.
Step 1: Define the Scope
Clarify what you're analyzing:
## Overview
- **Project/Product Name:** [e.g., "AI-Powered Invoice Automation for SMBs"]
- **Analysis Purpose:** [e.g., "Assess viability of launching in EU market"]
- **Analyst:** [Your name or team]
- **Date:** [Date of analysis]
- **Geographic Scope:** [e.g., "United States and European Union"]
- **Time Horizon:** [e.g., "Next 12-24 months"]
**Quality checks:**
- **Specific:** Not "analyze market" but "assess viability of EU launch"
- **Time-bound:** PESTEL factors change—state your horizon
---
Step 2: Analyze Political Factors
Examine government and regulatory influences:
## 1. Political Factors
### Government Policies
- [How could government policies impact the product?]
- [Example: "EU's AI Act requires transparency in AI decision-making; our invoice automation must explain recommendations"]
### Political Stability
- [Assess stability in relevant regions]
- [Example: "US political stability is moderate; potential for regulatory changes in financial tech under new administration"]
### Trade Regulations
- [Examine trade regulations and their effects]
- [Example: "Brexit complicates data transfer between UK and EU; may require separate infrastructure"]
### Taxation Policy
- [Analyze taxation policies and implications]
- [Example: "Digital services tax in EU (3% on revenue) could impact pricing strategy"]
**Quality checks:**
- **Specific to your product:** Don't list generic policies—explain the impact
- **Actionable:** Can you adjust strategy based on this insight?
---
Step 3: Analyze Economic Factors
Examine economic conditions:
## 2. Economic Factors
### Economic Growth
- [Evaluate growth rates and their impact]
- [Example: "SMB sector growing 5% annually in US; strong demand for automation tools"]
### Inflation Rate
- [Consider inflation and its effect on pricing/costs]
- [Example: "High inflation (6%) pressures SMB budgets; price sensitivity increases"]
### Exchange Rates
- [Analyze exchange rate fluctuations]
- [Example: "Weak Euro vs. Dollar makes US pricing less competitive in EU; may need regional pricing"]
### Consumer Spending
- [Assess consumer spending levels]
- [Example: "SMBs cutting discretionary spending due to recession fears; emphasize ROI (time savings) in messaging"]
**Quality checks:**
- **Data-driven:** Use real economic indicators (GDP growth, inflation rates, etc.)
- **Product-specific:** How do these trends affect *your* product?
---
Step 4: Analyze Social Factors
Examine societal and cultural trends:
## 3. Social Factors
### Demographics
- [Examine demographics and market influence]
- [Example: "Aging SMB owners (Baby Boomers) less tech-savvy; younger Gen X/Millennial owners more receptive to automation"]
### Cultural Trends
- [Analyze cultural trends and demand impact]
- [Example: "Growing 'hustle culture' among freelancers increases demand for time-saving tools"]
#
Read more
name: pestel-analysis description: Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy. intent: >- Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control. type: component
Purpose
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.
This is not internal analysis—it's outward-facing assessment of the big-picture forces shaping your product's environment.
Key Concepts
The PESTEL Framework
Originating from Francis Joseph Aguilar's 1967 PEST analysis, PESTEL extends the framework to six categories:
1. **Political:** Government policies, stability, trade regulations, taxation 2. **Economic:** Growth rates, inflation, exchange rates, consumer spending 3. **Social:** Demographics, cultural trends, lifestyle changes, consumer attitudes 4. **Technological:** Advancements, R&D, automation, digital transformation 5. **Environmental:** Climate change, sustainability, resource scarcity, regulations 6. **Legal:** Compliance, IP rights, employment laws, health/safety regulations
Why This Works
- **Comprehensive:** Covers all major external forces affecting your product
- **Proactive:** Identifies threats and opportunities before they become critical
- **Strategic:** Informs long-term planning, not just tactical decisions
- **Risk management:** Highlights vulnerabilities in your product strategy
Anti-Patterns (What This Is NOT)
- **Not competitive analysis:** PESTEL looks at macro factors, not competitors
- **Not internal analysis:** Focuses on external environment, not your company's strengths/weaknesses
- **Not static:** Macro environment changes—reassess regularly
When to Use This
- Entering a new market or geography
- Strategic planning (annual roadmapping, 3-5 year planning)
- Assessing product viability in a changing environment
- Risk assessment for new product initiatives
- Pitching to execs or investors (shows environmental awareness)
When NOT to Use This
- For tactical, short-term decisions (use competitive analysis instead)
- When external factors are stable and well-understood
- As a substitute for customer research (PESTEL is macro, not micro)
---
Application
Use `template.md` for the full fill-in structure.
Step 1: Define the Scope
Clarify what you're analyzing:
## Overview - **Project/Product Name:** [e.g., "AI-Powered Invoice Automation for SMBs"] - **Analysis Purpose:** [e.g., "Assess viability of launching in EU market"] - **Analyst:** [Your name or team] - **Date:** [Date of analysis] - **Geographic Scope:** [e.g., "United States and European Union"] - **Time Horizon:** [e.g., "Next 12-24 months"]
**Quality checks:**
- **Specific:** Not "analyze market" but "assess viability of EU launch"
- **Time-bound:** PESTEL factors change—state your horizon
---
Step 2: Analyze Political Factors
Examine government and regulatory influences:
## 1. Political Factors ### Government Policies - [How could government policies impact the product?] - [Example: "EU's AI Act requires transparency in AI decision-making; our invoice automation must explain recommendations"] ### Political Stability - [Assess stability in relevant regions] - [Example: "US political stability is moderate; potential for regulatory changes in financial tech under new administration"] ### Trade Regulations - [Examine trade regulations and their effects] - [Example: "Brexit complicates data transfer between UK and EU; may require separate infrastructure"] ### Taxation Policy - [Analyze taxation policies and implications] - [Example: "Digital services tax in EU (3% on revenue) could impact pricing strategy"]
**Quality checks:**
- **Specific to your product:** Don't list generic policies—explain the impact
- **Actionable:** Can you adjust strategy based on this insight?
---
Step 3: Analyze Economic Factors
Examine economic conditions:
## 2. Economic Factors ### Economic Growth - [Evaluate growth rates and their impact] - [Example: "SMB sector growing 5% annually in US; strong demand for automation tools"] ### Inflation Rate - [Consider inflation and its effect on pricing/costs] - [Example: "High inflation (6%) pressures SMB budgets; price sensitivity increases"] ### Exchange Rates - [Analyze exchange rate fluctuations] - [Example: "Weak Euro vs. Dollar makes US pricing less competitive in EU; may need regional pricing"] ### Consumer Spending - [Assess consumer spending levels] - [Example: "SMBs cutting discretionary spending due to recession fears; emphasize ROI (time savings) in messaging"]
**Quality checks:**
- **Data-driven:** Use real economic indicators (GDP growth, inflation rates, etc.)
- **Product-specific:** How do these trends affect *your* product?
---
Step 4: Analyze Social Factors
Examine societal and cultural trends:
## 3. Social Factors ### Demographics - [Examine demographics and market influence] - [Example: "Aging SMB owners (Baby Boomers) less tech-savvy; younger Gen X/Millennial owners more receptive to automation"] ### Cultural Trends - [Analyze cultural trends and demand impact] - [Example: "Growing 'hustle culture' among freelancers increases demand for time-saving tools"] #
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
Other skills on crew44.
- /brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Open skill - /executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Open skill - /finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Open skill - /receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Open skill - /requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Open skill - /systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Open skill

