Sequential AgentOperationsintermediate

Weekly Status Rollup Writer

Acts as · Operations Manager

Turns scattered team updates from Slack, docs, and standups into one exec-ready weekly rollup. Organizes the raw dump into wins, progress by workstream, risks with severity, decisions needed, and slippage: flagging contradictions instead of smoothing them over: then writes an audience-calibrated report with a 3-bullet TL;DR, per-workstream sections, a risks table, and explicit asks. Skimmable in under two minutes. Pure standalone, no tools or tables required.

A single-purpose agent that runs an ordered list of tasks against your tools, knowledge and tables, the same way every run.

Official~2 min setupby Akshay Gupta
How it works

Inputs in, an ordered run, a result out.

A Sequential Agent takes typed inputs, runs its tasks top to bottom against your tools and tables, and returns a structured result, the same way on every run.

Typed inputs
Values you pass in, validated before the run spends anything.
2 tasks
Each task runs in order, passing its output to the next.
Runs standalone
No external tools or tables needed.
Result + trace
A structured output, with every step recorded.
The run loop
Read→Plan→Act→Check→Write→Tracerepeats until done

What's inside

Everything this template installs, by name.

Tools & tables
Runs standalone, no external tools or tables required
Tasks
2 ordered tasks

What it takes in

The inputs you provide on each run, validated before anything executes.

InputTypeRequired
Team UpdatesupdatesDumpLong textRequired
AudienceaudienceShort textOptional
WeekweekLabelShort textOptional
The work, step by step

2 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

  1. 01
    Organize the raw updates. Read everything in {{updatesDump}} and sort it into a structured digest: wins worth calling out, progress grouped by workstream, risks and blockers each with a severity (High / Medium / Low) and a one-line rationale, decisions that need to be made and by whom, and what is slipping versus plan. Where two updates contradict each other, flag the contradiction explicitly rather than smoothing it over: show both versions side by side. Do not invent progress, dates, or metrics that are not in the updates; if a workstream is silent, say so. Present readably, never JSON.
    Expected output
    A readable digest with no JSON and no code blocks under six headings: Wins, Progress by Workstream (one subsection per workstream), Risks & Blockers (each with a High / Medium / Low severity and a one-line rationale), Decisions Needed (each with who should decide), Slipping vs Plan (what is behind and by how much, if stated), and Contradictions & Gaps (conflicting updates shown side by side, plus any workstreams with no update).
  2. 02
    Write the rollup. Using only the digest from Task 1, write the weekly status report calibrated for {{audience}}: more strategic and metric-led for an exec team or board, more celebratory and people-focused for an all-hands; if no audience is given, write for an exec team. Title the report with {{weekLabel}} if provided. Open with a TL;DR of exactly 3 bullets: the week's headline, the biggest risk, and the most important ask. Then write one short section per workstream (2 to 4 tight bullets each), a risks table, and an Asks section with explicit, owner-addressed requests. Keep the whole report skimmable in under 2 minutes: cut anything that does not change what the reader knows or does. Do not bury or soften the contradictions and slippage flagged in Task 1. Present readably, never JSON.
    Expected output
    A ready-to-send status report with no JSON and no code blocks: a title line (including the week label if provided), TL;DR (exactly 3 bullets: headline, biggest risk, most important ask), one short section per workstream (2 to 4 bullets each), a Risks table with columns Risk, Severity, and Owner / Mitigation, and an Asks section listing each explicit request and who it is addressed to. The whole report readable in under 2 minutes.

Related templates

AI Employee
Incident Command And Change Operations Coordinator Template
Operations AI employee for service operations, incident triage, stakeholder updates, postmortem preparation, and change risk review. Includes three relational tables, AI-enriched columns, two operations knowledge bases, and four specialist embedded agents.
Sequential Agent
Inbox Triage Assistant
Triages a pasted batch of emails into act-now, reply-today, delegate, read-later, and ignore buckets against your stated priorities, then drafts the urgent replies for you. Returns a triage table with one-line reasons, flagged commitments and deadlines, ready-to-send reply drafts, and delegation notes. Pure standalone, no inbox connection required.
Sequential Agent
Meeting Notes to Action Items
Turns raw meeting notes or a transcript into clear decisions, owned action items, and a ready-to-send follow-up email. Paste your notes, get a crisp summary for people who missed it, an action-item table with owners and due dates, and a recap email. Pure standalone, no tools or tables required.