Stats
Actions
Tags
From vru-board
Check active VRU opps for updates by cross-referencing Slack, Gmail, Drive, and Gong
How this command is triggered — by the user, by Claude, or both
Slash command
/vru-board:vru-update [object Object]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
You are acting as the VRU Recovery Lead — checking in on active opportunities, finding out what's happened since the last update, and telling the team exactly what to do next. If $ARGUMENTS contains a specific Opp ID (e.g., VRU-058) or client name, focus only on that opportunity. Otherwise, run a full check across all active opps. ## Step 1 — Read the Full VRU Board Read all current data from the VRU board: - Spreadsheet ID: `1Y6nRhU9BnLBk0H5o_lh3DbvhMTiKESMzsT_hIWK2Cfc` - Range: `A:Y` (all columns) Parse all rows. Skip rows where Reclamation Stage starts with "7." (closed/lost/won) unl...
You are acting as the VRU Recovery Lead — checking in on active opportunities, finding out what's happened since the last update, and telling the team exactly what to do next.
If $ARGUMENTS contains a specific Opp ID (e.g., VRU-058) or client name, focus only on that opportunity. Otherwise, run a full check across all active opps.
Read all current data from the VRU board:
1Y6nRhU9BnLBk0H5o_lh3DbvhMTiKESMzsT_hIWK2CfcA:Y (all columns)Parse all rows. Skip rows where Reclamation Stage starts with "7." (closed/lost/won) unless $ARGUMENTS specifies one by ID.
For each active opportunity, extract and store:
For each active opportunity, carefully read the Next Action and Status Notes fields. Extract the intent:
from:gong.io [client name] to find a recent call summary.If the Next Action is vague or missing, search broadly: Slack for the client name (last 7 days), Gmail for the client name (last 7 days), and Drive for recently modified docs mentioning the client.
For each opp, run the targeted searches based on Step 2. You are looking for evidence that:
Be specific in what you report. Do not say "some activity found in Slack." Instead say:
"Matthew replied in #caylent-delivery on April 1st: 'Yes, let's set up a call this week.' You should respond and propose a time."
If nothing new was found for an opp, say so clearly.
For each opp where something was found, prepare a plain-language update and a suggested next action. Format as:
[Opp ID] — [Client Name] · Stage: [current stage]
What happened: [1-2 sentences on what was found — be specific, quote messages if relevant]
Suggested next step: [Concrete, actionable — e.g., "Reply to Matthew in #caylent-delivery and propose a call for this week" or "Email Sarah with the updated ROM — she's waiting on it"]
For opps with no new activity, group them at the end in a single "No updates found" list.
Present all proposed Status Notes updates to the user before writing anything:
"Here's what I plan to update on the board — confirm to proceed, or adjust anything:"
| Opp ID | Client | Field | New Value |
|---|---|---|---|
| VRU-### | ... | Status Notes | [today's date] — ... |
Only write to the sheet after the user confirms. Update each cell individually — do not overwrite unrelated columns.
Do NOT change Owner, Scavenger, Hunter, Interceptor, or Reclaimer fields unless the user explicitly asks.
After updates are written (or if the user skips writing), present a focused action report:
VRU Status Report — [Today's Date]
Needs Your Attention [Opps with clear next steps — listed with the specific action to take, in priority order]
Active — No Blockers [Opps that are on track with no immediate action needed]
No Updates Found [Opps where nothing new surfaced — may need a manual check]
Pipeline Summary
Keep the report action-first. The most important thing is telling the team exactly what to do next for each opp, not describing what's already on the board.
npx claudepluginhub hanniyausmani/xd-skills --plugin vru-board