Formal Specification Driven Development

Formal verification with Idris2 uses dependent types and proofs to create precise specifications, compile them for correctness, then translate the verified design into Python, Rust, or TypeScript. Describe your problem, choose a target language, and the Skill generates specs in .specs/, verifies totality, and produces implementation templates with tests.

Yes. After writing and verifying your Idris2 spec, this Skill automatically translates the verified design to your chosen target language—Python, Rust, or TypeScript—with generated implementation templates, tests, and documentation linked back to the formal spec.

Specification-first development with dependent types catches errors at the specification stage. Write formal Idris2 specs with proofs, compile to verify totality and correctness, then implement in your target language knowing the design is formally verified.

The Skill guides Idris2 specification creation for you, but understanding dependent types and proof concepts helps. It handles automatic compilation, verification, and cross-language translation, making formal methods accessible without deep Idris2 expertise.

The Skill maintains traceability by linking each implementation artifact—functions, tests, documentation—directly to its Idris2 spec. This creates an auditable chain from formal specification through verified compilation to target-language code.

Automatic compilation catches totality violations and type errors in your spec. The Skill reports verification failures, helping you refine the specification until it compiles successfully, ensuring only correct designs reach implementation.