/decision-buy-build

Make it your own.

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

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

What the agent does

1. State the usage horizon and include the current workaround as an option; verify current vendor capabilities when relevant.
2. Compare fit, integration, operations, staffing, maintenance, migration, exit/export, failure ownership and total-cost assumptions.

Inputs

• capability, team capacity, compliance/integration constraints, volume, and budget.

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

Scope

Reads

Build, buy, and hybrid options across initial and ongoing ownership.

Writes

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

Mode

Plan; capability, team capacity, compliance/integration constraints, volume, and budget.

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

• Fit/gap matrix, cost model inputs and assumptions, ownership burden, recommendation, and a validation and exit plan.

How the work is checked

• Maintenance and migration effort appear alongside subscription cost; a vendor missing a hard feature is excluded.

When to stop or clarify

• No purchases or account creation. Do not convert speculative usage into precise budget claims.

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

Establish functional requirements, integration surfaces, support burden, data export and verified pricing terms.

Method

Compare lifecycle scenarios including maintenance, incident response, migration and exit; retain uncertainty ranges instead of invented estimates.

Pitfall

Vendor feature lists do not prove compatibility with the actual identity, offline or data-residency requirements.

Check

Validate the decisive integration with a bounded example and compare exit costs as well as the happy-path purchase.

Situational decisions

When a vendor lacks a hard requirement or usable export: Exclude it or state the explicit compromise before calculating weighted convenience.

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