Feature Map
For a first change, start with Story, Spec, checks, review, and PR preparation. The table below also includes optional analysis, judgment, and integration tools; it is not a checklist that every change must complete.
| Need | Command family | Stored result |
|---|---|---|
| Initialize and inspect a repository | init, doctor, status | .vibepro/ config and health context |
| Discover impact context | graph, env graph, diagnose | Graph and diagnosis artifacts |
| Preserve product intent | story, spec, trace | Story, Spec, and trace records |
| Preserve execution evidence | verify | Verification records tied to repository state |
| Preserve human or agent judgment | review, decision | Review and decision records |
| Frame questions and reconsider with evidence | judgment investigate | AI-host requests, investigation evidence, candidates, and unresolved questions |
| Carry investigation into judgment input | judgment prepare --investigation | An input draft awaiting explicit adoption |
| Suggest expert judgment from observations | judgment suggest | Hypotheses, options, and next checks on standard output |
| Evaluate senior engineering choices | judgment evaluate | Advisory decision DAG and immutable run history |
| Add command guardrails | guard | Local guard configuration and reports |
| Prepare a PR handoff | pr prepare, pr create | PR context and human-readable body |
| Configure coding agents | skills, codex, harness | Installed instructions and learning records |
| Maintain integrations/artifacts | brainbase, artifacts | Integration and migration outputs |
Removed from the minimal core
The following concepts may appear in historical release notes but are not current features: Gate DAGs, check packs, checkpoints, managed execution and merge, automatic adjudication, readiness/blocking verdicts from the former Gate DAG, review-lifecycle accounting, delivery-efficiency budgets, design-modernization pipelines, usage/ROI reporting, and automatic audit bundles.
The current Spec finalization checks and unresolved-review checks remain. pr prepare can summarize a blocked result; pr create refuses to create the PR from that result. These checks are not merge approval. See the Safety Model.
Run vibepro help --language en for the exact commands in your installed version.
Development Judgment operating loop
VibePro can now operate Development Judgment as an explicit non-blocking loop rather than an optional report command:
- record applicability,
- investigate and reconsider when needed, then review the input draft and explicitly adopt its meaning,
- evaluate the Development Judgment DAG,
- bind actionable guidance into Story planning,
- record disposition separately from later Outcome,
- feed observed Outcome into the next judgment run.
pr prepare only projects this lifecycle. Development Judgment never changes PR readiness, merge, or release authority.