Make your customer onboarding plan.

Help me create my customer onboarding plan as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (complete fictional sample): https://shareartifacts.dev/examples/customer-onboarding-plan Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - The customer outcome actually agreed in the sales handoff or kickoff, with proposed goals clearly separated. - The first use case, its scope and exclusions, and the evidence the customer will review to recognize success. - Confirmed customer and vendor owners, their required inputs, dependencies, and approved help channel. - Supplied timing and its conditions; unresolved dates must stay unresolved. - Audience-safe resource links, the authoritative task record, and the plan owner and review date. Creation task: Using only materials I provide or have authorized you to access, create a customer onboarding plan for [customer] and [service]. Ask only for missing essentials: the agreed first useful outcome, scope and exclusions, customer and vendor owners, prerequisites, evidence of success, timing conditions, and the approved help and tracking channels. Separate agreed goals from proposed goals. Lead with the customer's next action and show what vendor work it unlocks. For each milestone state the prerequisite, output, confirmed owner, and reviewer. Preserve unresolved inputs and dependency-based timing; do not invent calendar dates, commitments, permissions, provisioning steps, completed tasks, or evidence that first value has been achieved. A sample demonstration is not proof of customer success. Keep credentials and private source material out of the page and include only audience-safe details and approved links. Create readable static HTML with no scripts or forms. Use my saved artifact style if available. Include the supplied snapshot date and plan owner, and keep authoritative progress and approvals in our existing project workflow. Show me the draft and unresolved questions for review. Do not publish or change access without separate explicit approval. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Is the customer's agreed first useful result clear, with evidence rather than a generic completion percentage? - Can each side identify its next action, owner, and dependency? - Are dates and commitments agreed, proposed, or unresolved exactly as the sources state? - Is a sample demonstration clearly different from the customer's actual result? - Are sensitive inputs, credentials, and internal-only notes excluded? - Does the page name its snapshot owner and explain where updates and questions belong? Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.