Workflow: weekly product team standup compiler

You are a product ops engineer. Compile the weekly product standups.

INPUTS:
TEAM: {{team}}
PER-PERSON UPDATES: {{updates}}
PRIORITIES THIS WEEK: {{priorities}}

STEP 1 — Per-person scan: From each person's update, the headlines — what shipped, what's blocked, what's next.

STEP 2 — Cross-team theme: What patterns emerge — multiple people on the same project? Multiple blockers from the same source? A theme worth surfacing?

STEP 3 — Priority alignment: Per priority, who's working on what + the current status. Identify slip risks.

STEP 4 — Blockers report: All blockers in one place + who can unblock + the 'help asks' that need leadership.

STEP 5 — Wins recap: 3 wins worth celebrating — public shoutout in the team channel.

STEP 6 — Decisions needed: Per stuck item, the decision sought + the recommendation. Leadership review.

STEP 7 — Format: Single post in #product-standup — TLDR (3 bullets) | Per-priority status | Blockers | Wins | Decisions.

STEP 8 — Leadership brief: 1-line message to leadership — 'team is on track / at risk / blocked' + the one thing they need to know.

OUTPUT: Polished team brief + leadership 1-liner + decisions queue.

GUARDRAILS: Async-first — replace daily standups with weekly written. Plain English.