关于 team-dynamics
Team Dynamics & Leadership Skill 为工程经理提供团队领导框架与模板,涵盖一对一沟通、委派、团队健康和冲突处理,也为 team-leadership-agent 提供基础材料。
主要功能
- 01一对一会议模板
- 02RACI 委派框架
- 03团队健康评估
- 04冲突解决流程
- 05反馈与辅导模型
- 06领导决策树
适用场景
- 01规划定期经理一对一沟通
- 02依据经验匹配委派权限
- 03评估团队的心理安全感
- 04处理人际或任务冲突
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ pluginagentmarketplace/ custom-plugin-engineering-manager --skill team-dynamics安装后在 Claude Code 中输入/team-dynamics确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
assets/team_config.yamlreferences/TEAM_GUIDE.mdscripts/team_analyzer.py详细介绍
团队管理与领导力技能
用途
为工程经理提供可操作的框架、模板和指导,帮助他们打造高绩效团队、开展有效的 1 对 1 沟通、有效授权并培养心理安全感。
主要关联
Agent:team-leadership-agent 关系:此技能提供基础模板和框架,team-leadership-agent 会用它们为经理提供指导。
模板
1 对 1 会议模板
one_on_one_meeting:
duration: "30-60 min"
frequency: "Weekly recommended"
structure:
opening:
duration: "5 min"
focus:
- "Personal check-in"
- "Energy/mood assessment"
- "Their agenda items"
their_agenda:
duration: "15-20 min"
questions:
- "What's on your mind?"
- "What's blocking you?"
- "What wins to celebrate?"
- "What do you need from me?"
development:
duration: "10 min"
topics:
- "Progress on goals"
- "Skill development"
- "Career conversation"
feedback:
duration: "5-10 min"
bidirectional:
- "Manager to report"
- "Report to manager"
closing:
duration: "5 min"
outputs:
- "Action items documented"
- "Next meeting focus"
- "Support committed"
授权框架(RACI)
delegation_levels:
L1_direct:
authority: "Full decision authority"
support: "Available on request"
check_in: "Weekly"
use_when: "Experienced, proven track record"
L2_coach:
authority: "Decision authority with input"
support: "Proactive guidance"
check_in: "Bi-weekly"
use_when: "Growing, needs development"
L3_supervise:
authority: "Recommendation only"
support: "Active supervision"
check_in: "Daily"
use_when: "New to task, learning"
L4_control:
authority: "Execution only"
support: "Continuous oversight"
check_in: "Real-time"
use_when: "Critical task, new team member"
delegation_handoff_checklist:
- "Define outcome clearly (what done looks like)"
- "Explain context and why"
- "Clarify authority level (L1-L4)"
- "Set check-in schedule"
- "Confirm understanding"
- "Document decision rights"
团队健康评估
team_health_pulse:
dimensions:
psychological_safety:
questions:
- "I can speak up without fear"
- "Mistakes are learning opportunities"
- "I can ask 'dumb' questions"
scale: "1-5"
target: ">4.0"
clarity:
questions:
- "I know what's expected of me"
- "Team goals are clear"
- "My role is well-defined"
scale: "1-5"
target: ">4.0"
collaboration:
questions:
- "Team members help each other"
- "Information flows freely"
- "Conflicts are resolved constructively"
scale: "1-5"
target: ">4.0"
engagement:
questions:
- "I feel valued"
- "My work is meaningful"
- "I have growth opportunities"
scale: "1-5"
target: ">4.0"
interpretation:
excellent: ">4.5"
good: "4.0-4.4"
concerning: "3.5-3.9"
critical: "<3.5"
cadence: "Monthly pulse, Quarterly deep-dive"
冲突解决流程
conflict_resolution:
step_1_assess:
- "Identify conflict type (interpersonal vs task)"
- "Determine urgency and impact"
- "Gather facts (not opinions)"
step_2_individual:
- "Meet with each party separately"
- "Listen without judgment"
- "Understand interests (not positions)"
- "Document key points"
step_3_joint:
- "Facilitate joint session"
- "Establish ground rules"
- "Focus on interests, not positions"
- "Generate options together"
step_4_resolve:
- "Agree on solution"
- "Document commitments"
- "Set follow-up date"
- "Communicate to team if needed"
escalation_triggers:
- "No progress after 2 joint sessions"
- "Policy or legal concerns"
- "Harassment or discrimination"
- "Safety concerns"
决策树
何时授权
Task arrives
|
+-- Is this strategic/confidential?
| +-- Yes -> Keep it
| +-- No -> Continue
|
+-- Does someone else have better skills?
| +-- Yes -> Delegate to them
| +-- No -> Continue
|
+-- Is this a growth opportunity?
| +-- Yes -> Delegate with L2/L3 support
| +-- No -> Continue
|
+-- Do I have capacity?
+-- Yes -> Consider keeping, but still evaluate delegation
+-- No -> Must delegate, find right person
1 对 1 沟通频率决策
Team Member Situation
|
+-- New to role (<3 months)
| +-- Weekly, 45-60 min
|
+-- Struggling or PIP
| +-- Weekly or bi-weekly, 45 min
|
+-- Solid performer
| +-- Bi-weekly, 30 min
|
+-- High performer, autonomous
+-- Bi-weekly or monthly, 30 min
+-- But always available on request
反模式
anti_patterns:
micromanagement:
symptoms:
- "Checking in multiple times daily"
- "Redoing delegated work"
- "Requiring approval for small decisions"
remedy:
- "Focus on outcomes, not tasks"
- "Set clear success criteria upfront"
- "Trust and verify, don't hover"
absentee_manager:
symptoms:
- "Skipping 1-on-1s regularly"
- "Not knowing team's blockers"
- "Surprised by performance issues"
remedy:
- "Protect 1-on-1 time as sacred"
- "Weekly team check-ins"
- "Daily async standups"
conflict_avoidance:
symptoms:
- "Letting issues fester"
- "Not giving tough feedback"
- "Hoping problems resolve themselves"
remedy:
- "Address within 48 hours"
- "Use SBI feedback model"
- "Document and follow up"
快速参考卡
SBI 反馈模型
Situation: "In yesterday's standup..."
Behavior: "When you interrupted Sarah..."
Impact: "It made her hesitant to share ideas..."
GROW 辅导模型
Goal: "What do you want to achieve?"
Reality: "Where are you now?"
Options: "What could you do?"
Will: "What will you do?"
Tuckman 阶段
Forming -> Storming -> Norming -> Performing -> Adjourning
| | | | |
Polite Conflict Standards High-perf Transition
故障排除
| 问题 | 根本原因 | 解决方案 |
|---|---|---|
| 1 对 1 沟通让人感到尴尬 | 没有议程,经理说得太多 | 使用模板,倾听时间占 80% |
| 授权失败 | 期望不明确 | 使用交接检查清单 |
| 团队在会议中沉默 | 心理安全感不足 | 领导者展现脆弱,邀请大家发表意见 |
| 不断升级问题 | 授权给了错误层级 | 将任务与 L1-L4 级别匹配 |
验证规则
input_validation:
team_size:
type: integer
min: 1
max: 50
required: false
situation:
type: string
min_length: 10
required: true
urgency:
type: enum
values: [low, medium, high, critical]
default: medium
资源
书籍:
- The Manager's Path - Camille Fournier
- Radical Candor - Kim Scott
- Turn the Ship Around - David Marquet
- High Output Management - Andy Grove
研究:
- Google 的 Project Aristotle(心理安全感)
- Gallup Q12 员工敬业度研究
评论
支持 Markdown