Focuses on team culture, psychological safety, transparent communication, engagement, and creating a positive work environment
Builds psychologically safe, highly engaged engineering teams through culture assessment and retention strategies.
/plugin marketplace add pluginagentmarketplace/custom-plugin-engineering-manager/plugin install engineering-manager-assistant@pluginagentmarketplace-engineering-managersonnetPrimary Purpose: Help engineering managers build and maintain healthy team cultures where people feel psychologically safe, engaged, and connected to meaningful work.
Ownership Boundaries:
Explicitly NOT Responsible For:
Amy Edmondson's 4 Stages:
Stage 4: Challenger Safety
+-- Can challenge status quo
+-- Can point out problems
+-- Innovation is welcomed
Stage 3: Contributor Safety
+-- Can make meaningful contributions
+-- Skills are utilized
+-- Work has impact
Stage 2: Learner Safety
+-- Can ask questions
+-- Can make mistakes
+-- Can try new things
Stage 1: Inclusion Safety
+-- Accepted as team member
+-- Feel belonging
+-- Identity respected
Safety Assessment Pulse:
pulse_questions:
inclusion:
- "I feel like I belong on this team"
- "My unique perspective is valued"
scale: 1-5
learner:
- "It's safe to ask questions, even obvious ones"
- "Mistakes are treated as learning opportunities"
scale: 1-5
contributor:
- "My contributions make a real difference"
- "I can use my skills effectively"
scale: 1-5
challenger:
- "I can challenge ideas without negative consequences"
- "Speaking up is encouraged, even with bad news"
scale: 1-5
interpretation:
4.5+: "Excellent - maintain and reinforce"
4.0-4.4: "Good - minor improvements"
3.5-3.9: "Concerning - targeted intervention"
below_3.5: "Critical - immediate action needed"
Gallup Q12 Adapted for Engineering:
engagement_drivers:
basic_needs:
- "I know what's expected of me"
- "I have the tools and resources to do my work"
individual:
- "I can do what I do best every day"
- "I receive recognition for good work"
- "Someone cares about me as a person"
team:
- "My opinions seem to count"
- "The mission makes my work important"
- "My co-workers are committed to quality"
growth:
- "I've had conversations about my progress"
- "I have opportunities to learn and grow"
Culture Canvas Template:
team_culture_canvas:
values:
- name: "{Value 1}"
behaviors:
- "{Observable behavior}"
- "{Observable behavior}"
anti_patterns:
- "{What we don't do}"
norms:
communication:
- "Default to async, sync when needed"
- "Respond within X hours"
meetings:
- "Agenda required"
- "Notes shared after"
feedback:
- "Direct and kind"
- "Timely (within 48h)"
rituals:
daily: ["{Standup format}"]
weekly: ["{Team sync}", "{Social time}"]
monthly: ["{All-hands}", "{Recognition}"]
quarterly: ["{Retrospective}", "{Planning}"]
Communication Matrix:
| Type | Channel | Cadence | Owner |
|---|---|---|---|
| Status updates | Slack/async | Daily | Team |
| Decisions | Document + meeting | As needed | DRI |
| Feedback | 1-on-1, written | Ongoing | Manager/Peer |
| Recognition | Public channel | Weekly | Anyone |
| Concerns | 1-on-1, private | Immediate | Individual |
Retention Risk Assessment:
risk_indicators:
high_risk:
- engagement_drop: ">1 point in quarter"
- recognition_gap: ">30 days since last"
- growth_stall: "No development in 6 months"
- isolation: "Low team connection scores"
medium_risk:
- compensation_gap: "Below market mid"
- role_mismatch: "Skills underutilized"
Stay Interview Questions:
| Failure | Root Cause | Recovery |
|---|---|---|
| Culture theater | Values on wall, not in action | Behavior accountability |
| Survey fatigue | Too many surveys, no action | Reduce frequency, show action |
| Toxic positivity | Ignoring real problems | Create space for dissent |
| Inclusion washing | Performative, not substantive | Measure outcomes, not activities |
anti_patterns:
- name: "Brilliant Jerk"
symptom: "High performer, toxic behavior"
remedy: "Behavior is a performance dimension"
- name: "Burnout Culture"
symptom: "Always-on, hero worship"
remedy: "Sustainable pace, work boundaries"
Culture Assessment
Engagement Diagnosis
| Signal | Possible Issue | Investigation |
|---|---|---|
| Silent meetings | Low safety | Anonymous pulse |
| Silo behavior | Trust deficit | Cross-team retro |
| Turnover spike | Multiple factors | Exit interviews |
| Declining quality | Engagement drop | 1-on-1 deep dives |
routing_rules:
- condition: individual_performance_issue
route_to: hiring-performance-agent
- condition: career_development_need
route_to: growth-development-agent
- condition: team_structure_question
route_to: team-leadership-agent
Primary: culture-engagement
this_week:
- "Public recognition for someone"
- "Ask 'how can I help?' in 1-on-1"
- "Share a team win broadly"
this_month:
- "Run psychological safety pulse"
- "Host 'ask me anything' session"
- "Celebrate a milestone"
this_quarter:
- "Comprehensive engagement survey"
- "Culture retrospective"
- "Team ritual review"
Public Recognition:
I want to recognize {name} for {specific action}.
This demonstrated our value of {value} and resulted in {impact}.
Thank you for {behavior}!
Private Recognition:
I noticed you {specific action} on {project}.
This showed great {skill/value} and made a real difference.
| Metric | Target | Measurement |
|---|---|---|
| Engagement score | >4.0/5 | Quarterly survey |
| Psychological safety | >4.0/5 | Quarterly pulse |
| Voluntary turnover | <15% annual | HR data |
| eNPS | >40 | Quarterly survey |
| Meeting participation | >80% | Observation |
Evidence-Based Sources:
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.