libohad-dev/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Write a workflow for formal spec-driven development based on TLA+

Browse source
This commit is contained in:
Ohad Livne 2026-02-10 14:27:41 +02:00
parent a008426031
commit e8250ba10c
Signed by: libohad-dev
GPG key ID: 34FDC68B51191A4D
9 changed files with 944 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

49
.claude/commands/formspec.verify.3.md Normal file
View file

@ -0,0 +1,49 @@
---
description: Run the TLC model checker on the formal specification
allowed-tools: [Read, Glob, Grep, Bash]
---
# FormSpec Verify
You are running the TLC model checker on the existing TLA+ specification and reporting results. This command is **read-only** — it does not modify any spec files.
## Steps
### 1. Validate preconditions
Check that both files exist:
- `spec/formal/System.tla`
- `spec/formal/System.cfg`
If either is missing, tell the user to run `/formspec.formalize.2` first and stop.
### 2. Run TLC
```bash
tlc spec/formal/System.tla -config spec/formal/System.cfg -workers auto -metadir /tmp/tlc-states -cleanup
```
Run from the project root directory. The `-metadir` flag directs TLC's working state files to a temporary directory, and `-cleanup` removes them after a successful run. Use a 5-minute timeout by default. If TLC does not complete within this limit, stop it and report the partial state (states explored so far, queue size). If the developer expects and accepts a longer runtime, the timeout may be extended — but beyond 15 minutes, always alert the developer and wait for confirmation before continuing.
### 3. Parse and report
Read the TLC output and produce a structured report:
**Summary**:
- States explored / distinct states
- Duration
- Overall result: PASS or FAIL
**Property results** (table format):
| Property | Type | Result |
|----------|------|--------|
| Name | invariant/temporal | PASS/FAIL |
**For any violation**, include:
- The counterexample trace, simplified into domain language
- If `spec/formal/traceability.md` exists, map the violated property back to its design requirement and include that reference
### 4. No modifications
Do not modify `System.tla`, `System.cfg`, `traceability.md`, or any other file. This command is purely diagnostic. If violations are found, advise the user to run `/formspec.formalize.2` to address them.