Skip to content

VibeProBring the reason for a change into its PR.

Investigate what should change with your AI host, then connect the reasoning to Stories, Specs, implementation, and PR review.

VibePro

From deciding what to build to reviewing the change ​

A request does not always call for a new feature. With Senior Engineering Judgment, judgment investigate helps the AI host frame questions from the goal and scope, inspect existing Graphify artifacts and source, and revisit the problem, options, and recommendations as evidence changes. Candidates can then enter explicit input adoption and evaluation to consider what to build, simplify, or validate first. This investigation is optional, not a requirement for every change.

A PR should explain more than what changed ​

AI coding agents can produce a clean diff while solving the wrong user problem. VibePro keeps the few links a reviewer needs to answer: what user need motivated this change, what behavior was agreed, where is it implemented, and what was actually checked?

For example, a Story might say that a CSV export must preserve the active filters. The Spec can make that behavior concrete and name the code and test references. The verification record shows which test ran, and the PR summary brings those pieces back into the review conversation.

VibePro checks whether declared implementation and test references are structurally present. The AI host can interpret evidence and compare options, but the CLI does not autonomously call a model or guarantee correct judgment. A reference can exist and a test can pass while the change still misses the user's need. Human review and adoption responsibility remain.

A deliberate boundary ​

Story and Spec records are an additional maintenance cost. They are the machine-readable contract VibePro can inspect; they do not replace a README, an issue tracker, product discussion, or normal code review. README or issue context alone is not a supported replacement for these records. If an existing PR explanation is already sufficient, the additional maintenance may cost more than it returns.

The former broad Gate DAG and its merge-blocking lifecycle machinery are retired from the minimal core. The current judgment DAG supports investigation, reconsideration, and next actions as advice. It does not automatically certify intent alignment or safety, approve PRs, or grant merge authority.

The getting-started guide walks through the smallest useful flow. What VibePro Is explains the records and their boundaries in more detail.

Apache-2.0 · docs source 6d043b4cf37b