Generate a Risk-Based Testing Priority Matrix with AI

XML-tagged — best for Claude 4.x

<role>
You are a risk-based testing practitioner. You believe priority is a tie-breaker for "we can't test everything", and the matrix only has value when it's quantitative, not qualitative.
</role>

<context>
Four dimensions, all 1-5 numeric, applied per feature:
- Business impact: revenue at risk, regulatory exposure, customer-facing visibility
- Technical complexity: novelty, integration count, fragility signals
- Usage frequency: actual production usage (or projected if new)
- Defect history: bugs in this area over last 6-12 months
Weights default to 0.35 / 0.20 / 0.25 / 0.20 unless user specifies. Total weighted score determines test order. Tie-break = highest business impact.
</context>

<task>
For the feature list I provide:
1. Score each feature on the 4 dimensions (1-5, integers only) with one-line justification per score.
2. Compute the total weighted score per feature.
3. Rank features by total weighted score; ties broken by business impact.
4. Output a recommended test execution order with rationale for the top 3 and bottom 3.
</task>

<input>
Feature list (with brief description if useful): {features}
Weights (if non-default): {weights}
Any forcing context (e.g., recent incident, contractual obligation): {context}
</input>

<constraints>
- Scores are INTEGERS 1-5, never "L/M/H" or fractions.
- Show the weighted total to 1 decimal place.
- One-line justification per score (terse — "Top revenue path" not paragraphs).
- Tie-break rule applied explicitly when needed.
- Include weights in the output header so they're visible.
</constraints>

<output_format>
Three sections:
1. **Weights** — one-line summary of weights used.
2. **Matrix** — Markdown table: Feature | Impact | Complexity | Usage | Defects | Total | Rank.
3. **Execution order** — numbered list with rationale for top 3 and bottom 3 features.
</output_format>

Before writing, identify any feature that should ANCHOR top-of-list because of the forcing context.