Requirements Engineering with Formal Verification
Details
- External ID
- 48835012
- Source
- HN
- Company
- —
- Product
- Requirements Engineering with Formal Verification
- Website domain
- fizzbee.ai
- Launched
- July 8, 2026
- Cohort
- —
- Upvotes
- 27
- Upvotes percentile
- 0.7700119474313023
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I've been building an open source formal methods system (fizzbee.io) for the past few years.Today I'm launching a new app built on the same technology. It performs requirements engineering using formal verification to uncover gaps and produce precise instructions for your coding agents to follow.When given a prompt, it - asks high signal follow-up questions - converts to formal spec and identifies complex requirements gaps - generates validation scenarioAt the end, it produces a specification document that can be shared with coding agents. In my trials on various projects, it produces working code in fewer iterations.Please give it a try and share your feedback. https://fizzbee.ai/You can also look at a sample project. https://fizzbee.ai/projects/94bf2869-97a1-445c-8f5d-4445848b...
Enrichment
- Theme
- AI agent frameworks and developer tools
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- formal verification for requirements
- Manually corrected
- False
Could you build this?
No Building formal verification engines and mathematical state-space explorers requires specialized academic expertise in formal methods, logic solvers, and specification languages (like TLA+).
What it would actually take: This system relies on formal methods technology (such as the author's FizzBee model checker), which involves building state-space exploration algorithms, AST parsers for formal specs, model checkers, and invariance validators. Integrating an LLM involves mapping ambiguous natural language user requirements into mathematically provable state machines and constraint languages, requiring advanced research in formal verification, compiler design, and automata theory.
Discussion
5 comments analyzed.
Competitors mentioned: VS Code extensions, Cursor extension, MCP servers
Concerns raised: Web-based tool limits access to user's domain context and existing files, Formal spec format not suitable for AI agent iteration and execution
Feature requests: Export finalized specification to Markdown or Jira tickets, Local tool integration to access existing markdown files and code, Skills or MCP servers for AI agents to execute specs
Competitors
Other products that read as similar to this one — 64 launches clear the similarity bar, closest 8 shown.
Attention rank: #11 of 65 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 241 days after the earliest competitor.
- OQP · hn · 2026-04-13 · 8 upvotes · similarity 0.46
- Formally Verified Leaderless Log Protocol for Kafka · hn · 2026-04-10 · 5 upvotes · similarity 0.44
- Spec-Driven Development Workflow for Claude Code · hn · 2026-05-22 · 20 upvotes · similarity 0.38
- Kaktoos · ph · 2026-09-17 · 1 upvotes · similarity 0.37
- Kanten · ph · 2026-09-22 · 2 upvotes · similarity 0.37
- Forall · hn · 2026-07-17 · 7 upvotes · similarity 0.37
- Topos · hn · 2026-06-25 · 5 upvotes · similarity 0.36
- SpecMind · hn · 2025-11-11 · 8 upvotes · similarity 0.36
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.