SKILL.md
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
- 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
Optional but useful:
- 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
Output Format
Engineering Weekly Report — [Team Name]
Week: [Week Number] | [Date Range, e.g., May 12–16, 2025] Author: [Name or Team Lead] Distribution: [e.g., Eng leadership, Product, Team]