What problem does it solve?
When several solution candidates already exist, teams often collapse the choice into a single hidden score or let presentation order decide. This Skill enforces a fair, explicit comparison: constraints, targets, parity conditions, and a predeclared selection policy are stated before scoring, so trade-offs stay visible and the final value judgment remains with the operator.
Core Features & Use Cases
- Structured characteristic space: Separates hard constraints, optimization targets (at most 1-3), and passive observations before any scoring begins.
- Parity and policy declaration: Requires comparator set, evidence window, equalized budget, missing-data policy, and selection policy to be declared before results are seen.
- Non-dominated reporting: Eliminates constraint violations and reports the surviving trade-off set instead of a single winner; binding a choice is routed through h-decide only on explicit operator request.
- Optional typed persistence: Comparison artifacts stay conversational by default and are persisted via haft_problem/haft_solution MCP calls only on explicit save intent or a concrete receiving use.
- Use Case: An engineering team has three database options and asks the agent to compare them fairly; the Skill drafts the characteristic space, declares parity and policy, evaluates each dimension across all options, and returns the non-dominated set with concrete trade-offs.
Quick Start
Ask the agent to compare your existing candidates, for example: compare Postgres, SQLite, and DuckDB for our analytics workload under equal hardware and a declared selection policy.