/scope

Make it your own.

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

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

What the agent does

1. Identify user outcomes and distinguish essentials from enhancements.
2. Trace each proposed cut through a complete user journey and its operational dependencies, and keep the smallest usable outcome that remains viable under the limits.

Inputs

• proposed work, must-have outcomes, deadline/resources, and constraints.

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

Scope

Reads

Release boundaries and sequencing; no removal of already required behavior without identifying that tradeoff.

Writes

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

Mode

Plan; proposed work, must-have outcomes, deadline/resources, and constraints.

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

• Included journeys, explicit cuts with their dependency consequences, later phases and minimum release checks.

How the work is checked

• Deferred work does not break an included journey; an impossible deadline is exposed with concrete options.

When to stop or clarify

• Do not quietly reinterpret a hard requirement as optional. Mark unresolved priority choices and continue dependency analysis.

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

Identify the core user outcome, hard deadline/resources and dependencies between requested capabilities.

Method

Separate essential behavior from enhancements while preserving a usable end-to-end path.

Pitfall

Dropping error recovery or required authorization can make a smaller release unusable rather than merely simpler.

Check

Verify the retained scope completes the core journey and list deferred items with their explicit impact.

Situational decisions

When the remaining scope still exceeds a hard limit: Offer concrete tradeoffs in outcome, deadline or resources instead of unsupported estimates.

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