Skip to content

hoavdc/CodexKit / skills/codexkit-strategic-analysis-porter

codexkit-strategic-analysis-porter

Unverified

Conduct strategic analysis using Porter's Five Forces, PESTEL, and SWOT frameworks. Assess competitive dynamics, macro environment, and internal capabilities. Synthesize into strategic implications with ranked options. Use when entering new markets, evaluating competitive position, or strategic planning.

Strategic Analysis (Porter + PESTEL + SWOT)

When to Use

  • During annual strategic planning cycles
  • When evaluating entry into a new market or segment
  • When competitive dynamics shift significantly
  • When preparing strategic recommendations for the board

Procedure

Step 1 — Porter's Five Forces

Rate each force (1 = Low, 5 = High):

ForceGuiding Questions
Threat of New EntrantsBarriers to entry? Capital requirements? Regulatory hurdles?
Bargaining Power of SuppliersSupplier concentration? Switching costs? Unique inputs?
Bargaining Power of BuyersBuyer concentration? Price sensitivity? Switching costs?
Threat of SubstitutesAlternative solutions? Performance ratio? Switching ease?
Competitive RivalryNumber of competitors? Industry growth? Exit barriers?

Overall industry attractiveness: Average of 5 forces (inverted — lower score = more attractive).

Step 2 — PESTEL Scan

FactorKey TrendsImpact (H/M/L)Timeframe
PoliticalRegulation, trade policy, political stability
EconomicGDP growth, inflation, exchange rates, interest rates
SocialDemographics, consumer behavior, workforce trends
TechnologicalInnovation pace, automation, digital disruption
EnvironmentalSustainability pressure, resource scarcity, climate
LegalCompliance requirements, IP law, labor law

Step 3 — SWOT Synthesis

Combine Five Forces (external) + PESTEL (macro) + internal assessment:

HelpfulHarmful
InternalStrengthsWeaknesses
ExternalOpportunitiesThreats

Step 4 — Strategic Options

Generate strategic options by crossing:

  • Strengths × Opportunities → Offensive strategies
  • Strengths × Threats → Defensive strategies
  • Weaknesses × Opportunities → Reorientation strategies
  • Weaknesses × Threats → Survival strategies

Rank options by: Feasibility × Impact × Alignment with vision.

Inputs

InputRequiredFormat
Industry/market contextYesDescription or brief
Company positionYesProducts, market share, capabilities
Competitor listRecommendedKey competitors with known strengths

Output

## Strategic Analysis — [Company/Market]

### Five Forces Assessment

| Force | Rating | Rationale |
|-------|--------|-----------|
| New Entrants | 2/5 | High capital requirements, regulatory barriers |
| Supplier Power | 3/5 | Moderate concentration, some switching costs |
| Buyer Power | 4/5 | Price-sensitive market, low switching costs |
| Substitutes | 3/5 | Digital alternatives emerging |
| Rivalry | 4/5 | 5 major competitors, slow growth |
| **Industry Attractiveness** | **Moderate** (avg 3.2/5) | |

### PESTEL Summary
[Top 3–5 macro trends with impact assessment]

### SWOT Matrix
| Strengths | Weaknesses |
|-----------|------------|
| Strong brand | Limited digital capability |
| | |
| **Opportunities** | **Threats** |
| Emerging market expansion | New digital entrant |

### Strategic Options (Ranked)

| # | Strategy | Type | Feasibility | Impact | Rank |
|---|----------|------|-------------|--------|------|
| 1 | Digital transformation | Reorientation | High | High | ⭐ 1 |
| 2 | Market expansion APAC | Offensive | Medium | High | 2 |
| 3 | Cost leadership program | Defensive | High | Medium | 3 |

### Recommendation
[2–3 sentence strategic recommendation with rationale]

Definition of Done

  • Five Forces rated with rationale
  • PESTEL scan with top trends identified
  • SWOT matrix completed
  • Strategic options generated from SWOT cross-analysis
  • Options ranked by feasibility × impact
  • Clear recommendation provided

Examples

Prompt

Analyze the competitive landscape for our B2B SaaS company in the HR tech market.
We have 5% market share, strong product but weak sales team.
Key competitors: Workday, BambooHR, Deel.
Use Porter's Five Forces + PESTEL + SWOT and recommend strategic options.

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall