Project status report writer that turns raw notes into a RAG-rated weekly update
A portable assistant for project and program managers: paste messy notes, tickets or standup logs and get a consistent weekly status report with an honest red/amber/green rating, risks with owners, decisions needed and next steps.
Agent in Operations by AISkillHub Library
What it does
Status reports drift into one of two failure modes: a wall of activity nobody reads, or a green rating that hides a slipping date. This assistant takes raw inputs and produces the same structure every week, with ratings tied to written criteria.
**What it does**
- Accepts anything: bullet notes, a pasted ticket export, standup messages, meeting notes, last week's report. - Pulls out progress against milestones, what slipped and why, risks and issues, and decisions the project needs from someone else. - Rates overall status and each workstream **Green, Amber or Red** using explicit rules (schedule, scope, budget, risk) and states the reason in one line. - Writes two versions: a three-line executive summary and the full report. - Compares with last week's report if you paste it, and calls out changes in rating, new risks and closed items.
**When to use it**
- Weekly or fortnightly updates to stakeholders or a steering group - Consolidating several team leads' updates into one program report - Catching a quietly slipping milestone before it becomes a surprise
**What it will not do**
- It will not turn a status Green because you asked. If the rules say Amber, it says Amber and explains; you can override with a stated reason, which it records. - It will not invent dates, percentages complete or budget figures. Missing figures are listed as "not reported". - It does not assign blame. Issues are written as facts and impacts, with owners for the next action.
**Example**
Input notes: "API integration blocked on vendor credentials since Tue, testing can't start, launch still 14 Nov officially. Design done. Hired contractor starts Mon."
Output: overall **Amber**, reason "Testing start blocked; launch date at risk if credentials not received by <date you set>". Risk logged with owner placeholder, decision needed "Escalate to vendor account manager?", design workstream Green, and an executive summary that says the date is at risk instead of on track.
How to use it
The same `assistants/project-status-report-writer/instructions.md` works in all three products. Pick one:
- **ChatGPT custom GPT:** Explore GPTs, then **Create**, then the **Configure** tab. Name it `Status Report Writer` and paste the file into **Instructions**. Upload a previous report you liked, so the format matches what your stakeholders expect (optional) in the product's file or knowledge area. - **Claude Project:** create a project named `Status Report Writer`, paste the file into the project's custom instructions setting. Upload a previous report you liked, so the format matches what your stakeholders expect (optional) in the product's file or knowledge area. - **Gemini Gem:** in the Gems manager create a **New Gem** named `Status Report Writer` and paste the file into **Instructions**. Upload a previous report you liked, so the format matches what your stakeholders expect (optional) in the product's file or knowledge area. - **No setup option:** paste the whole file as the first message of a new chat in any of the three, then continue in that chat.
**Variables to fill before pasting:** `{{project_name}}`, `{{audience}}` (for example `steering committee` or `client sponsor`) and `{{report_cadence}}` (`weekly` or `fortnightly`). You can also edit the RAG rules in the file to match your PMO's definitions.
Test with one real example before sharing it with your team.
**Using it:** paste this week's notes. Add `Last report:` followed by the previous report to get a change summary. Type `exec only` for just the summary.
Files
Save each file at the path shown, relative to your project root.