Plan Execution Consistency

plan-execution-consistency

Registry Trigger

Use when

• plan execution consistency planned files actual changed files extra file stale validation unplanned behavior review scope repair re-review final handoff
• plan drift actual diff differs validation before final edit partial validation reported as full extra generated file missing planned file

Do not use when

• no task-local plan execution consistency decision is required

Skill Role

Reconcile the visible plan with actual changed files, behavior, commands, validation, review coverage, and unresolved discrepancies.

High-Value Rules

• Audit actual changes and evidence against the accepted plan or capsule.
• Record and explain any unplanned path, omitted path, or changed assumption that affects acceptance or evidence.
• Require fresh validation evidence after the final repository edit.
• Require explicit validation coverage for every changed file in scope.
• After repair, reconcile the latest diff, fresh validation, and re-review before closure.

Anti-Patterns

• An extra generated file can indicate editing the wrong source.
• A repaired finding invalidates review of the prior diff.
• Planned scope does not excuse an unreviewed actual change.

Stop Conditions

• Block closure when changed paths are unexplained, validation predates the last edit, any changed file is unreviewed, or repair lacks re-review.
• Escalate intentional behavior or scope changes not covered by acceptance.

Output Contract

• Return a plan-to-actual diff: state changed-file variance, behavior mapping, post-edit validation, review coverage, unverified scope, and residual risk

Targeted References