# Weekly Executive Report

> Synthesize scattered weekly updates, project notes, metrics, risks, and team reports into a concise executive-ready weekly report. Use when Codex needs to prepare leadership updates, operating reviews, weekly business reviews, board-style summaries, or cross-functional status narratives.

- Skill: `clarentcinematics/weekly-executive-report` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add clarentcinematics/weekly-executive-report`
- Raw SKILL.md: https://api.skillmd.com/api/skills/clarentcinematics/weekly-executive-report/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: ClarentCinematics (https://skillmd.com/u/clarentcinematics)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/clarentcinematics/weekly-executive-report

---


# Weekly Executive Report

## Workflow

1. Identify the reporting period, audience, strategic priorities, and source material boundaries.
2. Group updates by business outcome, initiative, team, or workstream depending on the source structure.
3. Distinguish progress, measurable impact, risks, decisions needed, and next-week commitments.
4. Remove low-signal activity narration unless it explains impact, risk, or required action.
5. Produce a polished report with clear escalation points and accountable next steps.

## Output Standard

Use this structure by default:

- **Headline**: one sentence describing the week.
- **Executive Summary**: 3-5 bullets focused on outcomes, risk, and decisions.
- **Progress By Priority**: concise updates grouped by priority or workstream.
- **Metrics And Signals**: reported numbers, trend direction, and caveats.
- **Risks / Blockers**: impact, owner, urgency, and support needed.
- **Decisions Needed**: decision, deadline, options, and recommended owner.
- **Next Week Commitments**: concrete outcomes expected next week.

## Rules

- Do not overstate progress beyond the evidence provided.
- Preserve uncertainty when metrics are incomplete or qualitative.
- Escalate only items with business impact, timeline risk, resource risk, or executive dependency.
- Keep the report concise enough for a senior leader to scan in under five minutes.

## References

Read `references/report-patterns.md` when the user asks for a board-facing, operating-review, or team-of-teams format.

