just-vibeDecisions · plan by default
/decision-adr
Write a decision record with alternatives and consequences
Use to record a proposed or adopted architectural decision; decide determines a recommendation first.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select decision-adr from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv decision-adr, /just-vibe decision-adr and /jv:decision-adr in Claude. See shortcut setup and context examples.
/just-vibe:decision-adr Draft an ADR for the proposed shared identity service; keep status proposed./just-vibe:decision-adr Write an ADR that supersedes an earlier database decision./just-vibe:decision-adr Draft an ADR without known meeting dates or approvers; do not invent them.What the agent does
- Inspect existing ADR numbering and status conventions, and separate actual agreement from recommendation.
- Write the context, decision, alternatives, rationale, tradeoffs and consequences, and link superseded records without rewriting history.
Inputs
- proposed/adopted decision, context, alternatives, and destination when saving.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Record one architectural decision with status and consequences; no new approval or implementation.
- Writes
- No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.
- Mode
- Plan; proposed/adopted decision, context, alternatives, and destination when saving.
- 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
- ADR with context, decision, alternatives, rationale, consequences, status, revisit triggers and supersession links where applicable.
How the work is checked
- A proposed choice remains proposed; a superseding ADR preserves the older record and links it.
When to stop or clarify
- Do not manufacture dates, participants, or consent. Save only in the requested or established documentation location.
Handling missing context
- Infer
- Recover hard constraints, the current option, adoption status and stated priorities from the brief and prior decisions.
- Assume
- Keep status proposed without adoption evidence; follow the existing ADR numbering and location.
- 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 decision context, proposal history, acceptance evidence and affected contracts.
- Method
- Record status, alternatives, consequences, rejected reasons and a concrete revisit trigger without rewriting prior rationale.
- Pitfall
- An agent recommendation is not an adopted organizational decision.
- Check
- Link each claimed constraint to evidence and distinguish proposed, accepted and superseded records.
Situational decisions
When adoption is not confirmed: Keep status proposed and distinguish the recommendation from actual agreement.
When the user wants reconsideration triggers: Also record the decision with decision save, tying its assumptions to watched files or numeric triggers.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.