retaining-developers

Diagnose engineer attrition risk and generate retention interventions with 1:1 scripts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill retaining-developers-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retaining-developers
Source: https://github.com/imsus/cto/tree/main/.agents/skills/retaining-developers
Command: npx skills add https://github.com/imsus/cto --skill retaining-developers-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering managers prevent engineer attrition by diagnosing why an engineer is at risk and selecting the right intervention before disengagement hardens into resignation.

Core Features & Use Cases

  • Five-state retention diagnostic: identifies whether the engineer feels unappreciated, lonely, bored, stuck, or apathetic based on signals in recent behavior and 1:1 context.
  • Action plan and conversation tooling: produces a week-to-month plan plus a ready-to-use retention conversation script tailored to the likely state.
  • Compensation, equity, and recognition playbooks: guides how to handle raise and equity/option conversations, and provides zero-budget recognition ideas when budget is constrained.
  • Special-case handling: includes a framework for when an engineer already has another offer and for recognizing warning signs of disengagement.

Quick Start

Use the retaining-developers skill when a manager says their engineer is disengaged, unhappy, or may be leaving, and then ask it to produce a risk read, likely state, targeted 1:1 questions, an action plan, and a conversation script.

Frequently Asked Questions about retaining-developers

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

FAQPage Schema
How do I diagnose why a software engineer is disengaged and at risk of leaving?

To diagnose engineer attrition risk, map observed behavioral signals and 1:1 context to a five-state retention model to determine if the developer feels unappreciated, lonely, bored, stuck, or apathetic.

What should I say in a 1:1 conversation to retain an engineer who wants to quit?

For a retention conversation, use a tailored 1:1 question set and conversation script designed for the engineer's specific disengagement state, including compensation, equity, and recognition guidance.

How do I handle an engineer retention conversation when they already have another offer?

Handle an engineer with another offer by applying the special-case retention framework to generate a targeted action plan and conversation script addressing compensation or equity concerns.

What are the best zero-budget recognition ideas to prevent developer attrition?

Zero-budget recognition ideas help prevent developer attrition when compensation budgets are constrained, integrated into the action plan to make engineers feel appreciated without financial cost.

When should an engineering manager intervene to prevent developer turnover?

An engineering manager should intervene to prevent developer turnover when disengagement warning signs appear, using a week-to-month action plan before disengagement hardens into resignation.