form

Constructs formal mathematical domain models through a six-phase validation workflow.

10|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/nrdxp/predicate --skill form-nrdxp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: form
Source: https://github.com/nrdxp/predicate/tree/main/skills/form
Command: npx skills add https://github.com/nrdxp/predicate --skill form-nrdxp

SYSTEM DOCUMENTATION & REQUIREMENTS

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/.

Frequently Asked Questions about form

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a formal model of a software domain?▼

Run the six-phase workflow: identify the domain's structural characteristics, select a formalism using the decision matrix, construct the model, validate consistency and adequacy, then record it from the MODEL.md template into docs/models/. Human approval is required after formalism selection.

What formalisms does the form workflow support?▼

It supports ologs, coalgebras, session types, linear relations, and hyperdoctrines drawn from the SDMA toolkit, plus external formalisms when the domain requires them. Selection follows the principle of minimal representation — the simplest formalism that faithfully captures the domain.

Can I apply formal modeling to an existing specification document?▼

Yes, Apply mode scrutinizes an existing protocol spec, whitepaper, or design doc to extract implicit structure and identify vagueness or inconsistency. Output is either a companion model document in docs/models/ or annotations integrated into the target document.

When should I not use formal domain modeling?▼

Avoid it for strategic planning, open-ended exploration, or implementation work — those belong to the ambient planning invariants, the sketch principle, and the core workflow respectively. FORM is structural analysis only; writing code means you have left its scope.

Why does the workflow halt after formalism selection?▼

The halt after SELECT exists because a wrong formalism choice cascades into wasted construction and validation work. The human must approve the selected formalism and its documented rationale before the model is built.