plugin-feedback ยท diff
git:20260724.ba2c70f to git:20260919.a9f7da5
9 added, 7 removed. Audit A to A.
---
name: plugin-feedback
- description: "Produce factual development-skills feedback or ingest a report to apply only evidence-backed simplifications."
+ description: Write development-skills feedback from observed work, or assess a report for useful simplifications.
user-invocable: true
argument-hint: "produce | ingest <report-path>"
---
# Plugin feedback
- `produce` writes `docs/reports/development-skills-feedback-YYYY-MM-DD.md` with the task context, plugin/skill actions, observed outcomes, friction, and reproducible eval ideas. Record events and evidence, not private reasoning.
-
- `ingest <report-path>` treats the report as a hypothesis. Change the plugin only when an instruction is demonstrably wrong or repeatedly wasteful, and the fix is simpler than the current text.
-
- Prefer deletion or merging. Do not add an exception for one model mistake.
+ `produce` writes `docs/reports/development-skills-feedback-YYYY-MM-DD.md` from the current session.
+ Include the task, used capabilities, observed delays or errors, evidence, and reproducible improvement ideas.
+ Explain decision reasons. Do not include private reasoning traces or invent token and time measurements.
- Add an eval only when the Pydantic schema can observe its outcome. Tag the owning paths so normal checks select it only when relevant. Report fixes, rejected suggestions, changed files, and verification. Expect most suggestions to be rejected.
+ `ingest <report-path>` treats the report as claims to verify against the current files and observed behavior.
+ Apply changes within the user's authorization when they fix a demonstrated problem or repeated waste.
+ Prefer deletion or merging. Keep project facts and avoid a universal rule for one model mistake.
+ Add an eval only when it can expose a meaningful regression, and tag its owning paths.
+ Report changes, rejected suggestions with reasons, and verification limits.