How to have your AI agent write the weekly status report

Set by agentvia Claude Code (offprint-admin)Rev 12026-10-08

A weekly status report is mostly gathering: what shipped, what slipped, what's blocked, and the numbers that go with it. An AI agent that can read your tickets, pull requests, and dashboards can do that gathering in a minute and write a first draft that you only need to check. Offprint turns the draft into a page at a stable link, so the report your team reads is the one you actually reviewed, and next week's lives next to this week's.

See an example report written by an agent for a fictional team.

What you need

An AI agent connected to Offprint: Claude, ChatGPT, Cursor, or any MCP client. See setup for every client.
A way for the agent to see the week's work. That can be another MCP connector (for your issue tracker, GitHub, or analytics), or simply notes and exports you paste into the chat.

1. Give the agent a fixed shape

Readers skim status reports, so a consistent structure matters more than prose. Ask for the same sections every week:

Write this week's engineering status report for the Platform team. Start with a three-sentence summary. Then sections for Shipped, In progress (as a table with owner, status, and expected date), Blocked (with the decision needed and by when), Risks, Metrics (this week vs. last week), and Next week.

Save that prompt somewhere you can reuse it. In Claude Projects or a ChatGPT project, put it in the project instructions so every chat starts with it.

2. Feed it the week's facts

The agent is only as accurate as what it can see. Point it at real sources:

Use the issues closed this week in the Platform project, the PRs merged to main, and the incident log. Here are this week's dashboard numbers: deploys 42, incidents 0, p95 checkout latency 540 ms.

If something isn't in a source, tell the agent not to guess: "Leave a TODO where you don't have data." It's much easier to fill a gap than to catch an invented number.

3. Review, then publish

Read the draft in the chat and fix anything the agent got wrong. Then:

Publish this to Offprint in the Status reports project, titled "Platform status, week of Oct 5". Give me the link.

The agent calls publish_document and returns the page's address and a permanent short link. The page shows the report's tables, headings, and links cleanly, and its imprint says it was set by an agent through your client, so readers know how it was made.

Post the link in your team channel or include it in the weekly email. Public documents are unlisted: anyone with the link can read them without an account, and they never appear in search engines. For reports that shouldn't leave the company, ask for a private document and share the Status reports project with your team, so everyone in it can open every week's report.

5. Let people respond in the margin

Status reports raise questions: "Why did the re-index slip?", "Who owns the gift card decision?" Add your team to the project as commenters, and they can ask on the exact line. Before next week's report, ask the agent:

Read the comments on last week's status report, answer the ones you can from the data, and list the ones that need a person.

Tips

One document per week, in one project. The project becomes a running history that anyone can scroll back through.
Keep the summary honest. Ask the agent to lead with the most important change, even when it's bad news. A report that opens with a slip gets read.
Reuse last week. "Compare with last week's report and call out what changed" helps the agent spot items that quietly stalled.