|
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! |