status-update
Skill0 starsChanged yesterdayMITView on GitHub
Write a short project status update that people actually read: the overall status first with honest criteria (on track, at risk, off track), progress against the plan, what is next, decisions needed from the reader, and risks, adapted to the audience (boss, client, board, family, volunteers). Use for weekly updates, client reports, steering committees, or any "where are we?" question. Triggers: "status update", "progress report", "weekly report", "project update", "point d'avancement", "rapport d'avancement", "reporting hebdomadaire", "où en est le projet", "informe de estado", "informe de avance", "reporte semanal".
12 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Robinnnnn/skillstheir own version, first seen Nov 1, 2026
- lost-rob0t/skillstheir own version, first seen Oct 30, 2026
- The-AI-Thinker/claude-code-pm-startertheir own version, first seen Oct 15, 2026
- Baba01hacker666/dummyskillstheir own version, first seen Oct 13, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- etrebels/claude-code-growth-os★ 21same name
- arezous/pm-pilot★ 20same name
- The-AI-Thinker/claude-code-pm-starter★ 13same name
- caidanw/skills★ 11same name
- Robinnnnn/skills★ 4same name
- CSPulse/customer-success-skills★ 2same name
- tmusser/context-to-action-skills★ 2same name
- tines/skills★ 1same name
- Baba01hacker666/dummyskills★ 0same name
- lost-rob0t/skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- decision-makingSkill
- delegation-briefSkill
- meeting-toolkitSkill
- project-budgetSkill
- project-charterSkill
- project-recoverySkill
- project-scheduleSkill
- responsibility-matrixSkill
- retrospectiveSkill
- risk-registerSkill
- scope-changeSkill
- stakeholder-mapSkill
- vendor-selectionSkill
- weekly-reviewSkill
- work-breakdownSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
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
- Distinctive: line 21
Every week or two during a project, and before a steering meeting.
- Distinctive: line 22
When something slips and the people involved need to know.
- Very specific: line 23
Not for a meeting agenda: use meeting-toolkit.
- Distinctive: line 58
Every slip has a new date and a reason.
“Common” is measured: kept by at least 6 in 10 of the 12 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.
Files
Status update
A good update is read in a minute and leads to decisions. This skill puts the conclusion first, as Minto's pyramid principle recommends, and keeps the status colors honest.
When to use
- Every week or two during a project, and before a steering meeting.
- When something slips and the people involved need to know.
- Not for a meeting agenda: use
meeting-toolkit.
Inputs
- The plan (milestones, budget) and what actually happened since the last update.
- The audience and what they need to decide or know.
- Risks and issues from the
risk-register.
Method
- Lead with the status and one sentence: on track, at risk or off track, using criteria written in advance (for example "at risk" when a milestone may slip by more than a week or the budget by more than the reserve).
- Say what changed since the last update: milestones reached, milestones slipped, with the new dates and the reasons.
- Ask for the decisions needed, each with the options, a recommendation and a date by which the decision is needed.
- Show the numbers that matter: schedule (milestones), budget (planned, committed, paid), and one or two indicators specific to the project.
- List the top risks and issues with their owners and next steps.
- Adapt the format to the reader: five lines for a busy executive or a family group, a table for a client or a committee. The content stays honest; only the length changes.
Output
### <Project>: status on <date>: <ON TRACK, AT RISK or OFF TRACK>
In one sentence: …
Decisions needed from you: 1. … (options, recommendation, by <date>)
Done since last update: … | Next: …
| Milestone | Planned | Forecast | Status |
|---|---|---|---|
Budget: planned … | committed … | paid … | forecast …
Top risks: …Quality bar
- The status and the decisions needed come first.
- The status color follows criteria set in advance; bad news is not softened into "on track".
- Every slip has a new date and a reason; every decision has a deadline.
- Written in the user's language, with the terms below.
Terminology
| English | Français | Español |
| Status update | Point d'avancement | Informe de estado |
| On track, at risk, off track | Dans les temps, à risque, en retard | En plazo, en riesgo, fuera de plazo |
| Steering committee | Comité de pilotage | Comité de dirección |
| Issue | Problème, point bloquant | Incidencia |
| Forecast | Prévision | Previsión |
| Escalation | Escalade | Escalado |
Sources
- Minto, B. (1996). The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving. Minto International.
- Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (7th ed.). Project Management Institute.
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
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.