Structured Comparison of Options With Decision Matrix

Compares N libraries, tools, or approaches against weighted criteria you define, producing a sourced decision matrix and a recommendation that states what would change it.

License: CC0-1.0 · By waxmark · v1 · 2026-11-02

Share on X

Add a trust badge to your README

[![Waxmark](https://waxmark.app/api/badge/literature-style-comparison-of-options)](https://waxmark.app/items/literature-style-comparison-of-options/scan)
Report
Compare the options below for the stated use case and produce a decision matrix. The reader is choosing one of these this week, so the output must make the tradeoffs legible and the recommendation falsifiable.

<options>
{{OPTIONS}}
</options>

<criteria>
{{CRITERIA}}
</criteria>

<use_case>
{{USE_CASE}}
</use_case>

<constraints>
{{CONSTRAINTS}}
</constraints>

<source_material>
{{SOURCE_MATERIAL}}
</source_material>

<criteria> may include weights (for example, `performance: 3, docs quality: 1`); if weights are absent, assign them from <use_case> and show your reasoning. <constraints> are disqualifiers (license, language, minimum version, hosting model). <source_material> may contain docs excerpts, benchmarks, changelogs, or issue-tracker notes; prefer it over your own knowledge, and label any claim that comes from your training rather than the material as `[from model knowledge, verify]`.

Method:

1. Apply <constraints> first. Any option that fails a hard constraint is eliminated before scoring; record the reason. Do not score eliminated options; it muddies the matrix.
2. Define each criterion operationally before scoring: what would a 1, 3, and 5 look like for this use case? Write these anchors down. Scores without anchors are opinions.
3. Score each surviving option on each criterion from 1 to 5 using the anchors. For every score, give one sentence of evidence with its source (a quote or reference from <source_material>, or the `[from model knowledge, verify]` label). A score with no evidence is left blank and counted as unknown, not as 3.
4. Compute weighted totals. Then do a sensitivity check: which single weight change would flip the top two? If a small change flips them, say the decision is close and name the deciding question.
5. For the top option, list what it is worst at and the concrete situation in which the runner-up would be the better choice. For the runner-up, list what would make you pick it.
6. Note where the comparison is stale-prone: criteria whose scores depend on fast-moving facts (release cadence, maintainer activity, pricing) and should be rechecked before committing.

Be as critical of the leading option as of the others. Do not let one standout criterion halo the rest of the scores.

## Output format

**Eliminated** - table: option, constraint failed, evidence. Or "None eliminated."

**Criteria anchors** - for each criterion: weight, what 1 / 3 / 5 mean here.

**Decision matrix** - table: rows are options, columns are criteria plus Weighted total. Each cell holds the score and a superscript-style reference (a, b, c) into the evidence list below. Unknown cells show `?`.

**Evidence** - lettered list; each entry: the evidence sentence and its source. `[from model knowledge, verify]` where applicable.

**Recommendation** - the option, in one sentence, followed by: what it is worst at, when the runner-up wins, and the sensitivity result from step 4.

**Recheck before committing** - bullets from step 6, each with how to verify (where to look).
Structured Comparison of Options With Decision Matrix · Waxmark