EW
Engineering Weekly Report
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.
What to give it
▸Team name and report period — team name plus week number or date range (e.g., "Platform Team, Week 21, May 12–16")
▸Work items shipped this week — what was completed and released or merged
▸Work items in progress — what is actively being worked on, with rough percent-complete if known
▸Blocked items — what is blocked, who owns the block, and what is needed to unblock
▸Key decisions made — any architecture, process, or priority decisions made this week
▸Decisions needed next week — any decisions that need to be made soon and who needs to make them
▸Risks and escalations — anything that threatens next week's commitments or needs leadership visibility
▸Next week's top priorities — the 3–5 things the team plans to accomplish next week
▸Key metrics — reliability (error rate, p99 latency), velocity (story points completed), or other health indicators
▸Team health notes — PTO, new joins, attrition, morale signals worth noting
▸Sprint or iteration number — if the team runs sprints
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every blocked item names a specific owner and states what is concretely needed to unblock it — not just "waiting on X"
✓Decisions-needed table includes a deadline and a named decision owner, not a vague "TBD"
✓Metrics table is either populated with real numbers or explicitly marked `[data needed]` — no fabricated metrics
✓Next week's priorities are written as outcomes ("ship X", "complete Y migration") not as activities ("work on X")
✓Escalations that need leadership attention are called out explicitly in the Risks section — not just buried in a table row
✓The entire report is readable in under 2 minutes — if it is longer than one printed page, trim it
✓Report period (week number and date range) is clearly stated in the header
⚠️ What it refuses to do
Do not fabricate metrics — if data is not available, mark the field as `[data needed]` rather than estimating; stakeholders making decisions on invented numbers is actively harmful
Do not write next week's priorities as activities ("work on X") — they must be outcomes ("ship X", "complete Y migration") so stakeholders can evaluate whether the team delivered
Do not bury escalations inside a risk table row — anything needing leadership attention must be called out explicitly in the Escalations section
Do not list blocked items without naming a specific owner and a concrete unblocking action — "waiting on X" is not a blocker entry, it is a placeholder
Do not write a report that exceeds two printed pages — length signals the author has not done the editorial work of deciding what matters to stakeholders
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="engineering-weekly-report"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Engineering Weekly Report is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog