competitive-intellisted

# Axon Competitive Intel Use this for monitoring competitors over time. This is not the broad competitor analysis workflow. ## Onboarding Interview Infer competitors, focus, cadence, and output format from context. If competitors are clear, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the competitor list, focus area, or whether authenticated pages/profiles are required. ## Axon Collection Plan For each competitor, use Axon surfaces by cadence: - One-off: `axon scrape` or `axon extract` for current pages; use `axon diff` when a prior URL/version exists. - Recurring: create a URL watch with `axon watch create`, verify with `axon watch exec`, and review history with `axon watch history`. - Alerts: treat these as report sections unless a notification path is separately configured. Collect: - pricing pages, annual/monthly toggles, expanded feature tables - feature and product pages - changelogs, blogs, release notes, docs updates - authenticated dashboards only when the user has legitimate access, source terms permit collection, and no auth, CAPTCHA, paywall, rate-limit, or terms boundary is bypassed ## Parallel Work If appropriate, use sub-agents or equivalent parallel task runners. A natural split is one competitor per researcher or one focus area per researcher. Each researcher should return pricing tiers, features, recent changes, source URLs, and confidence notes. ## Final Deliverable ```markdown # Competitive Intel: