Community写作与编辑github.com

thananon/management-talk

将面向工程师的内容重新改写,适用于工程组织管理层(如VP、总监、项目经理、发布经理等),并针对不同沟通渠道(JIRA评论、Slack、异步站会、邮件、会议要点)进行适配。

management-talk 是什么?

该技能旨在帮助AI代理将技术细节丰富的工程师间沟通内容,转化为面向工程组织管理层(如副总裁、总监、项目经理、发布经理及高管)的清晰、简洁、非技术化的表达。它不仅能降低技术术语密度,还能根据目标渠道自动调整格式和语气,例如从冗长的Slack消息精简为异步站会要点,或将技术文档转化为JIRA评论中的状态更新。支持多种输出格式:JIRA评论、Slack帖子、异步站会行、邮件或会议要点。当用户明确要求“写给管理层/执行摘要/领导更新/状态更新”、“降低技术性/减少行话”,或需要将工程师原文转为Slack/邮件/站会/会议版本时,即可触发该技能。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/thananon/9arm-skills/tree/main/skills/management-talk

Installed? Explore more 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

management-talk 是做什么的?

将面向工程师的内容重新改写,适用于工程组织管理层(如VP、总监、项目经理、发布经理及高管),并针对目标渠道进行适配——JIRA评论、Slack帖子、异步站会行、邮件或会议要点。当用户要求为管理层/执行层/VP/总监/项目经理/发布经理撰写或改写内容,要求“执行摘要/领导更新/状态更新”,说“降低技术性/减少行话”,或要求将原本面向工程师的内容转为Slack/邮件/站会/会议版本时,触发本技能。

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

thananon/debug-mantra

Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on /debug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken/throwing/failing, asks to debug/diagnose/investigate an issue, or pastes a stack trace or error log.

thananon/post-mortem

Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.

thananon/scrutinize

Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.

相关技能