onboarding-checklist
Generates customized client onboarding checklists with phased tasks, ownership assignments, dependencies, acceptance criteria, and email templates. Adapts to consulting, SaaS, or agency engagement models.
Works with
--- name: onboarding-checklist description: Generates customized client onboarding checklists with phased tasks, ownership assignments, dependencies, acceptance criteria, and email templates. Adapts to consulting, SaaS, or agency engagement models. license: MIT --- # Onboarding Checklist Generator Generate a comprehensive, customized client onboarding checklist saved as `onboarding-checklist.md` in the current working directory. The checklist is actionable, phase-structured, and tailored to the specific engagement type. ## Contents - `references/output-template.md` -- Full output structure: header block, four phases, handoff criteria, formatting rules. - `references/engagement-types.md` -- How to classify Consulting vs SaaS vs Agency, and per-type adaptation guidelines. - `references/task-banks.md` -- Reference task pools per engagement type and phase. - `references/email-templates.md` -- The five required email templates, their structure, and content guidelines. - `references/scaling-and-pitfalls.md` -- Timeline and team-size scaling rules, common pitfalls, and the final quality checklist. ## Required Inputs Gather these before generating. If any are missing, ask for them explicitly: 1. **Client Type**: Industry, company size, maturity (e.g., "Series B fintech startup"). 2. **Services Purchased**: Exact scope of work or product tiers. 3. **Team Size**: Number of people on both provider and client sides. 4. **Tech Stack**: Relevant technologies, platforms, tools, integrations. 5. **Timeline**: Total onboarding duration and any hard deadlines. ## Workflow 1. Collect all five required inputs from the user. 2. Classify the engagement type (Consulting, SaaS, or Agency) using `references/engagement-types.md`. This classification drives the structure and tone of the entire checklist. 3. Select and customize tasks from `references/task-banks.md`, adapting language, deadlines, and owners to the specific engagement. Reflect tech-stack items in relevant tasks. 4. Apply timeline scaling rules from `references/scaling-and-pitfalls.md` based on the specified duration. 5. Apply team-size scaling rules from `references/scaling-and-pitfalls.md` based on team composition. 6. Generate all five email templates with full body content per `references/email-templates.md`. 7. Compile the complete `onboarding-checklist.md` following `references/output-template.md`. Apply the per-type adaptations in `references/engagement-types.md`. 8. Verify the result against the quality checklist and common pitfalls in `references/scaling-and-pitfalls.md`. 9. Write the file to the current working directory using the Write tool. 10. Confirm completion and summarize key stats (total tasks, timeline, engagement type, file location).
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

