vibe-plan-execution

Plan execution with disciplined fidelity prevents drift by binding to the plan and implementing only the smallest verifiable change. It verifies local evidence against the bound plan and defers to planning if evidence contradicts it.

Plan deviation gating is a risk-management mechanism that applies explicit gates during implementation to preserve scope. It ensures unsafe or unapproved changes are blocked and provides clear traceability for auditable progress.

Bind to your existing plan file or inline plan, verify its sections, then implement only the smallest verifiable slice. The process extracts goals, requirements, acceptance criteria, and risks to drive execution while respecting plan-defined routes.

Local evidence verification checks implementation output against the bound plan. When evidence cannot be reconciled with the plan, the execution defers back to planning to ensure all decisions remain auditable and aligned with the original intent.

When local evidence contradicts the bound plan, you should return to planning. This ensures that any irreconcilable evidence triggers a planning review rather than forcing unsafe improvisation or unapproved scope changes.

Yes, you need an existing bound plan source. You can bind to a plan file or an inline plan, extracting its goals, requirements, acceptance criteria, test plans, and risks before implementing the smallest verifiable slice.