Onboarding Checklist Skill

Generates a tailored customer onboarding checklist as a saved deliverable file, plus a short summary of what it covers.

When to use

• A new customer or account has just closed and needs a structured onboarding plan.
• Customer success wants a repeatable, tailored checklist instead of a generic template.
• A prior onboarding checklist needs to be revised or extended for a specific customer's needs.

Tools

• read-file — load any prior onboarding checklist, intake notes, or requirements doc to base the new checklist on.
• write-file — save the finished onboarding checklist as a deliverable file.
• complete-task — finish the task with a structured summary of the checklist that was produced.

Playbook

1. Read the task brief carefully to identify the customer name, product/plan, key stakeholders, and any deadlines or special requirements.
2. If a prior checklist, intake form, or requirements doc is referenced, load it with read-file to understand what has already been captured.
3. Draft the checklist structure: group items into logical phases (e.g., kickoff, setup/configuration, training, go-live, 30-day check-in), tailored to the customer's product and stated goals.
4. For each phase, list concrete, actionable steps with clear owners (customer vs. internal team) where the source material specifies them.
5. Note any open questions or missing information as a separate "needs confirmation" section rather than guessing at details you were not given.
6. Assemble the full checklist into a single well-formatted markdown document with a short introduction stating the customer and purpose.
7. Save the finished checklist with write-file, using a clear filename that identifies the customer and document type.
8. Write a concise summary covering the number of phases, total checklist items, and any flagged open questions.
9. Finish with complete-task, attaching the summary and a reference to the saved file so the requester can review it.

Failure modes

• Missing or unclear customer/product details: do not fabricate specifics — flag them in the "needs confirmation" section and proceed with the best available structure.
• No prior checklist or intake doc found when one was expected: note this in the summary and build from a standard onboarding structure instead.
• Task requires updating a checklist inside another system (e.g., a CRM record) rather than a file: this is not possible with the declared tools — compile the needed changes and hand off to a human via a message instead of implying it was done automatically.
• Ambiguous scope (e.g., unclear which product tier or timeline applies): state the assumption made explicitly in the summary so a human can correct it if wrong.

Done when

• A complete onboarding checklist file has been saved via write-file, organized into clear phases with actionable items.
• The task has been finished via complete-task with a summary describing the checklist's structure and any open questions.
• Any information gaps are explicitly flagged rather than silently assumed.