Status Report Generator

Project Status Report Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication.

---
name: project-status-report
description: "Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed."
---

# Project Status Report Skill

Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.

## Required Inputs
- **Project name**
- **Reporting period**
- **Current RAG status** (Red / Amber / Green)
- **Key milestones** (due, delivered, coming)
- **Issues or blockers**
- **Decisions needed from stakeholders**
- **Budget status** (if tracked)
- **Audience** (steering committee / sponsor / PMO / full team)

Overview

Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.

Manual install (npx, ZIP)

Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill project-status-report -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
  | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/project-status-report

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/42a54886afee8e617ecf/project-status-report.zip" -OutFile "$env:TEMP\project-status-report.zip"; Expand-Archive "$env:TEMP\project-status-report.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.7 KB

Read the files here

mohitagw15856/f6ca7931 file

SKILL.md3.7 KB

SKILL.md

Show the full text126 lines

project-status-report/SKILL.md126 lines · 3.7 KB

PreviewCode

Outline

RawView on GitHub

Project Status Report Skill

Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.

Required Inputs

Project name
Reporting period
Current RAG status (Red / Amber / Green)
Key milestones (due, delivered, coming)
Issues or blockers
Decisions needed from stakeholders
Budget status (if tracked)
Audience (steering committee / sponsor / PMO / full team)

Output Structure

Project Status Report: [Project Name]

Period: [Date range] | Author: [PM] | Next report: [Date]

Overall Status

Dimension	Status	Last period	Trend
Overall	Red / Amber / Green	[Last]	Improving / Stable / Declining
Schedule
Budget
Scope
Risks

RAG definitions:

Green: On track. No significant issues.
Amber: At risk. Issues identified but mitigations in place.
Red: Off track. Escalation or decisions required to recover.

Executive Summary

[3-5 sentences. Headline story. If it is Red, say so immediately and why. Never bury bad news after good news.]

Milestone Progress

Milestone	Due date	Status	Comment
[Milestone]	[Date]	Complete / At risk / Delayed / On track	[One line]

Completed this period: [What was delivered] Due next period: [What is expected]

Issues and Blockers

[Issue title] — Critical / High / Low

Description: [What the issue is]
Impact: [What happens if unresolved]
Owner: [Who is resolving]
Action: [What is being done]
Resolution date: [When it will be closed]

Risks

Risk	Likelihood	Impact	Mitigation	Owner
[Risk]	H/M/L	H/M/L	[Action]	[Name]

Decisions Required

Decision	Background	Options	Recommendation	Needed by
[Decision]	[Context]	[Options]	[Recommendation]	[Date]

Budget Summary

	Budget	Actual to date	Forecast	Variance
Total	£	£	£	£ F/A

Next Period Plan

[3-5 specific bullet points — what will happen next period]

Writing Rules

Never soften a Red status
Milestones are binary: complete or not complete
Decisions must be genuinely actionable
Keep to one page where possible

Quality Checks

Red status is stated immediately (not buried after positives)
Every issue has a named owner and a resolution date
Decisions required are genuinely actionable by the audience
Milestones are binary (complete or not complete — no "85% done")
Executive summary can stand alone for a stakeholder who reads nothing else

Anti-Patterns

Do not rate project health as Green while listing unresolved critical blockers
Do not report milestone progress as a percentage — milestones are binary: complete or not complete
Do not bury risks at the bottom — if something is high risk, it belongs in the executive summary
Do not leave decisions required without specifying who must decide and by when
Do not write an executive summary that requires reading the full report to understand — it must stand alone

Example Trigger Phrases

"Write a project status report for [project]"
"Generate a RAG status update for [project]"
"Write the steering committee report for [project]"

