stepback

To catch scope drift during active code iterations, trigger a one-shot perspective reset that validates scope, side effects, and alternative approaches in under 10 lines. It forces a higher-level reframing question to restore focus on the right problem without generating code or starting dialogue.

The best way to reframe current work when fixing symptoms is to apply a mid-work perspective reset that generates a single abstract step-back question. This validates whether a more fundamental solution exists before you continue down a misguided path.

Your developer workflow expands scope unintentionally when direction drifts without high-level validation. A rapid three-step check verifies scope drift, potential side effects, and whether a better approach exists, preventing you from committing to the wrong path.

Yes, you can validate a better approach without interrupting flow by running a low-friction mid-work check. It scans your current work and outputs under 10 lines, verifying scope drift, side effects, and alternative solutions without spawning agents or requiring manual prompting.

You should not use a step-back perspective reset when you need executable code, extended dialogue, or detailed agent execution, because it strictly produces a one-shot abstract reframing question and validation checks without generating code or starting conversations.

No, the stepback reframing tool requires no dependencies or specific environment setup. It operates as a standalone one-shot command to instantly reframe work and validate scope, side effects, and approach without external components.