skills.rest
s3nex-com
s3nex-comCOMMUNITY
Explore all skills by this author →
GitHub

team-coaching-engineering-culture

Coordinate quarterly team coaching to surface cultural issues and produce structured artifacts.

Updated Apr 8, 2026
Search Tags:#retrospective#runbook#team-coaching#norms#engineering-culture#growth-plans#team-health-snapshot
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill team-coaching-engineering-culture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-coaching-engineering-culture
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase3/team-coaching-engineering-culture
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill team-coaching-engineering-culture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

For small senior engineering teams, culture is a key lever that drives delivery quality and reduces recurring friction; this skill provides structured artifacts and routines to surface cultural issues and drive measurable improvements.

Core Features & Use Cases

  • Quarterly structured retros and a Team Health Snapshot to surface root causes behind delivery friction.
  • Growth Plans, knowledge-concentration risk tracking, and Engineering Norms to codify and sustain improvements.
  • Coaching conversations and runbooks to standardize feedback, align on norms, and accelerate capability development.

Quick Start

Schedule and run the quarterly retro using the provided format to produce a Team Health Snapshot and update growth plans.

Frequently Asked Questions about team-coaching-engineering-culture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structured retrospective to improve engineering culture?▼

To improve engineering culture, run a structured retrospective by surfacing root causes behind delivery friction and producing a Team Health Snapshot to track measurable improvements.

What is a Team Health Snapshot and how does it track team norms?▼

A Team Health Snapshot is an artifact that surfaces cultural issues and tracks growth goals alongside Engineering Norms to codify and sustain measurable improvements in delivery quality.

Can I use this structured coaching framework for a small senior engineering team?▼

Yes, this structured coaching framework is applicable for a small senior engineering team of 3 to 5 members seeking to track growth goals and maintain delivery quality artifacts.

How do I create engineering growth plans to track knowledge-concentration risk?▼

You create engineering growth plans during quarterly coaching conversations to track knowledge-concentration risk and codify Engineering Norms that accelerate capability development.

What is the best way to standardize feedback and coaching conversations for developers?▼

The best way to standardize feedback is using structured runbooks and coaching conversations to align on norms, track growth goals, and accelerate capability development.

Do I need YAML frontmatter to generate team coaching artifacts?▼

Yes, you need production-grade YAML frontmatter containing name and description to generate structured artifacts stored under docs for audit and learning.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

retro

Analyze commit history and per-author contributions to generate team retrospectives.

Community
Advanced
v1bh0rv1bh0r

nw-production-readiness

Implement production readiness controls for monitoring, runbooks, and quality gates.

Community
Advanced
vertivolatamvertivolatam
1

Post-Mortem Process

Guide blameless post-mortems with timeline reconstruction and 5 Whys analysis.

Official
Advanced
himes19himes19

retro

Generate a weekly retrospective report with developer stats, shipping streaks, and test health trends.

Community
Intermediate