.md File is not a specification: Using formal analysis to find requirements gaps
jayaprabhakar
21 points
12 comments
October 08, 2026
Related Discussions
Found 5 related stories in 89.8ms across 8,906 title embeddings via pgvector HNSW
- Why don't people use formal methods? (2019) Thom2503 · 118 pts · July 30, 2026 · 48% similar
- SpecForge – A Platform for Authoring Formal Specifications agnishom · 75 pts · July 29, 2026 · 45% similar
- Why Software Factories Fail (or: harness engineering is not enough) dhorthy · 247 pts · July 23, 2026 · 42% similar
- OpenSpec – A lightweight and configurable AI spec framework etoxin · 115 pts · September 16, 2026 · 41% similar
- MPEG-CENC: Defective by Specification (2024) htgb · 12 pts · September 19, 2026 · 41% similar
Discussion Highlights (4 comments)
jackdaniels4me
Today, most coding agents support spec-driven development (or plan mode). They typically capture the requirements, design, and implementation plan in Markdown files. But is that Markdown file actually a specification? This article explores how formal analysis can uncover requirements gaps that are easy to miss.
ActionHank
Ok, so the proposed answer here is to define the spec in what is essentially code for another LLM to then interpret into different code? I'm not sure if this does much more than a grillme skill and then poking an agent to do the work.
meoleo
How is this different from what Kiro does? https://kiro.dev/blog/deep-spec-analysis/
pbronez
The related https://fizzbee.ai/ tool is pretty neat. It's similar to /grillme but with additional formalism. Not sure if the resulting specs are definitively better, if only because the FizzBee code is harder for me to decipher.