vibepro-workflowlisted

# VibePro Minimal-Core Workflow ## Authority `AGENTS.md` and `docs/management/REBUILD.md` are the authority for this Skill. VibePro is a small development aid. It exists to keep these four things connected: 1. what the user asked for, 2. what was designed, 3. what changed, 4. what was verified. It is not a workflow engine, a merge authority, or an evidence-collection game. Removed mechanisms must not be rebuilt through agent instructions. The standard development loop is: > Story → Spec → implement → affected tests → one review wave → GitHub PR → CI → merge For the VibePro repository itself, always use the ordinary GitHub flow: branch, test, `gh pr create`, review, merge. ## When to Use Use this Skill when a repository uses VibePro to connect a Story, Spec, implementation, verification, review, or PR. Also use it when deciding whether VibePro-managed evidence is current, sufficient, or blocking delivery. ## Completion Definition Work is complete when all of the following are true: - the accepted Story scope is implemented, - the acceptance criteria directly affected by the change are verified, - no unresolved finding can break the accepted scope, security boundary, data integrity, or rollback safety, - a PR exists and CI is green, - any useful but out-of-scope finding has been moved to a follow-up Story instead of being absorbed into the current Story. More evidence is not progress by itself. A new artifact, review, or test run counts as progress only when it re