Comments
Hacker News
very cool!
by abhishake85
looks great!
by aagarwal1012
Very nice! :-)
by vpk96
The questions shown in the Elicitation phase are useful in identifying edge cases and overall a pretty useful tool. It would be great to see an option to directly export the finalized specification to standard formats like Markdown or Jira tickets directly from the final 'Project complete' screen.
Looks good! The concept, approach, [formal + informal] specs - all great.
I would add a few points to consider:
1. I think it would be better as a VS Code / Cursor extension, or some other local tool. That's because I would want it to know my domain: see existing markdown files, specs, review existing code, available tools, concepts, terminology, and more. While prompting that fizzbee.ai tool, I want my domain to be discoverable, searchable, and link the important items manually. Like the usual work with AI agents.
2. I think it should come with skills or mcp servers, to instruct AI agents to execute the spec. Having a markdown file is nice, but I think the formal part should be in fizzbee files, referenced by the informal spec, so the AI agents will be able to iterate on it, execute, compare, drive, and if needed, even update it (after discovering inconsistencies in the code).
So, it looks like a very promising MVP and the right direction, but there so much more (existing) stuff to add!
by samyonr
Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- very cool!by abhishake85
- looks great!by aagarwal1012
- Very nice! :-)by vpk96
- The questions shown in the Elicitation phase are useful in identifying edge cases and overall a pretty useful tool. It would be great to see an option to directly export the finalized specification to standard formats like Markdown or Jira tickets directly from the final 'Project complete' screen.
- Looks good! The concept, approach, [formal + informal] specs - all great.
I would add a few points to consider:
1. I think it would be better as a VS Code / Cursor extension, or some other local tool. That's because I would want it to know my domain: see existing markdown files, specs, review existing code, available tools, concepts, terminology, and more. While prompting that fizzbee.ai tool, I want my domain to be discoverable, searchable, and link the important items manually. Like the usual work with AI agents.
2. I think it should come with skills or mcp servers, to instruct AI agents to execute the spec. Having a markdown file is nice, but I think the formal part should be in fizzbee files, referenced by the informal spec, so the AI agents will be able to iterate on it, execute, compare, drive, and if needed, even update it (after discovering inconsistencies in the code).
So, it looks like a very promising MVP and the right direction, but there so much more (existing) stuff to add!
by samyonr