engineering-weekly-report
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.
npx skills add mohitagw15856/pm-claude-skills --skill engineering-weekly-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Engineering Weekly Report Produce a weekly engineering status report that a team can send to stakeholders, their engineering manager, and the team itself. The format is fixed week-over-week so readers know exactly where to look — shipping progress at the top, decisions in the middle, risks and next steps at the bottom. The report must be readable in under 2 minutes. Avoid prose walls: use bullet points, status tags, and short tables. If metrics are not provided, leave the metrics section with [data needed] markers rather than fabricating numbers. ## Required Inputs Ask for these if not already provided: - **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 - *
- Required Inputs
- Output Format
- Shipping Progress
- Shipped This Week
- In Progress
- Blocked
- Key Metrics
- Decisions
- Made This Week
- Needed Next Week
- Risks and Escalations
- Team Health
- Next Week's Priorities
- Appendix: Sprint Scorecard (if applicable)
What does the engineering-weekly-report skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill engineering-weekly-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.