← ClaudeAtlas

feedbacklisted

Use when receiving feedback on your work — review findings, user corrections, audit results, external reviewer notes — to triage by authority, adjudicate each point on evidence, integrate without regressions, and close the loop with the source. Evidence flips positions; assertions don't.
davidlee/doctrine · ★ 1 · Code & Development · score 69
Install: claude install-skill davidlee/doctrine
# Feedback An interrupt procedure for the receiving side of feedback. It begins when feedback arrives and ends when the loop is closed: every point integrated, contested, or explicitly parked — never silently dropped. **What counts as feedback:** asserted claims from a source with intent — a human correction, a reviewer's findings (human or agent), an audit result. **What doesn't:** mechanical signals. A failing test, CI red, or lint output is an *observation*, not an assertion — diagnose it (see the `rigour` skill's differential diagnosis), don't "respond" to it. Two failure poles, both defects: - **Capitulation** — flipping position because someone asserted otherwise. "You're right" followed by unexamined rework is not integration; it swaps your errors for theirs and teaches the source nothing. - **Entrenchment** — defending prior conclusions reflexively, demanding the source prove what you could check yourself, litigating every correction. The rule that resolves both: **positions move on evidence, not on assertion — in either direction.** You may not flip on an unexamined claim, and you may not hold on unverified recollection. ## Authority - **Instructions bind.** What to *do* is the source's call (subject to your ordinary duty to flag consequences). Adjudication below applies to claims about what is *true*. - **User-supplied material and empirical knowledge outrank your recall.** Pasted documents, reported observations, domain knowledge: ground truth