mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v03-moat-definition
prd-v03-moat-definition
VerifiedAssess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| assets/br-targeting.md | markdown | 5.8 KB |
| assets/cfd-moat-analysis.md | markdown | 4.7 KB |
| references/examples.md | markdown | 7.6 KB |
assets/cfd-moat-analysis.md
View on GitHub# CFD Moat Analysis Template
Copy this template for each competitor moat analysis. Store completed entries in `customer_feedback.md`.
---
## CFD-MOT-[XXX]: [Competitor Name] Moat Analysis
**Competitor**: [Name]
**URL**: [website]
**Analysis Date**: [YYYY-MM-DD]
**Upstream CFD**: [CFD-### from v0.2 Competitive Landscape]
### Moat Classification
**Primary Moat Type**: [Switching Costs / Network Effects / Data/IP / Brand/Trust / Scale/Cost / Regulatory]
**Secondary Moat Type**: [if applicable]
**Moat Strength**: [Impenetrable / Strong / Moderate / Weak / Eroding]
### Evidence Summary
| Evidence Type | Finding | Source | Tier |
|---------------|---------|--------|------|
| [Type] | [What you found] | [Where] | [1-5] |
| [Type] | [What you found] | [Where] | [1-5] |
| [Type] | [What you found] | [Where] | [1-5] |
### Switching Cost Inventory
| Cost Type | Rating | Evidence | Hours/$ Impact |
|-----------|--------|----------|----------------|
| **Financial** | [Strong/Moderate/Weak/None] | [contract terms, penalties] | $[amount] |
| **Time/Effort** | [Strong/Moderate/Weak/None] | [migration estimate] | [X] hours |
| **Data Migration** | [Strong/Moderate/Weak/None] | [export options, format] | [X] hours |
| **Workflow Retraining** | [Strong/Moderate/Weak/None] | [unique methodology?] | [X] hours |
| **Integration Rework** | [Strong/Moderate/Weak/None] | [API dependencies] | [X] hours |
**Total Switching Cost Estimate**: $[amount] + [X] hours
### Moat Strength Evidence
**Strength indicators** (why moat is [tier]):
1. [Evidence point]
2. [Evidence point]
3. [Evidence point]
**Weakness indicators** (where moat fails):
1. [Evidence point]
2. [Evidence point]
3. [Evidence point]
### Vulnerability Assessment
**Vulnerable Segment**: [Which customers/segment is NOT protected by moat]
**Why Vulnerable**: [Specific reason moat doesn't apply]
**Evidence**: [How you know this]
**Erosion Signals** (if applicable):
- [ ] New entrants gaining share
- [ ] Increasing complaints about [specific issue]
- [ ] Feature becoming commoditized
- [ ] Pricing pressure in market
- [ ] Technology shift undermining moat
### Targeting Implication
**Decision**: [Don't Compete / Wedge Strategy / Direct Competition]
**Rationale**: [1-2 sentences explaining why this decision given moat analysis]
**Wedge Entry Point** (if applicable): [Specific feature/segment to enter]
### Confidence & Gaps
**Overall Confidence**: [High / Medium / Low]
**Confidence Rationale**: [Why this confidence level]
**Gaps requiring validation**:
- [ ] [What we don't know]
- [ ] [What we assumed]
### Related IDs
- **Upstream**: CFD-[###] (Competitor intelligence from v0.2)
- **Downstream BR**: BR-TGT-[###] (Targeting rule this supports)
---
## Quality Checklist
Before marking complete:
- [ ] Moat type is specific (not "they're big")
- [ ] Moat strength has evidence (not assumed)
- [ ] All 5 switching cost types assessed
- [ ] Switching costs quantified (hours + $)
- [ ] Vulnerability identified (where moat doesn't apply)
- [ ] Targeting decision stated
- [ ] Confidence level with rationale
- [ ] Evidence tier noted for each claim
---
## Example Entry (HomeFalcon Context)
```
CFD-MOT-001: Home Warranty Company (American Home Shield) Moat Analysis
Competitor: American Home Shield
URL: ahs.com
Analysis Date: 2025-01-07
Upstream CFD: CFD-012 (AHS competitor profile)
Moat Classification:
- Primary: Brand/Trust
- Secondary: Scale/Cost
- Strength: Moderate
Evidence Summary:
| Evidence Type | Finding | Source | Tier |
|---------------|---------|--------|------|
| Brand awareness | #1 recognized name in home warranty | Google Trends | 2 |
| Switching friction | Monthly cancelable, no data lock-in | Pricing page | 1 |
| Customer complaints | "Claims denial" primary complaint | BBB reviews | 2 |
Switching Cost Inventory:
| Cost Type | Rating | Evidence | Hours/$ Impact |
|-----------|--------|----------|----------------|
| Financial | Weak | Month-to-month available | $0 penalty |
| Time/Effort | Weak | No setup required | <1 hour |
| Data Migration | None | No customer data stored | 0 hours |
| Workflow Retraining | None | Passive service | 0 hours |
| Integration Rework | None | No integrations | 0 hours |
Total Switching Cost: ~$0 + <1 hour
Vulnerability:
- Segment: DIY homeowners who want control
- Why: AHS moat is "trust to handle claims" — doesn't apply to users
who want to self-manage and just need tracking
- Evidence: Reddit threads "AHS denied my claim, need alternative"
Targeting Implication:
Decision: DIRECT COMPETITION on self-serve segment
Rationale: No switching friction + active pain (claims denial) =
opportunity for tool that puts homeowner in control
Confidence: High — validated via complaint analysis + pricing page
```
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: 471k | 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: 471k | 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: 471k | 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 |