client-onboardinglisted

# Client Onboarding ## Purpose The first week of a client relationship sets the pattern for the whole engagement. This skill generates the three documents that prevent the most common early failures: unclear expectations, no communication cadence, and a first week that drifts without visible progress. ## Inputs to ask the user for - Client name and the project/engagement name - Scope summary (can reuse a proposal if one exists) - Engagement length: one-off project, or ongoing retainer - Communication channel(s): email, Slack, a project tool (Asana/Notion/etc.) - How often the user plans to send updates (weekly is the default if unsure) - Who the client's point of contact is (name, role) and who else, if anyone, needs to be looped in - Key dates already agreed: kickoff date, first milestone/delivery date - What the user needs from the client to start (access, content, brand assets, approvals) and by when - Any tools/access the user needs granted (repo access, CMS login, etc.) ## Step-by-step instructions 1. Produce three separate outputs, clearly labeled: (a) kickoff email, (b) a short expectations document, (c) a first-week plan. 2. **Kickoff email**: warm but brief. Confirms the engagement has started, states the communication cadence and channel, lists what's needed from the client and by when, and states the first milestone date. This is the client's first impression of how organized the engagement will be — keep it tight, no filler. 3. **Expectati