---
name: repo-adaptation-playbook
description: Safely adapt an external GitHub repository into an existing project, with evidence-based analysis and an approval gate before touching code.
---

# External Repo Adaptation Playbook

## 1. What it does
Evaluates an external repository and the target project before copying anything, producing a conflict matrix and an explicit integration contract the user must approve. Prevents blindly copying architecture from an external source.

## 2. When to use it
- Wanting to integrate a library or pattern from an external repo
- Evaluating whether an open-source solution fits the current project
- Migrating functionality from one project to another without breaking it

## 3. Steps
1. Analyze the source repository's architecture with concrete evidence
2. Analyze the target project's architecture
3. Build a conflict matrix between the two
4. Ask one clarifying question at a time
5. Present an integration contract for explicit approval
6. Implement in isolation only after approval

## 4. GoHighLevel angle
If the external repo includes a CRM integration, evaluate specifically how it fits GoHighLevel's contact and pipeline structure.

## 5. Safety rules
Always work in draft mode: nothing is sent, published, or paid for without explicit client approval. Never invent data, metrics, or results. No passwords, tokens, or API keys are requested or shown in chat.

## 6. Deliverable
A clear, reviewable draft of the output (text, code, report, or file), ready for the user to approve before it becomes final.