Skip to content

Agent Operating Guide

/coach-watchlist-inherit

Propagate an issue's watchlist to the watchers on every step of the workflow attached to it: idempotent, so re-running when they're already in sync changes nothing.

Keep an issue’s watchlist and its workflow in sync. When you change the watchlist on an issue, adding or removing a watcher, this skill applies the same change to the watchers on every step of any workflow attached to that issue, submitting the updates as suggestions for a human to approve. It’s idempotent: re-running when the watchlists already match produces zero changes.

After you change an issue’s watchlist and want that change reflected on the steps of its workflow, instead of editing each step by hand. Run it on a single issue, or use --batch to sweep every open issue with an attached workflow and fix any drift: good on a schedule.

Flag Required Notes
--issue <issue-id> One of the two Sync a single issue.
--batch One of the two Sweep every open issue with an attached workflow, propagating any drift.

/coach-watchlist-inherit --issue ISS-12 reads the issue’s watchlist, lists the steps on its attached workflow, and for each step whose watchers differ submits an update suggestion to match: then reports how many steps it touched and skipped. Run it again once approved and it finds nothing to change. /coach-watchlist-inherit --batch does the same across every open issue that has a workflow.

  • Idempotent. Re-running against watchlists that already match produces zero suggestions, so it’s safe to run repeatedly or on a schedule (/loop daily).
  • An issue with no attached workflow is a no-op: there’s nothing to propagate to. In --batch mode those issues are skipped silently.
  • To let one step’s watchers diverge from the parent, a specialist-only step, say, mark it independent with a step-level watchlist_independent flag or tag, and the sweep leaves it alone.