Skip to main content

status-report

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.

Quellinformationen

Repository
anthropics/knowledge-work-plugins
Letzte Quellaktivität
13. März 2026 um 15:57
Erkannte Sprache von SKILL.md
Englisch
Sterne
29.826
Forks
3.372

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
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](../../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 ```markdown ## 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 1. **Lead with the headline** — Busy leaders read the first 3 lines. Make them count. 2. **Be honest about risks** — Surfacing issues early builds trust. Surprises erode it. 3. **Make decisions easy** — For each decision needed, provide context and a recommendation.
Auf GitHub ansehen