# Client Handoff Package Builder Playbook

This playbook automates the creation of professional handoff packages for clients at the end of a project. It aggregates deliverables, documentation, credentials, and next steps into a cohesive "Welcome to Your Result" document, ensuring a premium client experience and reducing post-project support requests.

## 1. Prompt Pack

These prompts guide your AI in synthesizing project history into a structured handoff package.

### Core Handoff Package Prompt

```
"You are a Project Success Manager. Your task is to generate a 'Project Handoff Package' for [Client Name] regarding [Project Name]. 

Review the project memory, deliverables, and final status reports. Your output must include:
- **Executive Summary:** A warm greeting and a brief recap of the project's success and primary outcomes achieved.
- **Deliverable Directory:** A categorized list of all final assets with links/paths (e.g., Codebase, Documentation, Graphics, Final Report).
- **Access & Credentials:** (Placeholders only) List the systems the client now has access to and where they can find their login details.
- **Maintenance & Operations:** Brief instructions on how to maintain the result (or links to the relevant SOPs).
- **Support & Next Steps:** Clear instructions on how to get help if needed and 2-3 recommended 'Phase 2' opportunities for future growth.
- **Offboarding Checklist:** A list of items the client should complete (e.g., 'Update passwords', 'Schedule final review').

Save the output as a clean markdown file to memory/handoffs/[Client-Name]-[Project]-handoff.md."
```

### Prompt Variations:

*   **The 'Value Recap' Prompt:**
    ```
    "Focusing on the project goals defined at the start of [Project Name], cross-reference our final results. Generate a 'Value Realization Report' section for the handoff package that highlights exactly how we met or exceeded their KPIs."
    ```
*   **Technical Transition Prompt:**
    ```
    "Generate a technical transition guide specifically for the client's internal dev team. Include repository links, deployment instructions, and a summary of the tech stack used in [Project Name]."
    ```
*   **The 'Referral/Testimonial' Ask Prompt:**
    ```
    "Draft a personalized email for [Client Name] to be sent alongside the handoff package. The email should thank them for the partnership and include a soft request for a testimonial or referral, tailored to the specific successes we had during [Project Name]."
    ```

## 2. Setup Guide

To implement the Client Handoff Package Builder Playbook:

1.  **Save the Playbook:** Save this content as `playbooks/client-handoff-package-builder.md`.
2.  **Create Cron Configuration:** Create `playbooks/client-handoff-cron.json` (see Config Snippet below).
3.  **Integrate Project Data:** 
    *   **Memory Search:** Ensure the agent has read access to the project's `memory/` folder.
    *   **Deliverables Folder:** Point the agent to the folder where project outputs are stored.
4.  **Trigger the Build:** This playbook is usually triggered manually when a project status changes to "Completed" or "Handoff Phase."
5.  **Review and Send:** Always review the package to ensure all links are active and placeholders are filled before sharing with the client.

## 3. Config Snippet

This JSON snippet defines a task that the agent can execute when a project reaches the "Handoff" milestone.

```json
{
  "cron": [
    {
      "name": "Trigger Handoff Package Build",
      "schedule": "manual",
      "task": "When a project status is updated to 'Handoff', search project memory for [Project Name] and [Client Name]. Use the 'Core Handoff Package Prompt' to generate a draft handoff document. Save to 'memory/handoffs/' and notify the Project Lead for review.",
      "agent": "cmo",
      "model": "gemini-flash"
    }
  ]
}
```

## 4. Permissions Checklist

Your agent needs:

*   **Read Access:**
    *   `shared-context/projects/` (to check project status).
    *   `memory/` (to gather project history and outcomes).
    *   Deliverables directory (to list assets).
*   **Write Access:**
    *   `memory/handoffs/` (to store the generated packages).
*   **Execution Permissions:**
    *   Ability to summarize large volumes of project context into concise sections.

## Safety Check (Required)

- **NEVER** include raw passwords or secrets in the generated package. Use placeholders like `[REDACTED - See Secure Vault]`.
- Verify all deliverable links are accessible by the client (not just internal paths).
- Ensure the tone remains professional and celebratory, reflecting the project's success.