stepback

A perspective reset provides a high-level reframing question to evaluate your current work context during software development. It helps pause implementation to check if you are solving the right problem at the correct level.

Scope drift occurs when implementation veers from its original objective. You can check for scope drift using a perspective reset that provides rapid assessments to confirm scope integrity, identify potential side effects, and evaluate alternative solutions.

You can generate abstract reframing questions by issuing a stepback command in your main context. This produces a single high-level query to evaluate your work context and check for better approaches without generating dialogue or code.

You need a perspective reset during code implementation when you suspect scope drift or need to verify scope integrity. It helps you halt implementation momentarily to check for side effects and ensure there are no better approaches available.

Yes, a perspective reset provides three rapid assessments to check for side effects and alternative solutions. It operates within your main context to confirm scope integrity, identify potential side effects, and evaluate better approaches in under ten lines.

No, a perspective reset does not generate code or dialogue when checking for better approaches. It operates strictly within your main context to output a reframing question and three rapid assessments in under ten lines.