rite-povlisted

# /rite-pov: project-grounded external verdict Decide whether **this project** should adopt, trial, hold, reject, or ignore a named outside candidate. Chat verdict first; durable record only when the user asks or the decision changes an active feature. ## Rules consulted Step 0: Read `.claude/skills/devrites-lib/reference/standards/core.md`. Pull `source-driven`, `security`, or `deprecation` standards only when the candidate touches those risks. ## Operating rules - Verdict only after two floors clear: one verified project fact and one verified external source. - Named candidate only. If the user asks "what should we use?" over an open field, route to `/rite-pressure-test` or `/rite-spec` to surface criteria first. - Reversibility sizes rigor: two-way config/dependency < bounded internal migration < public/security/legal/data decision. ## Workflow 1. **Frame.** Parse `$ARGUMENTS` into candidate, intent (`adopt|switch|compare|CVE/deprecation impact|second opinion`), and reversibility tier. If intent is ambiguous, ask one blocking question before research. **Completion:** candidate, decision intent, and reversibility tier are explicit. 2. **Project floor.** Verify at least one concrete project fact: incumbent dependency/call site, current absence plus integration point, prior ADR/decision, or affected surface. Use `devrites-engine profile get`; on `MISS`, run `devrites-engine profile refresh` once, then inspect candidate-specific files fresh. Completion: at least one `fi