Bug Fix AI workflow template: From bug report to verified fix.

The ConvOps Bug Fix template makes your AI coding agent resolve a bug the same way every time: check the report is actionable, reproduce it, find the root cause, apply a surgical fix with a regression test, then verify. It stops twice for you, and a failed verification sends it back to Fix.

6 steps · 2 approvals · 1 loop back

Bug Fix · example runyour AI client
  1. 01Intake
  2. 02Reproducewaits for approval
  3. 03Analyzeplanner
  4. 04Fixdeveloper
  5. 05Verifywaits for approval
  6. 06Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Bug Fix template do?

For engineering teams who fix bugs with Claude Code, Codex, Cursor or OpenCode and want the reproduction and the root cause on record, not in a chat log.

Bug Fix is stored in ConvOps as six steps, and your AI client receives them one at a time. A Bug Fix run holds at Reproduce and Verify until an explicit approval is given.

  • Fix a login-page bug from report to confirmed resolution
  • Trace and fix an upload crash with the root cause documented
  • Debug a payment-processing error and verify the fix before close
step by step

How does the Bug Fix workflow run?

The 6 Bug Fix steps in order, each with the instruction your AI receives there as Bug Fix stores it.

Intake
Reproduceapproval
Analyzeplanner
Fixdeveloper
Verifyapproval
Completeclosing note

A closed bug with its reproduction recipe, root cause, regression test and verification result saved on the task.

  1. 01

    Intake

    the agent works

    Verify the bug report is actionable before investigation begins.

    Required elements:

    • A specific, unambiguous title
    • A one-line summary describing the incorrect behavior
    • Observed context (when, where, or under what conditions)

    If any element is missing, identify the gap and ask the operator to clarify. Do not advance with an under-specified report.

  2. 02

    Reproduce

    waits for your approvalrole · developer

    Produce a minimal, deterministic reproduction of the reported behavior.

    Capture:

    • Exact steps required to trigger the bug
    • Expected versus observed behavior
    • Relevant environment details (version, OS, configuration)

    If the bug cannot be reproduced, stop and report that finding explicitly. Do not proceed on speculation: an irreproducible report requires clarification, not guesswork.

    Request operator confirmation that this reproduction matches the reported issue before advancing.

    no rejection path · the run moves on only when approved

  3. 03

    Analyze

    the agent worksrole · planner

    Identify the root cause and scope the smallest corrective change.

    Document:

    • Location of the defect (files, functions, or subsystem)
    • Mechanism: why the observed behavior occurs
    • Proposed fix: the minimal change that resolves the root cause
    • Collateral impact: callers affected, tests that will shift, migrations or contracts potentially touched

    Keep the analysis focused and concise: depth of reasoning matters more than length.

  4. 04

    Fix

    the agent worksrole · developer

    Apply the corrective change defined in the analyze step. Keep the edit surgical: do not refactor adjacent code, rename unrelated symbols, or expand scope beyond the root cause.

    Add or update a regression test that would have caught this bug before the fix. The test must fail on the unfixed code and pass on the fixed code.

  5. 05

    Verify

    waits for your approvalrole · reviewer

    Verify the fix resolves the reported behavior without introducing regressions.

    Execute:

    • The reproduction recipe from the reproduce step
    • The regression test added in the fix step
    • The project's existing test suite at the relevant level

    Report what was executed, what passed, and what failed. If any check fails, reject this step: the workflow returns to fix so the gap can be addressed before another verification pass.

    Request operator approval before advancing.

    rejected → back to Fix

  6. 06

    Complete

    closes with a note

    The bug has been reproduced, analyzed, fixed, and verified. Mark the task completed and close it out.

reach for it when

  • Something that used to work is broken, and you can describe what you saw.
  • The fix must ship with a test that proves the bug cannot quietly return.
  • Someone will later ask for the root cause, and the answer needs to be on file.

something else fits when

  • The work is new behaviour rather than a defect: start a Feature or a Task.
  • The report is a question or a wish with no failure to reproduce.
  • Service is down right now and restoring it comes before any analysis.
