Address Feedback With Replies

Triage, fix, ship, and answer the Slack threads the user pointed at, in one pass. This is review-latest-feedback aimed at a specific set of threads instead of the whole sweep. That skill owns the Slack contract: the 👀 / ✅ / 🎫 reactions, the one-sentence reply and its wording, which channels are fair game, the "leave it alone" rules, and Steve's :upvote:. Read it first and follow it. This file adds only what is specific to working a given thread.

Use the connected Slack integration for every read and write, and confirm the profile is Steve before the first write. Never drive Slack through a browser or computer use.

1. Read everything first

• Read the parent message and every reply. Open every screenshot, file, video, transcript, and linked recording; the error text there is often the whole diagnosis.
• Fetch linked artifacts through their own connector or public URL. If one is permission-gated or expired, say so separately from "absent": ask for access or a fresh link only if you truly need it, otherwise carry on and note the limit.
• If someone in the thread already named the cause, shared a repro, linked a fix, or said it's being handled, verify that and build on it. Never ask the reporter to repeat it.
• If the report has a run ID, inspect that persisted run, its events and tool cards first. Don't ask for the prompt or last tool card until that is exhausted.
• Search recent Slack, local Git history, and merged PRs for repeat reports and existing fixes before editing. A repeat of something already fixed is a regression: find why the earlier fix didn't hold.
• Read address-feedback, concurrent-agents, and verifying-changes. Re-read dirty files and keep peer work intact; never reset, stash, or overwrite it.

2. Decide: fix, build, or needs a person

Apply the decision gate before reacting or editing, using the buckets in review-latest-feedback: