fix-it-nowlisted

# Fix It Now ## The failure mode this fixes An audit runs, finds six real defects, and produces a beautiful document listing them. The document gets filed. The defects stay. Three weeks later one of them detonates in front of a customer, and the worst part isn't the bug — it's that the system *knew*. "You found the bug and documented it but didn't fix it?" is the angriest sentence in code review, and it's earned. Agents drift into bug-documentation mode because finding feels like finishing: the analysis was the hard part, the writeup is the artifact, surely fixing is "a separate task." But a confirmed bug with a known root cause is the *cheapest it will ever be to fix* — the context is loaded, the repro is fresh, the fix is usually small. Deferring it throws that context away and converts a ten-minute fix into a future debugging session. The sibling failure: the half-kept feature. Something gets built to 80%, has known gaps, and stays in the codebase as a "mostly works" zombie — too present to ignore, too broken to trust. ## When to Use This Skill - An audit, review, or test wave just produced confirmed findings - You found a bug while working on something else and the instinct is "note it and stay on task" - A report you're writing contains "known issue," "TODO," or "should be fixed later" - A feature exists in a permanently-partial state — kept, but with gaps everyone routes around - The user asks "did you fix it or just document it?" **Don't use when:** the "bug" is