Status Report
This skill generates a polished status report for leadership or stakeholders. It provides a structured template to summarize progress, highlight key metrics,...
Install
npx promptshop add status-reportDetails
What This Skill Does
This skill generates a polished status report for leadership or stakeholders. It provides a structured template to summarize progress, highlight key metrics, identify risks and issues, and outline next period priorities. It's useful for project managers, team leads, and anyone needing to communicate project status.
When to Use
Provide a weekly update on project progress. Summarize key accomplishments for leadership. Highlight risks and issues requiring attention. Outline priorities for the next reporting period. Track key performance indicators. Communicate project status to stakeholders.
Key Features
Generates a markdown-formatted status report. Includes an executive summary and overall status indicator. Tracks key metrics with targets, actuals, and trends. Identifies risks and issues with mitigation plans. Highlights decisions needed with recommended actions. Can integrate with project trackers, chat, and calendar tools.
Manual Installation
- Manual installation
- View Full Skill Content
- The complete markdown content that gets installed/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
[Priority 1] [Priority 2] [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./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
[Priority 1] [Priority 2] [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.