gaspatchio-model-discovery

Run the discovery workflow, which asks one question at a time about your source specification, model points, assumption tables, projection settings, and outputs. It ends with a written model specification you approve before any model code is written.

Extract the workbook into a SQLite formula graph with XL Marinade, then scan for row offsets and strongly-connected components to split variables into recurrences and closed-form columns. The bundled spreadsheet-conversion reference covers lapse gates, COI timing conventions, rounding placement, and VLOOKUP overflow traps.

No. The Skill enforces a hard gate: no model code is written until a specification exists and the user confirms the summary. Even experienced actuaries must pin down data shape, assumptions, projection parameters, and outputs first.

It requires at least one concrete source: a documentation URL, a spec file in the repo, or a named Excel or lifelib model. If none exists, you must confirm that explicitly and create a minimal written spec together before proceeding.

The approved specification is handed to the gaspatchio-model-building skill for implementation. If a reference model such as Excel or lifelib exists, the workflow hands off to gaspatchio-model-reconciliation for a strict tie-out process.

Common causes include lapse gates hidden inside schedule lookups, COI timing conventions that agree only when rates are constant, rounding placed outside a recursion, and approximate-match VLOOKUP running past a table's end. The reference document catalogs each failure mode and its detection query.