Daily Standup
On the schedule you choose, a lead agent gathers recent activity and the planned queue, writes a prioritized markdown standup, and lands one inbox item where you approve and steer.
Saves you ~5.3 h / week
How it works
- Trigger
- On the “Daily standup” schedule.
- Job
- Gather activity, compose the prioritized standup.
- Outcome
- A prioritized standup with progress, plans, blockers, and decisions.
What it installs
Agents 2
-
Standup Lead
Prepares the standup and routes the day's work.
-
Daily Standup Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Daily Standup quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Daily Standup
Gather activity, compose the prioritized standup, and hand off for approval.
Documents 1
-
Standup format
The editable format the Standup Lead fills in each morning — sections, audience, tone, and channel.
Goals 1
-
Nothing stalls unseen
Every stalled item surfaces in a standup before it ages further — blockers are named, not discovered late. Success looks like: Each scheduled standup names every item with no movement (and how long it has been stalled) and is approved by the human, so no blocker reaches its second standup unnamed.
Skills 2
-
daily-briefing
Assemble a prioritized two-minute morning briefing: gather context, rank what matters, and surface the #1 thing and blockers. Adapted from anthropics/knowledge-work-plugins/daily-briefing.
-
status-report
Turn tracker activity into a leadership-ready status update: red/yellow/green health, risks, and decisions needed. Adapted from anthropics/knowledge-work-plugins/status-report.
Schedules 1
-
Daily standup
Runs the daily standup on the schedule you choose. ## Professional quality control Objective: complete the recurring Daily Standup operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Reconcile each status, owner, date, dependency, exception, and next action to the operating record. Confirm that proposed changes remain within authority. Internal communication must be decision-dense and plain, without generic AI phrasing, management filler, vague ownership, or a polished summary that omits blockers. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Folders 1
-
Daily Standup
Setup guide
How to Automate Daily Standup
A practical guide to turning daily standup into a prioritized briefing with blockers, decisions, and human steering.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.