understand-propose-implement-verify

A structured problem solving workflow enforces an understand, propose, implement, and verify execution order to convert requirements into validated solutions while minimizing change risk and churn.

To plan a low-risk code change, propose the smallest safe approach during the propose phase, reuse existing project skills to avoid duplicating logic, and coordinate changes across all affected codebase layers.

You verify a software implementation by checking outcomes against original requirements and running relevant tests or checks across the affected scope during the explicit verification step.

You need a four-step loop for refactoring and feature work when tasks require coordinated reasoning across multiple steps, touch multiple codebase layers, or carry high regression risk.

No specific testing frameworks are required; the verify step mandates running relevant checks and regression prevention applicable to your project's affected scope.

The best way to coordinate changes across layers is applying a disciplined cycle that separates understanding requirements, proposing minimal changes, implementing, and verifying related behavior.