reality-verification

To verify a software fix, capture the BEFORE state, apply the change, and validate the AFTER results using automated or manual checks. This BEFORE/AFTER comparison confirms the issue is resolved without introducing regressions.

Document bug fix reproduction steps and verification evidence in a standardized .progress.md file. This records the BEFORE/AFTER states and VF task formats to ensure changes are verifiable and auditable across QA pipelines.

Structure regression verification tasks using the VF task format, which scaffolds verification steps, evidence collection, and completion criteria. This ensures changes are validated consistently across CI pipelines and feature validations.

Yes, this approach supports both automated checks and manual QA validations. You log the BEFORE state, apply the fix, and then validate the AFTER results using whichever testing method suits the regression verification scenario.

You need VF task formats for issue diagnosis when you require guided failure reproduction and standardized evidence documentation. This ensures verifiable, auditable verification for bug fixes and feature changes.

Before-after state documentation provides a structured audit trail in a .progress.md file, whereas standard testing logs may lack context. This method explicitly maps failure reproduction to resolution, ensuring verifiable regression verification.