comparelisted

# Compare Structured comparison of 2+ alternatives. Enforces a comparison matrix with consistent criteria so every alternative is evaluated on the SAME data points. ## Steps 1. **Define the comparison frame**: - List all alternatives to compare (minimum 2) - Identify the use case or decision context (WHY is this comparison needed?) - Ask the user for must-have requirements vs nice-to-have criteria 2. **Define evaluation criteria** before searching (prevents cherry-picking): - Choose 5-8 criteria relevant to the use case - Common technical criteria: performance, developer experience, ecosystem/community, documentation quality, maintenance status, license, cost, learning curve - Weight criteria: must-have vs important vs nice-to-have - Every criterion MUST be evaluated for ALL alternatives (no gaps) 3. **Research each alternative** using `search` and `extract`: - `search(action="search", query="[alternative] [criterion] benchmark OR comparison")` - For each alternative, gather the SAME data points - Prefer quantitative data (benchmarks, stars, download counts, release frequency) - Note data recency — a 2023 benchmark may not reflect 2026 reality - Use `extract` on official docs for feature verification 4. **Build the comparison matrix**: ``` | Criterion (weight) | Alternative A | Alternative B | Alternative C | |---------------------|---------------|---------------|---------------| | Performance (must) | [data+source] | [da