Turn recent complaints into fixes
Convert recent user-reported problems into reusable failure patterns, fix every confirmed match, and verify a clean final pass.
Use this when
Use this after several days of project feedback when repeated mistakes may point to similar issues elsewhere and the agent can inspect both the conversation history and the complete current project.
How it runs
- Define the lookback window and complete project surface, then collect every accessible thread in which the user reported a problem and requested a fix.
- Deduplicate the reported issues, verify their current status, and turn the concrete examples into explicit failure patterns and audit checks.
- Audit every in-scope project surface for each pattern, fix one confirmed instance at a time, and add regression coverage where practical.
- Run targeted checks after each fix, then rerun the complete pattern audit and relevant full checks before declaring the sweep clean.
Done when
✓ The issue inventory is closed and a fresh pattern audit is clean. Every reported issue and newly found match has current proof of resolution; blocked, approval-gated, or budget-exhausted items remain explicitly open.
Why it works
Recent corrections are concrete examples of the quality bar the project missed. Grouping them into failure patterns turns one-off feedback into a reusable audit rubric, while a fresh full sweep catches sibling defects and verifies the current project rather than trusting old thread state.
Implementation note
Thread access and a complete surface inventory are prerequisites. Do not infer defects from neutral discussion, reopen resolved issues without checking current behavior, or claim success while an inaccessible, blocked, approval-gated, or budget-exhausted item remains. Get approval before destructive, production, or external actions.
Source: Forward Future ↗graded C · 55/100 — how grades work →
More maintenance loops
Upgrade to current Node LTS
Move the project to the current Node LTS across .nvmrc, CI config, Dockerfiles, and engines, fixing deprecations until everything is green on the new runtime.
Upgrade dependencies one at a time
Walk through outdated dependencies one package per turn, upgrading, running the full check suite, and pinning back anything that breaks.
Triage untriaged issues to zero
Pick the oldest untriaged issue, validate it against the current build, then label it, close if obsolete, or document repro steps—one per turn until the queue empties or 12 iterations pass.