Skip to content
Agent Orchestration
Skill

/new-feedback

Log a harness lesson / post-incident so the SYSTEM improves, not just this one bug — fires on "log a harness lesson", "post-incident", "we should make this less likely", System-Evolution moments. Part of the Agentsmith harness; scaffolds a numbered docs/feedback/NNNN-*.md with

BOOST
From plugin
agentsmith
17911 skills3 hooks
Install
$ npx -y skills add PromptPartner/agentsmith --skill new-feedback --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/new-feedback

Context preview

The summary Claude sees to decide when to auto-load this skill.

Log a harness lesson / post-incident so the SYSTEM improves, not just this one bug — fires on "log a harness lesson", "post-incident", "we should make this less likely", System-Evolution moments. Part of the Agentsmith harness; scaffolds a numbered docs/feedback/NNNN-*.md with

SKILL.md

new-feedback.SKILL.md
name: new-feedback
description: Log a harness lesson / post-incident so the SYSTEM improves, not just this one bug — fires on "log a harness lesson", "post-incident", "we should make this less likely", System-Evolution moments. Part of the Agentsmith harness; scaffolds a numbered docs/feedback/NNNN-*.md with the five-stage template (R9 — numbers are never reused).
compatibility: Requires filesystem access; the fast path requires the cross-platform Agentsmith CLI.

New feedback note (harness post-incident)

The point is not to fix THIS bug — it's to change the SYSTEM so this whole CLASS is less likely (core/60). Small, specific, traceable to the incident.

When this fires

You were corrected on something a rule could have prevented; you iterated more than you should have; a human stepped in; you re-derived a decision a past session already made. After fixing the immediate thing, capture the lesson.

Absence gate

Before filing or implementing a missing-item defect, confirm absence with an exact, count-based, or untruncated result. Truncated, paginated, filtered, or summarized search output is incomplete evidence.

Fast path — if the Agentsmith CLI is available

Run `agentsmith new-feedback "short symptom"` — use `.agentsmith/agentsmith` on macOS/Linux or `.agentsmith\\agentsmith.cmd` on Windows when the command is not on PATH. It computes the next number and writes `docs/feedback/NNNN-<slug>.md` with the five-stage template, Status `open`.

Fallback — no CLI

1. Next number = (highest existing `docs/feedback/NNNN-*.md` + 1), zero-padded to 4 digits. Numbers are **never reused** (R9), even if an old entry was archived. 2. Create `docs/feedback/NNNN-<slug>.md` (Status: open) with the five stages:

  • **Evidence / symptom** — what was observed, quoted.
  • **Failure mechanism** — WHY the system allowed it (missing rule / vague instruction / absent

guardrail / unreached tool / noisy context — almost never "the model was dumb").

  • **Bounded edit** — the smallest change that prevents the whole class.
  • **Named surface** — exactly where it lands (a core rule, a hook, a verify phase, a template);

prefer a deterministic surface over prose the model can skip.

  • **Non-regression** — the check that stays red on recurrence. Until it's real, Status stays open.

Report

Name the file, then land the bounded edit on its named surface and flip Status to `applied`.

Read more
Ships withagentsmith

Proof before done. Move from vibe coding to agentic engineering. Give Claude Code or Codex your project rules, a definition of done, and checks that produce evidence.

Get the whole plugin

Other skills on agentsmith.