Comment by realityfactchex
Comment by realityfactchex 5 days ago
1. Write a fully-defined specification file as markdown in technical-enough but business-enough language, without repeating anything, and including all requirements and context, being sure to emphasize what is important, how to make decisions if needed, and, most critically, what elements must exist and how they must behave in the outcome. This is logically outlined. A junior engineer could understand what the output needs to do without help, a mid engineer could implement it sufficiently well without help, and a senior engineer could implement it gracefully without help.
2. Submit the fully-defined requirements .md file to the LLM by drag-and-drop. If there are starting files to be modified, drag and drop those files as well (as a zip if hierarchical, or as unpackaged files if a flat structure is suitable).
3. Wait for LLM to be done. This can take as long as it needs to, since this process supports specification files with requirements of arbitrary complexity. Receive the correct, full output fileset as a downloadable file from the LLM. (If I asked for instructions on how to use the files that the LLM provides, that is included in the output fileset, too.)
Oh wait, this does not exist. Sorry! But it is what I want, so it is still my "ultimate AI-assisted coding setup".
I'm confused. It does exist. The "markdown reqs" has been a thing at work. Shared markdown is in the code and we review it.
Combine it with Cursor and you don't have to drag and drop or download anything.
I just set up an architecture.md for it to navigate. With Cursor and something like Gemini Pro, you can even make the AI do the work and edit the docs once done. I even have a roadmap.md so I can remember where I left off, which helps a lot when you return to the project in a month.