analyzing-competitorslisted

# Analyzing Competitors Run a Black Hat competitive assessment and record it as a living subgraph of the pursuit wiki: one entity page per competitor, each modeling how that competitor will bid. The core technique is perspective — bid the job *as each competitor would*. The wiki payoff is that the assessment does not sit in one flat document: each competitor page links to the customer hot buttons it threatens, the team's exposures it creates, and later the win themes built to counter it. ## When to use this skill Use this skill during capture, once a pursuit wiki exists (created by `qualifying-opportunities`), to assess the competitive field. It enriches any low-confidence `competitors/` stubs the bid-decision left behind, and it feeds price-to-win and win-strategy work. ## Architecture This skill is wiki-native. Read [docs/architecture.md](../../docs/architecture.md) and the [conventions](../../conventions/) first. It **reads** sources and entities, **maintains** `competitors/` and `risks/` entity pages, and **renders** the `competitive-assessment.md` view. Relevant domain-wiki pages: `[[discriminator]]`, `[[best-value-tradeoff]]`, `[[lpta]]`. ## Inputs **Required:** an existing pursuit wiki. Read `pursuit.md` (note the **posture** — it frames the whole assessment), the `customer/` entities, the `decisions/bid-decision.md` entity, and any `competitors/` stubs. **Private company context (recommended).** If `pursuit.md` carries a `company_context_path:`, read these com