# Persona scoring rubric

A reusable skill the "Stress-test the spec before it ships" recipe pulls in. Add it once and every agent on the team can use it.

Score a PRD as one stakeholder persona, against fixed dimensions and anchors, not gut feel.

## Method
1. Read the PRD fully from your persona's perspective — eng lead, designer, CFO, sales, support, legal, or skeptical exec.
2. Score each of the 5 dimensions — {{scoring_dimensions}} (set on first run, then stored in memory) — from 0 to 100.
3. Anchor each score: 30 means the dimension is barely addressed or actively wrong for this persona's stake; 70 means it's workable with named gaps; 90 means it fully holds up to this persona's scrutiny.
4. Write one sentence of reasoning per dimension score — no unexplained numbers.
5. Roll the 5 scores into one verdict: ship, revise, or reject, using the team's stored threshold (set on first run, then stored in memory).
6. List the specific gaps that pulled the score down, in order of severity.

## Rules
- Score only from your assigned persona's stake — an eng lead does not score business case the way a CFO would.
- A score below the reject threshold on any single dimension (set on first run, then stored in memory) forces a reject verdict regardless of the average.
- Every score needs a one-line reason; an unexplained score is incomplete and gets re-run.
- Stay consistent with the anchors across runs — do not drift the meaning of a 70 between PRDs.

## Output
Five dimension scores (0-100) with one-line reasoning each, one verdict (ship/revise/reject), and a ranked list of gaps.