status-report
プロジェクトの進捗、リスク、次のステップを自動で要約し、リーダーシップ層とステークホルダー向けの専門的なステータスレポートを生成します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill status-reportBefore / After 効果比較
1 组毎週、各チームの進捗を手動で収集し、複数のドキュメントやツールを切り替えてデータを検索し、レポートにまとめるのに1〜2時間かかります。重要なリスクやマイルストーンを見落としやすく、フォーマットが統一されていないため、関係者は主要な情報を迅速に把握するのが困難です。
プロジェクトツールから進捗データを自動で同期し、リスクやブロックをインテリジェントに識別し、5分で構造化されたステータスレポートを作成します。主要な指標と決定事項を強調し、多階層の関係者ビューをサポートし、ワンクリックでメール送信やコラボレーションプラットフォームへの同期が可能です。
status-report
/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.
Weekly Installs308Repositoryanthropics/know…-pluginsGitHub Stars10.6KFirst SeenMar 13, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex294gemini-cli291opencode290cursor290github-copilot289amp289
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価