Run any Skill in Manus with one click

handoff-intake

Stars0

Forks0

UpdatedMay 22, 2026 at 00:12

This skill should be used when an Orderful customer has just closed and the Implementation team needs to absorb the AE handoff. Triggers on: "intake new customer", "process the handoff for [customer]", "AE handoff for [customer]", "start onboarding for [customer]", "new customer just landed", "absorb the handoff doc", "kick off implementation for [customer]". Pulls the AE handoff document, Salesforce account context, any Slack handoff thread, and pre-sales call transcripts from the shared Drive folder, then produces a structured onboarding profile that downstream onboarding skills (kickoff-prep, partner-list-intake, migration-plan) consume.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Orderful

Orderful/orderful-onboarding-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

2 files

SKILL.md

readonly

More from this repository

same repository

customer-project-plan

Orderful/orderful-onboarding-skills

Draft a project plan for an Orderful customer onboarding — typically for a specific trading partner connection (e.g., Day Dream onboarding KeHE). Use when a user asks to 'build a project plan for [customer]', 'draft an onboarding plan for [customer] with [partner]', 'create a project plan for [customer] and [partner]', 'what's our plan for [customer]'s [partner] onboarding', or 'I need a plan and target dates for [customer]'. Produces an event-triggered three-phase plan (Pre-stage, Contract and Testing, Cutover) with explicit exit-criteria checklists per phase, an 'Already done' table that builds reader confidence, an 'In flight' table for active work, and a 'What we own this week' assignments table. Phases anchor to commercial gates (commercials close, contract sign, public launch) rather than fixed calendar dates. Internal and customer-facing variants are produced separately when both are needed — never combined.

2026-05-220

customer-project-watcher

Orderful/orderful-onboarding-skills

Set up a recurring background watcher for an Orderful onboarding customer that polls Slack, Gmail, the Orderful org, and Salesforce on a cadence and posts a concise digest back to the current chat whenever new activity is found. Use this whenever a user wants to stay on top of a specific customer's onboarding project without having to ask for updates — triggers include 'watch [customer] for updates', 'set up a watcher for [customer]', 'poll [customer] every hour', 'keep an eye on [customer]', 'background monitor for [customer]', 'don't let me miss anything on [customer]', or 'alert me when something changes on [customer]'. The skill resolves the customer's identifiers across systems, gathers the project stakeholder list, composes a self-contained polling prompt, and schedules it via the scheduled-tasks MCP. Designed for proactive project management — silent on quiet hours, vocal when there's signal.

2026-05-220

generate-sample-transactions

Orderful/orderful-onboarding-skills

Generate sample EDI transactions (850 POs, 856 ASNs, 810 invoices, 855 acks, 860 PO changes, 812 credit/debit adjustments) and inject them into Orderful as test-stream transactions, so a customer's connector and integration can be tested before their partnership is live. Uses real production transactions from comparable customers as the structural baseline and substitutes the target customer's product/SKU data. Triggers: 'generate sample 850s for [customer]', 'pre-stage test transactions for [customer] with [partner]', 'manufacture test PO for [customer]', 'inject sample [doc] for [customer]', 'create a test 850 from [partner] to [customer]'. Handles both phases — synthetic when product catalog is unknown (pre-NetSuite-access), real once the customer's catalog is pulled from their ERP. Always uses test stream, never live. Always uses real wire structure from existing partnerships.

2026-05-220

go-live-readiness

Orderful/orderful-onboarding-skills

This skill should be used when an Orderful customer is approaching their cutover date and the Implementation team needs to verify they're actually ready to flip to LIVE. Triggers on: "go-live readiness for [customer]", "pre-cutover check for [customer]", "is [customer] ready to go live", "run the cutover checklist", "what's blocking [customer] go-live", "ready to cutover [customer]". Produces a structured readiness report with a checklist of pre-cutover requirements, a risk assessment, and a cutover sequence plan.

2026-05-220

kickoff-prep

Orderful/orderful-onboarding-skills

This skill should be used when the Implementation team is preparing for the customer kickoff call — the first formal Implementation-led meeting after a customer signs. Triggers on: "kickoff prep for [customer]", "prep me for the [customer] kickoff", "build kickoff prep doc", "I have a kickoff call with [customer] tomorrow", "pre-call prep for [customer] kickoff", "AM prep for [customer]". Produces a structured pre-call .docx covering agenda, decisions to lock during the call, expected Q&A, exit criteria, and post-call action items. Reads from the onboarding profile produced by handoff-intake, the Customer Kick-Off SOP, and the shared pre-sales call-transcripts folder.

2026-05-220

migration-plan

Orderful/orderful-onboarding-skills

This skill should be used after partner-list-intake has produced a classified partner list and the Implementation team needs an actionable execution plan. Triggers on: "build the migration plan for [customer]", "execution plan for [customer]", "what should we do first for [customer]'s partners", "stack rank [customer]'s onboarding", "sequence the partner migration", "how do we run [customer]'s migration". Produces an Excel workbook with the execution plan stack-ranked by actionability, an outreach queue grouped by vendor, and a raw data sheet with per-partnership status and gap codes.

2026-05-220

name	handoff-intake
description	This skill should be used when an Orderful customer has just closed and the Implementation team needs to absorb the AE handoff. Triggers on: "intake new customer", "process the handoff for [customer]", "AE handoff for [customer]", "start onboarding for [customer]", "new customer just landed", "absorb the handoff doc", "kick off implementation for [customer]". Pulls the AE handoff document, Salesforce account context, any Slack handoff thread, and pre-sales call transcripts from the shared Drive folder, then produces a structured onboarding profile that downstream onboarding skills (kickoff-prep, partner-list-intake, migration-plan) consume.
version	0.2.0

