status-report

KPI, 위험 요소, 조치 항목이 포함된 상태 보고서를 생성합니다. 리더십을 위한 주간 또는 월간 업데이트를 작성할 때 사용하며, 프로젝트 상태를 요약할 때 활용합니다.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill 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.