Turn project activity into a leadership-ready status report with metrics, risks, and decisions. — Claude Skill
A Claude Skill for Claude Code by Anthropic✓ — run /status-report in Claude·Updated Jun 13, 2026·vmain@da04ccb
Creates weekly, monthly, or quarterly status reports with executive summary, green/yellow/red status, KPIs, accomplishments, work in progress, risks, decisions, and priorities.
- Turns raw tracker updates into a concise report leaders can scan.
- Separates accomplishments, in-progress work, risks, issues, and decisions.
- Uses an overall green, yellow, or red status with plain-language rationale.
- Makes decision asks explicit with context, deadline, and recommendation.
A project manager copies activity from tickets and chats, but leaders still cannot see the headline, risk, or decision needed.
Run /status-report to turn raw updates into a scan-friendly report with status, metrics, risks, decisions, and priorities.
Who this is for
What it does
Summarize project health, blockers, and decisions in one report.
Turn KPIs and activity into status narrative and next priorities.
Explain why work is yellow or red and what decision is needed.
How it works
Collect the project or team, reporting period, KPIs, completed work, in-progress items, risks, and decisions needed.
Write a 3-4 sentence executive summary.
Assign overall status and explain why.
Format KPIs, active work, risks, and decisions in clear tables.
End with next-period priorities.
Input options
Weekly, monthly, quarterly, or a custom date range.
Example
Project: onboarding launch Period: June 8-12 Launch target: June 28 Metrics: invite flow QA 82% complete, help docs 60%, beta activation 43% vs 55% target Completed: invite reminder shipped to beta, analytics events added In progress: help docs, enterprise admin copy, support macros Risks: legal review not complete, beta activation below target Decision needed: launch to all customers or limit to new workspaces.
**Author:** PMO **Date:** 2026-06-13 ### Executive Summary The onboarding launch is progressing, but the project is at risk because activation is below target and legal review is not complete. Engineering shipped the invite reminder to beta and analytics events are now available. The main decision is whether to launch broadly or limit the rollout to new workspaces while activation improves.
**Overall Status:** Yellow - At Risk The launch date is still possible, but two items need attention this week: legal approval and beta activation performance.
| Metric | Target | Actual | Trend | Status | |---|---:|---:|---|---| | Invite flow QA complete | 100% | 82% | Up | Yellow | | Help docs ready | 100% | 60% | Up | Yellow | | Beta activation | 55% | 43% | Flat | Red | | Support macros ready | 100% | 70% | Up | Yellow |
| Item | Owner | Status | ETA | Notes | |---|---|---|---|---| | Help docs | Support Ops | In progress | June 18 | Needs screenshots | | Enterprise admin copy | Product Marketing | In progress | June 17 | Legal review pending | | Support macros | Support Lead | In progress | June 19 | Based on beta questions |
### Risks and Issues | Risk/Issue | Impact | Mitigation | Owner | |---|---|---|---| | Legal review not complete | Launch copy may need changes | Daily review slot with Legal | Product Marketing | | Beta activation below target | Broad rollout may miss goal | Limit launch or add invite prompt | Product | ### Decisions Needed | Decision | Context | Deadline | Recommended Action | |---|---|---|---| | Launch scope | Activation is 43% vs 55% target | June 18 | Launch to new workspaces first, not all customers |
1. Finish legal review and enterprise admin copy. 2. Raise beta activation or narrow launch scope. 3. Complete help docs and support macros before launch readiness review.
Metrics this improves
Works with
Want to use Status Report?
Choose how to get started.
Install and run this skill locally on your computer.
Open a terminal on your computer and paste this command:
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
Start Claude Code, then type the command:
/status-report
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a polished status report for leadership or stakeholders. See the risk-assessment skill for risk matrix frameworks and severity definitions.
Usage
/status-report $ARGUMENTS
Output
## Status Report: [Project/Team] — [Period]
**Author:** [Name] | **Date:** [Date]
### Executive Summary
[3-4 sentence overview — what's on track, what needs attention, key wins]
### Overall Status: 🟢 On Track / 🟡 At Risk / 🔴 Off Track
### Key Metrics
| Metric | Target | Actual | Trend | Status |
|--------|--------|--------|-------|--------|
| [KPI] | [Target] | [Actual] | [up/down/flat] | 🟢/🟡/🔴 |
### Accomplishments This Period
- [Win 1]
- [Win 2]
### In Progress
| Item | Owner | Status | ETA | Notes |
|------|-------|--------|-----|-------|
| [Item] | [Person] | [Status] | [Date] | [Context] |
### Risks and Issues
| Risk/Issue | Impact | Mitigation | Owner |
|------------|--------|------------|-------|
| [Risk] | [Impact] | [What we're doing] | [Who] |
### Decisions Needed
| Decision | Context | Deadline | Recommended Action |
|----------|---------|----------|--------------------|
| [Decision] | [Why it matters] | [When] | [What I recommend] |
### Next Period Priorities
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
If Connectors Available
If ~~project tracker is connected:
- Pull project status, completed items, and upcoming milestones automatically
- Identify at-risk items and overdue tasks
If ~~chat is connected:
- Scan recent team discussions for decisions and blockers to include
- Offer to post the finished report to a channel
If ~~calendar is connected:
- Reference key meetings and decisions from the reporting period
Tips
- Lead with the headline — Busy leaders read the first 3 lines. Make them count.
- Be honest about risks — Surfacing issues early builds trust. Surprises erode it.
- Make decisions easy — For each decision needed, provide context and a recommendation.
Reference documents
name: status-report description: Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative. argument-hint: "[weekly | monthly | quarterly] [project or team]"
/status-report
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a polished status report for leadership or stakeholders. See the risk-assessment skill for risk matrix frameworks and severity definitions.
Usage
/status-report $ARGUMENTS
Output
## Status Report: [Project/Team] — [Period]
**Author:** [Name] | **Date:** [Date]
### Executive Summary
[3-4 sentence overview — what's on track, what needs attention, key wins]
### Overall Status: 🟢 On Track / 🟡 At Risk / 🔴 Off Track
### Key Metrics
| Metric | Target | Actual | Trend | Status |
|--------|--------|--------|-------|--------|
| [KPI] | [Target] | [Actual] | [up/down/flat] | 🟢/🟡/🔴 |
### Accomplishments This Period
- [Win 1]
- [Win 2]
### In Progress
| Item | Owner | Status | ETA | Notes |
|------|-------|--------|-----|-------|
| [Item] | [Person] | [Status] | [Date] | [Context] |
### Risks and Issues
| Risk/Issue | Impact | Mitigation | Owner |
|------------|--------|------------|-------|
| [Risk] | [Impact] | [What we're doing] | [Who] |
### Decisions Needed
| Decision | Context | Deadline | Recommended Action |
|----------|---------|----------|--------------------|
| [Decision] | [Why it matters] | [When] | [What I recommend] |
### Next Period Priorities
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
If Connectors Available
If ~~project tracker is connected:
- Pull project status, completed items, and upcoming milestones automatically
- Identify at-risk items and overdue tasks
If ~~chat is connected:
- Scan recent team discussions for decisions and blockers to include
- Offer to post the finished report to a channel
If ~~calendar is connected:
- Reference key meetings and decisions from the reporting period
Tips
- Lead with the headline — Busy leaders read the first 3 lines. Make them count.
- Be honest about risks — Surfacing issues early builds trust. Surprises erode it.
- Make decisions easy — For each decision needed, provide context and a recommendation.