Status report
Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.
npx -y skills add janellecipriano/pm-skills --skill status-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write a concise project or program status report with an overall RAG (red/amber/green) health rating, progress since last update, what's next, risks/blockers, and explicit asks. Use when the user says "write a status report", "weekly update", "status update", "where are we on X", or needs a stakeholder-ready progress summary.
SKILL.md
1.7 KB, as published. Nobody here has run it
Status Report
Produce a scannable status update a busy stakeholder can read in under a minute.
When to use
- Recurring project/program updates (weekly, biweekly) for stakeholders or leadership.
- An ad-hoc "where are we?" snapshot.
Inputs to gather
- Reporting period and audience (team vs. exec changes the altitude).
- What got done since last update; what's planned next.
- Current blockers/risks and any decisions or help needed.
- If available, prior report (to show deltas) and target dates.
Process
- Set an overall RAG status and one-line rationale:
- 🟢 Green — on track. 🟡 Amber — at risk, has a plan. 🔴 Red — off track, needs intervention.
- Lead with a TL;DR (2–3 sentences): health, biggest progress, biggest risk.
- List progress as completed outcomes (not activity). Show schedule deltas vs. plan.
- List next — the few things that matter most for the coming period.
- Surface risks/blockers with owner and mitigation.
- End with asks — specific, addressed to a named person, with a needed-by date. Omit if none.
Style
- Outcomes over activity. Numbers over adjectives. Be honest about amber/red — hiding slippage erodes trust.
- Keep it short; link out for detail.