pestel-analysis

Analyze political, economic, social, technological, environmental, and legal forces affecting a product.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill pestel-analysis-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pestel-analysis
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/pestel-analysis
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill pestel-analysis-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often miss macro-environment shifts—new regulations, rate changes, demographic trends—that materially affect roadmaps, or they produce padded PESTEL documents where every factor gets equal weight regardless of real impact. This Skill produces a sourced, product-specific PESTEL analysis that converts external forces into opportunities, threats, and roadmap guardrails. ## Core Features & Use Cases - Autonomous research workflow: The agent investigates macro factors itself using a search plan gate, marking published data as Fact with sources and product implications as Inference, with a question budget of three. - Honesty discipline: Low-impact factors are closed in one line instead of padded, and regulatory uncertainties are flagged for legal rather than asserted as fact. - Strategic synthesis and delta runs: Every analysis ends with top opportunities, threats, and roadmap guardrails, and repeat runs report only material movement against the prior document. - Use Case: A fintech team planning a card dispute product asks for a PESTEL covering Brazil plus card-scheme rules, and receives a sourced analysis showing that regulated acknowledgement timelines block scope lock and that status visibility must ship with submission. ## Quick Start Run a PESTEL analysis for my product covering the Brazilian market over the next 18 months for strategic planning purposes.

Frequently Asked Questions about pestel-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a PESTEL analysis for a product?▼

Provide the product name and what it does, then answer one question about geographic scope, which drives the Legal and Political sections. Time horizon defaults to 18 months and purpose to strategic planning unless you specify otherwise.

What is the difference between PESTEL and competitive analysis?▼

PESTEL covers macro-environment forces like regulation, inflation, and demographic shifts, not competitors. A rival's pricing move is not a PESTEL factor, but a regulation constraining everyone's pricing is.

Does PESTEL analysis require citing sources for data?▼

Yes. Every fact must carry a source and a date, labeled as Fact, while product implications are labeled Inference. Statistics, regulations, and compliance obligations must never be invented or asserted without evidence.

Can I re-run a PESTEL analysis to track changes over time?▼

Yes, the delta rule supports repeat runs. Given a previous PESTEL, the output reports only material movement such as new regulations or changed rates, referencing the prior document for everything static.

What are the limitations of a PESTEL analysis?▼

PESTEL does not cover internal factors like team capacity or tech debt, and it does not replace legal review. Regulatory interpretations are flagged as open questions for legal rather than asserted as compliance facts.