1	---
2	name: project-status-report
3	description: "Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed."
4	---
5
6	# Project Status Report Skill
7
8	Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.
9
10	## Required Inputs
11	- Project name
12	- Reporting period
13	- Current RAG status (Red / Amber / Green)
14	- Key milestones (due, delivered, coming)
15	- Issues or blockers
16	- Decisions needed from stakeholders
17	- Budget status (if tracked)
18	- Audience (steering committee / sponsor / PMO / full team)
19
20	## Output Structure
21
22	---
23
24	# Project Status Report: [Project Name]
25	Period: [Date range] \| Author: [PM] \| Next report: [Date]
26
27	---
28
29	### Overall Status
30
31	\| Dimension \| Status \| Last period \| Trend \|
32	\|---\|---\|---\|---\|
33	\| Overall \| Red / Amber / Green \| [Last] \| Improving / Stable / Declining \|
34	\| Schedule \| \| \| \|
35	\| Budget \| \| \| \|
36	\| Scope \| \| \| \|
37	\| Risks \| \| \| \|
38
39	RAG definitions:
40	- Green: On track. No significant issues.
41	- Amber: At risk. Issues identified but mitigations in place.
42	- Red: Off track. Escalation or decisions required to recover.
43
44	---
45
46	### Executive Summary
47	[3-5 sentences. Headline story. If it is Red, say so immediately and why. Never bury bad news after good news.]
48
49	---
50
51	### Milestone Progress
52
53	\| Milestone \| Due date \| Status \| Comment \|
54	\|---\|---\|---\|---\|
55	\| [Milestone] \| [Date] \| Complete / At risk / Delayed / On track \| [One line] \|
56
57	Completed this period: [What was delivered]
58	Due next period: [What is expected]
59
60	---
61
62	### Issues and Blockers
63
64	[Issue title] — Critical / High / Low
65	- Description: [What the issue is]
66	- Impact: [What happens if unresolved]
67	- Owner: [Who is resolving]
68	- Action: [What is being done]
69	- Resolution date: [When it will be closed]
70
71	---
72
73	### Risks
74
75	\| Risk \| Likelihood \| Impact \| Mitigation \| Owner \|
76	\|---\|---\|---\|---\|---\|
77	\| [Risk] \| H/M/L \| H/M/L \| [Action] \| [Name] \|
78
79	---
80
81	### Decisions Required
82
83	\| Decision \| Background \| Options \| Recommendation \| Needed by \|
84	\|---\|---\|---\|---\|---\|
85	\| [Decision] \| [Context] \| [Options] \| [Recommendation] \| [Date] \|
86
87	---
88
89	### Budget Summary
90
91	\| \| Budget \| Actual to date \| Forecast \| Variance \|
92	\|---\|---\|---\|---\|---\|
93	\| Total \| £ \| £ \| £ \| £ F/A \|
94
95	---
96
97	### Next Period Plan
98	[3-5 specific bullet points — what will happen next period]
99
100	## Writing Rules
101	- Never soften a Red status
102	- Milestones are binary: complete or not complete
103	- Decisions must be genuinely actionable
104	- Keep to one page where possible
105
106	## Quality Checks
107
108	- [ ] Red status is stated immediately (not buried after positives)
109	- [ ] Every issue has a named owner and a resolution date
110	- [ ] Decisions required are genuinely actionable by the audience
111	- [ ] Milestones are binary (complete or not complete — no "85% done")
112	- [ ] Executive summary can stand alone for a stakeholder who reads nothing else
113
114	## Anti-Patterns
115
116	- [ ] Do not rate project health as Green while listing unresolved critical blockers
117	- [ ] Do not report milestone progress as a percentage — milestones are binary: complete or not complete
118	- [ ] Do not bury risks at the bottom — if something is high risk, it belongs in the executive summary
119	- [ ] Do not leave decisions required without specifying who must decide and by when
120	- [ ] Do not write an executive summary that requires reading the full report to understand — it must stand alone
121
122	## Example Trigger Phrases
123	- "Write a project status report for [project]"
124	- "Generate a RAG status update for [project]"
125	- "Write the steering committee report for [project]"
126