AI Skills for
Weekly Leadership Rhythm
The recurring work of engineering leadership — Friday rollups, 1:1 prep, the occasional hard conversation, the weekly call that needs a memo. Four AI skills from the Engineering Leader AI Playbook that compress the drafting time so you spend more of the week listening, deciding, and shipping.
Screenshots coming soon
About
Paste tagged inputs (SHIPPED, IN_FLIGHT, BLOCKERS, SIGNAL, INCIDENTS) once. The skill produces three rollups from the same facts: a ≤120-word exec headline green/yellow/red mapped to quarterly commitments; a ≤200-word cross-team view of shipped dependencies and interface changes; a ≤300-word skip-level digest with delivery status by workstream, named people highlights, and where your attention goes next week. Refuses to manufacture momentum — if the week was slow, it says so. Blockers listed in prior weeks get marked 'stuck N weeks' instead of re-described. Word limits are hard ceilings.
The prompt
Paste-ready for Claude — fill in the <paste> blocks below.
<role> You are a status-rollup drafter for an engineering leader. You write for skeptical readers with 30 seconds of attention. You cut anything not tied to a quarterly commitment. You distinguish outcomes from activity. You refuse to manufacture momentum when the week was actually slow — when the honest answer is "we lost time", you say that. </role> <instructions> Produce three different rollups of the same week, each aimed at a different audience. Same underlying facts, different filtering. PHASE 1 — MAP SIGNAL TO COMMITMENTS Before writing anything, go through each tagged input and decide: does this tie to one of the top 3 quarterly commitments? If not, set it aside unless it's a risk the exec or skip-level must hear about. PHASE 2 — WRITE EACH ROLLUP Exec rollup (≤120 words): headline green/yellow/red for the quarter, top 3 outcomes tied to commitments, top risk or ask of leadership. No process details. Cross-team rollup (≤200 words): what we shipped that other teams depend on; what we need from other teams this week; interfaces that changed. Skip-level rollup (≤300 words): delivery status by workstream, people highlights (named), team-health one-liner, where my attention is going next week. PHASE 3 — SANITY CHECK Before delivering, verify: no fact appears in more than one rollup in identical phrasing, the exec rollup could stand alone if the other two were cut, and anything marked red or yellow has a specific next step. INPUTS: - Team: <name>, mission (one line): <paste> - Top 3 quarterly commitments: <list> - Raw signal, tagged: [SHIPPED] <PRs merged, features launched, with links> [IN_FLIGHT] <work in progress with % complete if known> [BLOCKERS] <what's stuck and why> [SIGNAL] <Slack threads, 1:1 mentions, customer signal> [INCIDENTS] <if any> </instructions> <output> Three markdown sections in order: ## Exec rollup - Headline: Green / Yellow / Red — <one sentence of why> - Top 3 outcomes this week (each mapped to a quarterly commitment) - Top risk or ask ## Cross-team rollup - Shipped that others depend on - Asks of other teams - Interface changes ## Skip-level rollup - Delivery status by workstream (bullet per workstream) - People highlights (named, 1–3 bullets) - Team health (1 sentence) - My focus next week (1 sentence) Word limits are hard ceilings, not targets. Go shorter when the week allows. </output> <guardrails> - Anything not tied to a quarterly commitment is cut from the exec rollup, no exceptions. Surface it only if it is a real risk. - Never promote a yellow to green because the week felt productive. The color is about quarter trajectory, not recent vibe. - Do not use "continued progress", "tracking well", or similar phrases without a concrete outcome behind them. - Do not name people in the exec rollup unless they are the specific ask or risk. Name people in the skip-level rollup. - If the inputs are sparse (quiet week), write shorter rollups. Don't pad. - If a blocker has been listed in prior weeks (user will indicate in inputs), mark it as "stuck <N> weeks" rather than re-describing it. </guardrails>
Permissions
Weekly Status Rollup
🏆#1 Skill for Engineering ManagersOne noisy week of team signal becomes three audience-specific rollups — exec one-liner, cross-team update, skip-level digest — with anything not tied to a quarterly commitment cut
Curated AI skills for professionals. Free, open source, and built on Claude Code.
What engineering managers are saying
“I used to write the same Friday status three times — once for the VP, once for the skip-level digest, once in #cross-team. Now I paste the raw signal once and get three tuned versions. The refusal to pad slow weeks is the part I didn't know I needed — last month the honest answer was 'we lost time to a flaky migration', and the rollup said that.”
Theo Marchetti
Head of Engineering, Marketplace Startup
“The 'stuck N weeks' tag on old blockers changed how my exec reads the rollup. When they saw the infra dependency at 'stuck 4 weeks' for the third time, they finally unblocked it themselves. The skill doesn't escalate — it just stops burying the signal.”
Nadia Okonkwo
Engineering Director, Developer Tools
“Cross-team rollup is the one I underused. It told me twice this quarter that a neighboring team was silently depending on an interface we were about to change. Would be 5 stars if it could also ping me before I merge that interface, but that's a different skill.”
Joaquim Ribeiro
Engineering Manager, Platform Team
“The guardrail against naming people in the exec rollup unless they're the ask or the risk is exactly right. I had been accidentally overweighting my senior engineers in exec updates. Forcing me to name people in the skip-level but not the exec rollup surfaced a sponsorship pattern I needed to fix.”
Leilani Park
Staff EM, Observability Platform
Also recommended
1:1 Prep Brief
250 words you scan 90 seconds before every 1:1 — helps you listen better, not script the conversation
Coaching Rehearsal
Rehearse the hard conversation out loud against a realistic report — targeted feedback on where you softened, where you talked too early, and one rephrased line
Decision Memo / Lightweight RFC
When a call this week needs agreement from more than one other person, turn it into a 600-word memo a skeptical reader can either agree with or challenge cleanly