agentleFS
fludofludo/pm-claude-kit/.claude/skills/status-reporting/SKILL.md

status-reporting

Skill0 starsChanged 6 days agoMITView on GitHub

Turn project-status.md or pasted project data into a clear period/weekly status report with a RAG status and executive summary. Use when the task mentions status report, weekly report, progress update, project dashboard narrative, RAG/traffic-light status, or steering-committee update. PMI Knowledge Area: Communications.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    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:

    Do not let the RAG drift from the previous report without saying what changed.

    line 21
  2. Very specific:

    Use the template at ${CLAUDE_PLUGIN_ROOT}/.claude/skills/pmi-project-management/templates/status-report.md, or the user's house template if …

    line 32

“Common” is measured: kept by at least 6 in 10 of the 4 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 Reporting

Convert the data the user pastes (or project-status.md) into an audience-ready report. Never invent progress, metrics, or dates — organise what you're given and mark gaps [TBC].

Inputs: project-status.md at the repo root plus any data pasted in the conversation; where they differ, the pasted data wins. A file still holding only template placeholders counts as missing. With neither, ask. Also read the newest report in docs/status/ dated before this one and docs/risk-register.md for continuity.

RAG: derive it from the Status tolerances in the project context and give a one-line rationale that names the tolerance. If the field says "kit defaults", apply the thresholds in the template. If it is unfilled, apply them and write "PM judgement — tolerances [TBC]". Do not let the RAG drift from the previous report without saying what changed.

Continuity: state the trend against the last report, every milestone forecast that moved, and carried-over actions. If the new data contradicts the last report, say so.

Writing: an executive summary a sponsor can read in 20 seconds — where we are, whether we are on track, the one thing needing attention. Tables for anything with dates or numbers. Always show budget and schedule: if a measure has no data, mark it [TBC], list it under "Data I still need", and report no better than Amber. Separate facts from PM judgement. End with "Data I still need".

Use the template at ${CLAUDE_PLUGIN_ROOT}/.claude/skills/pmi-project-management/templates/status-report.md, or the user's house template if they supply one (map their data into it exactly). Draft inline; for a pre-send check of a saved report, use the status-reporter agent.

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.