Skip to content

Agent Operating Guide

/coach-workflow-monitor

A supervisory, read-only sweep of step status across a workflow, item, or portfolio that flags overdue, stalled, and at-risk work and names who to nudge.

Sweep step status across a scope of workflows, one workflow, an item’s workflows, or a whole portfolio of items, and tell a lead exactly where attention is needed. The skill classifies every step (overdue, due-soon, stalled, awaiting-reviewer, dependency-unblocked, or on-track), names the specific person to nudge for each, and can compute the critical path to a workflow’s terminal step. It’s read-only: it never mutates and never sends the nudges itself.

When you’re watching other people’s work: a lead, PMO, or cycle owner checking progress across a portfolio or quarter, finding stalled or overdue work, or seeing what’s at risk. To triage your own assigned steps instead, use /coach-workflow-scan, which is self-scoped.

Flag Required Notes
--workflow <id> · --item <id> · --items <id,...> · --item-type <slug> · --portfolio <id> One scope The scope to sweep. The first one set wins; if none, the skill asks.
--stale-days <n> No Days of no activity that count as stalled. Default 5.
--due-horizon-days <n> No Days-until-due that count as due-soon. Default 3.
--critical-path No Also compute the chain of not-yet-done steps gating the terminal step.
--include-on-track / --include-completed No Show on-track or completed steps too. Both default off.
--headless No Suppress the interactive handoff; set automatically inside a loop.

/coach-workflow-monitor --item-type audit --critical-path fans out across every audit item’s workflows in parallel, classifies each step into the most-urgent bucket that applies, and returns a sweep grouped by bucket, overdue, due-soon, stalled, awaiting-reviewer, unblocked, with the person to nudge on each row and the critical path on the summary line. The canonical daily version runs it on a loop: /loop 1d coach-workflow-monitor --item-type audit.

  • It recommends, you act. The skill never messages anyone: it names the target user for each step and hands you off to the coach-notify skill to send the actual nudge.
  • Reviewer vs. assignee. Every bucket targets the step’s assignee except awaiting-reviewer, which targets the approver. Naming the wrong one nudges someone with nothing to do.
  • Not /coach-workflow-scan. Scan is self-scoped: it triages your own steps into doer-states for you to act on. Monitor is supervisory: it sweeps everyone’s steps against SLAs for a lead to chase.
  • Portfolio scope needs structure. --item-type sweeps every item of a type; --portfolio resolves a portfolio item’s member links. If neither exists, the skill asks you to pick a single workflow or item.