Standup Facilitate

Use this when standup is happening (or just finished) and you need structured running notes -- not a transcript, but the signal: what changed, what's blocked, what was decided, and what someone committed to doing. Output feeds directly into /client-standup-summary.

Related skills: Consumes /standup-prep output as context. Feeds into /client-standup-summary. Part of the /pm-daily-loop recipe.

---

Inputs

1. Standup prep sheet -- output from /standup-prep (paste it, or reference if same session)
2. Who's present -- team members in the room (names or roles)
3. Format -- how the team runs standup:
   • Walking the board (default) -- go story by story
   • Round-robin -- go person by person
   • Async -- paste written updates from Slack or a thread
4. Raw standup input -- what people say/report, pasted live or after the fact

Minimum: provide #4. The skill works best with all four.

---

Steps

Step 1: Set up

Load the standup prep sheet if provided. Identify:

• Stories expected to be discussed (from prep sheet's Story Status Table)
• Known blockers going in (from prep sheet's Blockers to Raise)
• Questions the PM planned to ask (from prep sheet's Questions to Ask)

If no prep sheet is provided, proceed without it. Do not error.

Confirm the format. If walking the board, organize capture by story. If round-robin, organize by person. If async, parse the written updates as-is.

Step 2: Capture

As standup input comes in (pasted live or after), extract signal into four categories:

Status changes -- any story that moved since yesterday.

• Format: (Story): (old status) -> (new status) -- (reason or detail)
• If the old status is unknown, write (Story): now (status) -- (detail)

Decisions made -- anything the team agreed on during standup.

• Format: (Decision) -- decided by (who)
• Include scope changes, priority shifts, approach changes, and "let's skip that" calls

New blockers -- blockers surfaced during standup that weren't in the prep sheet.

• Format: (Story/item): blocked on (what) -- needs (who) to (action)
• If a prep-sheet blocker was resolved, note it: (Blocker): resolved -- (how)

Action items -- things someone committed to doing, with a name and a deadline.

• Format: (Action): (who) will (do what) by (when)
• If no deadline was stated, flag it: (Action): (who) will (do what) -- [no deadline stated]

Do not invent. If something wasn't said, don't infer it. Silence on a story is captured in Step 3, not here.

Step 3: Surface gaps

Compare what was discussed against the prep sheet (if provided):

• Not discussed: Stories from the prep sheet that never came up. List them.
• Questions not asked: Questions from the prep sheet that weren't raised. List them.
• Unresolved blockers: Blockers from the prep sheet that weren't addressed. List them.

If no prep sheet was provided, skip this step.

For each gap, add a one-line recommendation:

• "Raise async in Slack" / "Follow up 1:1 with (person)" / "Monitor -- may resolve itself"

Step 4: Produce standup notes

Assemble the final output:

---

Standup Notes | (date)

Present: (names) Format: (walking the board / round-robin / async)

Status Updates

• (Story): (status change or current state) -- (detail)

Decisions

• (Decision) -- (who decided)

Blockers

• (Story/item): (blocker) -- needs (who) to (action)
• (Resolved): (blocker) -- resolved via (how)

Action Items

• (Who) will (do what) by (when)

Not Discussed (omit if everything was covered)

• (Story/question/blocker): (recommendation)

---

How it pairs

/standup-prep -> PM walks into standup -> /standup-facilitate -> standup notes -> /client-standup-summary

The standup notes output is the primary input for /client-standup-summary. The client summary translates the notes into jargon-free, client-appropriate language.

---

Frequency

Daily during active engagements. Takes 2-5 minutes depending on whether input is live or pasted after.