handoff-prompt-stale-user-hint-newer-statelisted

Gate execution of a structured runbook/handoff/plan prompt behind an AskUserQuestion when the user explicitly hints that newer state (issues filed, PRs merged, probes shipped) has landed since the prompt was authored. Use when: (1) the user invokes "execute docs/handoffs/session_NNN_*.md" or "run this plan" or "implement this ADR" AND adds an inline aside like "but please be aware of #642, #662, #663" / "watch out for PR #N" / "FYI #issue landed since this was written"; (2) before executing, a scan reveals issues/PRs in the user's hint list were filed/merged AFTER the prompt's authoring timestamp; (3) the newer artifacts could materially change what the prompt should do (e.g., a P1 issue surfacing that the prompt's design decision needs revisiting, a probe correction flipping a verdict, a sibling PR's merge claiming an ID the prompt reserved). Default behavior to avoid: execute the prompt verbatim and paper over the divergence in a post-merge comment. Correct behavior: pause, fetch current state of each hinte
wan-huiyan/agent-traffic-control · ★ 2 · AI & Automation · score 79

Install: claude install-skill wan-huiyan/agent-traffic-control

# Stale handoff prompt: user hints newer state landed since authoring ## Problem You're asked to execute a structured prompt (handoff, runbook, plan, ADR, implementation spec) that was authored at time `T0`. The user's invocation includes a casual aside — "but please be aware of #X, #Y, #Z" / "watch out for PR #N" / "FYI X landed". Between `T0` and execution, those artifacts were filed or merged and they materially change what the prompt should do. The default behavior is to execute the prompt verbatim and surface any divergence in a post-execution comment. That's wrong: the user is telling you the premise has changed and is asking you to re-evaluate scope **before** executing. Failure mode: you ship the prompt's original plan, the newer state's implications get documented retroactively, and the user has to file a follow-up PR (or worse — a fix-up PR after auto-deploy) to reconcile. ## Trigger conditions Activate this skill when **all** of these hold: 1. The user's instruction has two parts: (a) "execute / run / implement [structured prompt file or runbook]" AND (b) an aside flagging GitHub issues, PRs, commits, or state-of-the-world that should be "aware of" / "factor in" / "watch out for" / "FYI." Phrasings include: - "execute X, but be aware of #N" - "run the prompt — watch out for PR #M" - "implement this, factoring in #issue" - "but FYI #N was filed since" - "remember #X is open now" 2. Before any code changes, a quick check (`gh issue vi