competitive-analysislisted

# Competitive Analysis ## Purpose Map the landscape of competing products and prior art to identify proven patterns, differentiation opportunities, and lessons learned before building. ## Scope Constraints - Analyzes products and services at the feature and UX level, not individual code libraries. - Focuses on identifying patterns, gaps, and differentiation — not producing marketing materials. - Does not perform deep technical benchmarking; flag performance concerns for handoff. ## Inputs - Feature or product area to analyze - Known competitors or similar products (or let the process discover them) - Target user segment - Specific aspects to compare (if any focus areas are known) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Step 1: Identify Competing Products or Prior Art - Direct competitors (same problem, same audience) - Indirect competitors (different approach to the same underlying need) - Prior art in adjacent domains (similar interaction patterns in different contexts) - Open source alternatives - Note market positioning of each (enterprise vs indie, free vs paid, general vs niche) ### Step 2: Map Feature Sets For each competitor, catalog: - Core features (what they do well) - Secondary features (nice-to-haves they include) - Missing features (notable gaps) - Unique features (things only they offer) - Recent additions (direction they're heading) ###