Minimal Core Flow

VibePro preserves context through five explicit steps. It does not turn them into an automatic pass/fail gate.

1. Story

vibepro story diagnose /path/to/repo --id story-example --run-graphify

Use a Story to state the intended user or operational outcome. Graphify is optional.

2. Spec

vibepro spec readiness /path/to/repo --id story-example --base origin/main
vibepro spec write /path/to/repo --id story-example --draft --input spec.json

A Spec can carry acceptance clauses plus code and test references. Draft and final states remain explicit.

3. Verification

vibepro verify run /path/to/repo --id story-example --kind unit -- npm test

verify run executes an argv command and records its result. verify record is available for evidence produced elsewhere; the source remains distinguishable.

4. Review and decisions

vibepro review prepare /path/to/repo --id story-example --stage gate
vibepro review record /path/to/repo --id story-example --stage gate \
  --role implementation --status pass --summary "Reviewed"
vibepro decision status /path/to/repo --id story-example

These commands preserve review and decision records. They do not grant merge authority.

5. PR handoff

vibepro pr prepare /path/to/repo --story-id story-example --base origin/main

Inspect .vibepro/pr/story-example/pr-prepare.json and the generated PR body. Humans and repository policy decide what must happen next. pr create is an optional GitHub CLI handoff, not a safety gate.