run-standups — Claude Code command: what it does, how to install
run-standups runs a daily MQL→SQL pipeline standup, pulling routing metrics, logging blockers and assigning follow-up actions.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/run-standups.mdWhat run-standups does
The run-standups command walks through five steps. It pulls current lead-routing numbers (volume, conversion, SLA, backlog) filtered to a segment, then builds an agenda covering wins, blockers and escalations. Each issue gets an owner and next action, a recap with dashboards goes out to the shared channel, and the resulting action items sync into the RevOps tracker ahead of the next session.
Parameters include --segment, --hosts (a comma list such as revops, marketing, sales, cs), --mode set to live or async, plus optional --interval and --notes. Data-fetch or broadcast failures get up to two retries before escalating along Lifecycle Coordinator, then Sales Manager, then RevOps Director.
The command calls the lifecycle-coordinator and sales-manager agents and the enablement-kit skill for scripts and talk tracks. Every run writes or updates a plan entry at .claude/plans/plan-<timestamp>.json, tracking tasks, dependencies and success metrics.
What it helps with
- run a daily MQL→SQL pipeline standup
- log blockers and assign action owners
- broadcast a standup recap with dashboards to a shared channel
- sync follow-up tasks into the RevOps tracker between sessions
- hold an async standup for teams that can't attend live
Example prompts for the agent
- /sales-handoff-orchestration:run-standups --segment enterprise --hosts "revops,sales" --mode async
- Run the enterprise segment standup in async mode with revops and sales as hosts
- Switch this standup to weekly cadence and flag the SLA escalation in the notes
How to install run-standups
Manually: put the files in place
.claude/commands/run-standups.mdCall it with /run-standups. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/run-standups.mdCall it with /prompts:run-standups. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/run-standups.prompt.mdManually: put the files in place
.gemini/commands/run-standups.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about run-standups
How do I install run-standups in Claude Code?
Place the command file at .claude/commands/run-standups.md.
What does run-standups do?
It runs a daily MQL→SQL standup: pulling lead-routing metrics, building an agenda with blockers and wins, assigning action owners, and sending a recap to the team's channel.
Which agents and skills does run-standups call?
It invokes the lifecycle-coordinator agent for queue status and blockers, sales-manager for coaching notes, and the enablement-kit skill for scripts and collateral.
Source text
run-standups.md · Apache-2.0
--- name: run-standups description: Facilitates daily MQL→SQL standups with shared metrics, blockers, and follow-up actions. usage: /sales-handoff-orchestration:run-standups --segment enterprise --hosts "revops,sales" --mode async --- # Command: run-standups ## Inputs - **segment** – pipeline segment or program focus for the standup. - **hosts** – comma-separated facilitators (revops, marketing, sales, cs). - **mode** – live | async to determine meeting vs async summary. - **interval** – default daily; override for weekly/bi-weekly. - **notes** – optional agenda additions or urgent topics. ### GTM Agents Pattern & Plan Checklist > Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Standups typically run **pipeline** (data prep → agenda → discussion → broadcast → accountability). If discussion capture + broadcast can run in parallel (async mode), document a **diamond** segment with merge gate in the plan header. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, schedule, task IDs, dependencies (dashboards, channels), error handling, and success metrics (response SLAs, blocker resolution %, queue depth). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for CRM report diffs, Context7 for platform docs, Sequential Thinking for retro notes, Playwright for verifying embedded dashboard links if needed. - **Guardrails**: Default retry limit = 2 for data fetch/broadcast failures; escalation ladder = Lifecycle Coordinator → Sales Manager → RevOps Director. - **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm hosts, dependencies, deliverables. ## Workflow 1. **Data Prep** – pull latest routing stats (volume, conversion, SLA, backlog) filtered by segment. 2. **Agenda Builder** – auto-generate talking points: wins, blockers, experiments, escalations. 3. **Discussion Capture** – log owner + next action per issue, reference enablement resources. 4. **Broadcast** – send recap to shared channel/email with dashboards and follow-up tasks. 5. **Accountability Tracking** – sync action items into RevOps tracker for follow-up in next standup. ## Outputs - Standup agenda doc (metrics snapshot, topics, owners). - Action log with due dates and linked dashboards. - Optional async update message for teams that cannot attend live. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `lifecycle-coordinator` – surfaces queue status + blockers. - `sales-manager` – adds coaching notes + follow-up expectations. - `enablement-kit` skill – links relevant scripts, talk tracks, or collateral. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., RevOps Director covering Lifecycle Coordinator) when specialists unavailable. - **Escalation triggers**: if blockers remain unresolved for two standups or SLAs keep missing, escalate to Sales + Marketing leadership per GTM Agents rip-cord playbook. - **Plan maintenance**: update plan JSON/change log whenever cadence, hosts, or tooling links change to maintain GTM Agents-grade auditability. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents