just-vibeDecisions · plan by default
/decision-revisit
Reassess a decision using new constraints or evidence
Use when new evidence may invalidate a recorded choice; decision-adr preserves the resulting decision record.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select decision-revisit from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv decision-revisit, /just-vibe decision-revisit and /jv:decision-revisit in Claude. See shortcut setup and context examples.
/just-vibe:decision-revisit Reassess the cache decision now that writes occur in two regions./just-vibe:decision-revisit Revisit a queue choice after workload ordering requirements change./just-vibe:decision-revisit Review an old decision without its rationale; distinguish reconstruction from recorded facts.What the agent does
- If the decision was saved, run decision show NAME and then decision revisit NAME with attributed observations; otherwise reconstruct the rationale and label it as reconstructed.
- Compare the original assumptions with current facts.
- Weigh migration costs, disruption and option value, and recommend retaining, modifying or superseding the decision.
Inputs
- prior decision record, new evidence, and changed constraints.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Reassess a specific choice while preserving its historical rationale.
- Writes
- No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.
- Mode
- Plan; prior decision record, new evidence, and changed constraints.
- Prerequisites
- The decision question, constraints, alternatives or permission to identify them, and relevant project evidence. Current vendor claims and prices require current authoritative sources during execution. Scores are decision aids, not facts.
Expected output
- Changed-assumption table, alternatives and migration implications, and a retain/change recommendation with the proposed status update and adoption or revisit conditions.
How the work is checked
- New fashion alone does not invalidate a sound decision; a broken core assumption triggers a concrete alternative analysis.
When to stop or clarify
- Do not rewrite history or silently mark a decision superseded without an adoption instruction.
Handling missing context
- Infer
- Recover hard constraints, the current option, adoption status and stated priorities from the brief and prior decisions.
- Assume
- Compare feasible options qualitatively when weights were not supplied; make a reversible conditional recommendation when useful.
- Ask
- Ask only about a missing constraint or preference that could reverse the recommendation; do not demand a complete scoring questionnaire.
Technical guidance
- Evidence
- Read the original premise, accepted status, trigger and new evidence with dates.
- Method
- Change only conclusions affected by the new premise; compare continuing, adapting and replacing, preserving the original record.
- Pitfall
- A hindsight rewrite loses the information needed to understand why the earlier choice was reasonable.
- Check
- Show the changed premise, resulting recommendation and migration cost; unchanged conditions should not trigger automatic reversal.
Situational decisions
When only preferences or fashion changed: Retain the decision unless an explicit new priority justifies transition costs.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.