← ClaudeAtlas

requivo-impactlisted

Show what a change to a Requivo session touches — the decisions to re-validate and the artifacts that go stale — from the dependency DAG. Pure deterministic query, no reasoning, no API key. Use when the user asks "what does changing X affect?" or wants to know what to regenerate after a model change.
jbkkz/requivo · ★ 2 · AI & Automation · score 69
Install: claude install-skill jbkkz/requivo
# /requivo-impact Report the blast radius of a change. This is a **deterministic DAG query** — no Claude reasoning; run the command and translate. ## Run `$ARGUMENTS` is the session slug, optionally followed by slot names/ids to probe. ``` requivo impact <slug> [slot ...] # blast radius of those slots requivo impact <slug> # the full dependency map ``` To see what has *already* drifted since the last generation, also run: ``` requivo status <slug> --json # artifacts flagged stale carry a source revision behind current ``` ## Relay Present, in plain language: - the **decisions to re-validate** (they rested on a changed slot via `derived_from`), - the **premises to re-examine** (challenges that contest a changed slot via `contests`), - the **artifacts that go stale** and should be regenerated (`/requivo-prd`, `/requivo-brief`, …) — the saved assessment goes stale whenever a decision or premise it rests on is unseated, - and recommend **only the necessary** regenerations — not everything. Do not invent dependencies the command did not report; the DAG is authoritative.