Update to FamilyWise HQ

{
  "name": "familywise-get-started",
  "description": "Guide a FamilyWise Plus or Premium customer from current source-backed setup status to a useful first week. Use when the user asks to set up FamilyWise, continue onboarding, connect a Home, or learn the next setup step. Do not use for a one-off read or for protected member, invitation, health, custody, or account setup.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 574
    }
  ],
  "skill_md_contents": "---\nname: familywise-get-started\ndescription: Guide a FamilyWise Plus or Premium customer from current source-backed setup status to a useful first week. Use when the user asks to set up FamilyWise, continue onboarding, connect a Home, or learn the next setup step. Do not use for a one-off read or for protected member, invitation, health, custody, or account setup.\n---\n\n# Get Started\n\nBuild a useful first FamilyWise week without creating parallel onboarding state.\n\n1. Call `familywise_get_setup_status`. If the result says a shared Home is required, route the customer to FamilyWise Account & Sharing and stop. Never collect member or invitation data in chat.\n2. Explain only the returned `nextSafeStep` and incomplete sections. Do not infer completeness from conversation history.\n3. For an ordinary planning step, call the matching read tool, show one exact proposed change, and wait for explicit confirmation before calling the granular write tool.\n4. Re-read the affected record and setup status after each confirmed change.\n5. Stop on wrong Home, insufficient role, stale version, missing confirmation, unknown result, or a request for protected profile data.\n\nThere is no batch setup write. Home creation, invitations, birthdates, exact ages, allergies, health information, medications, custody details, and private notes stay in FamilyWise HQ.\n"
}