Skip to content

Operations · For your bots

Weekly status report

Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.

In Lobstack: Skills › Library › Add

Download Lobstack

When to use it

A weekly update is due for a team, a project or a client, or last week's exists and this one has to match it.

What your bot will do

  1. 01

    Find last week's report first (in the files, or the last document you posted) and keep its sections and their order. A report that changes shape cannot be compared with itself.

  2. 02

    Gather evidence for the period only: what merged, which tickets closed or moved, what shipped, the figures the report tracks. State the date range you used.

  3. 03

    Write four sections in this order: Done (outcomes, not activity), Numbers (each figure beside last week's, with the change), Blocked (what, on whom, since when), Next (three items at most, each with an owner).

  4. 04

    When a number moved for a dull reason — a holiday, a backfill, a renamed field — say so on the same line.

  5. 05

    Mark a section missing when its source was unavailable. Never fill it from memory or copy last week's.

  6. 06

    With three or more tracked figures, add a line chart of recent weeks in a chart fence.

  7. 07

    Post it as a document titled with the week, then reply with the one sentence a reader should take from it. Ask before sending it to anyone outside this thread.

One page. If it runs long, cut from Done, never from Blocked.

The file

weekly-status-report/SKILL.md37 lines
---name: weekly-status-reportdescription: "Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week."metadata:  title: "Weekly status report"  category: operations  tags: [reporting, status]--- ## When to use this A weekly update is due for a team, a project or a client, or last week's existsand this one has to match it. ## How 1. Find last week's report first (in the files, or the last document you posted)   and keep its sections and their order. A report that changes shape cannot be   compared with itself.2. Gather evidence for the period only: what merged, which tickets closed or   moved, what shipped, the figures the report tracks. State the date range you   used.3. Write four sections in this order: Done (outcomes, not activity),   Numbers (each figure beside last week's, with the change), Blocked   (what, on whom, since when), Next (three items at most, each with an   owner).4. When a number moved for a dull reason -- a holiday, a backfill, a renamed   field -- say so on the same line.5. Mark a section *missing* when its source was unavailable. Never fill it from   memory or copy last week's.6. With three or more tracked figures, add a line chart of recent weeks in a   chart fence.7. Post it as a document titled with the week, then reply with the one sentence   a reader should take from it. Ask before sending it to anyone outside this   thread. One page. If it runs long, cut from Done, never from Blocked.

Get Lobstack.