agentleFS
LwhieldonLwhieldon/claude-project-mgmt-playbook/.claude/skills/status-report/SKILL.md

status-report

Skill4 starsChanged 36 days agoMITView on GitHub

Generate a weekly project status report from a status CSV or free-text notes, with RAG status, accomplishments, upcoming work, risks, and actions. Use when you need a client-ready update from raw project data. Usage - /status-report path/to/status-data.csv

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use postmortem and meeting-notes.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hongyu-yuSkill

    postmortem

    Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the data. If it is a CSV, read every row, not just the last one.

    line 23
  2. Distinctive:

    Check budget burn against percent complete.

    line 24
  3. Very specific:

    Use professional, direct consulting language.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status Report

Generate a structured weekly status report from project data or a free-text summary. Output is formatted for direct use in a client email or a PowerPoint status slide.

Input

$ARGUMENTS is either:

  • the path to a status-data.csv (see sample-projects/acme-data-warehouse/status-data.csv for the expected columns), or
  • a short free-text description of the week: accomplishments, blockers, upcoming work, open issues.

Optionally reference last week's report for a comparison view. If nothing was given, ask.

Steps

  1. Read the data. If it is a CSV, read every row, not just the last one. The trend is the story.
  2. Check budget burn against percent complete. If burn is ahead of completion by more than a few points, say so explicitly. This is the most common early warning a status report hides.
  3. Propose a RAG rating with the reasoning that led to it. The rating is a proposal. The delivery lead confirms or overrules it; never present it as settled.
  4. Draft the report below. Compare the figures you were given; do not extrapolate from them. A cost at completion, a percentage over budget, or a revised go-live date is a forecast, and a forecast is a commitment the delivery lead makes, not the report. If the data points to one, say so to the delivery lead in a note outside the report and leave the report's figures as given.

Output

Overall Status: [🔴 Red / 🟡 Amber / 🟢 Green]: one-sentence rationale

Accomplishments This Week:

  • 3 to 5 bullet points tied to specific deliverables or milestones

Upcoming (Next 2 Weeks):

  • 3 to 5 bullet points with target dates

Risks & Issues:

Risk/IssueSeverityOwnerMitigation / Status

Action Items:

ActionOwnerDue DatePriority

Drafted with Claude Code on YYYY-MM-DD; reviewed by [NAME]

Use professional, direct consulting language. No filler sentences. If data is missing or ambiguous, flag it explicitly with [NEEDS INPUT] rather than guessing. An invented number that reaches a client is worse than a blank.

Example Output

Overall Status: 🟡 Amber. Sprint 4 velocity is 15% below plan due to delayed UAT environment setup; mitigation plan in progress.

Accomplishments This Week:

  • Completed data migration scripts for Orders and Inventory modules
  • Delivered revised data mapping document to client for sign-off
  • Onboarded two new client SMEs to the UAT process

Action Items:

ActionOwnerDue DatePriority
Finalize UAT environment configurationDev LeadFri May 10High
Client sign-off on data mapping documentClient PMWed May 8High

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.