jamillazarev Load the opsinist skill (SKILL.md) and run this flow — the procedure is in self-maintenance.md.
Something went wrong, or made the work harder than it needed to be. You do not have to know whose defect it is — that is the first thing this decides, and it decides it from the evidence rather than asking you to classify your own frustration.
Friction in your project becomes a field note in _ops/FIELD-NOTES.md, one line, swept at the next status check; a second occurrence earns a task with both occasions named. Friction in the skill operating it is assembled from evidence — version, flow, symptom, the run record, the state of the files involved — de-identified, and written whole to a file outside your repository, with its path said out loud and the ways to send it named. Publishing is yours: the file is made here, you post it.
Args: $ARGUMENTS