Write a structured project status report for any project
Project Status Report Skill
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 Code
npx skills add mohitagw15856/pm-claude-skills --skill project-status-report -g -a claude-codeClaude 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-reportWindows (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" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.7 KB
Read the files here
mohitagw15856/
SKILL.md
Show the full text126 lines
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 |
Details
- Updated
- Sep 23, 2026
- License
- MIT
- Stars on the repo
- ★ 1,395
- Checked
- Source
- mohitagw15856/pm-claude-skills ↗
- Creator
- mohitagw15856 · 193 listings
Made with project-status-report
Project Status Report Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Project Status Report Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Similar skills
See all →
SkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboard
alirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub stars
SkillTurn a LinkedIn Analytics exportAnalytics dashboard
charlie947/social-media-skills · by charlie947Turn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.★ 3.7k GitHub stars
SkillGenerate a pre-earnings briefing for any stock using YahooEarnings Preview Skill
himself65/finance-skills · by himself65Generate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.★ 3.3k GitHub stars
SkillVet a perf measurement before you report or act on itBenchmark checklist
michael-denyer/pstack-claude · by michael-denyerVet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.★ 1k GitHub stars
SkillReport a bug, file an issue, submit a bug reportReport Issue — mobile-app
microsoft/power-platform-skills · by microsoftUse when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.★ 954 GitHub stars
SkillBuild the agency dashboard across all client brands: health/digital-marketing-pro:agency-dashboard
indranilbanerjee/digital-marketing-pro · by indranilbanerjeeBuild the agency dashboard across all client brands: health, pacing, risk. "how are all our clients doing"★ 866 GitHub starsMore from mohitagw15856
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skill
mohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub stars
SkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub stars
SkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub stars
SkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub stars
SkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub stars
SkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars