controller

Phase-based bugfix workflow orchestration coordinates multi-stage bug resolution across reproduction, diagnosis, fixing, testing, and documentation. It enforces structured progression by requiring explicit user approvals before advancing between phases, ensuring disciplined and safe execution.

You enforce a structured bugfix workflow by using a controller that mandates reading instructions before executing any phase. It validates inputs, transitions between assess, reproduce, diagnose, fix, test, review, document, and pr phases, and requires explicit user approval via prompts before advancing.

Yes, you can re-enter previous bugfix workflow phases based on user guidance. The controller supports optional phase re-entry, deferring the decision to the user via explicit questions, allowing you to loop back to reproduction or diagnosis if initial fixes fail.

The best way to gate approvals safely is to use interactive user questions before advancing any phase. This ensures explicit confirmation at each step from assessment to documentation, preventing automated transitions and keeping human oversight in the loop.

You only need to provide the initial bug report to start. The controller guides the phase flow from assess to subsequent steps, validating inputs and recommending next actions while deferring to your explicit decisions for phase progression.