Archive / Hand off a bug without becoming the copy-paste person

Hand off a bug without becoming the copy-paste person

Create a work packet that makes reproduction, scope and verified completion clear.

For: Solo founders, Small business owners

Topics: Agent management, Productivity

A good bug handoff lets someone else reproduce the problem without you sitting next to them. The same packet should make it clear what they are not allowed to change.

1. Make the packet

Prompt

Turn [sanitized bug notes] into environment, exact steps, expected behavior, observed behavior, smallest repro, allowed scope and do-not-touch areas. Ask for only blockers to reproducing it. Remove production data and secrets.

2. Agree what done looks like

Prompt

Draft acceptance checks for [bug] with a normal case and a failure case. State the baseline and how to verify after a change. Separate source inspection from tests that must actually run. Do not implement or claim verification.

3. Review the handback

Prompt

Compare [report] against the original packet. Return verified changes, tests with evidence, untested cases, remaining blockers and the next owner. A merged change or ‘done’ comment by itself does not count as a passing test.

Try it on one example

If a save button claims success but loses a setting after refresh, hand over one fictional setting, the exact reload steps and where to verify that the value persisted.

Inspired by Matt Pocock’s reusable engineering skills: https://github.com/mattpocock/skills.

Use it for: Create a work packet that makes reproduction, scope and verified completion clear.

Back to the archive