Read-set manifest: devrites-engine context --skills-root .omp/skills <slug> --skill rite-pov (no workspace: --out <path>) bundles every file named below into one deduplicated read.
/rite-pov: project-grounded external verdict
Decide whether this project should adopt, trial, hold, reject, or ignore one
named outside candidate.
Workflow
- Frame the candidate, decision intent, and reversibility tier (two-way = locally
reversible; bounded-one-way = reversible via a recorded rollback; high-stakes =
irreversible or costly). Route an
open-ended market search to
/rite-pressure-test or /rite-spec.
- Inspect the live repository for at least one concrete project fact: an
incumbent dependency/call site, integration seam, relevant ADR/decision, or
confirmed absence. No profile cache.
- Verify the external claim from current primary documentation, source,
advisory, or release notes, cited with URL, version or advisory id, and
retrieval date (
tooling.md citation contract). A CVE verdict also needs the
installed version from the lockfile (path:line) checked against the
advisory's affected range, and a call-site search for the affected API
(reachable / unreachable / unknown). Known exploitation (a KEV listing)
raises priority, never severity.
- Compare fit, existing alternatives, migration cost, reversibility, project
principles, security, licensing, and deprecation risk.
- Return exactly one verdict:
Adopt, Trial, Hold, Reject, or
Not-our-problem.
- Persist only when asked: use the active feature's
decisions.md for a
feature-scoped choice or propose an ADR for a durable architecture decision.
Do not write a parallel rejection or learning index.
Output
Verdict: <grade> — <one sentence>
Tier: <two-way | bounded-one-way | high-stakes>
Project evidence: <file:line or local doc>
External evidence: <URL — version/advisory id — retrieved YYYY-MM-DD>
CVE applicability: <n/a | range in/out (lockfile path:line); reachability reachable/unreachable/unknown>
Why: <three bullets max>
Next: <one action | done>
Record: <path | not written>
No project evidence or no primary external source means Hold, not a generic
technology opinion.
Non-trigger
Not a market survey or premise stress-test (/rite-pressure-test / /rite-spec),
not implementation, not a patch plan. A CVE still needs a live advisory URL
before any Adopt/Trial.
Failure and recovery
- Missing project evidence or missing live primary source →
Hold. Failing
case: "Adopt Redis" with no incumbent call site and no opened docs URL.
- High-stakes / irreversible without a named rollback → cannot be
Adopt.
- A citation missing version or retrieval date, or a CVE verdict missing range
evidence →
Hold. Not-our-problem for a CVE needs out-of-range or
unreachable evidence. Failing case: "Not-our-problem: we don't call that
function" with no call-site search, or "Adopt upgrade" while the lockfile already
pins a fixed version.
- Persist only when asked; a chat-only verdict is not a decision record.
1---2name: rite-pov-63description: Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.4argument-hint: "[candidate/link/question]"5user-invocable: true6metadata:7 source: https://skillmd.com/skills/viktorsbaikers/rite-pov-68---910<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"workspace":["decisions.md"]} -->11> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --skill rite-pov` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.1213# /rite-pov: project-grounded external verdict1415Decide whether this project should adopt, trial, hold, reject, or ignore one16named outside candidate.1718## Workflow19201. Frame the candidate, decision intent, and reversibility tier (two-way = locally21 reversible; bounded-one-way = reversible via a recorded rollback; high-stakes =22 irreversible or costly). Route an23 open-ended market search to `/rite-pressure-test` or `/rite-spec`.242. Inspect the live repository for at least one concrete project fact: an25 incumbent dependency/call site, integration seam, relevant ADR/decision, or26 confirmed absence. No profile cache.273. Verify the external claim from current primary documentation, source,28 advisory, or release notes, cited with URL, version or advisory id, and29 retrieval date ([`tooling.md`](skill://devrites-lib/reference/standards/tooling.md) citation contract). A CVE verdict also needs the30 installed version from the lockfile (`path:line`) checked against the31 advisory's affected range, and a call-site search for the affected API32 (`reachable` / `unreachable` / `unknown`). Known exploitation (a KEV listing)33 raises priority, never severity.344. Compare fit, existing alternatives, migration cost, reversibility, project35 principles, security, licensing, and deprecation risk.365. Return exactly one verdict: `Adopt`, `Trial`, `Hold`, `Reject`, or37 `Not-our-problem`.386. Persist only when asked: use the active feature's `decisions.md` for a39 feature-scoped choice or propose an ADR for a durable architecture decision.40 Do not write a parallel rejection or learning index.4142## Output4344```text45Verdict: <grade> — <one sentence>46Tier: <two-way | bounded-one-way | high-stakes>47Project evidence: <file:line or local doc>48External evidence: <URL — version/advisory id — retrieved YYYY-MM-DD>49CVE applicability: <n/a | range in/out (lockfile path:line); reachability reachable/unreachable/unknown>50Why: <three bullets max>51Next: <one action | done>52Record: <path | not written>53```5455No project evidence or no primary external source means `Hold`, not a generic56technology opinion.5758## Non-trigger5960Not a market survey or premise stress-test (`/rite-pressure-test` / `/rite-spec`),61not implementation, not a patch plan. A CVE still needs a live advisory URL62before any `Adopt`/`Trial`.6364## Failure and recovery6566- Missing project evidence or missing live primary source → `Hold`. **Failing67 case:** "Adopt Redis" with no incumbent call site and no opened docs URL.68- High-stakes / irreversible without a named rollback → cannot be `Adopt`.69- A citation missing version or retrieval date, or a CVE verdict missing range70 evidence → `Hold`. `Not-our-problem` for a CVE needs out-of-range or71 `unreachable` evidence. **Failing case:** "Not-our-problem: we don't call that72 function" with no call-site search, or "Adopt upgrade" while the lockfile already73 pins a fixed version.74- Persist only when asked; a chat-only verdict is not a decision record.