triage-findings-list ยท git:20260927.87257af ยท 2026-09-27 ยท sha256 57233a4ddb49f9aa
triage-findings-list git:20260927.87257afA
Immutable. This exact content never changes and is served at /api/v1/blob/57233a4ddb49f9aa.
--- name: triage-findings-list description: Merges findings from several reports (verification, browser testing, red team, production readiness, code review) into one numbered, deduplicated change list with traffic lights, grouped by when each change should happen and tagged with its source. Use it whenever the user asks to turn reports into a list of changes, prioritize findings, "what do we fix first", build a backlog from reviews, or decide what goes before merge and what goes later. --- # Triage findings list ## Inputs Read every report the user names, and by default every `*-report.md` in `.scratchpad/<slug>/`. Give each report a short source tag, for example V (verification against the spec), U (browser testing), RT (red team), P (production readiness). ## Build the list 1. **Deduplicate.** One change can fix findings from several reports. Merge them and keep all source tags and ids: `(RT O2, U H1)`. 2. **Write each change as an action**, not as a problem: "Wrap long words in the order list", not "Long words break the layout". 3. **Give it a light** with `traffic-light-findings`. Keep the highest light that the evidence supports. 4. **Group by timing:** ๐ด before merge (mandatory); ๐ before merge (recommended, little code); ๐ before production; ๐ technical debt; ๐ก minor improvements; accepted (no change), with the reason. 5. **Number the changes 1..N** in that order. These numbers are what the user will use to approve work, so do not change them after you share the list. For each change give: number, light, action, a short "why", the main files, and the source tags. ## Output - Save `.scratchpad/<slug>/change-list.md`. - In the chat, show the list compactly: one line per change with number, light, action and source. - Ask which changes to apply. Suggest a default: all ๐ด plus the cheap ๐ before merge. - Apply the approved changes with `execute-plan-loop` in change-list mode.