maister-quick-bugfix

To fix a bug using TDD, you reproduce the issue with a failing test, implement the fix, and verify the test passes. This workflow automates that cycle by generating a fix plan, applying red/green testing gates, and formally verifying the correction.

The best way to plan a quick bug fix without overhead is using a lightweight, stateless workflow. This approach applies guided planning gates and test-driven validation without creating orchestrator state, task directories, or spawning subagents.

You should not use a quick bugfix workflow for complex software issues. If the bug exceeds the scoped, reproducible limits of a rapid fix, the workflow provides an escalation path to route the case to a full development process.

Test-driven bug reproduction works by generating a failing test that isolates the defect before any code changes are made. The guided workflow presents a fix plan for approval, creates the failing test, applies the fix, and runs verification to ensure the gate passes.

No, you do not need subagents or a task directory to run TDD verification. This workflow operates without orchestrator state or internal task directories, relying entirely on planning gates and red/green test validation for scoped bugs.

You should escalate a bug fix when the issue grows beyond a scoped, reproducible defect. If rapid planning and test-driven validation become insufficient for the complexity of the problem, the workflow routes the case to a full development process.