Learn from mistakes

learn-from-mistakes-axi runs a retro: it reads a project's records of past work, its own agents label and judge them, and it counts the causes that repeat. You start it and read the result to the user. Never judge a record yourself, and never edit the sources or instruction files: a change is the user's call.

You do not need it installed: run npx -y learn-from-mistakes-axi <command>. If its output shows a command starting with learn-from-mistakes-axi, run it as npx -y learn-from-mistakes-axi ... instead.

1. No .learn-from-mistakes.yaml in the project? Run npx -y learn-from-mistakes-axi init.
2. Run npx -y learn-from-mistakes-axi doctor. Fix each fail line with the fix: line under it, then run doctor again.
3. Run npx -y learn-from-mistakes-axi retro --wait 8m. While the run is still running, run npx -y learn-from-mistakes-axi attach (or status) until it ends.
4. Read the run's report.txt (npx -y learn-from-mistakes-axi report prints its path as report_txt) and tell the user what it says in plain words.
5. If sign-off is installed and signoff is not off, use sign-off's skill on the run's decisions (the whole report goes there only with signoff_report: on, or signoff report); else ask the user the questions in section 7 of report.txt.
6. Once the user has made a change, record it with npx -y learn-from-mistakes-axi change applied --proposal <run>:<n> --ref <git sha>; it records the fix's check command (--check sets another), and the next retro checks whether it worked.

One failure: an incident

When the user wants to go deep on one failure, not on what repeats, run npx -y learn-from-mistakes-axi incident "<what failed>" --evidence <path> --wait 8m instead of the retro. <what failed> is the user's own words, a file, or a GitHub PR or issue link; repeat --evidence for each file, screenshot or link the user names. The run reads only those and the project context. Read its report.txt (the next: line names it) and tell the user, in order: the timeline, each root cause with its why chain and cost, why no check caught it, how to avoid it now, and each fix with its owner, priority and due date. Then say what section 7 did not check: the agents cannot see a screenshot, so ask the user to describe it in text. Once the user makes a fix, record it with npx -y learn-from-mistakes-axi change applied --proposal <run>:<n> --ref <git sha>; npx -y learn-from-mistakes-axi incident --status then runs the check of each shipped fix and lists the fixes still open. A fix stays open until its check passes.

The retro method