Record a short repro for coding agents instead of describing bugs in Slack

The author argues that vague bug descriptions in Slack threads give coding agents too little to work with, leading to patches that miss the actual problem. Instead, they recommend a brief, replayable repro such as numbered steps, a failing URL, a minimal network snippet, a short recording, or the relevant console stack trace. The piece stresses keeping the effort proportionate, so the repro is cheaper than guessing. It also offers a reusable template that captures surface, environment, steps, expected and actual results, and artifacts, along with rules for keeping recordings useful. Slack is positioned for routing and triage, while the agent chat or pull request serves as the artifact layer.