Skill

Weekly Status Report

Transform raw work logs into a polished, stakeholder-ready weekly status report in minutes.

Goal

Convert unstructured weekly work logs into a clear, professional status report covering accomplishments, blockers, and next steps for stakeholder communication.

Trigger

Invoke at the end of each work week when preparing a status update for stakeholders, managers, or clients.

Steps

  1. 1

    Analyze the raw work log provided below and extract all meaningful work activity, noting dates, projects, tasks completed, time spent, and any issues mentioned: $work_log

    • All days of the week are accounted for
    • Project names and task references are identified
    • Any blockers or issues are flagged
  2. 2

    Group extracted activities by project or workstream. Consolidate related tasks, remove redundant entries, and prioritize items by business impact. Distinguish clearly between completed work, in-progress work, and stalled items.

    • Tasks are grouped logically by project or theme
    • Completed vs. in-progress items are separated
    • Low-signal or trivial entries are omitted
  3. 3

    Write a concise executive summary (3–5 sentences) capturing the week's overall progress, headline achievements, and any critical risks or blockers. Use plain business language suitable for a non-technical stakeholder audience.

    • Summary is 3–5 sentences max
    • Avoids jargon and technical acronyms
    • Highlights impact, not just activity
  4. 4

    Draft the Accomplishments section as a bulleted list. Each bullet should start with a strong past-tense action verb, name the project, and briefly state the outcome or value delivered. Limit to the 5–8 most significant items.

    • Bullets lead with action verbs
    • Outcomes or impact are stated, not just tasks
    • List is capped at 8 items
  5. 5

    Draft the Blockers & Risks section listing any impediments, dependencies, or open questions that require stakeholder attention or decisions. For each item, state the issue, its impact if unresolved, and the owner or action needed.

    • Each blocker has a stated impact
    • Required action or owner is identified
    • Items needing immediate escalation are marked
  6. 6

    Draft the Next Week Priorities section as a numbered list of 3–5 planned focus areas, each tied to a project and expected deliverable. Ensure priorities logically follow from this week's status and any open blockers.

    • 3–5 priorities listed
    • Each priority names a project and deliverable
    • Addresses any carryover from current blockers

Output format

Produce a structured report with four clearly labeled sections: (1) Executive Summary — short paragraph; (2) Accomplishments — bulleted list with action-verb leads; (3) Blockers & Risks — bulleted list with issue, impact, and required action; (4) Next Week Priorities — numbered list. Use professional business prose throughout. Total length should be 300–500 words.

Use it everywhere

Copy this skill into your library to inject it into Claude, ChatGPT, and Gemini — or install your whole library as / slash commands in Claude Code and Cowork.

Get started free →