easyspecs.ai

Congratulations @xesca_i_am @carlos_guirao & team @easyspecs.ai 🚀. Question, Having written the specifications, what would be the way to keep them consistent with the changing source code? Manually running them, or keeping them constantly up-to-date?

Does it review the spec against the existing codebase, or the document on its own?

Can EasySpecs automatically detect gaps between specs and the existing codebase??

How does EasySpecs handle specs for complex legacy systems?

This is a really useful product for AI teams How do you see EasySpecs fitting into the dev workflow long term?

How do you keep the specs tied to the code over time, do they update automatically when the code changes?

FINALLY!!!! 🍾🎉🎊

Didn't know that these sort of tools existed. Excited to see this in action going forward

Can the approved specs be directly used by coding agents through MCP?

Hey Product Hunt 👋I'm Xesca, CTO turned founder. Before EasySpecs, I spent 15+ years being the person accountable for code I didn't personally write, across fintech, insurtech, and media.That's the job now for every engineering leader: your agents ship code faster than anyone can read it, and you're still the one who answers for what breaks.The problemI kept hitting the same wall everywhere I looked:Teams adopt AI coding agents, and PRs pile up faster than anyone can review themSpecs get written against a mental model of the codebase, not the actual codebaseAgents generate code against those specsThings break silently, and nobody can trace why, because nobody documented what was actually there to begin withCode review is dead. Spec review is where quality lives now. But spec review only works if the spec is grounded in reality, not guesswork.What EasySpecs doesTwo things, one workflow:1. We document your codebase automaticallyEven the undocumented, nobody-wants-to-touch-it kind. Our first real test was a pharmaceutical company's legacy Delphi system. If it works there, it works on whatever you're building.2. We turn that understanding into specs your team and your agents can actually trustEvery spec comes paired with validators, so you know it matches the app before anyone codes against it.Here's the part I'm most proud of: as you write a spec, the specs crafter suggests oracles and rubrics for it, concrete, checkable ways to verify the change actually did what the spec said.Oracles — the "does this pass or fail" checks a machine can runRubrics — the judgment calls that need a human or an AI reviewer to score against clear criteriaYou're not staring at a blank page trying to guess how to verify your own spec. The tool proposes it alongside the spec itself.Built for more than developersYou don't need to be a developer to use it. Right now the only way to sanity-check a spec against reality is to go read the source yourself.We built EasySpecs so product managers and team leads get that confidence without opening a single file.Try itFree to start — connect a repo, bring your own AI key, see what it findsWorkbench — €5/repo/month while launch pricing lasts (normally €10)Factory — €150/month if you want us to run the AI side too, with credits to use on any repoI'd genuinely love your feedback, especially if you throw a messy, undocumented codebase at it. That's the case we built for.