pest-analysis
Guides PEST (Political, Economic, Social, Technological) analysis for strategic planning. Use when analyzing external macro-environmental factors or evaluating business decisions.
Best use case
pest-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guides PEST (Political, Economic, Social, Technological) analysis for strategic planning. Use when analyzing external macro-environmental factors or evaluating business decisions.
Teams using pest-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pest-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pest-analysis Compares
| Feature / Agent | pest-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guides PEST (Political, Economic, Social, Technological) analysis for strategic planning. Use when analyzing external macro-environmental factors or evaluating business decisions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# PEST Analysis for Strategic Planning
A strategic framework that examines four key external factors affecting an organization:
- **Political** (government policies, regulations, tax laws)
- **Economic** (inflation, interest rates, market conditions)
- **Social** (demographics, cultural trends, lifestyle changes)
- **Technological** (innovation, automation, digital transformation)
> 💡 **Note:** Often expanded to PESTLE (adding Legal and Environmental) for comprehensive analysis.
## When to Use
- Market entry decisions
- Product development planning
- Business direction/strategy changes
- Annual strategic reviews
- Competitive positioning analysis
## Initial Questions (Ask Before Starting)
Before creating the PEST analysis, ask 1-3 of these questions to ensure relevance:
1. **What specific decision will this analysis inform?** (e.g., entering a new market, launching a product, pivoting strategy)
2. **What industry/sector and geographic scope should we focus on?** (e.g., SaaS in Europe, healthcare in the US)
3. **What time horizon matters most for your business?** (e.g., next 12 months, 3-5 years, long-term)
Choose the questions most relevant to the context. If the user already provided this information, proceed directly to the analysis.
## Analysis Framework
### 1. Define Scope
- Clarify the decision the analysis will inform
- Set scope (industry, geography, time horizon)
### 2. Identify Factors
For each PEST category, identify 3-5 relevant factors:
- Cover all four PEST categories
- Consider industry-specific issues
- Look for both current trends and emerging changes
### 3. Analyze Each Factor
For every factor identified, assess:
- Is this an opportunity or threat?
- What's the likelihood (high/medium/low)?
- What's the potential impact (high/medium/low)?
### 4. Prioritize
- Rank by likelihood × impact
- Focus on top 5-10 factors that matter most
### 5. Develop Strategic Responses
- Create specific action items
- Assign owners and deadlines
- Link to strategic goals
### 6. Review Schedule
- Plan to update every 6-12 months
- Or when major external changes occur
## Common Mistakes to Avoid
Watch for these pitfalls during analysis:
- **Too generic factors** — Not actionable, be specific to your industry
- **Ignoring interconnections** — Misses systemic risks, map how factors influence each other
- **One-time analysis** — Becomes outdated, plan quarterly reviews
- **Only focusing on threats** — Miss opportunities, balance positive and negative
- **No follow-through** — Analysis wasted, create action items with owners
- **Using outdated data** — Wrong conclusions, research current trends
- **Working in silos** — Miss diverse perspectives, involve cross-functional team
## Success Factors
- **Involve diverse perspectives** — not just leadership
- **Use current data** — not assumptions from years ago
- **Connect to strategy** — how does this inform decisions?
- **Quantify when possible** — e.g., "15% increase in regulations"
- **Review regularly** — external environment changes fast
- **Make it actionable** — every factor needs a response
## PEST Category Deep Dive
### Political Factors to Consider
- Government stability and policy changes
- Tax regulations and incentives
- Industry-specific regulations
- Trade restrictions and tariffs
- Labor laws and employment regulations
- Data privacy laws (GDPR, CCPA)
- Professional licensing requirements
- Cross-border regulations (if international)
- Healthcare regulations (if health-related)
### Economic Factors to Consider
- Economic growth rates
- Inflation and interest rates
- Exchange rates (if international)
- Disposable income trends
- Consumer confidence indices
- Unemployment rates
- Market conditions and competition
- Remote work permanence trends
- Healthcare cost trends
- Corporate budget allocations
### Social Factors to Consider
- Demographic shifts and population trends
- Cultural attitudes and lifestyle changes
- Education levels and skills availability
- Health consciousness trends
- Generational shifts (Gen Z expectations)
- Work-life balance evolution
- Diversity, Equity, Inclusion (DEI) focus
- Social media influence and trends
- Mental health awareness
- Celebrity/influencer impact
### Technological Factors to Consider
- Innovation and R&D activity
- Automation and AI adoption
- Digital transformation trends
- Platform and infrastructure changes
- Wearable device integration
- Video platform evolution
- Cybersecurity threats
- Virtual/augmented reality emergence
- Data analytics capabilities
- Communication technology changes
## Templates
### Quick PEST Matrix
```
OPPORTUNITIES THREATS
POLITICAL [factor 1] [factor 1]
[factor 2] [factor 2]
ECONOMIC [factor 1] [factor 1]
[factor 2] [factor 2]
SOCIAL [factor 1] [factor 1]
[factor 2] [factor 2]
TECHNOLOGICAL [factor 1] [factor 1]
[factor 2] [factor 2]
```
### Detailed Factor Analysis Template
```
Factor: [name]
Category: [P/E/S/T]
Type: [Opportunity/Threat]
Likelihood: [High/Medium/Low]
Impact: [High/Medium/Low]
Evidence: [data/sources]
Strategic Response: [action plan]
Owner: [name]
Timeline: [deadline]
```
## Industry-Specific Examples
### Online Coaching Business
**Political:**
- Health insurance regulations covering coaching
- Data privacy laws (GDPR, CCPA)
- Professional licensing requirements
- Cross-border service regulations
**Economic:**
- Inflation impact on discretionary spending
- Disposable income trends
- Corporate wellness budget trends
- Remote work permanence
**Social:**
- Acceptance of coaching as profession
- Mental health awareness increase
- Gen Z wellness expectations
- DEI focus in corporate programs
- Celebrity/influencer endorsement
**Technological:**
- AI chatbots and automation
- Wearable device integration
- Video platform evolution
- Social media marketing channels
- Cybersecurity requirements
### E-commerce Business
**Political:**
- Sales tax regulations
- Import/export tariffs
- Consumer protection laws
- Data privacy regulations
**Economic:**
- Consumer spending patterns
- Shipping cost inflation
- Currency fluctuations
- Supply chain disruptions
**Social:**
- Online shopping behavior shifts
- Sustainability expectations
- Mobile shopping preferences
- Social commerce trends
**Technological:**
- Payment technology evolution
- AI personalization
- AR/VR shopping experiences
- Logistics automation
## Output Format
Structure your PEST analysis as:
1. **Executive summary** — top 3-5 most critical factors
2. **Detailed quadrant analysis** — Opportunities vs Threats across 4 categories
3. **Prioritized action plan** — with owners and timelines
4. **Review schedule** — when to update
---
**Best Practices:**
- ✅ Involve diverse, cross-functional perspectives
- ✅ Use current data from reliable sources
- ✅ Connect insights to strategic decisions
- ✅ Quantify impacts when possible
- ✅ Create actionable response plans
- ⚠️ Review regularly (6-12 months minimum)
- ⚠️ Don't focus only on threats—identify opportunities
- ⚠️ Avoid generic factors—be industry-specificRelated Skills
what-not-to-do-as-product-manager
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
visual-cues-cta-psychology
Design effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
value-realization
Analyze if end users discover clear value. Use when evaluating product concepts, analyzing adoption, or uncertain about direction.
user-story-fundamentals
Capture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.
typescript-satisfies-operator
Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.
typescript-interface-vs-type
Guides when to use interface vs type in TypeScript. Use this skill when defining object types, extending types, or choosing between interface and type aliases.
typescript-best-practices
Guides TypeScript best practices for type safety, code organization, and maintainability. Use this skill when configuring TypeScript projects, deciding on typing strategies, writing async code, or reviewing TypeScript code quality.
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
trust-psychology
Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
theme-epic-story
Structure product work hierarchically using themes, epics, and stories. Use when organizing backlogs, planning releases, communicating with stakeholders, or breaking down large initiatives into manageable work.
tailwind-v4-configuration
Configure Tailwind CSS v4 with CSS-first approach. Use when installing, migrating from v3, setting up build tools (Vite/PostCSS/CLI), customizing themes with @theme, or configuring plugins.