team-dynamics について
Team Dynamics & Leadership Skillは、エンジニアリングマネージャー向けにチーム運営のフレームワークとテンプレートを提供します。1on1、委任、チームの健全性、対立解決を扱い、team-leadership-agentの基礎資料にもなります。
主な機能
- 011on1ミーティング用テンプレート
- 02RACI委任フレームワーク
- 03チーム健全性の評価
- 04対立解決プロトコル
- 05フィードバックとコーチングモデル
- 06リーダーシップの判断ツリー
活用シーン
- 01定期的なマネージャー1on1の構成
- 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ミーティングを実施し、効率よく委任し、心理的安全性を育むための、実践的なフレームワーク、テンプレート、ガイダンスを提供します。
主な関連付け
エージェント: 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?"
タックマンモデルの段階
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 対応