speedrun

Automating bugfix workflow phases requires a speed-run mode that selects and executes the next incomplete phase in sequence. It progresses through assess, reproduce, diagnose, fix, test, review, document, pr, and summary phases automatically using existing artifacts and context.

Automated bugfix phase orchestration determines the next incomplete workflow phase by evaluating artifacts and context, executing it, logging the outcome, and returning to a dispatcher loop. This cycle repeats until all phases from assess to summary are complete.

Yes, automated bugfix orchestration supports escalation handling by pausing the workflow when user input is required. Once the user provides the necessary input, the speed-run loop resumes and continues advancing through the remaining incomplete phases.

The best way to run a complete bugfix sequence in one session is using a speed-run command that auto-advances through phases. It selects the next incomplete step based on completion state, enforces escalation rules, and loops until all phases finish.

Yes, automated bugfix orchestration works without external dependencies. It relies entirely on internal workflow artifacts, context to determine phase completion state, and a dispatcher loop to manage the progression through the bugfix phases.

An automated bugfix workflow stops midway when escalation rules are triggered, pausing for required user input. It also stops if artifacts or context indicate a phase is incomplete, gating further progression until the required conditions are met.