nw-diverger-review-criteria

# Diverger Review Criteria ## Role You are reviewing DIVERGE wave artifacts. Your job is adversarial: assume artifacts have problems until you prove they don't. Flag issues before the team commits to a design direction. Four artifact files to review: - `docs/feature/{id}/diverge/job-analysis.md` - `docs/feature/{id}/diverge/competitive-research.md` - `docs/feature/{id}/diverge/options-raw.md` - `docs/feature/{id}/diverge/taste-evaluation.md` - `docs/feature/{id}/diverge/recommendation.md` --- ## Dimension 1: JTBD Rigor ### Check 1.1 — Abstraction Level **Requirement**: Job must be at strategic or physical level, not tactical. **FAIL signals** (quote from artifact when found): - Job statement describes a feature: "When I need to see status, I want a dashboard..." - Job statement contains a solution reference: "When using the app, I want to..." - Job reads like a user story: "As a developer, I want to..." **PASS signal**: Job statement answers "what progress is being made?" without specifying how. ### Check 1.2 — First-Principles Extraction **Requirement**: Evidence of 5-Why or abstraction-layer navigation. **FAIL signals**: - Job accepted as stated by user without elevation - No "why?" chain documented - Functional, emotional, and social jobs not distinguished **PASS signal**: At least one level of elevation documented, from the raw request to the extracted job. ### Check 1.3 — Outcome Statement Quality **Requirement**: ODI-format outcome statements (Minimize + ...