사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/victor-shulga/gtm-strategy-skills --skill status-report시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
/status-report
Generate a polished status report for leadership or stakeholders. See the risk-assessment skill for risk matrix frameworks and severity definitions.
Usage
/status-report $ARGUMENTSTerms and plain-language output
<!-- glossary:start terms=rag-status,kpi,eta,executive-summary,mitigation --> Rules for every document a client or their team will read (review, roast, canvas, offer cards, instruction):
- Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
- No internal codes or letter scales in the text (A/B/C, D L T E, BLEND numbers without words, Own/Shared/Generic, Z1.4, GATE 2.5, T1–T6). Write the meaning instead: «є цифра з клієнтом», not «A».
- Use the plain form from the table below. English stays only for tool names and for copy that ships in English (promises, hooks, subject lines). If the document is in another language, translate the plain form, never the internal term.
- Do not score what cannot exist yet. A block that depends on work not done (signal catalog, case studies, a previous step) gets «пропущено: спершу потрібно <що саме>», not a score.
- Every section of a review opens with one concrete action («до наступного дзвінка: …»), then at most five lines of why. No paragraph that only restates the framework.
| Internal term (this skill) | Write for the reader | What it means |
|---|---|---|
| 🟢 On Track / 🟡 At Risk / 🔴 Off Track | у графіку · під загрозою · відстаємо | загальний стан проєкту одним кольором і словами. |
| KPI | ключовий показник | цифра, за якою оцінюють результат роботи за період. |
| ETA | очікувана дата | коли пункт буде готовий. |
| Executive Summary | коротко головне | 3–4 речення: що йде за планом, що потребує уваги, головні перемоги. |
| mitigation | як зменшуємо ризик | дії, що знижують ймовірність або наслідки. |
<!-- glossary:end -->
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
- 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.