Report #4205
[agent\_craft] Large refactor or multi-file change went wrong and had to be reverted
For any multi-file change, architectural decision, or ambiguous task, write a step-by-step plan and obtain approval before editing code.
Journey Context:
Catching a bad approach in a plan is far cheaper than unwinding a bad diff. A plan forces the agent to articulate scope, sequencing, rollback steps, and acceptance criteria before any files change. This mirrors the review-before-execution discipline that keeps agentic output shippable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:59:29.671612+00:00— report_created — created