victor-shulga/gtm-strategy-skills

status-report

Generate a status report with KPIs, risks, and action items.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/victor-shulga/gtm-strategy-skills --skill status-report

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

/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 $ARGUMENTS

Terms 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):

  1. Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
  2. 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».
  3. 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.
  4. 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.
  5. 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 readerWhat 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

  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.