The handover from sales to the delivery team is one of the moments where customer projects most often lose momentum. What was discussed in the sales conversation often only partially carries through to the project team. The Handover Package collects all available sources, reconciles them and condenses them into one document that gives the delivery team a complete picture: customer, contacts, agreed deliverables, expectations, timeline, specifics and a concrete checklist for the first two weeks.
\nThe skill is built for agencies and consultants where sales and delivery are separate roles, especially when running several customer projects in parallel. It does not replace a CRM or contract review. What it deliberately does not do: carry internal sales data such as margins or ratings into the customer facing delivery document, and it does not invent information. Where details are missing, it flags them as an open point instead of filling them in.
\nThe quality of the result depends directly on the quality of the input. Without meeting notes or a quote, the document is built on the three required fields alone and stays correspondingly brief.
\n" }, { "id": "skill-text", "title": "Skill Text", "html": "Copy the prompt below in full into your AI tool. As a file: uebergabe-paket.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Provide the details", "beschreibung": "Customer, agreed deliverables, planned project start and available sources such as meeting notes, quote or emails are handed over.", "rolle": "mensch" }, { "nr": 2, "titel": "Consolidate sources", "beschreibung": "All sources are reviewed, contradictions are flagged and the details are sorted chronologically.", "rolle": "automatisch" }, { "nr": 3, "titel": "Stakeholder map and expectations", "beschreibung": "Contacts are listed, customer expectations and known risks are documented.", "rolle": "automatisch" }, { "nr": 4, "titel": "Build the onboarding checklist", "beschreibung": "A practical checklist for the first two weeks is created, with ownership and deadlines.", "rolle": "automatisch" }, { "nr": 5, "titel": "Finished handover document", "beschreibung": "A complete document of roughly 800 to 1,500 words is ready: customer overview, deliverables, risks and recommendations for the kickoff.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Gather the information", "text": "Meeting notes, quote and CRM records are collected before the start." }, { "titel": "Use the skill", "text": "The skill text is copied and filled in with the available information." }, { "titel": "Have the handover reviewed", "text": "The delivery team reviews the document before it is passed on." }, { "titel": "Establish it as the standard", "text": "Every handover runs through this skill going forward." } ], "zutaten": [ "Customer", "Agreed deliverables", "Project start", "Sources" ], "beispielSzenario": "A customer has signed the quote and the project start is scheduled for the coming week. Available are meeting notes from three appointments, a quote, email correspondence and CRM records. The skill brings all sources together into a handover document that gives the project team a complete overview of the customer, deliverables, expectations and open points.", "eingaben": [ { "feld": "Customer company name and contact person", "pflicht": true }, { "feld": "Agreed deliverables or booked package", "pflicht": true }, { "feld": "Planned project start date", "pflicht": true }, { "feld": "Meeting notes or minutes from sales calls", "pflicht": false }, { "feld": "Quote or contract", "pflicht": false }, { "feld": "Special agreements or customer requests", "pflicht": false }, { "feld": "Known risks or sensitivities", "pflicht": false }, { "feld": "Budget and billing details", "pflicht": false } ], "ausgabe": "A structured handover document of roughly 800 to 1,500 words: customer overview, stakeholder map, agreed deliverables, expectations and success criteria, project scope, specifics, open points, a short summary of the sales history, an onboarding checklist and recommendations for the kickoff.", "prompt": "# DESCRIPTION\nBuilds a complete handover document from all available sources for the transition from sales to delivery or the project team. Brings together information from conversations, quotes and CRM into one structured handover document.\n\n# INPUT\n- Customer company name and contact person (required)\n- Agreed deliverables or booked package (required)\n- Planned project start date (required)\n- Meeting notes or minutes from sales calls (optional)\n- Quote or contract (optional)\n- Special agreements or customer requests (optional)\n- Known risks or sensitivities (optional)\n- Budget and billing details (optional)\n\n# OUTPUT\n- Format: Structured handover document\n- Structure:\n 1. Customer overview (company, industry, size, market position)\n 2. Contacts and stakeholders (with roles and contact details)\n 3. Agreed deliverables (details from the quote or contract)\n 4. Customer expectations and success criteria\n 5. Project scope (timeline, milestones, budget)\n 6. Specifics and sensitivities\n 7. Open points, still to be clarified\n 8. Sales history (short summary of the sales process)\n 9. Onboarding checklist\n 10. Recommendations for the kickoff\n- Length: 800 to 1,500 words\n\n# CONTEXT\n- Domain knowledge: handover from sales to delivery, customer project onboarding, stakeholder management\n- Constraint: use only verified information. Where facts are missing, explicitly mark the assumption as an assumption. No confidential sales internals (for example margins) in the customer facing part.\n- Address the user in a professional manner throughout.\n\n# WORKING INSTRUCTIONS\n\n## Step 1: Consolidate information\nGo through all available sources and extract relevant information.\n- Rule: identify and flag contradictions between sources\n- Rule: sort chronologically, what was discussed or agreed and when\n- Rule: distinguish contractual agreements from verbal arrangements\n- No-go: sales internals (margins, internal ratings) do not belong in the handover\n\n## Step 2: Build the stakeholder map\nList all relevant people on the customer side and internally.\n- Rule: role, responsibility and communication preference per person\n- Rule: separate decision makers from operational contacts\n\n## Step 3: Document expectations and risks\nMake customer expectations explicit, name known risks.\n- Rule: phrase expectations in the customer's own language\n- Rule: rate risks by likelihood and impact\n- Rule: propose possible countermeasures\n\n## Step 4: Build the onboarding checklist\nPractical checklist for the first two weeks.\n- Rule: each item with ownership and a deadline\n- Rule: separate technical and organizational tasks\n- Rule: kickoff preparation as the first block\n\n# QUALITY CONTROL\n[ ] Customer overview with industry, size and context present\n[ ] All contacts captured with roles and contact details\n[ ] Agreed deliverables reproduced in detail and correctly\n[ ] Customer expectations documented explicitly\n[ ] Timeline and milestones defined\n[ ] Specifics and risks named\n[ ] Open points clearly marked as such\n[ ] Onboarding checklist with ownership\n[ ] Recommendations for the kickoff included\n[ ] No confidential sales internals in the document\n[ ] Missing facts marked as an assumption\n\n# CONVERSATION START\nHello. I will help you prepare the handover to your delivery team.\n\nTo make the handover complete, please share what you have:\n1. Customer, company, contact person, industry\n2. Booked deliverables, what was agreed\n3. Project start, when it begins\n4. Context, meeting notes, quote, emails, specifics\n\nThe more you provide, the more precise the handover will be. Even with just the basic details, a solid handover document will result.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the skill text above using the copy button.", "Click your profile picture and select \"Skills\".", "Click \"Create skill\" and paste the copied text as the instruction.", "Adjust inputs, outputs and format where your case requires it.", "Save the skill. It is available in all chats from that point on." ], "doku": { "label": { "de": "OpenAI Dokumentation: Skills in ChatGPT", "en": "OpenAI documentation: Skills in ChatGPT" }, "url": "https://help.openai.com/de-de/articles/20001066-skills-in-chatgpt" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the skill text above using the copy button.", "Open claude.ai and go to \"Skills\" in your profile.", "Create a new skill and paste the copied text as the instruction.", "The skill works in claude.ai, in Claude Code and through the API.", "Available on the Pro, Max, Team and Enterprise plans." ], "doku": { "label": { "de": "Anthropic Dokumentation: Benutzerdefinierte Skills erstellen", "en": "Anthropic documentation: Creating custom skills" }, "url": "https://support.claude.com/de/articles/12512198-benutzerdefinierte-skills-erstellen" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the skill text above using the copy button.", "Open Copilot Studio and create a new agent.", "Paste the copied text as the instruction.", "Connect knowledge sources and tools where needed.", "Publish the agent for yourself or for your organisation." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the skill text above using the copy button.", "Open the sidebar and click \"Add skill\".", "Paste the copied text directly as the instruction.", "Connect the skill to integrations such as Gmail or Slack where needed.", "Save the skill and release it for yourself or your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Skills", "en": "Langdock documentation: Skills" }, "url": "https://docs.langdock.com/de/product/chat/skills" } } ] }, "itemIcon": "package-check", "recommended": [ { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "aufgaben-raster", "category": "skill", "name": "The Task Grid", "teaser": "Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "list-checks" }, { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "office", "category": "skill", "name": "The Office Workbench", "teaser": "The Office Workbench is an executable Claude skill that builds, reads, and edits Word, PowerPoint, and Excel files with the right tools, formatting rules, and quality checks for each format.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "table" }, { "slug": "pdf", "category": "skill", "name": "The PDF Workbench", "teaser": "The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "file-type-2" }, { "slug": "retro-regelwerk", "category": "skill", "name": "The Retro Rulebook", "teaser": "The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "rotate-ccw" }, { "slug": "tagesabschluss-protokoll", "category": "skill", "name": "The Shutdown Protocol", "teaser": "The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "moon" }, { "slug": "onboarding-strecke", "category": "workflow", "name": "The Onboarding Pipeline", "teaser": "Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "door-open" }, { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "team-digest-schleife", "category": "workflow", "name": "The Team Digest Loop", "teaser": "A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mails" }, { "slug": "termin-bruecke", "category": "workflow", "name": "The Appointment Bridge", "teaser": "A workflow that reads incoming appointment requests, checks calendar availability, and drops a ready reply draft with three time proposals into the inbox for review before sending.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "calendar-check" }, { "slug": "buero-lotse", "category": "assistent", "name": "The Office Navigator", "teaser": "An assistant that guides you through three recurring office tasks, structured brainstorming, ready-to-use communication drafts, and concrete project planning, based on the context knowledge you provide.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "printer" }, { "slug": "okr-stratege", "category": "assistent", "name": "The OKR Strategist", "teaser": "Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "target" }, { "slug": "prozess-dokumentierer", "category": "assistent", "name": "The Process Documenter", "teaser": "Captures undocumented business processes through a structured interview and turns them into clear, visual process documentation with steps, decision points and responsibilities.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "route" }, { "slug": "risikomatrix-pruefer", "category": "assistent", "name": "The Risk Matrix Reviewer", "teaser": "Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "grid-3x3" }, { "slug": "statusbericht-kurator", "category": "assistent", "name": "The Status Report Curator", "teaser": "Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "clipboard-check" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "korrespondenz-skript", "category": "skill", "name": "The Correspondence Script", "teaser": "Drafts a ready-to-send business email, from subject line to a concrete next step, matched to the recipient, occasion and tone.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mail" }, { "slug": "nuwacom", "category": "tool", "name": "Nuwacom", "teaser": "Nuwacom is an AI-powered communication platform that unifies a company's chat, voice and meetings in a single interface with built-in summaries and action items.", "domaene": "Betrieb & Projektmanagement", "logoFile": "nuwacom.svg", "logoEinzug": 1 } ] }