From grimoire
Runs structured exit interviews that capture retention insights from departing employees. Useful for HR, people analytics, or talent management workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:run-exit-interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conduct a structured exit interview that surfaces actionable retention insights from departing employees.
Conduct a structured exit interview that surfaces actionable retention insights from departing employees.
Adopted by: LinkedIn, Deloitte, McKinsey, and organizations with mature people analytics functions Impact: Work Institute (2020) found 77% of employee turnover is preventable; organizations that act on exit interview data reduce voluntary attrition by 10–25%. HBR research shows most companies collect exit data but only 4% systematically use it. Why best: Departing employees often share candid feedback they withheld while employed. Aggregated exit data identifies systemic issues (management quality, compensation gaps, career ceiling) that engagement surveys underreport due to social desirability bias.
Sources: Garvin "Making Exit Interviews Count" HBR (2008); Work Institute "Workforce Retention Report" (2020); SHRM Exit Interview Best Practices (2022)
Decide the interviewer — never have the direct manager conduct the exit interview. Use HR, a skip-level, or an independent third party. Departing employees are less candid with their own manager.
Schedule promptly — conduct within the last week of employment. Earlier risks the employee not yet being candid; later risks memory degradation and declining willingness.
Set the context — open by explaining the purpose: the conversation is confidential, feedback improves the organization for current employees, and no response will affect references or final pay.
Use a structured question set — cover: reason for leaving, job satisfaction, manager relationship, team culture, compensation competitiveness, career development opportunities, and what would have caused them to stay.
Ask the "stay question" — "What could we have done differently to retain you?" This is the single highest-signal question. Probe the first answer: "What else?"
Explore the new opportunity — ask about the new role (function, company size, industry, compensation). This reveals where talent is going and what pulls employees away.
Probe on management — this is often the real reason, rarely volunteered first. Ask: "How would you describe your relationship with your manager?" and "What could your manager have done differently?"
Document verbatim quotes — write down key phrases exactly as stated, not paraphrased. Verbatim quotes are more persuasive to leadership than sanitized summaries.
Aggregate and analyze quarterly — categorize exit reasons by theme (compensation, career growth, management, culture, work-life balance, external pull). Track trends over time and by team.
Report to leadership with recommendations — present quarterly exit data with trend analysis and specific, actionable recommendations. Measure whether interventions change exit reasons over subsequent quarters.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireRuns a structured stay interview with a valued direct report — before flight risk shows — surfaced when a manager wants to learn what keeps the person engaged or might drive them to leave.
Structure offboarding processes and knowledge transfer. Activate for: offboarding, offboard, exit process, resignation, leaver, departing employee, employee leaving, last day, exit interview, notice period, handover plan, knowledge handover, departure checklist, systems access removal, final paycheck, P45, exit documentation, farewell, redundancy process, termination process, how to offboard. NOT for: onboarding plans (use onboarding), knowledge capture plans without a departure (use knowledge), performance reviews (use performance-review).
Prepares hypothesis-driven user interview guides based on Teresa Torres, Rob Fitzpatrick, Bob Moesta, and Cindy Alvarez. Runs live or imports from Granola, extracts signal into FEEDBACK.md.