loom-review-responselisted

# loom-review-response Review response is a feedback-handling playbook. It turns incoming comments into checked technical work instead of blind acceptance, performative agreement, or untracked follow-up. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-tickets`, `loom-audit`, `loom-evidence`, `loom-specs`, `loom-research`, `loom-constitution`, `loom-retrospective`, and `loom-knowledge`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. Incoming feedback is input to judgment. It is not automatically a durable record fact. ## Use This Playbook When Use this playbook when: - a human gives multi-item feedback - an audit finding needs disposition - PR comments or external review suggestions arrive - a worker reviewer challenges implementation or evidence - feedback seems plausible but may not fit the codebase - unclear feedback could lead to wrong implementation if guessed Skip it for trivial local comments that can be fixed immediately without changing scope, behavior, evidence, or ticket state. ## Route Use this route: ```text collect -> clarify -> verify -> classify -> act -> prove -> disposition ``` ## Collect Gather the feedback as concrete items. For each item, preserve: - source of feedback - linked file, line, record, evidence, audit finding, or PR comment - requested change or concern - affected ticket `ACC-*`, spec `REQ-*` or `SCN-*`,