Skip to content

deanpeters/Product-Manager-Skills / skills/swot-analysis

swot-analysis

Verified

Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

FileKindSize
SKILL.mdskill md10.0 KB
examples/sample-industrial.mdmarkdown5.9 KB
examples/sample.mdmarkdown5.8 KB
template.mdmarkdown2.2 KB

template.md

View on GitHub
# Evidence-Cited SWOT Template

Copy this to record a SWOT of one company built from the public record. Every entry carries a
source and a **Fact/Inference/Assumption** label — evidence per entry is what separates this SWOT
from the four-box brainstorm nobody trusts. The crossings section is the deliverable; the quadrants
are its evidence.

Quadrant discipline: **S and W are internal and current; O and T are external.** If an
"opportunity" requires the company to act, it's a strategy in disguise — reclassify it.

## Template

```markdown
# SWOT: [Company / Scope]
**As-of date:** [YYYY-MM-DD]
**Decision supported:** [the decision this SWOT informs]
**Perspective:** [theirs, or yours competing with them]

## 1. Strengths (internal, evidenced)
- [Entry — corroborated by customer voice, filings, or independent coverage, not just their marketing] — [URL, date] — [Fact/Inference]
- [Max 5, ranked by defensibility]

## 2. Weaknesses (internal, evidenced)
- [Entry — customer voice weighs heaviest here; buyers document weaknesses vendors won't] — [URL] — [label]
- [Max 5, ranked by exploitability]

## 3. Opportunities (external)
- [Entry — a market/macro signal, stated so it exists whether or not the company acts] — [URL] — [label]
- [Max 5, ranked by fit to their strengths]

## 4. Threats (external)
- [Entry — competitor/regulatory/technology signal] — [URL] — [label]
- [Max 5, ranked by likelihood x damage]

## 5. The Crossings (the "so what")
- **S-O (attack):** [which strength unlocks which opportunity — 1-2 moves, labeled Inference]
- **W-T (exposure):** [which weakness a threat will find first — 1-2 risks, labeled Inference]
- **For your decision:** [what this SWOT says about the decision named above, in 2 sentences]

### Assumptions to Validate
- [Assumption 1]
- [Assumption 2]
- [Assumption 3]
```

## Quality checks before you call it done

- No strengths entry rests solely on the company's own website — corroborate it or label it a claim
- Every O and T entry would still be true if the company did nothing (the external test)
- The crossings name specific quadrant entries, not new ideas that appear from nowhere
- The final "for your decision" sentences would survive being read aloud to the exec who owns that decision
receiving-code-reviewobra/superpowersUse 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 implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall