{"id":82349,"plugin_id":"plugin_asdk_app_6ada95c2df48819199322a8e97725d2f","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-05T06:11:36.364Z","digest":"cd073fa82c35638c3c1d797a45a9c1e4a81a16abb9c96757e974264fa7fba58c","against":null,"payload":{"description":"Plan upcoming card payments, cash needs, a purchase or a savings goal using Fina's saved financial context. Use when the user asks what is due, whether a purchase fits, or how to plan toward a goal. This plans and records preferences; it never pays bills or moves money.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":506},{"relative_path":"references/fina-core.md","size_in_bytes":7447},{"relative_path":"references/financial-facts.md","size_in_bytes":5203},{"relative_path":"references/host.md","size_in_bytes":4255},{"relative_path":"references/refresh-and-scheduling.md","size_in_bytes":6117}],"name":"plan-payments-and-goals","skill_md_contents":"---\nname: plan-payments-and-goals\ndescription: Plan upcoming card payments, cash needs, a purchase or a savings goal using Fina's saved financial context. Use when the user asks what is due, whether a purchase fits, or how to plan toward a goal. This plans and records preferences; it never pays bills or moves money.\n---\n\n# Plan payments and goals\n\nRead [Fina's shared workflow](references/fina-core.md) and [financial facts](references/financial-facts.md). Check setup and guide missing prerequisites before the dependent plan; use partial evidence only when the user deliberately proceeds with its limitations.\n\n1. For an overall decision first read `get_financial_context(detail=summary)` for the relevant horizon, even if the proposed purchase price is missing. Reuse saved goals and constraints. A simple card-due question can use `get_upcoming_card_payments` directly after setup.\n2. For this calendar month use `period=current_month` on `get_projection` / `get_upcoming_card_payments`. For a specific horizon use paired `from`/exclusive `to` within their 91-day maximum; do not combine selectors. `get_financial_context` uses paired dates, not the `period` argument.\n3. Separate current recorded cash, expected receipts, dated cash obligations, total card debt, loan obligations and assets. Use the backend's `financial_decision` and coverage fields. Recorded cash already includes earlier purchases and payments: never subtract them again.\n4. Show upcoming obligations with their actual dates and the correct amount meaning. Unknown card schedule amounts stay unknown, even when an estimated component exists. A transfer association or a passed due date does not prove a statement was paid.\n5. For a purchase, obtain missing price, currency, payment method and timing together. If `spending_approval_supported=false` or `safe_to_spend=null`, do not turn a known subtotal into permission to spend. Explain the material gap and still compare supported options or next steps. Never invent current product prices.\n6. For a goal, reuse its saved amount, currency, target date and reserve preference. Ask only missing decision inputs. Explain where the proposed plan depends on future income or incomplete obligations. Do not sell guaranteed returns or infer risk tolerance from the user's wealth.\n\nWhen asked to save a goal or preference, read current context/version and use `update_financial_preferences` with only the user-declared changed fields. A hypothetical discussion alone does not authorize saving. Re-read to confirm the saved result. Use wealth-and-debt for supported debt/fixed-income scenarios; do not implement a second amortization engine.\n\nDeliver a dated, understandable plan with concrete options and assumptions. A suggested repayment is a plan; it never authorizes executing it or recording a payment that has not happened.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}