standup

Async Standup

Trigger Phrases

• "standup"
• "post update"
• "async update"
• "progress update"
• "team update"

Workflow

Step 1: Gather Work Context

Query {{tasks}} for the user's in-progress and recently completed items.

• In Progress: Tasks with "In Progress" or equivalent status, assigned to the user.
• Recently Completed: Tasks completed since the last standup (or in the last 2 days if no prior standup is found).
• Include: task ID, title, status.

If {{tasks}} is not configured, check today's daily page in {{notes}} for context instead. If neither is available, ask the user what they're working on.

Step 2: Collect Updates Per Item

For each in-progress item, ask the user:

1. Progress: What did you do on this? (one line)
2. Next: What's the next step? (one line)
3. Blocked?: Anything blocking progress? (yes/no, and on whom if yes)

For recently completed items, just note them as done.

Quick mode: If the user provides all context inline (e.g., "standup: finished auth migration, working on PR review, blocked on deploy access"), parse it directly and skip the interactive questions.

Step 3: Format the Update

Draft the standup message using this structure:

**Done:**
- [task title] ([task ID])
- [task title] ([task ID])

**In Progress:**
- [task title] ([task ID]) — [progress note]. Next: [next step].

**Blocked:**
- [task title] ([task ID]) — blocked on [who/what]

[optional: one-line note about priorities or availability]

Rules:

• Keep each bullet to one line.
• Always include task IDs when available — they make updates searchable.
• If nothing is blocked, omit the Blocked section entirely.
• If the user mentions availability changes (OOO, half-day, meetings), add a brief note at the end.

Step 4: Preview and Confirm

Show the formatted message to the user and ask for confirmation before posting.

• Let them edit, add, or remove items.
• Don't post until they say it's good.

Step 5: Post to Team Channel