borghei/Claude-Skills / project-management/strategy-frameworks/swot-analysis
swot-analysis
VerifiedBuilds and audits an evidence-backed SWOT with TOWS actions for one explicit strategic question. Use when assessing a market entry, pivot, competitive response or restructure, or as input to annual planning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| assets/sample_swot.json | config | 2.8 KB |
| assets/sample_swot_flawed.json | config | 452 B |
| assets/swot_template.md | markdown | 1.9 KB |
| references/swot-anti-patterns.md | markdown | 5.1 KB |
| references/swot-framework.md | markdown | 6.7 KB |
| scripts/swot_scorer.py | script | 9.8 KB |
references/swot-anti-patterns.md
View on GitHub# SWOT — Anti-Patterns + Fixes
The 10 most-common SWOT failures.
## A1 — No explicit scope
**Symptom:** "SWOT analysis" with no statement of what it's analyzing.
**Fix:** Lead with: "This SWOT analyzes [specific question]." Without
scope, items can point in 4 directions and the SWOT yields no action.
## A2 — Generic items
**Symptom:** Strengths = "Great team, great product, strong brand."
**Fix:** For each item, name specifics:
- WHICH team is great? (not all of them)
- WHICH product features?
- WHAT brand recognition (in which segment, measured how)?
## A3 — No weaknesses
**Symptom:** Strengths = 10 items. Weaknesses = 2 trivial items.
**Fix:** Either bias is hiding real weaknesses, or candor is low. Add:
- "Where are competitors better than us?"
- "What customer feedback do we routinely dismiss?"
- "What does our board worry about?"
## A4 — Vague opportunities
**Symptom:** Opportunities = "AI", "Globalization", "Market growing."
**Fix:** Opportunities are specific shifts you can act on. Each should answer:
- What shifted? (trigger event)
- What's the time window?
- What's the size?
- What's our right to win?
## A5 — Abstract threats
**Symptom:** Threats = "Competition is fierce", "Tech changes fast."
**Fix:** Threats need likelihood × severity. Each should answer:
- WHICH competitor? doing what?
- WHEN is this likely?
- HOW MUCH does it cost us if realized?
- WHAT can we do to mitigate?
## A6 — Internal/external confusion
**Symptom:** "Our customers love us" under Strengths. "Engineering team is small"
under Threats.
**Fix:** Customer sentiment = External. Team size = Internal. Apply the
"do we own it?" test.
## A7 — No TOWS follow-up
**Symptom:** SWOT presented; planning meeting ends.
**Fix:** Always run TOWS:
- SO: strengths × opportunities → offensive moves
- ST: strengths × threats → defensive moves
- WO: weaknesses × opportunities → build/buy
- WT: weaknesses × threats → mitigation
## A8 — Wishful Strengths
**Symptom:** "Industry-leading R&D" — when R&D produces 3 papers/year.
**Fix:** Strength = what is, not what we want. Aspiration goes to "weakness to fix" or "opportunity to develop."
## A9 — SWOT for the company instead of the question
**Symptom:** General company SWOT used to inform a specific decision.
**Fix:** SWOT per question. New SWOT for: market entry decision, M&A target,
pricing change, etc. Same company; different SWOT per question.
## A10 — One person built it
**Symptom:** SWOT reflects single-person view; no triangulation.
**Fix:** Input from: customer-facing team, engineering, finance, BD,
external advisor. Single-perspective SWOT is bias dressed as analysis.
## Worked example — strong vs weak SWOT
**Scope:** Acme entering European compliance market.
### Weak version
- **S:** Strong product, great team, good investors
- **W:** Small team
- **O:** EU GDPR market is huge
- **T:** Competition
### Strong version
**S1:** Product depth advantage (4-year compliance automation, 12+ integrations); demonstrated in NA enterprise SOC 2 wins ($X ARR).
**S2:** Existing $X ARR with 3 European-headquartered customers using us
NA-first; positive references available.
**W1:** No EU legal entity; no EU data residency; cannot serve EU
customers fully under GDPR Art. 28 without changes.
**W2:** Sales motion is NA-flavored; outbound playbook unproven in EU
market; no in-language content for top 5 EU markets.
**O1:** EU regulatory body's 2026 enforcement push expected to drive
$3-5B incremental spend in compliance automation, 18-month window.
**O2:** Major NA competitor (Acme-Z) acquired by US PE; signals
will reduce EU investment, opening 6-12 month talent + customer window.
**T1:** EU-headquartered competitor (Vendor-Y) has 60% mid-market
penetration in DACH; well-funded ($X), 200+ EU FTE.
**T2:** Possible EU AI Act provisions affecting our ML-based detection
features; need to assess by Q3.
### TOWS
| | O1: enforcement push | O2: competitor exit |
|---|---|---|
| S1: product depth | SO: lead with product depth in PR + analyst briefings | SO: target the orphaned competitor customer base |
| S2: existing EU customers | SO: case-study + reference these | WO: hire EU CSM to retain + grow |
| | T1: EU competitor | T2: AI Act risk |
|---|---|---|
| W1: no EU entity | WT: partner with EU SI to reduce time-to-market | WT: file EU entity + DPA process |
| W2: sales playbook | WT: hire EU sales lead with Vendor-Y compete experience | (no overlap) |
Recommended strategic moves (top 3):
1. Hire EU-based sales lead + CSM (Q3)
2. File EU entity + execute DPA (Q3-Q4)
3. PR + analyst push to capture enforcement-driven demand (Q4)
This version is actionable. The weak version is wallpaper.
## SWOT validation checklist
Before declaring a SWOT done:
- [ ] Explicit scope stated
- [ ] Each item has evidence
- [ ] Each item has specificity
- [ ] At least 3 substantive weaknesses
- [ ] Each opportunity has trigger + size + window
- [ ] Each threat has likelihood + severity
- [ ] Internal/external classified correctly
- [ ] TOWS generated
- [ ] 2-3 prioritized strategic moves identified
- [ ] Multiple stakeholders input
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |