VibeProShip what you meant to build

Keep the chain from product intent to Story, Spec, implementation, verification, decisions, and PR handoff explicit for AI-assisted development.

Install the Beta

What VibePro Is

CLI Reference

Keep product intent attached to the work

Connect Stories and Specs to implementation and test references so technically valid code can still be checked against what the product was meant to become.

Make intent drift inspectable

Record verification, review, trace, and explicit decisions so humans and coding agents can see where implementation diverges from the accepted Story or Spec.

Hand off evidence, not an automatic verdict

Summarize intent-to-implementation evidence for PR review while leaving product meaning, approval, and merge authority with people and repository policy.

Intent and traceability, not agent permissions

VibePro is not primarily an agent sandbox or tool-permission system. Restricting whether an agent may use Bash, Edit, or deploy controls execution capability; VibePro addresses a different failure mode: a constrained agent can still build the wrong thing.

The current minimal core keeps the chain from Story to Spec, implementation references, verification, review, decisions, trace, and PR handoff repository-local and inspectable. It does not autonomously decide product meaning or certify that a change is safe.

The minimal-core boundary

VibePro no longer provides the former broad Gate DAG, managed execution controller, review-lifecycle accounting, delivery-efficiency budget enforcement, or automatic audit bundles. That reduction is deliberate: the core focuses on preserving product intent and the evidence needed to review whether implementation still matches it.

What VibePro Is explains the boundary. Version History separates the published package from development history.