Receber por email
← Voltar para o catálogo

executive-update

Transforma atualizações detalhadas de produtos em resumos executivos concisos. Ideal para briefings de liderança ou C-suite, gerando um documento estruturado de 250 palavras com métricas, progresso, riscos e próximos passos.

991estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add mohitagw15856/pm-claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/executive-update-mohitagw15856/svg)](https://www.skillteca.com.br/skills/executive-update-mohitagw15856)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Executive Update Skill

Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.

Required Inputs

Ask the user for these if not provided:

  • Product update or notes (raw input to transform — even bullet points work)
  • Audience (CEO, board, specific exec, or general leadership)
  • Period (this week / sprint / month / quarter)
  • Key metrics (what numbers matter to this audience)

Executive Communication Principles

  • Lead with the headline, not the context
  • Every update should answer: "So what does this mean for the business?"
  • Flag decisions needed clearly — don't bury asks in paragraphs
  • Be honest about risks — executives hate surprises more than bad news

Process

  1. Read the full product update provided
  2. Identify: key metric movements, decisions required, risks to flag, wins to celebrate
  3. Write in reverse pyramid style — most important first
  4. Limit to 250 words maximum for the main body
  5. Add a "Decisions Needed" section with clear options and your recommendation
  6. Validate — Confirm every decision needed has a specific option and recommendation (not just "TBD"), and every risk has a mitigation or watch plan

Output Structure

Product Update — [Date / Sprint / Month]

Headline: [One sentence on the most important thing]

By the Numbers:

  • [Metric 1]: [value] ([vs. target / last period])
  • [Metric 2]: [value] ([vs. target / last period])
  • [Metric 3]: [value] ([vs. target / last period])

Progress This Period: [3-4 bullet points, outcome-focused not activity-focused]

Risks & Watch Items: [2-3 bullets — be direct, include mitigation]

Decisions Needed:

  1. [Decision] — Options: [A] or [B] — Recommendation: [your view] — Needed by: [date]

What's Next: [2-3 bullets on next period priorities]

Quality Checks

  • [ ] Whole update is under 250 words (if not, cut ruthlessly)
  • [ ] Every metric includes a comparison point (vs. target or last period)
  • [ ] Every risk has a mitigation or watch action
  • [ ] Every decision needed has at least two options and a recommendation
  • [ ] Written for a CFO or CEO — no jargon, all outcomes
Compartilhar X LinkedIn