management-talk

Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA comment, Slack post, async standup line, email, or meeting talking-points. Trigger when the user asks to write/rewrite for management / exec / VP / director / PM / release manager, asks for an "executive summary / leadership update / status update", says "make this less technical / less jargony", or asks for a slack / email / standup / meeting version of work originally written engineer-to-engineer.

Try your first task

Turn an engineering update into a leadership Slack post

Start a fresh conversation. Replace the highlighted placeholders.

Use the management-talk skill to rewrite the following engineer-to-engineer update as a concise Slack post for engineering-org leadership. Preserve relevant product or framework names, issue keys, PR numbers, status, impact, owner, and next step. Remove function names, file paths, commit SHAs, and other code-level identifiers, and translate the mechanism into plain-English cause and effect. Do not send the message. Source update: [paste update].

Required inputs

Engineer-to-engineer source update
Relevant status, impact, owner, issue or PR references, and next step

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

173 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