跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

prd-v03-moat-definition

Assess 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.

mattgierhart · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-moat-definition

技能说明


name: prd-v03-moat-definition description: Assess 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. context: fork allowed-tools:

  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • WebSearch
  • WebFetch

Moat Definition

Position in HORIZON workflow: v0.2 Competitive Landscape → v0.3 Moat Definition → v0.3 Pricing Model Selection

Consumes

This skill requires prior work from v0.2:

  • Landscape map artifact (from Competitive Landscape Mapping) — Current behavior documentation, feature matrix, competitor analysis
  • CFD-* entries (competitive intelligence, from Competitive Landscape Mapping) — Documented competitors with pricing, features, user feedback
  • BR-* product type entry (from Product Type Classification) — Classification constrains which competitors are relevant to analyze

This skill assumes v0.2 analysis is complete with documented competitors.

Produces

This skill creates/updates:

  • CFD-* entries (competitor moat analysis) — Assessment of each competitor's defensibility by moat type
  • BR-* entries (targeting rules) — Constraints derived from moat analysis, defining where to compete vs. avoid
  • Moat strength inventory artifact — Summary of competitor moats with vulnerability signals

All CFD moat analysis entries should include:

  • confidence: 2-3/5 (based on public evidence + user interviews about switching friction)
  • Evidence source (pricing pages, reviews, customer interviews)
  • Forward target: "Would move to 4/5 if we interview 5+ current/former customers about switching costs"

Example moat analysis entry:

CFD-055: Competitor Moat Analysis — Notion

Competitor: Notion
Primary Moat Type: Switching Costs (data lock-in)
Moat Strength Tier: Strong
Confidence: 3/5 (source: public-research + 2-user-interviews)
Date: 2026-02-01

Switching Cost Quantification:
  - Financial: Multi-year contract, no early termination ($0 direct cost)
  - Time/Effort: 20+ hours migration, team retraining
  - Data Migration: Proprietary database format (complex export)
  - Workflow Retraining: Unique templates, team habits
  - Integration Rework: Deep Slack/GitHub dependencies

Total Switching Cost: $3K in labor + 20 hours = Material friction
Moat Verdict: Strong — switching costs >$3K + meaningful time investment

Vulnerability Signal: SMB segment with small teams; they use <20% of feature set (opportunity for simpler tool)
Targeting Decision: Avoid direct competition. Wedge in SMB with simplified, cheaper offering.

Evidence:
  - CFD-042 (landscape): Reviews show enterprise love; SMB complaints focus on cost + complexity
  - CFD-015 (value hypothesis): SMB would save $12,500/year with simpler tool
Next Target: "Would move to 4/5 if we interview 5+ SMB teams about exact switching cost dollars"

Moat Type Taxonomy

Every moat falls into one of six types. Identify primary + secondary moats per competitor:

Moat TypeDefinitionStrong WhenWeak When
Switching CostsFriction to leave (data, workflow, contracts)Multi-year data, deep integrationsEasy export, monthly contracts
Network EffectsValue increases with usersTwo-sided marketplace, content platformSingle-player tool, linear value
Data/IPProprietary data or algorithmsUnique training data, patentsCommodity ML, public datasets
Brand/TrustRecognition, credibilityRegulated industry, high-risk decisionsLow-stakes, undifferentiated
Scale/CostVolume economicsInfrastructure-heavy, marginal cost near zeroLabor-intensive, linear cost
RegulatoryCompliance barriersCertifications required, government contractsNo compliance requirements

For micro-SaaS: Switching costs and brand/trust matter most. Network effects and scale rarely apply.

Moat Strength Tiers

Rate each competitor's defensibility:

TierCriteriaEvidence SignalsTargeting Implication
ImpenetrableMulti-layered moat, 10+ years data lock-in"Would take years to switch"Avoid direct competition
StrongSignificant switching friction, 1-2 year contractsHigh NPS + low churn despite complaintsTarget underserved segments only
ModerateSome friction, workarounds existChurn 5-10%, export optionsWedge opportunity exists
WeakEasy to replace, commodity offeringMonthly plans, high churn, price shoppingDirect competition viable
ErodingFormer strength decliningNew alternatives gaining shareAggressive targeting

Gate rule: Don't compete where incumbent has Impenetrable or Strong moat unless targeting segment they explicitly ignore.

Switching Cost Inventory

Quantify ALL switching costs — the sum determines moat strength:

Cost TypeHigh ImpactLow ImpactHow to Assess
Financial>6mo contract, early termination feesMonthly billing, no penaltyCheck pricing page terms
Time/Effort40+ hr migration, retraining<4 hr setup, familiar UXTrial the competitor
Data MigrationProprietary format, no exportStandard export (CSV, API)Test export function
Workflow RetrainingUnique methodology, team habitsStandard patternsRead onboarding docs
Integration ReworkDeep API dependenciesStandalone toolMap their
阅读完整来源 ↗