/build

Make it your own.

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

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

What the agent does

1. Inspect current patterns, trace the closest existing journey, and resolve critical ambiguity before editing.
2. Implement the smallest complete vertical slice, including its error states, and exercise failure recovery before expanding optional states.
3. Run checks appropriate to the behavior changed.
4. For a multi-phase feature, fix, refactor or MVP, use the relevant phase contract in the composed-workflows guide. Keep simple work direct. Delegate only when authorized, and use the reviewed worker result and acceptance flow before dependent work. Offer the plan-review canvas only when browser feedback is useful or requested.

Inputs

• feature goal, constraints, and observable success criteria. Requires writable source and relevant local tooling.

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

Scope

Reads

Complete the requested feature and necessary integration; no unrelated modernization or automatic publication.

Writes

Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.

Mode

Apply; feature goal, constraints, and observable success criteria. Requires writable source and relevant local tooling.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Working changes with the files changed, acceptance criteria and failure paths exercised, and remaining integration gaps or limitations.

How the work is checked

• The requested journey works end to end; an error path preserves existing contracts and user data.

When to stop or clarify

• Missing secrets/services produce a specific integration blocker, not fabricated success. Preserve unrelated edits and report checks that could not run.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Inspect the relevant architecture, data/interface contracts, existing conventions and acceptance criteria.

Method

Implement one coherent vertical path, load applicable domain guides and verify user-visible behavior plus material failure states.

Pitfall

Building isolated components without connecting the actual entry point leaves the feature unusable.

Check

Exercise the integrated result and check the exact changed artifacts, preserving explicit gaps when real dependencies are unavailable.

Situational decisions

When a business rule is unspecified: Continue independent plumbing and ask only for the rule that changes user-visible behavior.

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