Skill

Weekly Status Report

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

Goal

Convert raw weekly work logs into a structured, professional status report highlighting accomplishments, blockers, and next steps for stakeholders.

Trigger

Invoke at the end of each work week when the user is ready to compile and share progress with stakeholders.

Steps

  1. 1

    Analyze the work logs provided below and extract all notable activities, completed tasks, in-progress items, blockers, and upcoming priorities: $work_logs

    • All days of the week are accounted for
    • Blockers and risks are identified
    • Upcoming tasks are noted
    Paste your raw work logs here:
    
    $work_logs
  2. 2

    Group extracted items into four categories: Accomplishments (completed this week), In Progress (started but not finished), Blockers & Risks (anything slowing the team down), and Next Week Priorities (planned work).

    • Every extracted item is assigned to exactly one category
    • No category is left empty without a note
  3. 3

    Rewrite each item in stakeholder-friendly language: use action verbs, remove jargon, quantify impact where possible (e.g., 'Reduced load time by 40%' instead of 'fixed slow query'), and keep each bullet to one concise sentence.

    • Jargon and internal shorthand are eliminated
    • At least one metric or outcome is included where data was available
  4. 4

    Write a 2–3 sentence executive summary that captures the week's overall theme, the most important achievement, and any critical blocker or risk that requires stakeholder attention.

    • Summary is self-contained and readable without the detail sections
    • Critical risks are surfaced, not buried
  5. 5

    Assemble the final report in order: Executive Summary, Accomplishments, In Progress, Blockers & Risks, Next Week Priorities. Add a header with the reporting week date range and the preparer's team or name if inferable from the logs.

    • Sections appear in the correct order
    • Date range is present in the header
    • Report reads as a single cohesive document

Output format

Deliver the report as clearly labeled sections with a bold heading for each (Executive Summary, Accomplishments, In Progress, Blockers & Risks, Next Week Priorities). Use bullet points within each section. Keep the full report under 500 words. Use professional, confident tone suitable for senior stakeholders.

Use it everywhere

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

Get started free →