UUpskillHelpful AI tools for people who are not AI experts.

Operations & Planning

Weekly Status Writer

Useful when your updates live across Slack, docs, and your head and you need one clean summary by the end of the week.

Try this workflow freeCompare plans
Free
ChatGPTClaudeGoogle GeminiOpenAI Codex

Free tier workflow for Operations & Planning.

Before

Weekly updates come together at the last minute and leave out risks or important context.

After

You get a calm summary of what happened, what is next, and what needs attention.

what you start with

Won approval on homepage draft, onboarding bug still open, next week focused on analytics setup and sales enablement deck.

what you get back

This week: homepage draft approved. In progress: onboarding bug remains open. Next week: analytics setup and sales enablement deck. Watchout: bug may affect launch timing.

Copy this to start

paste into ChatGPT or Claude

Help me turn rough weekly notes into a short status update.

Audience:
[Client, manager, leadership team, internal team]

Tone:
[Calm, direct, friendly, executive, etc.]

This week:
[Wins, completed work, meaningful progress]

Still in progress:
[Open work or moving pieces]

Risks or blockers:
[Anything that may affect timing or quality]

Next week:
[Top priorities]

Asks or decisions needed:
[Optional]

Write:
1. A concise weekly update
2. A shorter summary version
3. A list of any unclear points I should verify before sending

Quick tip

Good source material usually matters more than a perfect prompt. Rough notes, bullets, or a half-finished draft are enough to begin.

Good moment

At the end of the week when progress lives across Slack, notes, and your memory.

Best input

Wins, work in progress, blockers, next-week priorities, and any decisions or asks a manager or client should notice.

What to expect

A calmer weekly update with clear sections, visible risks, and less last-minute rewriting.

Gather this first

  • What moved forward this week
  • What is still in progress
  • Any blocker, risk, or delay
  • The top priorities or asks for next week

Ways to use it

simple workflow

1. Gather the week before you write
Pull in rough bullets from messages, meeting notes, and task lists instead of relying on memory alone.

2. Separate progress from noise
Keep the update focused on movement, risks, and next steps instead of every small activity.

3. Use a predictable structure
Ask for sections like this week, in progress, risks, and next so the update is easy to scan every time.

4. Check for false calm
Make sure blockers and timing concerns are named plainly instead of getting softened away.

optional plugin or advanced install

npx upskill install weekly-status-writer

Best for

  • Weekly reporting
  • Manager updates
  • Client status notes

Review before you send

  • The update shows movement, not just effort.
  • Risks are plain enough for a busy reader to spot quickly.
  • Next steps are specific instead of generic.
  • The tone feels steady and useful, not defensive or overexplained.

Common watchouts

  • Do not hide blockers just to make the update sound smoother.
  • Skip low-value detail that does not change the picture.
  • If the audience is external, remove internal shorthand before sending.

Changelog

1.4.02026-03-22

Made the output easier to skim for busy managers.

1.3.22026-03-08

Improved treatment of blocker and risk language.