Command: chase-open-commitments

Nudge or close every open commitment and deliver the updated open-loop list.

Inputs

• Commitment log — spreadsheet or structured list of open commitments with owner, description, due date, and current status
• Review scope — which commitments to assess: all open, or filter by date range (e.g., "overdue only", "due within 14 days")
• Action threshold — criteria for nudge vs. close: e.g., nudge if due within 7 days, escalate if 14+ days overdue
• Stakeholder contacts — names and email or Slack handles for commitment owners
• Escalation authority — which commitments you can close and which require stakeholder approval

Steps

1. Extract all open commitments from the log; sort by due date and owner.
2. Flag items that are overdue or due within your action threshold.
3. For each flagged item, send a brief status nudge to the owner: confirm completion, propose a closure date, or identify the blocker.
4. For items past the escalation threshold, draft a proposed closure or handoff; note any human-required decisions (travel booking, payment, stakeholder approval).
5. Compile responses and update the log with new status, completion evidence, or escalation note.
6. Generate a summary report: total commitments, closed, in progress, blocked, and recommended next actions.

Constraints

• Do not replan or restructure commitments; only nudge, close, or escalate as-is.
• Travel booking, payment decisions, and stakeholder escalations require human judgment and approval before execution.
• Preserve the audit trail: record who was nudged, when, and what response was received.

Done when: every open commitment has been nudged, closed, or escalated with the updated log delivered to you.