Status Report
Generate a project status report for "$ARGUMENTS" in RAG format (Red/Amber/Green) suitable for leadership review. Summarize progress against milestones, highlight risks and issues, note upcoming milestones, and list asks from leadership.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"project-management-status-report","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill. It can be run at any time, with or without existing project artifacts.
If .singularskills/project-management/<project>/ exists, read any available artifacts for context. If it does not exist, proceed based on information the user provides.
Process
Read existing context:
- If
.singularskills/project-management/<project>/ exists, read all available artifacts for comprehensive context:
- Project charter, roadmap, and backlog for planned scope and milestones
- Sprint data for recent progress and velocity
- Risk assessments for known risks
- Decision logs for recent decisions
- Previous status reports for trend comparison
- If no artifacts exist, gather the information from the user through targeted questions
Set overall RAG status with justification:
- Green — on track: project is progressing as planned, no significant risks or blockers, timeline confidence is high
- Amber — challenges but manageable: some risks or issues exist but have mitigation plans, timeline may slip slightly, needs monitoring
- Red — blocked or at-risk: significant blockers or risks threatening delivery, timeline is at serious risk, needs leadership attention or intervention
- Provide a one-line justification for the status: "Green: delivering on schedule with all milestones met this period"
- If the status has changed from the previous report, explain why
- Be honest — do not default to Green to avoid difficult conversations
Summarize progress against milestones:
- For each milestone or major deliverable:
- Status — completed, in progress, not started, at risk, blocked
- % complete — estimated progress
- Key accomplishments this period — what was delivered or achieved since last report
- Highlight any milestones that slipped and explain why
- Note velocity trends: is the team accelerating, maintaining, or slowing down?
List top 3 risks and issues:
- Distinguish between risks (potential problems) and issues (current problems)
- For each:
- Description — what is the risk or issue
- Impact — what happens if it materializes or is not resolved
- Mitigation — what is being done about it
- Owner — who is responsible for managing it
- Limit to top 3 — leadership does not need an exhaustive list, they need the critical items
- If there are more than 3, note "N additional risks tracked in the risk register"
Note upcoming milestones and timeline confidence:
- List the next 2-3 milestones with target dates
- For each, state confidence level: high (>80% likely on time), medium (50-80%), low (<50%)
- If any milestone is at medium or low confidence, briefly explain why
- Note any dependencies on external teams, vendors, or decisions
List asks and decisions needed from leadership:
- Be specific: "We need approval for X by [date]" or "We need a decision on Y to unblock Z"
- For each ask, explain: what is needed, why, by when, and what happens if it is delayed
- Limit to 2-3 actionable asks — this is the most important section for leadership
- If there are no asks, explicitly state "No asks this period"
Include team capacity note:
- Is the team fully staffed or are there gaps?
- Note any planned or unplanned absences that affect delivery
- Flag if the team is at capacity and new work cannot be absorbed without deprioritizing something
- Note upcoming capacity changes (new hires, departures, leaves)
Write the artifact — save to .singularskills/project-management/<project>/status-report.md:
- Report Date — date of this report
- Overall Status — RAG indicator with one-line justification
- Progress Summary — milestone status with % complete and key accomplishments
- Risks & Issues — top 3 with impact, mitigation, and owner
- Upcoming Milestones — next 2-3 milestones with dates and confidence levels
- Asks from Leadership — specific requests with deadlines
- Team Capacity — staffing and availability notes
- Trend — comparison with previous report status if available
Output
Status report saved to .singularskills/project-management/<project>/status-report.md. Present a summary highlighting:
- Overall RAG status with justification
- Key accomplishment this period
- Top risk or issue requiring attention
- Most urgent ask from leadership (if any)
1---2name: project-management-status-report3description: Generate a project status report for leadership in RAG format — progress against milestones, top risks and issues, timeline confidence, asks and capacity. Use when leadership or a steering group wants to know where the project stands and what it needs from them. Not for a sprint-by-sprint update to stakeholders; see /project-management-stakeholder-update.4metadata:5 source: https://skillmd.com/skills/bromso/project-management-status-report6 argument-hint: "[project] [--skip-checks]"7---89# Status Report1011Generate a project status report for "$ARGUMENTS" in RAG format (Red/Amber/Green) suitable for leadership review. Summarize progress against milestones, highlight risks and issues, note upcoming milestones, and list asks from leadership.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"project-management-status-report","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Prerequisites1617None — this is a utility skill. It can be run at any time, with or without existing project artifacts.1819If `.singularskills/project-management/<project>/` exists, read any available artifacts for context. If it does not exist, proceed based on information the user provides.2021## Process22231. **Read existing context:**24 - If `.singularskills/project-management/<project>/` exists, read all available artifacts for comprehensive context:25 - Project charter, roadmap, and backlog for planned scope and milestones26 - Sprint data for recent progress and velocity27 - Risk assessments for known risks28 - Decision logs for recent decisions29 - Previous status reports for trend comparison30 - If no artifacts exist, gather the information from the user through targeted questions31322. **Set overall RAG status with justification:**33 - **Green — on track:** project is progressing as planned, no significant risks or blockers, timeline confidence is high34 - **Amber — challenges but manageable:** some risks or issues exist but have mitigation plans, timeline may slip slightly, needs monitoring35 - **Red — blocked or at-risk:** significant blockers or risks threatening delivery, timeline is at serious risk, needs leadership attention or intervention36 - Provide a one-line justification for the status: "Green: delivering on schedule with all milestones met this period"37 - If the status has changed from the previous report, explain why38 - Be honest — do not default to Green to avoid difficult conversations39403. **Summarize progress against milestones:**41 - For each milestone or major deliverable:42 - **Status** — completed, in progress, not started, at risk, blocked43 - **% complete** — estimated progress44 - **Key accomplishments this period** — what was delivered or achieved since last report45 - Highlight any milestones that slipped and explain why46 - Note velocity trends: is the team accelerating, maintaining, or slowing down?47484. **List top 3 risks and issues:**49 - Distinguish between risks (potential problems) and issues (current problems)50 - For each:51 - **Description** — what is the risk or issue52 - **Impact** — what happens if it materializes or is not resolved53 - **Mitigation** — what is being done about it54 - **Owner** — who is responsible for managing it55 - Limit to top 3 — leadership does not need an exhaustive list, they need the critical items56 - If there are more than 3, note "N additional risks tracked in the risk register"57585. **Note upcoming milestones and timeline confidence:**59 - List the next 2-3 milestones with target dates60 - For each, state confidence level: high (>80% likely on time), medium (50-80%), low (<50%)61 - If any milestone is at medium or low confidence, briefly explain why62 - Note any dependencies on external teams, vendors, or decisions63646. **List asks and decisions needed from leadership:**65 - Be specific: "We need approval for X by [date]" or "We need a decision on Y to unblock Z"66 - For each ask, explain: what is needed, why, by when, and what happens if it is delayed67 - Limit to 2-3 actionable asks — this is the most important section for leadership68 - If there are no asks, explicitly state "No asks this period"69707. **Include team capacity note:**71 - Is the team fully staffed or are there gaps?72 - Note any planned or unplanned absences that affect delivery73 - Flag if the team is at capacity and new work cannot be absorbed without deprioritizing something74 - Note upcoming capacity changes (new hires, departures, leaves)75768. **Write the artifact** — save to `.singularskills/project-management/<project>/status-report.md`:77 - **Report Date** — date of this report78 - **Overall Status** — RAG indicator with one-line justification79 - **Progress Summary** — milestone status with % complete and key accomplishments80 - **Risks & Issues** — top 3 with impact, mitigation, and owner81 - **Upcoming Milestones** — next 2-3 milestones with dates and confidence levels82 - **Asks from Leadership** — specific requests with deadlines83 - **Team Capacity** — staffing and availability notes84 - **Trend** — comparison with previous report status if available8586## Output8788Status report saved to `.singularskills/project-management/<project>/status-report.md`. Present a summary highlighting:89- Overall RAG status with justification90- Key accomplishment this period91- Top risk or issue requiring attention92- Most urgent ask from leadership (if any)