Handoff Intake

Absorb a freshly-closed customer into the onboarding pipeline. Produce a single structured profile that every other skill in this plugin reads from.

When this fires

The customer has just moved to Type = "Customer" in Salesforce. The AE has dropped a handoff doc and probably a Slack message. The Implementation team needs to know who this customer is, what was sold, who the contacts are, what partners they trade with, and what was promised — before the kickoff call.

Inputs to gather

Run these in parallel; don't wait for one to finish before starting the next.

Salesforce — the source of truth for the deal

Account record (use find or soqlQuery): name, ID, owner (AE), industry, employee count, ARR, close date, type, OrgID custom field.
Latest Closed Won Opportunity: amount, contract length, line items, products purchased, sales engineer.
Contacts on the Account: name, title, email, role (decision-maker vs. day-to-day).

AE handoff document

Search Google Drive / the user's connected file system for a doc titled "[Customer] handoff" or similar.
If found, read it end to end. Extract: stated goals, in-scope transactions, partner list (if attached), promised timelines, known constraints, escalation contacts.
If not found, flag it — don't fabricate.

Pre-sales call transcripts (Google Drive)

Folder ID: 1QEycvwoKScvJ0zv-d8WbQql_X-Ujjpep (Orderful's shared call-transcripts folder).
Use the Google Drive MCP to search_files within that folder for filenames containing the customer name or slug — try both forms (e.g., "Acme Foods" and "acme-foods"). Match permissively; people name calls inconsistently.
For each hit, download the content via read_file_content. Transcripts are usually .docx, .txt, or .vtt.
Read each transcript in full. Extract verbatim quotes (1–2 sentences each) for:
- Stated goals — what the customer said they wanted, in their words.
- Concerns / pain points — what they said is broken today.
- Scope edges — transactions, partners, or integrations they mentioned that aren't in the handoff doc.
- EDI vendor history — who they're moving off of and why.
- Promises the AE made on the call — even if not captured in the handoff doc.
Cap extraction at ~3–6 quotes per transcript. Don't dump full transcripts into the profile.
If multiple customers could match the filename (e.g., "Acme Foods" vs. "Acme Manufacturing"), list the candidates and flag the ambiguity — don't silently include both.
If no transcripts are found, write "No transcripts found in shared folder for " — don't fabricate.

Slack handoff thread

Search #sales-handoff (or equivalent) for the customer name in the last 60 days.
Pull the thread. Surface anything the AE said in Slack that didn't make it into the doc — promises, concerns, "watch out for X".

Orderful org (if it exists)

search_organizations by name. If a result exists, fetch get_account_context for the org.
Capture: Org ID, ISA ID, communication channels configured, partnerships already created (rare at this stage, but possible).

Output

A single Markdown profile saved to the user's workspace as <customer-slug>-onboarding-profile.md. Use this exact structure:

# <Customer Name> — Onboarding Profile

**Generated:** <date>  ·  **Stage:** Just landed  ·  **SFDC:** <link>  ·  **Orderful org:** <id or "not provisioned">

## The deal in one paragraph
<2–3 sentences. What did they buy, why, who from, when does the contract start, what's the dollar value.>

## Contacts
| Name | Title | Role | Email |
|---|---|---|---|
...

## In-scope work
- Transactions: <810, 850, etc.>
- Partner count promised: <N or "TBD">
- EDI vendor situation: <e.g. moving off Cleo VAN>
- Integration: <e.g. NetSuite via SFTP>
- Go-live target: <date or "TBD">

## What the AE promised
- <bullet list of explicit commitments — timelines, scope, custom asks>
- <Append any on-call commitments captured in transcripts but not in the handoff doc. Format as a bullet with a block-quote and a source link, e.g.:
  - On the 2026-03-12 discovery call the AE committed to a 60-day go-live:
    > "We can absolutely get you live in 60 days from contract signature."
    [discovery call transcript](<drive link>)>

## Known risks / watch-outs
- <Things the AE flagged in the doc or Slack. Be specific.>
- <Append customer-voiced concerns from transcripts. Format with a block-quote and source link, e.g.:
  - Strong skepticism about SPS-managed partners:
    > "We've been burned by SPS twice — we don't want to repeat that."
    [demo call transcript](<drive link>)>

## Missing information
- <Anything you'd expect in a handoff that wasn't there. This drives the kickoff agenda.>
- <Surface any topic raised on calls that the handoff doc doesn't address, and any contradiction between the transcripts and the handoff doc.>

## Sources
- AE handoff doc: <link or "not found">
- Slack handoff thread: <link or "not found">
- Salesforce Account: <link>
- Closed Won Opportunity: <link>
- Call transcripts:
  - [<file name>](<drive link>) — <1-line gist>
  - <or "No transcripts found in shared folder for <customer>">

Rules

Don't fabricate. If the partner list wasn't in the handoff, write "TBD — must gather at kickoff." Don't invent partners.
Be skeptical of the AE. AEs sometimes promise things Implementation can't deliver. List those promises explicitly under "What the AE promised" so the AM can decide whether to push back.
Trust the customer's voice over the AE's summary. If a transcript and the handoff doc disagree on scope, timeline, or promises, surface the transcript version and flag the discrepancy in "Missing information". Quote, don't paraphrase.
Pull contacts from Salesforce, not the handoff doc. The doc often lists one or two; SFDC has the full list.
One profile per customer. If a profile already exists for this customer, ask whether to overwrite or update.
Workspace path. Save to the user's selected folder if available, else save to the temporary workspace and provide a computer:// link.

After saving, output a 4–5 line summary in chat: who the customer is, what they bought, the biggest open question for kickoff, and a link to the profile file. Then suggest: "Next step — run kickoff-prep once you have a kickoff call scheduled."