Management Talk

You've written the update. Now you need to send it to your VP, post it in the release channel, or turn it into talking points for standup, and the engineer-to-engineer version you drafted isn't going to work. This skill rewrites technical content for engineering-org leadership: people who read JIRA keys and product names but not function signatures or commit SHAs. It keeps the frameworks and ticket numbers, strips the code identifiers, translates mechanisms into plain cause-and-effect, and reshapes everything for the channel it's going into. JIRA comment gets structure and bolded labels. Slack gets a one-line TL;DR and three bullets. Standup gets a single sentence. It's the translation layer between how engineers talk to each other and how they talk up the org.

skills.sh installs: 4.7K
GitHub stars: 3.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thananon/9arm-skills --skill management-talk --agent claude-code

Installs into .claude/skills of the current project.

Files

Management Talk

Same audience and translation rules as a written status report, but shaped for the channel — JIRA comment, Slack post, async standup, email, or meeting talking-points. The audience reads code names but not code. The channel decides the length, formatting, and how much structure to leave on the page.

Use this any time engineering content needs to flow up the org, sideways into product/release, or into a non-engineering meeting — regardless of the destination.

When to invoke

"write something for management / exec / VP / director / PM / release manager"
"rewrite this for [non-eng audience]"
"make this non-technical" / "less techy" / "less jargony"
"send a slack update / standup note / email" about a piece of engineering work
"executive summary" / "exec summary" / "leadership update" / "status update"
"talking points for [meeting]" based on an engineering update

If the channel is unclear after the trigger, ask one short question — "JIRA, Slack, standup, or email?" — and stop.