/decision-reversible

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select decision-reversible from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv decision-reversible, /just-vibe decision-reversible and /jv:decision-reversible in Claude. See shortcut setup and context examples.

What the agent does

1. Inventory persisted data, external promises, dependency adoption, switching mechanisms and operational costs.
2. Classify reversibility with evidence, distinguishing rollback of code from reversal of consequences, and design a cheaper experiment with a usable exit.

Inputs

• candidate decisions, migration constraints, contracts, and timeline.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Reversibility, lock-in, exit cost, and staged commitment.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Plan; candidate decisions, migration constraints, contracts, and timeline.

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

• Decision map with reversibility dimensions, reversal steps, exit cost assumptions, dependencies, commitment checkpoints and the experiment boundary.

How the work is checked

• A simple config toggle with irreversible downstream data effects is not marked freely reversible; a trial has a usable exit path.

When to stop or clarify

• Avoid unsupported effort estimates. Unknown contractual constraints remain explicit dependencies.

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

Identify persisted data, external promises, migrations, lock-in and rollback dependencies.

Method

Describe reversal steps, time, retained artifacts and irreversible consequences separately from changing a feature flag.

Pitfall

A reversible code change may already have sent messages or transformed data irreversibly.

Check

Walk reversal after partial adoption and identify what the previous version can no longer read or undo.

Situational decisions

When a configuration toggle has irreversible downstream effects: Classify those effects separately and design a bounded trial with cleanup or reconciliation.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring