What problem does it solve? Informal specifications and verbal descriptions of a domain cannot be verified, composed, or checked for consistency. This Skill provides a structured protocol for turning a domain or existing specification document into a rigorous formal model (olog, coalgebra, session type, linear relation, etc.) that downstream verification and testing can build on. ## Core Features & Use Cases - Dual-Mode Operation: Create mode produces a new model document from a template; Apply mode scrutinizes an existing protocol spec, whitepaper, or design doc through a formal lens. - Six-Phase Workflow: Identify, Select, Construct, Validate, Record, Connect — with mandatory human approval gates after formalism selection and before recording. - Formalism Selection Discipline: Uses a decision matrix and the principle of minimal representation to pick the simplest adequate formalism, with independence checks against user-suggested framings. - Use Case: Given a payment protocol specification, run the workflow to extract its implicit state machine as a session type model, validate internal consistency, and commit the model to docs/models/ for the test suite to verify against. ## Quick Start Invoke the form workflow to build a formal model of the payment protocol described in docs/specs/payment.md and save it under docs/models/.