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.

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.

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.

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.

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.

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.

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.

Draft an outreach email to an Orderful onboarding customer — welcome notes, pre-kickoff prep, access requests, re-engagement, follow-ups. Use whenever the user asks to write, draft, or send an email to a customer who's in onboarding — pre-kickoff emails asking for system access, welcome / kickoff-prep messages, NetSuite / ERP access requests, requests for partner lists or EDI system credentials, re-engagement notes for stalled customers, or any outbound message to the customer-side stakeholders during onboarding. Also trigger on phrases like 'draft an email to [customer]', 'welcome email for [customer]', 'ask [customer] for NetSuite access', 'send the access request to [customer]', 'pre-kickoff outreach', 're-engage [customer]'. The skill verifies names and emails from Salesforce and Slack before drafting (never invents addresses), structures the email so the lede isn't buried, and saves the result as a Gmail draft with HTML formatting so bold renders properly.

This skill should be used when an Orderful customer has provided their list of trading partners (usually as a spreadsheet, email body, or screenshot) and the Implementation team needs to normalize it into something Orderful can act on. Triggers on: "normalize the partner list for [customer]", "process the partner spreadsheet", "classify [customer]'s partners", "the customer sent their partner list", "intake the partner list", "ingest [customer] partners", "I got the partner list, what now". Produces a normalized .xlsx classifying each partner by Orderful network status, EDI vendor, transaction scope, and priority — ready to feed into migration-plan.

Draft a project status update to an Orderful customer project Slack channel — EOD recaps, milestone updates, post-call summaries, weekly status notes. Use whenever the user asks to post an update, recap, status, or note to a customer project channel (typically #{customer}-mts-project). Triggers: 'push an update to slack', 'slack the team on [customer]', 'post EOD status for [customer]', 'recap today on [customer]', 'send a status update', 'push a slack note to the team'. The skill enforces Slack-native formatting (single-asterisk bold, real @mentions for assigned owners), keeps updates high-level and skimmable (not engineering logs), and always saves as a draft so the user can review before sending. Anchors progress in real comparables and confident framing rather than hedged 'drafted, ready to file' language.

Guide and execute SPS Commerce Testing & Certification (TnC) setup for an Orderful customer end-to-end. Use this skill whenever a user asks to configure, submit, or monitor an SPS certification setup — including populating EDI info, connection details, EDI setup, test document details, and checking scenario/test results. The skill pulls EDI configuration from the Orderful customer's account via MCP and calls the SPS TnC Bridge API directly. Also trigger for: "set up SPS testing", "configure SPS certification", "SPS TnC setup", "fill in SPS test details", "check SPS scenario status", "what's failing in SPS testing", "submit SPS setup", "configure SPS for this customer", "help with SPS testing".

Sync newly-learned trading partner intel into the canonical Jira AOC network profile (the {PARTNER}_NETWORK_PROFILE document in project AOC). Pairs with trading-partner-playbook — after a deep dive surfaces fresh information from Confluence/Intercom/Slack/Orderful/Salesforce, this skill diffs that against what's already in the AOC profile and updates Jira with the additions, preserving the existing structure and using the AOC confidence-level scheme (VERIFIED / HIGH / MEDIUM / INFERRED). Use when a user says 'update the AOC profile for [partner]', 'push our new [partner] findings to Jira', 'sync the [partner] playbook with AOC-XXX', 'we just learned something new about [partner] — update the network', or 'after the playbook run, push deltas to Jira'. Always runs in propose-then-confirm mode: surface the proposed additions for human review before applying. Never overwrites existing AOC content; only adds, with source attribution and refreshed Last-Updated stamp.

Draft a testing kickoff email to a trading partner, engaging them to begin EDI test document exchange. Use this skill whenever a trade request has been accepted and configured and the next step is to notify or re-engage the partner to start testing. Reads the Intercom ticket for prior contact history and partner replies, pulls configuration details from Orderful (transaction types, EDI versions, guideline sets, comm channel), and produces a draft tailored to whether this is a first-touch or a thread continuation. Always requires human approval before sending. Also trigger for: "kick off testing with [partner]", "notify partner we're ready to test", "draft testing email for [ticket]", "re-engage [partner] for testing", "send testing kickoff for [customer] <> [partner]", "start testing on [partnership]".

Produce a deep-dive playbook on a specific trading partner (KeHE, Target, Kroger, etc.) by mining Confluence, Intercom, Jira, Slack, and the Orderful platform for everything Orderful institutionally knows about that partner — comm channel, ISA IDs, document types, onboarding flow, testing process, gotchas, reference customers. Use when a user asks to deep-dive a trading partner, build a TP profile, research a partner before onboarding a customer, or stop asking customers questions whose answers we already have. Triggers: 'deep dive on [partner]', 'build a playbook for [partner]', 'what do we know about [partner]', 'research [partner] before we ask the customer', 'TP playbook for [partner]', 'partner intelligence on [partner]'. Output: a structured Markdown playbook any AM, CEA, or onboarding engineer can read in 5 minutes to skip rediscovery.

Draft a weekly exec-sponsor progress email for an Orderful onboarding customer. Pulls the last 7 days from the customer's #mts Slack channel, recent Gmail threads, open Intercom outreach tickets, and live Orderful org and partnership state, then synthesizes everything into a one-screen email addressed to the customer's exec sponsor and saves it as a Gmail draft. Use this skill whenever the user asks for a weekly update, exec update, weekly progress email, status email, weekly recap, Friday update, or progress note for an Orderful onboarding customer — even when they don't say "exec sponsor" explicitly. Also trigger on "draft an update for [customer]", "send [customer] a progress email", "weekly [customer] update", "status email for [customer]", "weekly check-in for [customer]", or any request to produce a short customer-facing weekly progress note. If the customer name isn't in the conversation, ask for it before doing anything else.