handle-feedback

• SKILL.mdcore · 13,383 bytes
• SKILL.mdcore · 13,383 bytes
• SKILL.mdcore · 13,383 bytes

# Handle feedback

## Goal

Every piece of human feedback is written down once, verbatim, before anything is done with it, so the owner's words are never paraphrased away and every later memory entry can be traced back to them. Each piece then becomes exactly what it should and nothing more. That means a fact or rule when the model would otherwise repeat the mistake, a deterministic test or a verifier so code catches the mistake from then on, and updates to the existing entries the feedback contradicts or confirms. Three subagents make those three decisions separately, each from the same inputs and each writing to its own files, so no single reading of the feedback can quietly skip one outcome or overwrite another's work. Nothing is left pending: when this skill ends, the feedback entry says what was kept and where, or why nothing was. The rejected artifact is regenerated with the new memory applied, so the owner sees the correction take effect in the same request rather than in the next one. The repo measures itself by fewer corrections over time, and this skill is the only place a correction is turned into something that prevents the next one. A correction that is logged but never becomes a check is the failure this skill exists to prevent.

## Objective

Log the feedback as an FB entry holding the owner's verbatim words and the context in which they were said. Launch the three feedback subagents, fact, test and update, with the same inputs and with write scopes that do not overlap, so they can run at the same time without one undoing another. Stitch their three reports into one consistent memory: point each new fact or rule at the test or verifier that now checks it, apply the operations the update agent could only report, and mark every superseded entry. Fill the disposition line so the log says what this piece of feedback became. Regenerate the rejected artifact with the new entries applied and confirm the new test passes on it. Regenerate the footprint and run the full suite until it is green. The skill is done when the feedback log, the memory files, the tests and the artifact all agree with the owner's words.

## Tasks

1. Append the feedback to `memory/feedback-log.md` as a new entry, numbered as the highest existing FB number plus one, in the exact shape below. The verbatim line holds the owner's words unchanged, including typos, because the admission checks and later audits depend on what was actually said. The context line names the run, the artifact path and where the artifact was rejected or confirmed, so a future reader can find the evidence. Write `disposition: pending` and nothing else on that line; it is filled in task 6.
   ```