SpecForge – A Platform for Authoring Formal Specifications
agnishom
75 points
10 comments
July 29, 2026
Related Discussions
Found 5 related stories in 336.6ms across 15,380 title embeddings via pgvector HNSW
- Mistral AI Releases Forge pember · 252 pts · March 17, 2026 · 53% similar
- Show HN: InsForge – Open-source Heroku for coding agents mrcoldbrew · 42 pts · May 18, 2026 · 51% similar
- Leaving GitHub for Forgejo jorijn · 559 pts · May 13, 2026 · 50% similar
- We need a federation of forges icy · 548 pts · April 29, 2026 · 50% similar
- Spectre Programming Language asdkop · 29 pts · May 15, 2026 · 49% similar
Discussion Highlights (8 comments)
IshKebab
Strong SVA vibes. Also it seems to be only free for non-commercial use. Interesting anyway!
abbasov_murad
This method is certainly good to learn, but I had some difficulties understanding it
itomato
Whose formalities? The horse still comes first.
poslathian
Nice, very LTL
giancarlostoro
The word "AI-Powered" is shown on the front-page of this project as such: An AI-powered platform for developers to "forge" rigorous and precise system specifications through an iterative process of formalization and analysis. https://imiron.io/specforge/ This title should maybe include that so people are aware that if you adopt this tool, there is some expectation that AI is involved, unless it's an AI optional product, then they need to clarify.
esafak
From what I gather this marries a self-correcting formal specification based on Signal Temporal Logic (cf. https://en.wikipedia.org/wiki/Temporal_logic ) with a natural language requirement definition (like OpenSpec). STL is a spec for continuous, real-time signals over dense time that is appropriate for physical devices and real-time streams. See the "Use Cases for Integration" section in their landing page: https://imiron.io/specforge/ If I were them I would lead with how they differ from existing spec languages.
effnorwood
SCRUM is that my PRD you?
OutOfHere
I have been thinking about how to write specifications for an AI agent to write code for a new project with detailed requirements. I was simply going write it as a list of requirements, starting at REQ001, one beneath the other, with subsequent requirements also building upon prior ones. The developed code would be intended to mark as a comment where in the code each individual requirement is implemented. There might also exist one primary unit test for each requirement. If tests are to not be implemented, then a human is more closely responsible for reviewing changes to the implementation. Over time, I would update/insert/delete individual requirements, and gaps may come to exist in their numbering, but this is okay. The numbers are sorted identifiers only, so a new requirement can even be added as say REQ033B. Overall, this is not a formal system, and it's loose enough that any human and any AI can work with it. For a formal system, an AI may even translate my prose into a formal definition language that it is familiar with, of which there are many. In conclusion, I don't think it's the job of a human to write specifications in a formal spec language.