Scenario Scorer

Total-score rule

• Keep the final total transparent and reproducible.
• Prefer a normalized 0-100 total when weights sum to 100.
• If you do not use scripts/score_options.py, show the exact formula used for totals.
• Do not emit weighted totals that cannot be recomputed from the displayed scores and weights.

Pipeline role

When used together with orchestrate-analysis and analysis-verifier:

• accept the coordinator's scoring handoff as input,
• keep scoring independent from the verifier's judgment,
• do not rewrite the coordinator's merged draft,
• return only the scoring artifact needed for the final merge.

When pipeline-coordinator is active, return the scoring artifact to that skill for final merge.

Default criteria

If the user did not provide criteria, propose:

• Impact: 35
• Feasibility: 25
• Risk: 20
• Time-to-value: 20

Output format

Return:

• scoring table,
• ranked options,
• recommended option,
• criteria and weights used,
• sensitivity note if one criterion dominates the outcome.

Safety

• Keep scoring rules visible.
• Do not hide assumptions.
• If weights are arbitrary, say so.

References

• Example inputs and outputs live in examples/.
• Weighting tips live in references/weighting-guide.md.