Update to NestPilot

{
  "description": "Coordinate an anonymous educational retirement checkup when a user asks whether they can retire or wants retirement age, Social Security, Roth conversion, healthcare, or Medicare decisions analyzed together, or wants one retirement-age or claiming question modeled on their plan. Do not use for a single definition, product selection, transactions, account access, or plan saving.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 633
    },
    {
      "relative_path": "references/adaptive-routing.md",
      "size_in_bytes": 3074
    },
    {
      "relative_path": "references/decision-snapshot.md",
      "size_in_bytes": 1123
    },
    {
      "relative_path": "references/intake-and-defaults.md",
      "size_in_bytes": 5298
    }
  ],
  "name": "nestpilot-retirement-checkup",
  "skill_md_contents": "---\r\nname: nestpilot-retirement-checkup\r\ndescription: Coordinate an anonymous educational retirement checkup when a user asks whether they can retire or wants retirement age, Social Security, Roth conversion, healthcare, or Medicare decisions analyzed together, or wants one retirement-age or claiming question modeled on their plan. Do not use for a single definition, product selection, transactions, account access, or plan saving.\r\n---\r\n\r\n# NestPilot Retirement Checkup\r\n\r\nOpen the appropriate interactive NestPilot experience. Model-visible tools only\r\nlaunch a review UI. Financial calculations run only after the user explicitly\r\nclicks the corresponding button in that UI.\r\n\r\n## Routing Precedence\r\n\r\nClassify the whole request before selecting a tool.\r\n\r\n- A complete checkup, or any request connecting two or more retirement\r\n  decisions, uses `start_retirement_checkup` without `focus`.\r\n- One retirement-age or Social Security claiming question uses\r\n  `start_retirement_checkup` with `focus` when the user has given the plan\r\n  facts, or asks for their plan, portfolio, spending, taxes, or a couple's\r\n  joint claiming to be modeled; ask for any missing plan facts first.\r\n- The same question with only a few facts and no request for plan modeling\r\n  uses the matching explorer, `open_retirement_age_explorer` or\r\n  `open_social_security_explorer`; after an explorer result, offer the focused\r\n  analysis once, naming the facts it needs, and never open it unasked.\r\n- A Roth conversion candidacy question uses `open_roth_explorer`; plan-backed\r\n  Roth modeling runs as the Roth step of a retirement checkup, which\r\n  `start_retirement_checkup` opens without `focus`.\r\n- `medicare-guardian` answers only a Medicare enrollment question the user asked; never suggest it, launch it from age alone, or offer it as a next step.\r\n- A definition or general educational question may be answered without a tool.\r\n\r\nThe plan facts are current age, planned retirement age, filing status, the\r\nprimary person's income, annual spending, and savings; when married, also the\r\nspouse's age, planned retirement age, and income, with 0 only when the user\r\nsaid so; for a claiming question, also the benefit estimates at full\r\nretirement age. A focused claiming analysis needs the user's own benefit\r\nestimate above 0, or the question uses the explorer instead; a focused\r\nretirement-age analysis needs someone still earning, or explain that no\r\nretirement age is left to compare.\r\n\r\nThis whole-request classification takes priority over topic keywords. Never\r\nopen multiple focused explorers for a complete checkup.\r\n\r\n## Complete Checkup Workflow\r\n\r\n1. Read [intake-and-defaults.md](references/intake-and-defaults.md). Ask for\r\n   all missing core inputs together. Do not guess financial values.\r\n2. Identify the connected decisions requested. Use these exact\r\n   `requestedAnalyses` values:\r\n   - `retirement_age`\r\n   - `social_security`\r\n   - `roth`\r\n   Use [adaptive-routing.md](references/adaptive-routing.md) to include only\r\n   relevant requested analyses.\r\n3. Use Roth policy `conservative` unless the user explicitly chooses\r\n   `optimized`. Explain that optimized includes modeled ACA subsidy effects\r\n   before Medicare and Medicare IRMAA effects where applicable.\r\n4. Call `start_retirement_checkup` once with the collected facts, requested\r\n   analyses, and Roth policy.\r\n5. Tell the user that no calculation ran from the launcher. Ask them to review\r\n   the displayed inputs and defaults and click **Run my checkup**.\r\n6. Do not call any calculator from the conversation. The widget calls the app-only calculators only after explicit clicks. The\r\n   checkup is one card that moves forward: it shows the plan as understood, then\r\n   each calculation runs only on its own click and the card becomes the verdict,\r\n   the next decisions, and one decision's answer; the full-screen view keeps\r\n   every completed result as a tab. It keeps **Continue in the NestPilot\r\n   planner**. When the user's message repeats one of the card's questions, the\r\n   answer is already on screen: summarize that result and do not call a tool\r\n   again.\r\n7. When the widget reports a completed step through model context, summarize\r\n   only values grounded in that completed result. Do not invent missing\r\n   financial numbers. Use [decision-snapshot.md](references/decision-snapshot.md)\r\n   for the compact response.\r\n\r\nIf an input changes before calculation, call `start_retirement_checkup` again\r\nwith the corrected facts. If an input changes after calculations, explain that\r\nthe user should start a fresh checkup so dependent results are not mixed.\r\n\r\n## Focused Analysis Workflow\r\n\r\nFor one retirement-age or Social Security claiming question backed by the\r\nplan facts:\r\n\r\n1. Read [intake-and-defaults.md](references/intake-and-defaults.md). Ask for\r\n   every missing plan fact together, the spouse's facts included when\r\n   married. Do not guess financial values.\r\n2. Call `start_retirement_checkup` once with the collected facts and `focus`\r\n   set to `retirement_age` or `social_security`.\r\n3. Tell the user that no calculation ran from the launcher. Ask them to review\r\n   the displayed inputs and defaults and click **Compare retirement ages** or\r\n   **Compare Social Security ages**.\r\n4. The widget runs that one analysis on the plan, with no baseline forecast,\r\n   and lists every default it applied. It offers no next step. Picking other\r\n   ages in the widget runs only on each pick's own click.\r\n5. For another analysis, start a new checkup rather than extending this one,\r\n   so results computed on different inputs are never mixed.\r\n\r\n## Quick Explorer Workflow\r\n\r\nFor a question a quick explorer answers, as the routing above describes, call\r\nexactly one matching `open_*` launcher with any known inputs. The launcher\r\nnever calculates. Tell the user to review the form and click its calculation\r\nbutton.\r\n\r\nDo not call `social_security_explorer`, `roth_explorer`, or\r\n`retirement_age_explorer` from the conversation. Those are app-only\r\ncalculators retained for widget calls and backward compatibility.\r\n\r\n## Medicare\r\n\r\nOnly when the user asks about Medicare enrollment. Never suggest Medicare, launch\r\nit from the user's age alone, or offer it as a next step after another tool.\r\nCall `medicare-guardian` with any known birth month/year, employment,\r\ncoverage, employer-size, HSA, and creditable-drug-coverage hints. The interface\r\ncollects missing values and calls its app-only calculator after the user\r\nclicks. Use only birth month and year; never request an exact birth day. If the\r\nuser volunteers that they were born on the 1st of the month, pass\r\n`bornOnFirst: true` — Medicare's one day-dependent rule shifts their eligibility\r\nmonth and IEP one month earlier.\r\n\r\nDo not compare, recommend, sell, or enroll the user in Medicare plans.\r\n\r\n## Allowed Model-Visible Tools\r\n\r\nUse only these tools from the conversation:\r\n\r\n- `start_retirement_checkup`\r\n- `open_social_security_explorer`\r\n- `open_roth_explorer`\r\n- `open_retirement_age_explorer`\r\n- `medicare-guardian`\r\n\r\nDo not call or name app-only calculators, render helpers, handoff helpers, or\r\ntools outside this allowlist. In particular, never call\r\n`retirement_forecast`, `retirement_age_analysis`,\r\n`social_security_analysis`, `roth_analysis`, `roth_simulate`,\r\n`roth_optimize`, `render_retirement_checkup`,\r\n`create_plan_handoff`, or `medicare-analyze` from the conversation.\r\n\r\n## Failure Rules\r\n\r\n- Missing or invalid core input: continue intake without calling a launcher.\r\n- Missing plan fact for a focused analysis: ask for it before launching; the\r\n  focused review keeps its button disabled until every plan fact is given.\r\n- Launcher failed: retain the user's facts, explain that the UI did not open,\r\n  and offer to retry the same launcher.\r\n- App calculation failed: keep prior valid tabs and do not invent a result.\r\n- Missing baseline `planInput`: dependent app-only analyses must not run.\r\n- Unsupported request: do not invoke NestPilot tools.\r\n\r\n## Boundaries\r\n\r\n- Treat every result as an educational estimate, not financial, investment,\r\n  tax, legal, medical, or benefits advice.\r\n- Do not recommend products, investments, trades, advisors, or Medicare plans.\r\n- Do not file taxes, apply for benefits, enroll in coverage, move money, send\r\n  messages, or execute transactions.\r\n- Do not request an exact birth date, Social Security number, credentials,\r\n  password, MFA code, or email address.\r\n- Do not authenticate users, access accounts, or save plans. The results UI may\r\n  create a temporary, 24-hour, single-use planner handoff only after the user\r\n  explicitly clicks **Continue in the NestPilot planner**.\r\n- Say \"the modeled result shows\" rather than \"you should.\"\r\n"
}