Skip to main content

metrics.daily-standup

Type: commands | Track: Enterprise

Enterprise daily standup ceremony. Outputs sprint health score, top 2 objectives status, DORA quick view, and a single recommendation. Autonomous local-first — works offline. Delegates to observability-engineer. Exempt from PO+CA coordination.

Quick Start​

# Run daily standup
/metrics:daily-standup

# Override sprint
/metrics:daily-standup --sprint CloudOps-S1

Output Template​

The standup follows a fixed ~43-line template:

═══════════════════════════════════════════════════════════════
  DAILY STANDUP — {sprint} | {date} | Day {N} of {total}
═══════════════════════════════════════════════════════════════

  SPRINT HEALTH: {score}/100 — {status}

  YESTERDAY: [top 3 completed items, no file paths]
  TODAY:     [top 3 planned items]
  BLOCKERS:  [blockers or NONE]

  OBJECTIVES: [KR1 status] | [KR2 status]
  DORA:       DF:{value} | LT:{value} | CFR:{value} | MTTR:{value}

  RECOMMENDATION: [single action for HITL]
═══════════════════════════════════════════════════════════════

Benefits​

  1. Exempt from PO+CA coordination — reads existing CSV and coordination log data only (no architecture decisions)
  2. Local-first — works offline via git log and CSV files; cloud data is enrichment only
  3. Fixed template prevents verbose output anti-pattern — exactly the information HITL needs, nothing more
  4. DORA quick view from docs/static/data/dora.csv — sprint health in a single glance

When to Use​

AttributeDetail
PersonaHITL / Engineering Manager
TriggerDaily standup ceremony — every morning session start, or when the manager needs a quick sprint health snapshot before a stakeholder meeting
Business ValueSprint health, DORA quick view, and top 2 objectives in a fixed 43-line format — gives the HITL the information needed to make the day's prioritization decision in under 2 minutes
FrequencyDaily

Example: As an Engineering Manager (HITL), I need the daily standup output because I start each session by reviewing sprint progress and blockers before directing the agent team's work. I run /metrics:daily-standup which reads stories.csv, dora.csv, and recent coordination logs to produce the sprint health score, yesterday/today/blockers summary, DORA metrics, and a single recommendation — all in the fixed 43-line template.

Coordination-exempt command. Reads existing data only — no architecture decisions.