example · card paymentsenterprise

Card declines after a provider update

A bank's card team files the decline report. The agent reproduces it against a test card, finds a changed response code, fixes the mapping with a failing test first, and the on-call lead approves at Verify.

Reproduce and Verify approvals

where approval is required

Where do you approve in Bug Fix?

Bug Fix holds at Reproduce and Verify until an explicit approval is given, recorded with the account that gave it.

step 2

Reproduce

A fix built on the wrong reproduction fixes the wrong thing. You confirm the recipe matches the reported issue before any analysis starts.

what you review

  • Exact steps required to trigger the bug
  • Expected versus observed behavior
  • Relevant environment details (version, OS, configuration)

no rejection path · approve to continue

step 5

Verify

The reviewer reports what ran, what passed and what failed. You decide whether the fix closes. Reject it and the run goes back to Fix.

what you review

  • The reproduction recipe from the reproduce step
  • The regression test added in the fix step
  • The project's existing test suite at the relevant level

reject → back to Fix

gates the engine checks without you

  • Complete closes Bug Fix only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Bug Fix?

make it yours

How do you customize Bug Fix?

Once installed, Bug Fix is a workflow in your workspace. Ask your AI to change Bug Fix in plain words; the edit lands on the one step that needs it.

Claude Codeexample

new chat

Add an approval to Analyze so I sign off on the proposed fix before any code changes.
workflow_step_update · Bug Fix
Done. Bug Fix in your workspace now has the change, and every new run follows it.

more example prompts

  • "Add an approval to Analyze so I sign off on the proposed fix before any code changes."
  • "After Verify, add a step that writes a one-paragraph release note for the fix."
  • "In Intake, also require a severity: low, medium, high or critical."
the difference

Bug Fix: without a workflow vs with it

  • An urgent fix ships straight to production because no one had time to review it
  • The same bug returns later because the root cause was never written down
  • Each developer triages bugs differently, so severity and handling are inconsistent
  • The Bug Fix process lives in a prompt, and each run follows it a little differently
  • The AI drives through Reproduce and Analyze first, then pauses at an approval step before the fix is closed out
  • Every step (Intake, Reproduce, Analyze, Fix, Verify) is logged automatically, so the root cause and the audit trail are already there
  • The AI drives the same six-step triage every time, from intake through verified resolution
  • Your AI receives the 6 stored steps one at a time, and the run holds at Reproduce and Verify until an explicit approval is given
questions

Bug Fix template FAQ

What is the ConvOps Bug Fix template?

The ConvOps Bug Fix template makes your AI coding agent resolve a bug the same way every time: check the report is actionable, reproduce it, find the root cause, apply a surgical fix with a regression test, then verify. It stops twice for you, and a failed verification sends it back to Fix.

What happens if the bug cannot be reproduced?

In ConvOps, the Reproduce step tells your AI to stop and report that finding explicitly instead of guessing, because an irreproducible report needs clarification, not speculation. The report goes back to you, and the run holds at the Reproduce approval until an explicit approval is given that the reproduction matches the reported issue. Analysis and code changes come only after that.

Does the template require a regression test?

Yes. The ConvOps Fix step asks for a regression test that fails on the unfixed code and passes on the fixed code, and keeps the edit surgical: no refactoring of adjacent code and no renamed unrelated symbols. Verify then runs that test together with the reproduction recipe from Reproduce and the project's existing test suite at the relevant level.

What happens when verification fails?

ConvOps sends the run back. The reviewer at Verify reports what was executed, what passed and what failed, and rejects the step if any check fails. The workflow then returns to Fix, the gap is fixed there, and verification runs again. Complete comes only after Verify is approved, so a failed check never closes the bug.

Which task type does it attach to?

Bug. Once installed in your ConvOps workspace, the Bug Fix template applies to the bug task type, so a new bug starts on this workflow and your AI receives Intake as its first step. Intake checks for a specific title, a one-line summary of the incorrect behavior and the observed context, and asks you to clarify before advancing if any is missing.