mh-coo-client-offboarding

Manage client offboarding transitions from accepted to handed-off engagement states.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-client-offboarding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mh-coo-client-offboarding
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/coo/client-ops/mh-coo-client-offboarding
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-coo-client-offboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mh-coo-project-delivery-framework, mh-coo-feedback-collection, mh-ceo-referral-system, mh-ceo-relationship-map, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a structured and professional approach to client offboarding, ensuring deliverables are transferred correctly, client relationships are preserved, and all systems are updated.

Core Features & Use Cases

  • Engagement Management: Coordinates the transition from accepted to handed-off engagement state.
  • Deliverable Handoff: Packages and transfers all necessary materials to the client with detailed guidance.
  • Client Feedback & Referrals: Facilitates feedback collection and manages referral requests based on satisfaction.
  • Post-Delivery Follow-Up: Schedules and manages 30-day and quarterly follow-ups to ensure client satisfaction and identify future opportunities.
  • System Updates: Updates the engagement and client records across all relevant systems to reflect the offboarding status.

Quick Start

Run the mh-coo-client-offboarding skill with the Engagement ID.

Frequently Asked Questions about mh-coo-client-offboarding

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

FAQPage Schema
What is the best way to manage client offboarding and transition deliverables?▼

Client offboarding manages the accepted-to-handed-off engagement transition by executing a multi-step process involving package assembly, feedback collection, referral request management, and follow-up scheduling.

How do I collect feedback and request referrals during the client handoff process?▼

You collect feedback and request referrals during client handoff by utilizing automation scripts and reference materials that facilitate feedback collection and manage referral requests based on satisfaction levels.

How do I schedule post-delivery follow-ups to maintain client relationships?▼

You schedule post-delivery follow-ups to maintain client relationships by managing 30-day and quarterly check-ins, ensuring client satisfaction and identifying future opportunities through automated task scheduling.

Does client offboarding require a specific project delivery framework?▼

Client offboarding requires the mh-coo-project-delivery-framework as a prerequisite dependency, alongside feedback collection, referral system, and relationship map modules to execute its multi-step transition process.

Can I automate system updates when offboarding clients from an engagement?▼

You can automate system updates when offboarding clients by using included scripts to update engagement and client records across all relevant systems, reflecting the handed-off status accurately.